[Desktop-packages] [Bug 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

2024-03-27 Thread Bug Watch Updater
** Changed in: mesa (Debian)
   Status: Confirmed => Fix Released

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Fix Released

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed

2024-03-26 Thread Bug Watch Updater
** Changed in: network-manager
   Status: New => Fix Released

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

Title:
  network-manager fails to trigger dispatcher scripts with action
  dhcp4-change when dhcp lease is renewed

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  We rely on network-manager dispatcher scripts on our desktop and
  laptop computers. The dispatcher scripts are used to update DNS
  records with nsupdate when the dhcp lease is renewed.

  With jammy this is not working anymore. It seems that dispatcher
  scripts are run only when the interface comes up (with action 'up')
  and with the initial dhcp lease (with action 'dhcp4-change'), but when
  the lease is renewed, the dispatcher scripts are not run with any
  action. The only action the dispatcher scripts are run regularly with
  is 'connectivity-change', which seems to occur twice in a row every
  few hours.

  I have made a simple script to log how the dispatcher scripts are run:
  /etc/NetworkManager/dispatcher.d/99-test:
  #!/bin/bash
  PATH='/bin:/sbin:/usr/bin:/usr/sbin'

  echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log

  This script proves that action 'dhcp4-change' only occurs when I
  manually restart NetworkManager.service or unplug and replug the
  ethernet cable.


  network-manager version: 1.36.6-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1997553/+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 2059033] Re: Xorg crashes with SIGABRT

2024-03-25 Thread Bug Watch Updater
** Changed in: mesa
   Status: Unknown => New

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

Title:
  Xorg crashes with SIGABRT

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I am running an Intel Kabylake CPU with Ubuntu 22.04, and i915
  graphics driver.  I am seeing random Xorg crashes due to SIGABRT,
  which kicks me back to the login screen.

  Ubuntu version: 22.04
  Kernel version: 5.19.0-50-generic
  libgl1-mesa-dri version: 23.0.4-0ubuntu1~22.04.1 

  I am seeing this message in kern.log:

  i915 :00:02.0: [drm] GPU HANG: ecode 9:1:85db, in Xorg [1617]

  I have also gotten a core dump; here is the track trace:

  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140131874372224) at ./nptl/pthread_kill.c:44
  #1  __pthread_kill_internal (signo=6, threadid=140131874372224) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #4  0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79
  #5  0x560c5cc756a0 in OsAbort () at ../../../../os/utils.c:1352
  #6  0x560c5cc7aea9 in AbortServer () at ../../../../os/log.c:879
  #7  0x560c5cc7be9a in FatalError (f=f@entry=0x560c5ccadc10 "Caught signal 
%d (%s). Server aborting\n") at ../../../../os/log.c:1017
  #8  0x560c5cc72abd in OsSigHandler (unused=, 
sip=0x713ae7b0, signo=6) at ../../../../os/osinit.c:156
  #9  OsSigHandler (signo=6, sip=0x713ae7b0, unused=) at 
../../../../os/osinit.c:110
  #10 
  #11 __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=140131874372224) at ./nptl/pthread_kill.c:44
  #12 __pthread_kill_internal (signo=6, threadid=140131874372224) at 
./nptl/pthread_kill.c:78
  #13 __GI___pthread_kill (threadid=140131874372224, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #14 0x7f72fec42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  #15 0x7f72fec287f3 in __GI_abort () at ./stdlib/abort.c:79
  #16 0x7f72fc49d86d in _iris_batch_flush (batch=0x560c5e916118, 
file=, line=) at 
../src/gallium/drivers/iris/iris_batch.c:1116
  #17 0x7f72fd1da6ff in iris_fence_flush (ctx=0x560c5e915be0, 
out_fence=0x0, flags=) at 
../src/gallium/drivers/iris/iris_fence.c:267
  #18 0x7f72fc55f127 in st_flush (flags=0, fence=0x0, st=0x560c5e93bbc0) at 
../src/mesa/state_tracker/st_cb_flush.c:60
  #19 st_glFlush (ctx=, gallium_flush_flags=0) at 
../src/mesa/state_tracker/st_cb_flush.c:94
  #20 0x7f72fe56b604 in _glamor_block_handler (screen=0x560c5e8655a0, 
timeout=0x713af054) at ../../../../glamor/glamor.c:285
  #21 0x7f72fe5a6157 in msBlockHandler (pScreen=0x560c5e8655a0, 
timeout=0x713af054) at 
../../../../../../../hw/xfree86/drivers/modesetting/driver.c:701
  #22 0x560c5cb01095 in BlockHandler 
(pTimeout=pTimeout@entry=0x713af054) at ../../../../dix/dixutils.c:394
  #23 0x560c5cc6c0c9 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:201
  #24 0x560c5cafc3e7 in Dispatch () at ../../../../dix/dispatch.c:492
  #25 0x560c5cb006b4 in dix_main (argc=11, argv=0x713af268, 
envp=) at ../../../../dix/main.c:272
  #26 0x7f72fec29d90 in __libc_start_call_main 
(main=main@entry=0x560c5cae95d0 , argc=argc@entry=11, 
argv=argv@entry=0x713af268) at ../sysdeps/nptl/libc_start_call_main.h:58
  #27 0x7f72fec29e40 in __libc_start_main_impl (main=0x560c5cae95d0 , 
argc=11, argv=0x713af268, init=, fini=, 
rtld_fini=, stack_end=0x713af258) at ../csu/libc-start.c:392
  #28 0x560c5cae9605 in _start ()

  This post describes a similar issue:
  https://gitlab.freedesktop.org/drm/intel/-/issues/4858

  I tried using a workaround from the above link, to set GPU to max
  frequency using command "intel_gpu_frequency -m", this seemed to
  reduce the rate of occurrence from once per day to once every 3 days,
  but this is not a permanent solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2059033/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-24 Thread Bug Watch Updater
** Changed in: gobject-introspection (Debian)
   Status: New => Fix Released

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  Fix Released

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 1988754] Re: libreoffice writer crashes when edit the page break

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

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

Title:
  libreoffice writer crashes when edit the page break

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

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 1729433] Re: LibreOffice doesn't remember window size when running under Wayland

2024-03-21 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/1729433

Title:
  LibreOffice doesn't remember window size when running under Wayland

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

Bug description:
  1. Open any LibreOffice document, e.g., a Writer or Calc document.
  2. Make the window a reasonable, non-maximized size.
  3. Maximize the window.
  4. Close LibreOffice.
  5. Open the document again; it will open maximized.
  6. Un-maximize the window.
  7. Observe how the window has a ridiculously small size, not its previously 
unmaximized size.

  LibreOffice or gnome-shell bug? Not sure.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libreoffice-core 1:5.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 16:21:29 2017
  InstallationDate: Installed on 2017-05-19 (166 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to artful on 2017-10-20 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1729433/+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 192056] Re: [Upstream] [hardy] Cannot Open password-encrypted MS Office 2003 files

2024-03-21 Thread Bug Watch Updater
Launchpad has imported 37 comments from the remote bug at
http://qa.openoffice.org/issues/show_bug.cgi?id=46307.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2005-03-30T15:25:29+00:00 Thomas-hovezak wrote:

when trying to open an password-encrypted ppt you get following message:

read error
the loading of password-encrypted Microsoft PowerPoint presentation is not
supported..

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/0


On 2005-03-30T15:31:59+00:00 Thomas-hovezak wrote:

Created attachment 24419
the ppt file which caused the issue

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/1


On 2005-03-30T16:13:16+00:00 Wolframgarten wrote:

Changed to defect, reassigned.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/2


On 2005-04-06T15:16:11+00:00 Christian-guenther-v wrote:

set to new and change the target.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/3


On 2005-04-06T15:20:00+00:00 Christian-guenther-v wrote:

With the internal bug 115982 you fixed something about password protected 
PPT-Files.
Why can't we load this file.
Has  this file another encryption?
Please have a look.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/4


On 2005-04-26T11:11:54+00:00 Sven-jacobi wrote:

sj->cgu: As you can read in 115982 PowerPoint is providing RC4 encryption only,
and RC4 is not be supported by OOo. That time I added the new error message"read
error the loading of password-encrypted Microsoft PowerPoint presentation is not
supported.." so that you are not getting the general io error if trying to load
protected files.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/5


On 2005-05-02T18:40:41+00:00 Christian-guenther-v wrote:

OOo should support RC4 encryption to load Password protected PPT-Files.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/6


On 2005-05-23T13:54:49+00:00 Bettina-haberer wrote:

Set issue type, target and keywords.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/7


On 2006-03-09T09:03:44+00:00 Christian-guenther-v wrote:

*** Issue 62955 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/8


On 2006-05-15T08:47:49+00:00 Wolframgarten wrote:

*** Issue 65376 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/9


On 2007-12-19T09:05:43+00:00 Marcelly-bernard wrote:

We can see in various OOo forums that PowerPoint files password protected for 
modifications, but not protected for reading, are becoming common.

Windows users (Win 200 and above) can display them with the free PowerPoint 
Viewer 
2007.
But users of other OS (Linux, Mac) cannot read these PowerPoint files.

This is a real lack of compatibility for OpenOffice.org in the non-
Microsoft world.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/10


On 2008-04-07T09:18:17+00:00 Wolframgarten wrote:

*** Issue 61691 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/17


On 2008-04-07T09:18:38+00:00 Wolframgarten wrote:

*** Issue 87922 has been marked as a duplicate of this issue. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/192056/comments/18


On 2008-04-07T09:28:22+00:00 Cno wrote:

added 'Powerpoint' to the issues summary

Reply at:

[Desktop-packages] [Bug 2032992] Re: [snap] chromium snap does not allow to read symlinks to /usr/share/javascript

2024-03-21 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Fix Released

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

Title:
  [snap] chromium snap does not allow to read symlinks to
  /usr/share/javascript

Status in Mozilla Firefox:
  Fix Released
Status in chromium-browser package in Ubuntu:
  In Progress
Status in firefox package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1) Install chromium snap
  snap install chromium
  2) Install openjdk-21 documentation
  sudo apt install openjdk-21-doc
  3) Browse API documentation
  chromium /usr/share/doc/openjdk-21-doc/api/index.html

  The search bar is inactive and dev console contains:
  jquery-3.6.1.min.js:1 Failed to load resource: net::ERR_FILE_NOT_FOUND

   
  $ls -l 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  lrwxrwxrwx 1 root root 43 Mar 17 13:31 
/usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js -> 
../../../../javascript/jquery/jquery.min.js

  cat /usr/share/doc/openjdk-21-jre-headless/api/script-dir/jquery-3.6.1.min.js
  prints the file contents

  Downloaded version of chrome opens documentation with active search bar and 
no javascript errors
  /tmp/chrome/chrome /usr/share/doc/openjdk-21-doc/api/index.html

  Expected results:

  Chromium snap should be able to follow symlink into
  /usr/share/javascript and correctly load OpenJDK API documentation.

  Note: this probably should be a specific exclusion for Debian-based
  systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/2032992/+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 1826544] Re: media button to disable touchpad not working

2024-03-20 Thread Bug Watch Updater
** Changed in: gnome-settings-daemon
   Status: New => Fix Released

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

Title:
  media button to disable touchpad not working

Status in GNOME Settings Daemon:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged

Bug description:
  I have an ASUS UX305CA laptop and after upgrading to 18.04 I am no
  longer able to disable the touchpad by hitting Fn+F9 .  When I hit
  Fn+F9 it shows the graphic indicating that it's disabling the
  touchpad, but the touchpad continues to work.  I tried using a LiveUSB
  copy of 18.04 and it the button works fine, so there seems to be
  something related to upgrading.  I upgrading from 16.04 where it
  worked fine before.

  I'm not sure which package to file this bug against, sorry.

  Here are some details:

  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04
  $ lsmod | grep asus
  asus_nb_wmi28672  0
  asus_wmi   28672  1 asus_nb_wmi
  sparse_keymap  16384  1 asus_wmi
  wmi24576  1 asus_wmi
  video  45056  2 asus_wmi,i915
  asus_wireless  16384  0
  $ dconf read /org/gnome/desktop/peripherals/touchpad/send-events
  'enabled'
   
  I also went through a diff between gsettings on the LiveUSB and my current 
install and nothing stood out to me as being related.  I do have 
`org.gnome.desktop.interface gtk-im-module 'ibus'` which differs from LiveUSB 
which is set to 'gtk-im-context-simple', but I don't know if it's related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1826544/+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 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

2024-03-20 Thread Bug Watch Updater
** Changed in: mesa
   Status: New => Fix Released

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 2057851] Re: abseil: FTBFS on arm{el,hf}:

2024-03-19 Thread Bug Watch Updater
** Changed in: abseil (Debian)
   Status: New => Fix Released

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

Title:
  abseil: FTBFS on arm{el,hf}:

Status in abseil package in Ubuntu:
  New
Status in abseil package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/1065770:

  Source: abseil
  Version: 20220623.1-3.1
  Severity: serious
  Tags: ftbfs
  Justification: fails to build from source (but built successfully in the past)
  X-Debbugs-Cc: sramac...@debian.org

  
https://buildd.debian.org/status/fetch.php?pkg=abseil=armel=20220623.1-3.1=1709076797=0

  182/182 Test  #83: absl_random_beta_distribution_test
  .   Passed  110.45 sec

  98% tests passed, 3 tests failed out of 182

  Total Test time (real) = 113.40 sec

  The following tests FAILED:
165 - absl_mutex_test (Subprocess aborted)
166 - absl_notification_test (Failed)
167 - absl_per_thread_sem_test (Failed)
  Errors while running CTest
  make[2]: *** [Makefile:74: test] Error 8

  Cheers
  -- 
  Sebastian Ramacher

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/abseil/+bug/2057851/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-18 Thread Bug Watch Updater
** Changed in: gobject-introspection
   Status: New => Fix Released

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  Fix Released
Status in gobject-introspection package in Ubuntu:
  Fix Committed
Status in gobject-introspection package in Debian:
  New

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386

2024-03-14 Thread Bug Watch Updater
** Changed in: openjdk-8 (Debian)
   Status: New => Fix Released

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

Title:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386

Status in java-atk-wrapper package in Ubuntu:
  New
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in openjdk-8 package in Debian:
  Fix Released

Bug description:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to
  dependency on java-atk-bridge.

  This dependency was introduced by dropping condition present in 392:
  --
    ifeq ($(derivative),Ubuntu)
  ifeq ($(DEB_HOST_ARCH),i386)
    ifeq (,$(filter $(distrel),precise trusty xenial bionic))
  with_bridge =
    endif
  endif
    endif
  --

  Note:
   java-atk-wrapper is present in noble on i386

  This is a regression introduced in 8u402-ga-2:

    * Restore M-A installability of focal/i386 package (LP#1916327)
  by adding xenial, bionic, focal, jammy to the list of releases
  built with the ATK bridge, but not enabling it by default;
  keep jessie on, stretch and sid and mantic/noble off the list:
  please report bugs for issues with the bridge, so sthibault
  can find, debug, fix them

  See LP: #1916327

  The alternative is to publish atk-wrapper for i386 in mantic, jammy
  and focal.

  Options:
   a) rollback the fix in Ubuntu
   b) publish atk-wrapper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+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 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

2024-03-13 Thread Bug Watch Updater
** Changed in: evolution-ews
   Status: New => Fix Released

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  Fix Released
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  Earlier I could add outlook.com to gnome calendar with exchange in
  Gnome online accounts and evolution-ews installed, now Microsoft has
  changed something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

  edit 10.3.24: upgraded to Ubuntu 23.10 and it still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+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 2054851] Re: [radeon] gnome-shell and Xorg both crash with SIGSEGV in radeon_bo_reference()

2024-03-13 Thread Bug Watch Updater
** Changed in: mesa (Debian)
   Status: Unknown => Confirmed

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

Title:
  [radeon] gnome-shell and Xorg both crash with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa package in Debian:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 2057836] Re: gst-python1.0 fails to build: test failures

2024-03-13 Thread Bug Watch Updater
** Changed in: gst-python1.0 (Debian)
   Status: Unknown => Confirmed

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  New
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Confirmed

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2057836] Re: gst-python1.0 fails to build: test failures

2024-03-13 Thread Bug Watch Updater
** Changed in: pygobject
   Status: Unknown => New

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

Title:
  gst-python1.0 fails to build: test failures

Status in pygobject:
  New
Status in gst-python1.0 package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gst-python1.0 package in Debian:
  Unknown

Bug description:
  gst-python1.0 fails to build because of test failures.

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.22.10-1build1

  https://launchpad.net/ubuntu/+source/gst-python1.0/1.24.0-1

  I have reported the issue to the upstream developers

  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/3353

To manage notifications about this bug go to:
https://bugs.launchpad.net/pygobject/+bug/2057836/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-11 Thread Bug Watch Updater
** Changed in: gobject-introspection (Debian)
   Status: Unknown => New

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  New
Status in gobject-introspection package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gobject-introspection package in Debian:
  New

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2056753] Re: pygobject FTBFS on armhf: time_t build test failure

2024-03-11 Thread Bug Watch Updater
** Changed in: gobject-introspection
   Status: Unknown => New

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

Title:
  pygobject FTBFS on armhf: time_t build test failure

Status in GObject Introspection:
  New
Status in gobject-introspection package in Ubuntu:
  Triaged
Status in pygobject package in Ubuntu:
  Triaged
Status in gobject-introspection package in Debian:
  Unknown

Bug description:
  pygobject fails to build on armhf, the only Ubuntu 32-bit architecture
  that has done the time_t transition.

  test_gi.py runs a time_t test that I believe is using functions in
  glib2.0

  Test log excerpt
  

  tests/test_gi.py ... [ 
21%]
  .
  --- stderr ---
  Fatal Python error: Aborted

  Current thread 0xf785e020 (most recent call first):
File "/<>/tests/test_gi.py", line 579 in test_time_t_in
File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
File "/usr/lib/python3.12/unittest/case.py", line 634 in run
File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
File "/usr/lib/python3/dist-packages/_pytest/unittest.py", line 338 in 
runtest
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 170 in 
pytest_runtest_call
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 263 in 

File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 342 in 
from_call
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 262 in 
call_runtest_hook
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 223 in 
call_and_report
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 134 in 
runtestprotocol
File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 115 in 
pytest_runtest_protocol
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 352 in 
pytest_runtestloop
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 327 in _main
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 273 in 
wrap_session
File "/usr/lib/python3/dist-packages/_pytest/main.py", line 320 in 
pytest_cmdline_main
File "/usr/lib/python3/dist-packages/pluggy/_callers.py", line 102 in 
_multicall
File "/usr/lib/python3/dist-packages/pluggy/_manager.py", line 119 in 
_hookexec
File "/usr/lib/python3/dist-packages/pluggy/_hooks.py", line 501 in __call__
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 175 
in main
File "/usr/lib/python3/dist-packages/_pytest/config/__init__.py", line 198 
in console_main
File "/usr/lib/python3/dist-packages/pytest/__main__.py", line 7 in 
File "", line 88 in _run_code
File "", line 198 in _run_module_as_main

  Full build log
  ==
  
https://launchpad.net/ubuntu/+source/pygobject/3.47.0-3build1/+latestbuild/armhf

To manage notifications about this bug go to:
https://bugs.launchpad.net/gobject-introspection/+bug/2056753/+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 2039801] Re: Locate pointer not working when animations are disabled

2024-03-11 Thread Bug Watch Updater
** Changed in: gnome-shell
   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/2039801

Title:
  Locate pointer not working when animations are disabled

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  In Progress

Bug description:
  I have just upgraded to Ubuntu 23.10 (Mantic Minotaur), going through the 
regular process of settling in with the new features and so forth, I realised 
that the 'locate pointer' is not working as expected. 
  When the focus is on a screen element (like this text field that I am 
entering information into) I can press the left ctrl button and the border will 
flash around the element/text field/button etcetera. 
  (I have made a screen cast, if I can I will upload it)
  Previously when pressing the left ctrl button the mouse pointer would be 
shown with a circular pulsing image (like a something dropping into calm 
water). 
  I have read several forums and have looked specifically how to set the locate 
pointer option, I have set it in accessibility->pointing & clicking->Locate 
Pointer, also via cli with "gsettings set org.gnome.desktop.interface 
locate-pointer true" and using the gnome tweaks gui. 
  None of these things work.
  Ubuntu 23.10,gnome 45, gdm3, acer aspire V 17 nitro black edition 
  Description:  Ubuntu 23.10
  Release:  23.10
  Not seemingly specific to any 'package' so package version is not relevant.

  Expect the mouse pointer to be highlighted instead only the cursor position 
is located.
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2019-10-17 (1464 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 45.0-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  RelatedPackageVersions: mutter-common 45.0-3ubuntu3
  Tags: mantic
  Uname: Linux 6.5.0-9-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (7 days ago)
  UserGroups: adm cdrom debian-transmission dip lpadmin lxd plugdev sambashare 
sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2039801/+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 2056671] Re: Mouse pointer toggle in the screenshot/screencast dialog is hard to discover

2024-03-11 Thread Bug Watch Updater
** Changed in: gnome-shell
   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/2056671

Title:
  Mouse pointer toggle in the screenshot/screencast dialog is hard to
  discover

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

Bug description:
  Press the Print Screen button, select the Record Screen option and
  then press capture [1]. The screen recording works as expected however
  does not display the mouse cursor making it hard to use the screen
  capture for a tutorial without using a third-party capture device.

  The screen cast should capture the mouse pointer by default. Or [1]
  you include an option to show/hide the mouse pointer in the recording.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar 10 12:04:47 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 530 [1028:06b9]
  InstallationDate: Installed on 2024-03-10 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Dell Inc. OptiPlex 7040
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic 
root=UUID=6b60e9f2-5ca2-4299-85bd-4fb992af91dd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2022
  dmi.bios.release: 1.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.24.0
  dmi.board.name: 096JG8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.24.0:bd07/14/2022:br1.24:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn096JG8:rvrA01:cvnDellInc.:ct3:cvr:sku06B9:
  dmi.product.family: OptiPlex
  dmi.product.name: OptiPlex 7040
  dmi.product.sku: 06B9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1
  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/gnome-shell/+bug/2056671/+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 2054924] Re: color emoji are broken with fontconfig 2.15

2024-03-10 Thread Bug Watch Updater
** Changed in: fontconfig (Debian)
   Status: Confirmed => Fix Released

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Fix Released

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

2024-03-10 Thread Bug Watch Updater
** Changed in: evolution-ews
   Status: Fix Released => New

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  New
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  Earlier I could add outlook.com to gnome calendar with exchange in
  Gnome online accounts and evolution-ews installed, now Microsoft has
  changed something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

  edit 10.3.24: upgraded to Ubuntu 23.10 and it still does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+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 2056649] Re: Outlook.com does not authenticate anymore with evolution-ews or gnome online accounts

2024-03-09 Thread Bug Watch Updater
** Changed in: evolution-ews
   Status: Unknown => Fix Released

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

Title:
  Outlook.com does not authenticate anymore with evolution-ews or gnome
  online accounts

Status in evolution-ews:
  Fix Released
Status in evolution-ews package in Ubuntu:
  New
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.4
  evolution-ews 3.44.0-1
  gnome-online-accounts 3.44.0-1ubuntu1

  
  Earlier I could add outlook.com to gnome calendar with exchange in Gnome 
online accounts and evolution-ews installed, now Microsoft has changed 
something and it does not authenticate anymore..

  https://support.microsoft.com/en-us/office/outlook-and-other-apps-are-
  unable-to-connect-to-outlook-com-when-using-basic-
  authentication-f4202ebf-89c6-4a8a-bec3-3d60cf7deaef

  It's not very long to the release date for 24.04 LTS, and I hope this
  is fixed before that..

  In evolution it does ask for outlook.com password and I use the right
  password, nothing happens, other than it just asking for password
  again.. edit: I got a error message now (see screenshot in comment #1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-ews/+bug/2056649/+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 1825227] Re: gnome-calendar overcompensates time zone difference in web ics calendar

2024-03-08 Thread Bug Watch Updater
** Changed in: gnome-calendar
   Status: New => Fix Released

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

Title:
  gnome-calendar overcompensates time zone difference in web ics
  calendar

Status in GNOME Calendar:
  Fix Released
Status in gnome-calendar package in Ubuntu:
  Triaged

Bug description:
  Upon adding a web ics calendar (via Evolution due to Bug #1825224),
  the events from this calendar were not properly time-compensated for
  my time zone. While Evolution and Gnome Shell displayed the time of my
  events properly, gnome-calendar displayed the events 7 hours in the
  past, likely attempting to compensate for my time zone (GMT -7).

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:47:17 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-calendar/+bug/1825227/+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 2043517] Re: gnome-shell on non-active VT busy-loops through libwayland-server.so (sometimes)

2024-03-07 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Unknown => New

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

Title:
  gnome-shell on non-active VT busy-loops through libwayland-server.so
  (sometimes)

Status in X.Org X server:
  New
Status in mutter package in Ubuntu:
  New
Status in xwayland package in Ubuntu:
  New

Bug description:
  I run several gnome sessions at once - different users on different
  Virtual Terminals.

  Sometimes, gnome-shell for a non-active VT starts using 100% CPU.  Or,
  actually 99% CPU because it's doing IPC as well.  And the
  corresponding XWayland uses 40% CPU.

  FWIW, sending SIGSTOP to either gnome-shell or XWayland stops the
  other one from busy-looping as well.

  If I switch back to the affected VT, it appears to function fine, but
  it is still using 100% + 40% CPU.

  
  Version numbers:

  Ubuntu 22.04.3 LTS
  gnome-shell 42.9-0ubuntu2
  xwayland 2:22.1.1-1ubuntu0.7

  
  $ ps -aux | grep 'alan .*gnome-shell$'
  alan9248 26.1  3.4 5492888 269136 ?  Rsl  19:54  30:26 
/usr/bin/gnome-shell

  $ sudo strace -p 9248 2>&1|head
  strace: Process 9248 attached
  epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}], 
32, 0) = 1
  recvmsg(21, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\1\0\0\0\0\0\f\0\3\0\0\0", iov_len=752}, {iov_base="", 
iov_len=3344}], msg_iovlen=2, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_CMSG_CLOEXEC) = 12
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  sendmsg(21, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="\3\0\0\0\0\0\f\0[\2\0\0\1\0\0\0\1\0\f\0\3\0\0\0", 
iov_len=24}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 
MSG_DONTWAIT|MSG_NOSIGNAL) = 24
  poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}, {fd=9, events=POLLIN}, 
{fd=19, events=POLLIN}, {fd=20, events=POLLIN}, {fd=23, events=POLLIN}, {fd=24, 
events=POLLIN}, {fd=25, events=POLLIN}, {fd=34, events=POLLIN}, {fd=36, 
events=POLLIN}, {fd=37, events=POLLIN}, {fd=54, events=POLLIN}, {fd=63, 
events=POLLIN}, {fd=66, events=POLLIN}], 14, 79809702) = 2 ([{fd=4, 
revents=POLLIN}, {fd=37, revents=POLLIN}])
  read(4, "\2\0\0\0\0\0\0\0", 16) = 8
  write(4, "\1\0\0\0\0\0\0\0", 8) = 8
  epoll_wait(37, [{events=EPOLLIN, data={u32=403234816, u64=139797293752320}}], 
32, 0) = 1

  
  The recvmsg() call is here:

  #0  __libc_recvmsg (fd=21, msg=0x7fff1de64a50, flags=1073741888) at 
../sysdeps/unix/sysv/linux/recvmsg.c:35
  #1  0x7f2531ea5ad6 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #2  0x7f2531ea4eea in wl_event_loop_dispatch () at 
/lib/x86_64-linux-gnu/libwayland-server.so.0
  #3  0x7f2531d2b45b in wayland_event_source_dispatch (base=, callback=, data=)
  at ../src/wayland/meta-wayland.c:110
  #4  0x7f2532b42d3b in g_main_dispatch (context=0x55c0046cc8f0) at 
../../../glib/gmain.c:3419
  #5  g_main_context_dispatch (context=0x55c0046cc8f0) at 
../../../glib/gmain.c:4137
  #6  0x7f2532b98258 in g_main_context_iterate.constprop.0
  (context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../glib/gmain.c:4213
  #7  0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at 
../../../glib/gmain.c:4413
  #8  0x7f2531cd0b79 in meta_context_run_main_loop 
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
  at ../src/core/meta-context.c:437
  #9  0x55c003cf4f12 in main (argc=, argv=) 
at ../src/main.c:650

  
  The sendmsg() call is here:

  Thread 1 "gnome-shell" hit Breakpoint 1, __libc_sendmsg (fd=21, 
msg=0x7fff1de64c50, flags=16448) at ../sysdeps/unix/sysv/linux/sendmsg.c:26
  26../sysdeps/unix/sysv/linux/sendmsg.c: No such file or directory.
  (gdb) where
  #0  __libc_sendmsg (fd=21, msg=0x7fff1de64c50, flags=16448) at 
../sysdeps/unix/sysv/linux/sendmsg.c:26
  #1  0x7f2531ea1c9d in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #2  0x7f2531ea565e in wl_display_flush_clients () at 
/lib/x86_64-linux-gnu/libwayland-server.so.0
  #3  0x7f2531d2b437 in wayland_event_source_prepare 
(base=base@entry=0x55c004a374d0, timeout=timeout@entry=0x7fff1de64dc4)
  at ../src/wayland/meta-wayland.c:97
  #4  0x7f2532b428e7 in g_main_context_prepare (context=0x55c0046cc8f0, 
priority=0x7fff1de64e50) at ../../../glib/gmain.c:3739
  #5  0x7f2532b98123 in g_main_context_iterate.constprop.0
  (context=0x55c0046cc8f0, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../glib/gmain.c:4193
  #6  0x7f2532b422b3 in g_main_loop_run (loop=0x55c00698ae30) at 
../../../glib/gmain.c:4413
  #7  0x7f2531cd0b79 in meta_context_run_main_loop 
(context=context@entry=0x55c0046c70c0, error=error@entry=0x7fff1de64f08)
  at ../src/core/meta-context.c:437
  #8  0x55c003cf4f12 in main (argc=, argv=) 
at ../src/main.c:650

To manage notifications about this 

[Desktop-packages] [Bug 2056331] Re: [SRU] fix suspend/resume when there are no input devices

2024-03-06 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Unknown => Fix Released

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

Title:
  [SRU] fix suspend/resume when there are no input devices

Status in X.Org X server:
  Fix Released
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  [Impact]

  Bug is impacting the suspend/resume flow when there is no input device
  connected to machine. xorg hangs in this case.

  [Where problems could occur]

  The problem could occur in places where there is no input device
  connected to the system but a suspend/resume is triggered.

  [Test Case]

  * Enable proposed updates (https://wiki.ubuntu.com/Testing/EnableProposed)
  * Update xorg-server to the version in -proposed: sudo apt install -t 
jammy-proposed xorg-server
  * Unplug all USB devices such as USB drive, keyboard, mouse, etc.
  * Set RTC timer and suspend the system via UART console
  $ echo 8 > /proc/sys/kernel/printk
  $ sudo rtcwake -v -m no -s 240
  $ sudo systemctl suspend

  [Regression Potential]

  The patch defines a default behavior in systemd_logind_drop_master
  function so there is a possibility that there might be a regression
  that may affect all the systems that utilizes
  systemd_logind_drop_master

  
  Upstream Bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/2056331/+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 2055762] Re: Closing window button doesn't appear correctly on the second display

2024-03-06 Thread Bug Watch Updater
** Changed in: gnome-shell
   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/2055762

Title:
  Closing window button doesn't appear correctly on  the second display

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

Bug description:
  If toggle it to the Activity task, its closing window button on second 
display (other monitor) is showed as well, however if toggle it to the Program 
Menu then the X button doesn't show completely.
  I attached a recorded explains it. Please observe the left screen's X button.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-23 (469 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  NonfreeKernelModules: zfs
  Package: gnome-shell 42.9-0ubuntu2
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ko_KR.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags: jammy wayland-session third-party-packages
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom cvdnetwork dip kvm libvirt lpadmin lxd plugdev render 
sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2055762/+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 2052913] Re: Large Performance Regression in fullscreen windows from Ubuntu Jammy to Ubuntu Noble

2024-03-05 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

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

Title:
  Large Performance Regression in fullscreen windows from Ubuntu Jammy
  to Ubuntu Noble

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble 
(gnome-shell 45.3-1ubuntu1)
  Default Ubuntu GNOME desktop environment used with no user added extensions.

  GPU driverstack identical between the two distros (eliminated as a variable).
  Linux kernel identical between distros (eliminated as a variable)
  CPU, GPU, and RAM clocks pinned to max.

  Test case: Minecraft Java Edition (shared drive with identical setup
  between Ubuntu versions). Fullscreen 1080p. Xorg display server.

  FPS (uncapped):
  Ubuntu Jammy: 177fps
  Ubuntu Noble: 140fps

  Observations:
  Ubuntu Jammy:
  gnome-shell process cpu% when camera is still: 0-1%
  gnome-shell process cpu% when camera is moving: 10-20%
  Memory Bandwidth (CPU and GPU shared): 40%

  Ubuntu Noble:
  gnome-shell process cpu% when camera is still: 20-55%
  gnome-shell process cpu% when camera is moving: 30-55%
  Memory Bandwidth (CPU and GPU shared): 50%

  In both cases GPU utilization is observed to be near 100%.

  So in summary, large performance regression regression which appears
  to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on
  ubuntu jammy when there the camera is still (even with a fps graph
  drawn onscreen) in stark contrast to ubuntu noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2052913/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

2024-03-04 Thread Bug Watch Updater
** Changed in: upower
   Status: Fix Released => New

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  New
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 2056079] Re: Serious playback timing problems affecting GStreamer and other pulseaudio and pipewire audio clients

2024-03-04 Thread Bug Watch Updater
** Changed in: gst-plugins-good
   Status: Unknown => New

** Changed in: pipewire
   Status: Unknown => Fix Released

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

Title:
  Serious playback timing problems affecting GStreamer and other
  pulseaudio and pipewire audio clients

Status in gst-plugins-good:
  New
Status in PipeWire:
  Fix Released
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  This is a request for a backport of an existing bug fix, present in
  the recent Pulseaudio version 17 release, to the outdated Pulseaudio
  16 releases in jammy - noble.

  Affects: Ubuntu 22.04.0 LTS and all later versions.

  The fix fixes an annoying start of playback timing bug that affects my
  own software package octave-psychtoolbox-3 (part of Ubuntu universe),
  see
  
https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/814#issuecomment-1723827374
  which uses GStreamer for video and audio playback. Psychtoolbox is a
  very popular toolkit for neuroscience and related medical research,
  with Ubuntu as the recommended target distribution. It requires high
  reliability in audio and video presentation timing, so the bug
  described in the various links below is serious to our users.

  The bug also in the same way affects other media applications in
  Ubuntu which play back audio via the default (auto-plugged)
  pulseaudiosink GStreamer plugin. See GStreamer bug report
  https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1735). The
  GStreamer bug turned out to be a pulseaudio client library bug (in
  libpulse.so.0).

  Any native pulseaudio client is affected, even if pipewire is used as
  desktop sound server in recent Ubuntu releases, given that many audio
  applications still access pipewire via its pulseaudio frontend
  (package pipewire-pulse). See pipewire bug
  https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3399

  The bug in libpulse.so.0, reported against Pulseaudio 16 in
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1383 has
  been fixed for the Pulseaudio 17 release.

  See the following merge request for the following trivial one-liner
  patch that would need to be backported to Ubuntu's current
  implementation:

  
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/745/diffs

  I hoped that Pulseaudio 17 would be included in Debian in time for
  integration into Ubuntu 24.04-LTS, but apparently not much maintenance
  of pulseaudio is happening on the Debian side at the moment.

  Given that this bug affects all Ubuntu versions since Ubuntu
  22.04-LTS, I'd ask kindly for a backport, ideally for Pulseaudio
  15.99.1 in 22.04-LTS and Pulseaudio 16.1 in upcoming 24.04-LTS, but at
  least for the upcoming 24.04-LTS.

  Alternatively it would have been great to get Pulseaudio upgraded to
  version 17 for upcoming Ubuntu 22.04-LTS to fix many more bugs, but
  apparently that is too late now, according to
  https://answers.launchpad.net/ubuntu/+source/pulseaudio/+question/709476

  Thanks,
  -mario

To manage notifications about this bug go to:
https://bugs.launchpad.net/gst-plugins-good/+bug/2056079/+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 2022954] Re: RDP and VNC fail when headless with no monitor (but work otherwise!)

2024-03-03 Thread Bug Watch Updater
** Changed in: gnome-remote-desktop
   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/2022954

Title:
  RDP and VNC fail when headless with no monitor (but work otherwise!)

Status in GNOME Remote Desktop:
  Fix Released
Status in mutter package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:

  *  Install fresh Ubuntu 22.04.2 LTS
  *  Enable RDP and VNC via sharing control panel
  *  Test RDP and VNC, verify working
  *  Unplug monitor
  *  Try RDP.  Authenticate, then connection closed with no display
  *  Try VNC.  Authenticate, then connection closed with no display
  *  Plug monitor back in
  *  Try RDP.  Works!
  *  Try VNC.  Works!
  *  Unplug monitor
  *  Try RDP.  AUthenticate, then connection closed with no display
  *  Try VNC.  Authenticate, then connection closed with no display
  *  GOTO 10

  Symptoms are present with both wayland and X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  5 11:02:41 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: ZOTAC International (MCO) Ltd. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [19da:b301]
  InstallationDate: Installed on 2023-06-01 (4 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ZOTAC ZBOX-CI323NANO
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_j45abz@/vmlinuz-5.19.0-43-generic 
root=ZFS=rpool/ROOT/ubuntu_j45abz ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: B301P027
  dmi.board.asset.tag: N/A
  dmi.board.name: ZBOX-CI323NANO
  dmi.board.vendor: ZOTAC
  dmi.board.version: XX
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrB301P027:bd09/11/2019:br5.11:svnZOTAC:pnZBOX-CI323NANO:pvrXX:rvnZOTAC:rnZBOX-CI323NANO:rvrXX:cvnDefaultstring:ct3:cvrDefaultstring:skuN/A:
  dmi.product.family: N/A
  dmi.product.name: ZBOX-CI323NANO
  dmi.product.sku: N/A
  dmi.product.version: XX
  dmi.sys.vendor: ZOTAC
  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.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/gnome-remote-desktop/+bug/2022954/+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 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows

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

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

Title:
  Thunderbird under Wayland does not correctly close (or manage) windows

Status in GNOME Shell:
  Fix Released
Status in Mozilla Thunderbird:
  Expired
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default.
  Thunderbird version: 78.11.0 with "gnome-support" package.
  Same problem in safe mode.
  Description:
  By default in this context, TB is a Wayland task.
  When opening a compose windows (or reply or transfer), sending mail 
apparently close the windows, but gnome shell continue to show multiple 
"points", as if multiple windows are still active.
  And after closing TB, it seems maintained in the same state, so it becomes 
impossible to relaunch it from the desk. But task manager of "looking glass" 
does not show it and it is possible to launch from terminal.
  Provisional solution:
  Modify .desktop file to launch with --display=:0 option, that force to use 
XWayland interface, as shown by xlsclients (for example).
  But it is actually a bug under Wayland context, that also badly interfer with 
many add-ons or extensions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1932328/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2024-03-01 Thread Bug Watch Updater
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.altlinux.org/show_bug.cgi?id=29591.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2013-11-18T17:19:32+00:00 Norbert wrote:

Description of problem:
In previous GNOME versions (for example, in 3.4) I was able to set keyboard 
layout switching to Alt+Shift, Ctrl+Shift, both Shifts, etc. In AltLinux p7 I 
can't set it from gnome-control-center keyboard.
This bug come from GNOME.

Version-Release number of selected component (if applicable):
gnome-control-center 3.8.6-alt0.M70P.1

How reproducible:
Go to gnome-control-center keyboard and try to set Alt+Shift or Ctrl+Shift as 
layout switching keys.


Steps to Reproduce:
1. Go to gnome-control-center keyboard (Shortcuts -> Typing)
2. Try to set Alt+Shift or Ctrl+Shift at 'Switch to next input source'
3. Get 'Disabled' in 'Switch to next input source'. 

If you set default Super+Space - it set and work normally, but it is not
comfortable and universal for all users.

This bug is very hot in Ubuntu 13.10 too (689 users are affected, see
https://bugs.launchpad.net/bugs/1218322), but Canonical fixed it.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/365


On 2013-11-19T09:35:16+00:00 Aris-x wrote:

Shortcuts -> Typing -> Modifiers-only switch to next source

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/367


On 2013-11-19T09:52:54+00:00 Norbert wrote:

Спасибо, Юрий!
Но сочетания Ctrl+Shift+C/V на русской раскладке в терминале и выделение текста 
по Ctrl+Shift+стрелки не работают если переключение поставлено на привычное 
Ctrl+Shift. Мне создать новый багрепорт здесь или писать сразу в апстрим?

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/369


On 2013-11-19T11:42:45+00:00 Aris-x wrote:

Это у вас с одной стороны не работает, -- используйте другую. В апстрим 
написать можете, но проще приспособиться. 
Мне, например, правым Ctrl-ом удобно переключаться.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/371


On 2013-11-19T12:42:09+00:00 Norbert wrote:

Спасибо! Действительно "другая сторона" работает. Но в апстрим я все-
таки написал (https://bugzilla.gnome.org/show_bug.cgi?id=712667).

Этот (29591) баг можем закрывать. Спасибо!

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/372


On 2024-02-29T18:28:11+00:00 Lav-7 wrote:

(Ответ для Nikolay Strelkov на комментарий #2)
> Спасибо, Юрий!
> Но сочетания Ctrl+Shift+C/V на русской раскладке в терминале и выделение
> текста по Ctrl+Shift+стрелки не работают если переключение поставлено на
> привычное Ctrl+Shift. Мне создать новый багрепорт здесь или писать сразу в
> апстрим?
Есть задача и патч, исправляющий поведение (делает переключение раскладки при 
_отжатии_ клавиш):
https://bugzilla.altlinux.org/34900
Также эта проблема не актуальна для wayland.

Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1218322/comments/549


** Changed in: gnome-control-center (ALT Linux)
   Status: Unknown => Invalid

** Changed in: gnome-control-center (ALT Linux)
   Importance: Unknown => Medium

** Bug watch added: bugzilla.gnome.org/ #712667
   https://bugzilla.gnome.org/show_bug.cgi?id=712667

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

Title:
  Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

Status in GNOME Settings Daemon:
  Unknown
Status in System76:
  New
Status in Ubuntu Flashback:
  New
Status in Ubuntu GNOME:
  Fix Released
Status in Ubuntu GNOME Flashback:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon package in Ubuntu:
  Triaged
Status in gnome-control-center package in ALT Linux:
  Invalid
Status in gnome-control-center package in Baltix:
  Confirmed
Status in gnome-control-center package in Gentoo Linux:
  Unknown
Status in gnome-control-center package in Mandriva:
  Unknown

Bug description:
  [Impact]

  Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift,
  etc. Shift, Caps Lock keys are just ignored in settings.

  [Test Case]

  - 

[Desktop-packages] [Bug 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)

2024-03-01 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => 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/2055519

Title:
  Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform /
  framebuffer-get-bits (due to Mesa >= 23.1.1)

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  Mutter's test cases fail on jammy since Mesa got updated:

  mutter:cogl+cogl/conform / framebuffer-get-bits

  [ Test Plan ]

  Build mutter and run its tests (done automatically during packaging)

  [ Where problems could occur ]

  More tests fail.

  [ Other Info ]

  27/113 mutter:cogl+cogl/conform / framebuffer-get-bits
RUNNING
  >>> RUN_TESTS_QUIET=1 
PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py 
/<>/cogl/tests/run-tests.sh 
/<>/obj-s390x-linux-gnu/cogl/tests/config.env 
cogl/tests/conform/test-conformance test_framebuffer_get_bits
  ― ✀  ―
  Starting D-Bus daemons (session & system)...
  Starting mocked services...
  Running test case...
     Test GL+GLSL  GL3   ES2
   test_framebuffer_get_bits: ok FAIL   n/a
  Traceback (most recent call last):
    File "/<>/src/tests/meta-dbus-runner.py", line 184, in 
  test_case.wrap_call(rest[1:])
    File "/<>/src/tests/meta-dbus-runner.py", line 171, in 
wrap_call
  self.assertEqual(p.wait(), 0)
    File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual
  assertion_func(first, second, msg=msg)
    File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual
  raise self.failureException(msg)
  AssertionError: 134 != 0
  ――
   27/113 mutter:cogl+cogl/conform / framebuffer-get-bits   
 FAIL 2.35s   exit status 1

  and

   27/113 mutter:cogl+cogl/conform / framebuffer-get-bits   
 RUNNING
  >>> MALLOC_PERTURB_=159 
PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py 
/<>/cogl/tests/run-tests.sh 
/<>/obj-aarch64-linux-gnu/cogl/tests/config.env 
cogl/tests/conform/test-conformance test_framebuffer_get_bits
  ― ✀  ―
  Starting D-Bus daemons (session & system)...
  Starting mocked services...
  Running test case...
     Test GL+GLSL  GL3   ES2
   test_framebuffer_get_bits: ok FAIL   n/a
  Traceback (most recent call last):
    File "/<>/src/tests/meta-dbus-runner.py", line 184, in 
  test_case.wrap_call(rest[1:])
    File "/<>/src/tests/meta-dbus-runner.py", line 171, in 
wrap_call
  self.assertEqual(p.wait(), 0)
    File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual
  assertion_func(first, second, msg=msg)
    File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual
  raise self.failureException(msg)
  AssertionError: 134 != 0
  ――
   27/113 mutter:cogl+cogl/conform / framebuffer-get-bits   
 FAIL 0.83s   exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2055519/+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 2036388] Re: Login screen grey background flickers

2024-03-01 Thread Bug Watch Updater
** Changed in: yaru
   Status: New => 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/2036388

Title:
  Login screen grey background flickers

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in yaru-theme package in Ubuntu:
  Fix Committed

Bug description:
  Login screen grey background flickers on startup and again on login.
  It looks like it's trying to fade between two very similar shades of
  grey and there just aren't enough colours between them to fade
  smoothly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2036388/+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 1872594] Re: Ubuntu logo shifts vertically when the login screen appears

2024-02-29 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/1872594

Title:
  Ubuntu logo shifts vertically when the login screen appears

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

Bug description:
  Ubuntu logo shifts upward about 1px when the purple login screen
  appears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1872594/+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 1962566] Re: gnome-shell crash after resume from suspend in gdm/util.js:154

2024-02-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/1962566

Title:
  gnome-shell crash after resume from suspend in gdm/util.js:154

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

Bug description:
  ### Affected version
  * Your OS and version: ubuntu 22.04 (dev series, before release)
  * Affected GNOME Shell version: 41.3-1ubuntu1
  * Issue appears in Wayland

  ### Bug summary

  Sometimes gnome-shell hangs when I open the laptop to login from the
  suspend state, preventing the rest of gdm to load. Because I am
  running wayland, I cannot open another tty either. If I close the
  laptop lid again and wait 30s or so and reopen to retry, it will work.

  ### Steps to reproduce
  Not 100% reproducible, happens sometimes.
  1. open laptop to login from suspend
  2. see login screen with time and all looks normal but is unresponsive

  ### What happened

  
  The login screen is hung and unresponsive to clicks/touches(touchscreen)/any 
keyboard input events.

  ### What did you expect to happen

  The login screen should be responsive to input.

  ### Relevant logs, screenshots, screencasts etc.

  After a successful login, I see a crash in journalctl:

  ```
  Mar 01 09:58:40 fenrir gnome-shell[2799]: JS ERROR: Gio.DBusError: Error 
calling StartServiceByName for net.reactivated.Fprint: Failed to activate 
service 'net.reactivated.>
    
_injectToMethod/klass[method]@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:273:25
    
_makeProxyWrapper/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:250:17
    
ShellUserVerifier@resource:///org/gnome/shell/gdm/util.js:154:31
    
_init@resource:///org/gnome/shell/gdm/authPrompt.js:72:30
    
_ensureAuthPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:691:28
    
_showPrompt@resource:///org/gnome/shell/ui/unlockDialog.js:730:14
    
vfunc_key_press_event@resource:///org/gnome/shell/ui/unlockDialog.js:630:14
  ```

  

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: fprintd 1.94.2-1
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashCounter: 1
  Date: Tue Mar  1 09:58:16 2022
  ExecutablePath: /usr/libexec/fprintd
  ExecutableTimestamp: 1645749862
  InstallationDate: Installed on 2020-06-29 (609 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcCmdline: /usr/libexec/fprintd
  ProcCwd: /
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  SegvAnalysis: Skipped: missing required field "Disassembly"
  Signal: 11
  SourcePackage: fprintd
  UpgradeStatus: Upgraded to jammy on 2022-01-04 (55 days ago)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1962566/+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 2036388] Re: Login screen grey background flickers

2024-02-29 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/2036388

Title:
  Login screen grey background flickers

Status in Yaru Theme:
  New
Status in gnome-shell package in Ubuntu:
  Fix Committed
Status in yaru-theme package in Ubuntu:
  In Progress

Bug description:
  Login screen grey background flickers on startup and again on login.
  It looks like it's trying to fade between two very similar shades of
  grey and there just aren't enough colours between them to fade
  smoothly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/2036388/+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 1825710] Re: Remove "Application is ready" notification

2024-02-28 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/1825710

Title:
  Remove "Application is ready" notification

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  The "Application is ready" notification is pointless, really. Say, I
  click on the open downloads folder button in Firefox and GNOME Shell
  gives me a notification saying "Application is ready" but doesn't open
  the notification. I'm totally expecting an app to open because I
  actively initiated it.

  As a workaround, I'm using a GNOME extensions "Focus my Window" which
  removes the "Application is ready" message and focuses the app window
  automatically. However, this cannot be treated as a solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1825710/+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] Re: LibreOffice has started displaying a donation nag

2024-02-28 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/1949291

Title:
  LibreOffice has started displaying a donation nag

Status in LibreOffice:
  Fix Released
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 2054667] Re: Displays in the settings app can't be overlapped

2024-02-28 Thread Bug Watch Updater
** Changed in: gnome-control-center
   Status: Unknown => New

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

Title:
  Displays in the settings app can't be overlapped

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

Bug description:
  I have three displays: the laptop internal display and two 24"
  external displays. In the Gnome settings app, the displays can be
  overlapped, but then the Apply button is greyed out so I can't press
  it.

  The error message is "Changes Cannot be Applied, This could be due to
  hardware limitations."

  I wasn't actually trying to overlap the displays originally, but just
  change the arrangement of the displays. I found the solution
  accidentally, i.e. I didn't overlap the displays, and then the Apply
  button worked.

  1) Ubuntu 22.04.4 LTS
  2) gnome-control-center: Installed: 1:41.7-0ubuntu0.22.04.8

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 22 10:29:16 2024
  InstallationDate: Installed on 2024-02-21 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/2054667/+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 2054924] Re: color emoji are broken with fontconfig 2.15

2024-02-27 Thread Bug Watch Updater
** Changed in: fontconfig (Debian)
   Status: New => Confirmed

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fonts-noto-color-emoji package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Confirmed

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2054769] Re: Boot animation and login screen use different display scales

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

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

Title:
  Boot animation and login screen use different display scales

Status in Plymouth:
  New
Status in mutter package in Ubuntu:
  Won't Fix
Status in plymouth package in Ubuntu:
  Fix Committed

Bug description:
  Boot animation and login screen use different display scales, on some
  (not many) machines.

  For example on a Microsoft Surface Laptop 4, Plymouth seems to use
  scale 2 for the boot screen while GNOME selects scale 1 for the login
  screen. This means the Ubuntu logo shrinks.

  I've tried a few laptops and so far it's only the Surface Laptop 4
  that has the problem: 13.5" 2256x1504, 201 PPI

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/2054769/+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 2054851] Re: [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()

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

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

Title:
  [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in
  radeon_bo_reference()

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Idont know

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: gnome-shell 45.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Feb 23 10:38:05 2024
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-10-01 (146 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=es_CO.UTF-8
   LANGUAGE=es_CO:es
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45.3-1ubuntu1
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  Title: gnome-shell crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2054851/+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 2054924] Re: color emoji are broken with fontconfig 2.15

2024-02-25 Thread Bug Watch Updater
** Changed in: fontconfig (Debian)
   Status: Unknown => New

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  New

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2054924] Re: color emoji are broken with fontconfig 2.15

2024-02-25 Thread Bug Watch Updater
** Changed in: fontconfig
   Status: Unknown => Fix Released

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

Title:
  color emoji are broken with fontconfig 2.15

Status in Fontconfig:
  Fix Released
Status in fontconfig package in Ubuntu:
  Triaged
Status in fontconfig package in Debian:
  Unknown

Bug description:
  The Noto Color Emoji font is no longer used to show emoji. Many emoji
  no longer show and the few that do are not in color.

To manage notifications about this bug go to:
https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output

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

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

Title:
  Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only
  visible part of terminal output

Status in MATE Desktop:
  Unknown
Status in Gnome Virtual Terminal Emulator:
  Fix Released
Status in mate-terminal package in Ubuntu:
  Invalid
Status in vte2.91 package in Ubuntu:
  Triaged
Status in vte2.91 package in Debian:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu MATE 21.04 installed (or use Live session)
  2. Launch MATE Terminal
  3. Enable infinite history (Edit - Profile Preferences - Scrolling, 
Scrollback - Unlimited)
  4. Execute command with long output such as `journalctl | cat`
  5. Select Edit - Select All (or press ++), then Edit - Copy 
(or press ++)
  6. Open Pluma text editor and paste just copied terminal output

  Expected results:
  * whole terminal output is copied - staring by `user@host:~$ journalctl | 
cat` and ending by `user@host:~$`

  Actual results:
  * only last 15 lines were copied (depends on terminal size)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: mate-terminal 1.24.1-1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.461
  Date: Thu Apr  1 17:35:47 2021
  LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  SourcePackage: mate-terminal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1922276/+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 2023322] Re: GTK internal browser does not render with Nvidia drivers

2024-02-23 Thread Bug Watch Updater
** Bug watch added: bugs.webkit.org/ #210100
   https://bugs.webkit.org/show_bug.cgi?id=210100

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an 
override-redirect window 

[Desktop-packages] [Bug 2054761] Re: gnome-shell crashed with signal 5: Settings schema 'org.gnome.mutter.wayland' does not contain a key named 'xwayland-allow-byte-swapped-clients'

2024-02-22 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => 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/2054761

Title:
  gnome-shell crashed with signal 5:  Settings schema
  'org.gnome.mutter.wayland' does not contain a key named 'xwayland-
  allow-byte-swapped-clients'

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

Bug description:
  Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema 
'org.gnome.mutter.wayland' does not contain a key named 
'xwayland-allow-byte-swapped-clients'
  Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 5
  Feb 21 21:39:12 autopkgtest gnome-shell[17959]: Settings schema 
'org.gnome.mutter.wayland' does not contain a key named 
'xwayland-allow-byte-swapped-clients'
  Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application 
'org.gnome.Shell.desktop' killed by signal 5

  https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2054761/+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 2054109] Re: nautilus fails to build on armhf

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

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

Title:
  nautilus fails to build on armhf

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Nautilus 46 fails to build on armhf because of a test failure.
  However, the test failure might be revealing a bug in nautilus's
  functions that would affect 32-bit architectures. I have filed the
  issue with the Nautilus developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2054109/+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 2023322] Re: GTK internal browser does not render with Nvidia drivers

2024-02-22 Thread Bug Watch Updater
** Changed in: webkit
   Status: Confirmed => Fix Released

** Bug watch added: bugs.webkit.org/ #261874
   https://bugs.webkit.org/show_bug.cgi?id=261874

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a029e2 for 

[Desktop-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

2024-02-21 Thread Bug Watch Updater
** Bug watch added: github.com/PJungkamp/yoga9-linux/issues #11
   https://github.com/PJungkamp/yoga9-linux/issues/11

-- 
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 2054510] Re: Incomplete screen redraws in virtual machines running Xorg

2024-02-20 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => 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/2054510

Title:
  Incomplete screen redraws in virtual machines running Xorg

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Jammy:
  Triaged
Status in mutter source package in Mantic:
  Triaged
Status in mutter source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  When using software rendering on Xorg (so usually just in VMs), some
  parts of app windows may fail to redraw.

  https://gitlab.gnome.org/GNOME/mutter/-/issues/2880

  [ Test Plan ]

  TODO: Figure out a minimal test plan that doesn't require modifying
  code.

  [ Where problems could occur ]

  The fix adds a new synchronization point between the compositor and X
  server. This should be inconsequential, although there is a "sync
  ring" in mutter used for this, and if a mistake occurs there then
  other parts of the desktop could appear to stop responding in Xorg
  sessions.

  [ Other Info ]

  This is a regression that started in 3.37.3 via 551101c65cda.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/2054510/+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 2034395] Re: Console is not accessible to the screen reader

2024-02-20 Thread Bug Watch Updater
** Changed in: gnome-console
   Status: New => Fix Released

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

Title:
  Console is not accessible to the screen reader

Status in GNOME Console:
  Fix Released
Status in gnome-console package in Ubuntu:
  Triaged
Status in gtk4 package in Ubuntu:
  Triaged

Bug description:
  Test Case
  =
  0. Install the gnome-console app
  1. Open the Settings app
  2. Switch to the Accessibility panel. Select Seeing and enable Screen Reader
  3. Open the Console app
  4. Type cd /
  5. Type ls

  The screen reader should read the list of files in /

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-console/+bug/2034395/+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 1872594] Re: Ubuntu logo shifts vertically when the login screen appears

2024-02-18 Thread Bug Watch Updater
** Changed in: yaru
   Status: Unknown => 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/1872594

Title:
  Ubuntu logo shifts vertically when the login screen appears

Status in Yaru Theme:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged
Status in plymouth package in Ubuntu:
  Triaged
Status in yaru-theme package in Ubuntu:
  Triaged

Bug description:
  Ubuntu logo shifts upward about 1px when the purple login screen
  appears.

To manage notifications about this bug go to:
https://bugs.launchpad.net/yaru/+bug/1872594/+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 2053110] Re: openjdk-8 402 fails to install in focal, jammy, mantic on i386

2024-02-18 Thread Bug Watch Updater
** Changed in: openjdk-8 (Debian)
   Status: Unknown => New

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

Title:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386

Status in java-atk-wrapper package in Ubuntu:
  New
Status in openjdk-8 package in Ubuntu:
  New
Status in openjdk-8 package in Debian:
  New

Bug description:
  openjdk-8 402 fails to install in focal, jammy, mantic on i386 due to
  dependency on java-atk-bridge.

  This dependency was introduced by dropping condition present in 392:
  --
    ifeq ($(derivative),Ubuntu)
  ifeq ($(DEB_HOST_ARCH),i386)
    ifeq (,$(filter $(distrel),precise trusty xenial bionic))
  with_bridge =
    endif
  endif
    endif
  --

  Note:
   java-atk-wrapper is present in noble on i386

  This is a regression introduced in 8u402-ga-2:

    * Restore M-A installability of focal/i386 package (LP#1916327)
  by adding xenial, bionic, focal, jammy to the list of releases
  built with the ATK bridge, but not enabling it by default;
  keep jessie on, stretch and sid and mantic/noble off the list:
  please report bugs for issues with the bridge, so sthibault
  can find, debug, fix them

  See LP: #1916327

  The alternative is to publish atk-wrapper for i386 in mantic, jammy
  and focal.

  Options:
   a) rollback the fix in Ubuntu
   b) publish atk-wrapper

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/2053110/+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 2054109] Re: nautilus fails to build on armhf

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

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

Title:
  nautilus fails to build on armhf

Status in Nautilus:
  New
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  Nautilus 46 fails to build on armhf because of a test failure.
  However, the test failure might be revealing a bug in nautilus's
  functions that would affect 32-bit architectures. I have filed the
  issue with the Nautilus developers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2054109/+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 2052794] Re: 2.79.1 test issue on s390x

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

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

Title:
  2.79.1 test issue on s390x

Status in GLib:
  Fix Released
Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  One of the newly added tests in the 2.79 serie is failing on s390x.
  The issue is being discussed upstream on
  https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new
  and is currently buggy. Upstream/Debian/Ubuntu already disabled
  similar tests in 2.79.1 but that one as not noticed to fail because
  it's skipped during build so is only showing now in the installed-
  tests result and in autopkgtest. (And the package is in
  Debian/experimental where it didn't get tested by the Debian CI)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2052794/+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 1568772] Re: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with exit code 99.

2024-02-11 Thread Bug Watch Updater
** Changed in: alsa-driver (Debian)
   Status: Unknown => New

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

Title:
  Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' failed with
  exit code 99.

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Debian:
  New

Bug description:
  Get that error logged into journalctl, on a fresh xenial 64 bits
  installed from mini.iso and sharing a /home partition with a wily
  installation. No third party package, only genuine default install.

  Note that sound has no trouble; only this logged.
  There is no sound card on this system, only a mobo chipset.

   systemd-udevd[412]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 0' 
failed with exit code 99.
  systemd-udevd[407]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' 
failed with exit code 99.

  Maybe its related to the 'i' aka '--no-init-fallback' found here:
  http://manpages.ubuntu.com/manpages/wily/man1/alsactl.1.html

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem1755 F pulseaudio
   /dev/snd/pcmC0D0p:   oem1755 F...m pulseaudio
   /dev/snd/controlC0:  oem1755 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Apr 11 13:50:55 2016
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772/+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 1903632] Re: Touchscreen can't be used to scroll anymore. Instead it will select everything on its way.

2024-02-09 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Importance: Wishlist => Medium

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

Title:
  Touchscreen can't be used to scroll anymore. Instead it will select
  everything on its way.

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

Bug description:
  Ever since I upgrade to 20.10 from 20.04, I have been experiencing this issue.
  There are times when a user might want to scroll their screen by touching 
their screen. But I can't do this anymore.

  I want to know what went wrong? What can I do?

  Any info is appreciated.

  Note:
  Currently, I can scroll without in issue in Nautilus. But I can't do the same 
in Firefox, Tor browser, Libre Office, etc. Except Nautilus, all apps select 
words on screen whenever I touch my screen to scroll. 

  But we all know, SCROLL ≠ SELECT.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 10 09:25:39 2020
  DistUpgraded: 2020-10-28 23:47:17,717 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: groovy
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 6.1.14, 5.8.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Dell HD Graphics 5500 [1028:0641]
  InstallationDate: Installed on 2020-02-16 (267 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Inspiron 5548
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i45x0v@/vmlinuz-5.8.0-26-generic 
root=ZFS=rpool/ROOT/ubuntu_i45x0v ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to groovy on 2020-10-28 (12 days ago)
  dmi.bios.date: 05/28/2019
  dmi.bios.release: 5.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0FFJC4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A10
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd05/28/2019:br5.4:svnDellInc.:pnInspiron5548:pvrA10:rvnDellInc.:rn0FFJC4:rvrA00:cvnDellInc.:ct8:cvrA10:
  dmi.product.name: Inspiron 5548
  dmi.product.sku: 0641
  dmi.product.version: A10
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1903632/+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 222635] Re: firefox ftp client don't understand links in cyrillic letters

2024-02-09 Thread Bug Watch Updater
** Changed in: firefox
   Importance: Wishlist => Medium

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

Title:
  firefox ftp client don't understand links in cyrillic letters

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: firefox-3.0

  Ubuntu 8.04
   3.0~b5+nobinonly-0ubuntu2

  When ftp session is open and I want to follow a link that contains
  cyrillic letters in, Firefox getting an error

  ProblemType: Bug
  Architecture: i386
  Date: Sat Apr 26 19:59:05 2008
  DistroRelease: Ubuntu 8.04
  NonfreeKernelModules: nvidia
  Package: firefox-3.0 3.0~b5+nobinonly-0ubuntu2
  PackageArchitecture: i386
  ProcEnviron:
   PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: firefox-3.0
  Uname: Linux 2.6.24-16-generic i686

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/222635/+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 1811596] Re: Ubuntu Single Sign-On GUI not showing login button

2024-02-09 Thread Bug Watch Updater
** Changed in: gnome-online-accounts
   Status: New => Fix Released

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

Title:
  Ubuntu  Single Sign-On GUI not showing  login button

Status in gnome-online-accounts:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  System Settings->Online Accounts->Ubuntu Single Sign-On

  I can enter my email address and password abd select "I have an Ubuntu
  Single Sign-On account". But there is no "Save" or "Login" or any
  other button. I can only close the window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1811596/+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 1867130] Re: spinner theme doesn't support fsckd progress messages

2024-02-09 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/1867130

Title:
  spinner theme doesn't support fsckd progress messages

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

Bug description:
  In ubuntu, systemd-fsckd & casper send fsckd: special status messages
  with progress of integrity checks of disks.

  It then prints something like Checking disk 1 of 3 (70%), in a
  separate message, such that one can still see keycodes message (ie.
  "press S to skip") or any other messages, i.e. "Please unlock drive
  nvme0n1p3".

  This is a regression from ubuntu-logo theme.

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1867130/+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 2052794] Re: 2.79.1 test issue on s390x

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

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

Title:
  2.79.1 test issue on s390x

Status in GLib:
  New
Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  One of the newly added tests in the 2.79 serie is failing on s390x.
  The issue is being discussed upstream on
  https://gitlab.gnome.org/GNOME/glib/-/issues/3252 , the test is new
  and is currently buggy. Upstream/Debian/Ubuntu already disabled
  similar tests in 2.79.1 but that one as not noticed to fail because
  it's skipped during build so is only showing now in the installed-
  tests result and in autopkgtest. (And the package is in
  Debian/experimental where it didn't get tested by the Debian CI)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/2052794/+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 2051478] Re: Typing passphrase pretty quickly using Yubikey fails to unlock a LUKS partition

2024-02-07 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/2051478

Title:
  Typing passphrase pretty quickly using Yubikey fails to unlock a LUKS
  partition

Status in Plymouth:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  New

Bug description:
  It looks like there are some behavioral changes between 22.02.122 and
  23.360.11. I didn't have any issue until recently but after upgrading
  to 23.360.11 on Ubuntu, the same unlocking method of LUKS partition
  stopped working.

  How to reproduce:
  1. format Yubikey with a static password
  ```
  $ ykman otp static --generate 2
  ```
  (it will emit 38 characters and the ENTER event within a moment when a button 
is long pressed)

  2. add the new key to LUKS
  ```
  $ sudo cryptsetup luksAddKey /dev/nvme0n1p3
  ```

  3. reboot and use the Yubikey to input the passphrase

  Actual:
  it fails to unlock

  When typing the same passphrase by-hand it works. Furthermore, when
  not using Plymouth, both by-hand typing and Yubikey work.

  WORKAROUND:
  1. boot into the recovery mode
  2. unlock the volume in the console
  3. remove "splash" from /etc/default/grub and run `update-grub`
  3. reboot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: cryptsetup 2:2.6.1-6ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 29 15:41:03 2024
  InstallationDate: Installed on 2024-01-08 (21 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240104)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: cryptsetup
  UpgradeStatus: No upgrade log present (probably fresh install)
  cmdline: BOOT_IMAGE=/vmlinuz-6.6.0-14-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash
  crypttab: dm_crypt-0 UUID=cfd8c295-9988-4934-a91a-460a9d16d80f none luks

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/2051478/+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 2025169] Re: pasdsp LIB dir incorrect

2024-02-05 Thread Bug Watch Updater
** Changed in: pulseaudio (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  pasdsp LIB dir incorrect

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

Bug description:
  /usr/bin/padsp script is generated with wrong
  LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so"

  It must be generated like
  LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so"

  A patch is anexed
  thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025169/+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 1988754] Re: libreoffice writer crashes when edit the page break

2024-02-04 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: In Progress => Fix Released

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

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

Title:
  libreoffice writer crashes when edit the page break

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

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 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 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 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 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


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

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

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

-- 
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:
  Confirmed
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] Re: NO-GUI headless convert-to function error in 7.6.1.2 60(Build:2)

2024-01-30 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 2022941] Re: Zoom window not centered on text cursor

2024-01-29 Thread Bug Watch Updater
** Changed in: gnome-control-center
   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/2022941

Title:
  Zoom window not centered on text cursor

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

Bug description:
  In certain applications, the zoomed in window moves to center on the
  text cursor instead of the pointer when typing but it does not focuses
  properly. This causes the typed text to be completely out of view. I
  use the default full-screen zoom in Ubuntu under the accessibility
  settings with the following settings:

  Magnification: 4.00 - 6.00
  Magnifier position: Follow mouse cursor

  The problem primarily occurs when using Alt+Tab to witch tabs, but it 
sometimes appears when switching 
  normally. 

  To reproduce the problem, the following steps can be followed:
  - Activate the zoom function.
  - Start up Files and rename a file.
  - The zoomed in window will move to the upper left corner.

  Other applications in which the problem sometimes occurs (mostly when using 
Alt+Tab):
  Firefox, VSCode
  I also want to note that for other applications like Text Editor or Terminal, 
the cursor is always followed correctly.

  lsb_release -rd:
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/2022941/+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 2022941] Re: Zoom window not centered on text cursor

2024-01-29 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/2022941

Title:
  Zoom window not centered on text cursor

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  In certain applications, the zoomed in window moves to center on the
  text cursor instead of the pointer when typing but it does not focuses
  properly. This causes the typed text to be completely out of view. I
  use the default full-screen zoom in Ubuntu under the accessibility
  settings with the following settings:

  Magnification: 4.00 - 6.00
  Magnifier position: Follow mouse cursor

  The problem primarily occurs when using Alt+Tab to witch tabs, but it 
sometimes appears when switching 
  normally. 

  To reproduce the problem, the following steps can be followed:
  - Activate the zoom function.
  - Start up Files and rename a file.
  - The zoomed in window will move to the upper left corner.

  Other applications in which the problem sometimes occurs (mostly when using 
Alt+Tab):
  Firefox, VSCode
  I also want to note that for other applications like Text Editor or Terminal, 
the cursor is always followed correctly.

  lsb_release -rd:
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2022941/+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 186771] Re: use more GTK stock icons.

2024-01-28 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Won't Fix

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

Title:
  use more GTK stock icons.

Status in Mozilla Firefox:
  Won't Fix
Status in firefox package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: firefox-3.0

  I think Firefox would look better and more integrated with gnome if
  some of its icons were replaced with gnome defaults:

  -the search icon at the right of the search bar could be replaced with
  /usr/share/icons/gnome/16x16/actions/find.png

  -the RSS icon in the URL bar could be replaced with the one in
  Epiphany, which follows the Tango guidelines. It can be found in
  /usr/share/epiphany-browser/icons/hicolor/16x16/status

  -the lockpad icon when you visit a secure webpage could be replaced
  with /usr/share/icons/gnome/16x16/status/security-medium.png or
  security-high.png.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/186771/+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 2051188] Re: Firefox 122 update breaks webextensions permission

2024-01-28 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Fix Released

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

Title:
  Firefox 122 update breaks webextensions permission

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  We build webextensions for Firefox.

  Since the latest update to Firefox 122, the native webextension bridge
  stopped working.

  ```
  $ flatpak permission-show snap.firefox
  Table ObjectApp  
Permissions   Data
  desktop-used-apps application/vnd.debian.binary-package snap.firefox 
gnome-software-local-file,1,3 0x00
  webextensions net.downloadhelper.coapp  snap.firefox yes  
 0x00
  ```

  This used to work and be enough, but not anymore.

  In the logs I see:

  
  ```
  Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
  Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop 
firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/2051188/+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 1926799] Re: Cursor is not rendered in the correct location when at maximum desktop zoom

2024-01-27 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/1926799

Title:
  Cursor is not rendered in the correct location when at maximum desktop
  zoom

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Affected version
  LSB Version: 
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
 
  Gnome Version: 3.38.4 
  Occurs in: Xorg and Wayland

  Bug summary

  1. zoom focus shifts - lets assume a window in the center of the
  screen and i am at 3x zoom and i try to point my mouse at something
  and try to click that. 90% of the time zoom focus shifts away from the
  mouse location to mostly top left corner of the screen.

  2. mouse pointing away from the object - Similarly when i reach above
  some zoom limit sets say 4x and now lets say i am in a browser trying
  to click a link i point at the link cursor changes to hand and when i
  try to click i couldnt. So i try to zoom out and i fid that the
  pointer was not exactly placed on the link. To sum up when zoomed in
  it seems like i am pointing at a link while the cursor is actually
  placed away from the link

  3. Compressing text - after reaching certain high zoom level as said
  4x or 5x the content on the screen becomes a bit compressed on the
  sides texts and images and everything on screen becomes elongated

  Steps to reproduce

  1. Turn on zoom from settings -> Accessibility
  2. Zoom in above 3.x
  3. Try clicking on some object inside a window
  4. Choose Follow mouse cursor or on screen part droopdown choose full screen.
  5. My current settings are Screen part: Full Screen, Magnifier cursor pushes 
content arround. However these issues persist with all the other options under 
magnifier position. Such as Follow mouse cursor or magnifier cursor pushes 
content arround or any such option provided.
  Screenshot_from_2021-05-03_14-37-09

  What happened

  1. Zoom focus shifts away from the cursor mostly towards top left of the 
window or the desktop.
  2.While zoomed in cursor seems to be placed above a link or an object but is 
actually placed awway either to the left or right of the object. Original 
position of the cursor reveals when zoomed out.
  3.Content on screen seems to be compressed from the sides as text and other 
objects appear elongated.

  I have also posted the same issue on the GNOME Community: 
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4228
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 21.04
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: gnome-shell 3.38.4-1ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  Tags:  wayland-session hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1926799/+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 2012698] Re: Plymouth is stuck on a plain black screen

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

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

Title:
  Plymouth is stuck on a plain black screen

Status in Plymouth:
  New
Status in plymouth package in Ubuntu:
  Triaged

Bug description:
  Plymouth never displays anything -- the boot process is a plain black
  screen.

  Workaround:

  Tap Esc once to see text mode.
  Tap Esc a second time to get the Plymouth graphical screen.

  I only figured that out when I had been waiting too long for the disk
  decryption prompt.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: plymouth 22.02.122-3ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  Date: Fri Mar 24 13:50:04 2023
  DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth
  InstallationDate: Installed on 2023-03-24 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230317)
  MachineType: LENOVO 21CBCTO1WW
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-18-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2023
  dmi.bios.release: 1.36
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N3AET71W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76530 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.17
  dmi.modalias: 
dmi:bvnLENOVO:bvrN3AET71W(1.36):bd01/31/2023:br1.36:efr1.17:svnLENOVO:pn21CBCTO1WW:pvrThinkPadX1CarbonGen10:rvnLENOVO:rn21CBCTO1WW:rvrSDK0T76530WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CB_BU_Think_FM_ThinkPadX1CarbonGen10:
  dmi.product.family: ThinkPad X1 Carbon Gen 10
  dmi.product.name: 21CBCTO1WW
  dmi.product.sku: LENOVO_MT_21CB_BU_Think_FM_ThinkPad X1 Carbon Gen 10
  dmi.product.version: ThinkPad X1 Carbon Gen 10
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/2012698/+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 1925683] Re: Cursor Tracking with Gnome Shell Magnifier on Wayland

2024-01-26 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/1925683

Title:
  Cursor Tracking with Gnome Shell Magnifier on Wayland

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix

Bug description:
  Affected version
  GNOME 3.36 - 3.40.
  Ubuntu 20.04, 20.10, 21.04 and Fedora 34 Beta.
  Wayland only.
  Bug summary
  When running GNOME shell with Wayland, the cursor and focus tracking 
functionality of the magnifier (a11y feature) do not correctly compute the 
cursor/focus location. The position is calculated from the top left of the 
window but the windows position is not included. This causes the magnifier to 
track the wrong location when the window is not maximiser or is on a second 
monitor.

  I suspect this is related to the way in which wayland is designed. But
  my experience in this area is minimal. When using X11 this feature
  works correctly.

  The wiki page states that under wayland the cursor and focus tracking
  work but this information is either out dated or was not tested
  correctly.

  Steps to reproduce
  From the Gnome desktop, open a terminal by pressing ctrl + alt + t or by 
opening the activities overlay and searching for "terminal".
  Press super + left arrow key to maximize the terminal window on the left side 
of the screen.
  Activity the magnifier by pressing super + alt + 8.
  Type text into the terminal window. The magnified view will move with the 
text cursor.
  Press super + right arrow key to maximize the terminal windows on the right 
side of the screen.
  Type text into the terminal. The magnified view will move but it will not 
show the text cursor. It will move when text is entered but will focus on the 
left side of the screen.
  What happened
  The magnified view does not follow the text/focus cursor correctly.

  What did you expect to happen
  The magnified view should follow the cursor and show the cursor as it does 
when the widnows is maximized. The correct behaviour can also be seen in Gnome 
shell running with X11.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu2
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 22 20:55:25 2021
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' redacted by apport
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'gb')]"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2021-04-22 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1)
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1925683/+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 1793124] Re: [upstream] Scrolling on Calc leaves content invisible if cell is higher than screen

2024-01-26 Thread Bug Watch Updater
** Bug watch added: bz.apache.org/ooo/ #7722
   https://bz.apache.org/ooo/show_bug.cgi?id=7722

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

Title:
  [upstream] Scrolling on Calc leaves content invisible if cell is
  higher than screen

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

Bug description:
  I sometimes receive Calc documents where the content of an individual
  cell is split on so many lines that it fills up the whole screen and
  more. I can easily see the top part of these cells but scrolling to
  the bottom does not seem to work. Whether I try dragging the scrollbar
  or moving the screen with my laptop’s touchpad, Calc seems to skip the
  bottom part of the cell and jump directly to the following cell. See
  the attached screenshots of a document which has numbers 1 to 50 so
  that numbers 4 to 40 occupy one single cell (A4). In the first
  screenshot I see the top part of that cell (4 to 23) and in the next I
  have scrolled down the screen as little as possible, and now I see
  cell A5 (number 41) on the top. Everything in between is visually
  inaccessible whatever I try.

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

Installed: 1:6.0.3-0ubuntu1
Candidate: 1:6.0.3-0ubuntu1
Version table:
   *** 1:6.0.3-0ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-calc 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:16:17 2018
  InstallationDate: Installed on 2017-02-13 (582 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: libreoffice
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (109 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1793124/+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 2051188] Re: Firefox 122 update breaks webextensions permission

2024-01-26 Thread Bug Watch Updater
Launchpad has imported 13 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1876447.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-01-25T05:06:07+00:00 Me+bz wrote:

Steps to reproduce:

- Update to Firefox 122 on Ubuntu
- Install Video DownloadHelper and its Companion App.
- In the settings of the addon, see that the Companion App is not recognized

The command:

```
$ flatpak permission-show snap.firefox
``

Shows that Firefox is allowed to read the manifest.

But it doesn't. The logs say:

```
Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: 
OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: 
No such method “GetManifest”
Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: 
[Parent 154219, Main Thread] WARNING: OnGetManifestDone error: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method 
“GetManifest”: 'glib warning', file 
/build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
```

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/1


On 2024-01-25T05:07:58+00:00 Me+bz wrote:

launchpad bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/2051188

@Sylvestre Can you see if you find anyone who could assist?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/2


On 2024-01-25T05:15:14+00:00 Me+bz wrote:

I'm working on the Video DownloadHelper extension (100_000+ Linux users,
mostly Ubuntu), and the Snap sandbox has always been a problem, but that
specific update made it worse. We're getting those bug reports since the
yesterday.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/3


On 2024-01-25T05:41:16+00:00 Release-mgmt-account-bot wrote:

:me+bz, if you think that's a regression, could you try to find a
regression range using for example
[mozregression](https://wiki.mozilla.org/Auto-
tools/Projects/Mozregression)?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/4


On 2024-01-25T05:41:56+00:00 Release-mgmt-account-bot wrote:

The [Bugbug](https://github.com/mozilla/bugbug/) bot thinks this bug
should belong to the 'Core::Widget: Gtk' component, and is moving the
bug to that component. Please correct in case you think the bot is
wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/5


On 2024-01-25T05:44:28+00:00 Me+bz wrote:

(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #3)
> :me+bz, if you think that's a regression, could you try to find a regression 
> range using for example 
> [mozregression](https://wiki.mozilla.org/Auto-tools/Projects/Mozregression)?

That's a little tricky because it's a snap-sandbox specific issue, and
mozregression doesn't work with Snap:
https://bugzilla.mozilla.org/show_bug.cgi?id=1763188

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/6


On 2024-01-25T06:00:02+00:00 Me+bz wrote:

Created attachment 9376384
Screenshot 1 of the exception

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/8


On 2024-01-25T06:00:56+00:00 Me+bz wrote:

I've attached the exception from the js console.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/9


On 2024-01-25T06:10:18+00:00 Me+bz wrote:

More investigation: the code that's throwing comes from a patch by
Canonical: https://github.com/canonical/firefox-
snap/blob/stable/patches/native-messaging-portal.patch

Reply at:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051188/comments/11


On 2024-01-25T06:19:58+00:00 Me+bz wrote:

This is the code that's breaking the extension:
https://github.com/canonical/firefox-
snap/blob/7f87c2af624891313906abe7fdccfda1ad76a0f7/patches/native-
messaging-portal.patch#L748

Commit: https://github.com/canonical/firefox-
snap/commit/f1bf0d6dd649e13a1a9a159de63ae74068966c0c

If you guys have a quick access to Canonical, help would be appreciated.

Reply at:

[Desktop-packages] [Bug 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

2024-01-25 Thread Bug Watch Updater
** Bug watch added: 
github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues #2
   https://github.com/milkovsky/Linux-on-Lenovo-Slim-7-Carbon-AMD/issues/2

-- 
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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)

2024-01-25 Thread Bug Watch Updater
** Changed in: gnome-shell-extension-tiling-assistant
   Status: Unknown => New

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

Title:
  GNOME Wayland session crashes with
  
libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor:
  assertion failed: (logical_monitor)

Status in Gnome Shell Extension Tiling Assistant:
  New
Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I am observing multiple issues with external monitor in a hybrid
  system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session:

  - Disconnecting HDMI cable crashes the desktop to login screen

  The HDMI port is connected to NVIDIA. I use the latest updates and
  drivers of 22.04 LTS.

  I am not sure how to auto-report this with ubuntu-bug. The system is
  similar to this report:
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)

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

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

Title:
  GNOME Wayland session crashes with
  
libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor:
  assertion failed: (logical_monitor)

Status in Gnome Shell Extension Tiling Assistant:
  Unknown
Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  I am observing multiple issues with external monitor in a hybrid
  system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session:

  - Disconnecting HDMI cable crashes the desktop to login screen

  The HDMI port is connected to NVIDIA. I use the latest updates and
  drivers of 22.04 LTS.

  I am not sure how to auto-report this with ubuntu-bug. The system is
  similar to this report:
  https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2049237] Re: libwacom-dev: Needs Depends: libevdev-dev

2024-01-22 Thread Bug Watch Updater
** Changed in: libwacom (Debian)
   Status: New => Fix Released

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

Title:
  libwacom-dev: Needs Depends: libevdev-dev

Status in libwacom package in Ubuntu:
  Triaged
Status in libwacom package in Debian:
  Fix Released

Bug description:
  I'm filing this on the Ubuntu side to prevent migration out of
  proposed since the autopkgtest regression isn't being correctly
  detected. See LP: #2035101

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/2049237/+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 2045737] Re: Logitech MX Master 3 is detected as a keyboard in Power Statistics

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

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

Title:
  Logitech MX Master 3 is detected as a keyboard in Power Statistics

Status in Upower:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  My Logitech MX Master 3 is detected as a keyboard in Power Statistics,
  it's not a critical issue as beyond this everything works fine.

  I'm using the Logitech Unifying Receiver to connect my MX Keys
  Keyboard and MX Master 3 Mouse, those are working fine but sometimes I
  get the notification of low battery, but I'm not so sure what is the
  device as it says Keyboard and the mouse is identified by Power
  Statistics as a Keyboard.

  This is the info from Power Statistics window:

  Device: battery_hidpp_battery_o
  Type: Leyboard
  Model: Wireless Mouse MX Master 3
  Serial number: bc-83-96-ed
  Supply: No
  Refreshed: 0 seconds
  Present: Yes
  Rechargable: Yes
  State: Discharging
  Percentage: 50.0%

  
  This is the info related to the Dongle from lsusb:

  ```
  Bus 003 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
  ```

  lshw information:

  ```
*-input:12
 product: Logitech MX Keys
 physical id: e
 logical name: input33
 logical name: /dev/input/event6
 logical name: input33::capslock
 logical name: input33::compose
 logical name: input33::kana
 logical name: input33::numlock
 logical name: input33::scrolllock
 logical name: /dev/input/mouse2
 capabilities: usb
*-input:13
 product: Logitech MX Master 3
 physical id: f
 logical name: input34
 logical name: /dev/input/event7
 logical name: input34::capslock
 logical name: input34::compose
 logical name: input34::kana
 logical name: input34::numlock
 logical name: input34::scrolllock
 logical name: /dev/input/mouse3
 capabilities: usb
  ```

  From the information above, this could be related to another package
  (even the kernel?) and not specifically gnome-power-manager

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-power-manager 43.0-1
  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: Wed Dec  6 08:33:41 2023
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2023-05-04 (215 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/2045737/+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 2050033] Re: gettext: msgfmt --java2 does not support Java 21

2024-01-21 Thread Bug Watch Updater
** Changed in: gettext (Debian)
   Status: Unknown => New

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  New
Status in gettext package in Debian:
  New

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 1988754] Re: libreoffice writer crashes when edit the page break

2024-01-19 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed => In Progress

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

Title:
  libreoffice writer crashes when edit the page break

Status in LibreOffice:
  In Progress
Status in libreoffice package in Ubuntu:
  New

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 2048931] Re: [noble] extension pref dialog turns hidden

2024-01-19 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => Fix Released

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

Title:
  [noble] extension pref dialog turns hidden

Status in gjs:
  Fix Released
Status in GNOME Shell:
  Fix Released
Status in gjs package in Ubuntu:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I get this after:
  1) open Extensions app
  2) open a pref
  3) prefs window after a quarter of second gets hidden
  4) no way to access this window

  JS ERROR: Gio.IOErrorEnum: GDBus.Error:org.gnome.gjs.JSError.Error: Already 
showing a prefs dialog
  asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  
_init/GLib.MainLoop.prototype.runAsync/https://bugs.launchpad.net/gjs/+bug/2048931/+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 2049434] Re: Nautilus crashes when trying to open file options in administrator mode

2024-01-19 Thread Bug Watch Updater
** Changed in: nautilus
   Status: Unknown => Fix Released

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

Title:
  Nautilus crashes when trying to open file options in administrator
  mode

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu 23.10
  nautilus 1:45~rc-1ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: nautilus 1:45~rc-1ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 16 00:46:25 2024
  InstallationDate: Installed on 2024-01-11 (4 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.49.92-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/2049434/+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 2048931] Re: [noble] extension pref dialog turns hidden

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

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

Title:
  [noble] extension pref dialog turns hidden

Status in gjs:
  Fix Released
Status in GNOME Shell:
  New
Status in gjs package in Ubuntu:
  Triaged
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Hi,

  I get this after:
  1) open Extensions app
  2) open a pref
  3) prefs window after a quarter of second gets hidden
  4) no way to access this window

  JS ERROR: Gio.IOErrorEnum: GDBus.Error:org.gnome.gjs.JSError.Error: Already 
showing a prefs dialog
  asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23
  
_init/GLib.MainLoop.prototype.runAsync/https://bugs.launchpad.net/gjs/+bug/2048931/+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 1988754] Re: libreoffice writer crashes when edit the page break

2024-01-18 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Importance: Medium => High

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

Title:
  libreoffice writer crashes when edit the page break

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

Bug description:
  LibreOffice Writes crashes when editing the page break. It happens in Xubuntu 
22.04.1 and also in LinuxMint 21.
  I have tried also using LibreOffice from ppa and it still crashes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1988754/+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 2029010] Re: dummy sound on huawei mate d15 laptop

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

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

Title:
  dummy sound on huawei mate d15 laptop

Status in Linux:
  New
Status in alsa-driver package in Ubuntu:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  I tried different options, but I couldn't raise the sound.
  saber716rus@saber716rus-BOM-WXX9 ~> cat /etc/os-release
  NAME="Green Linux"
  VERSION="21.2 (Victoria)"
  ID=linuxmint
  ID_LIKE="ubuntu debian"
  PRETTY_NAME="Green Linux 21.2.0 Pro (Cubic 2023-06-14 22:01)"
  VERSION_ID="21"
  HOME_URL="https://greenlinux.ru/;
  SUPPORT_URL="https://forum.linuxmint.su/;
  
BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/;
  PRIVACY_POLICY_URL="https://greenlinux.ru/;
  VERSION_CODENAME=victoria
  UBUNTU_CODENAME=jammy
  saber716rus@saber716rus-BOM-WXX9 ~ [1]> cat /proc/asound/cards 
   0 [Generic]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xd03c irq 80
   1 [acp]: acp - acp
HUAWEI-BOM_WXX9-M1010-BOM_WXX9_PCB_B2
  saber716rus@saber716rus-BOM-WXX9 ~>

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2029010/+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 1971168] Re: [snap] Files on local network shares are not opened / written

2024-01-18 Thread Bug Watch Updater
** Changed in: firefox
   Status: Confirmed => Fix Released

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

Title:
  [snap] Files on local network shares are not opened / written

Status in Mozilla Firefox:
  Fix Released
Status in firefox package in Ubuntu:
  Triaged
Status in xdg-desktop-portal package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gnome source package in Jammy:
  Triaged
Status in xdg-desktop-portal-gnome source package in Lunar:
  Triaged

Bug description:
  [ Impact ]

  When the user is running a containerized application (like the snapped
  Firefox or Chromium), and tries to save a document, the xdg-desktop-
  portal-gnome backend does show remote drives (like SMB or SFTP ones),
  and allows to choose them, but then the save operation fails.

  The previous backend, xdg-desktop-portal-gtk, did work fine in these
  cases, because it returned the local path that corresponded to the
  local file exported by Gvfs using FUSE, so this behaviour is not only
  a serious bug, but also a regression.

  [ Test plan]
  Steps to reproduce:

  1. Run Firefox as a Snap package in Ubuntu 22.04
  2. Have a SMB file server available where the network shares can be mounted 
just by clicking on the share in Nautilus file manager (smb:// protocol, 
usually mounted dynamically via `/var/run/user/.../gvfs/...`)
  3. Have one such share mounted and writable
  4. Open any website containing images in Firefox
  5. Right-click on an image and select "Save Image As..."
  6. In the file save dialog, navigate to the mounted share
  7. Assert content of network share is visible and browsable from within the 
save dialog
  8. Select "Save" at any folder in the network share

  Actual behavior:

  * File is not saved to selected network share location
  * No download entry is created
  * No error is shown

  Expected behavior:

  * File is saved to selected network share location
  * No error is shown

  [ Where problems could occur ]

  - If the remote drives aren't exported as local files by Gvfs using
  FUSE, the patch won't work and the behaviour will be the same than
  now.

  - Any hidden  bug in g_file_get_path() when managing remote drives
  could be triggered by this patch.

  [ Additional information ]

  * When saving to a folder on the local machine instead, saving works 
correctly as expected
  * In contrast to files, new folders that are created from within the save 
dialog are saved correctly on the network share
  * Similar situation when trying to open a file with Ctrl + O on a network 
share from Firefox / Chromium. After double-clicking e.g. an image file in the 
file dialog, the file dialog closes but nothing happens otherwise. Opening an 
image on a local folder works fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1971168/+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 1845732] Re: nautilus --check stuck after nautilus_self_check_directory

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

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

Title:
  nautilus --check stuck after nautilus_self_check_directory

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Triaged

Bug description:
  According to
nautilus --help
  there is an option
-c, --checkPerform a quick set of self-check tests.

  Running 'nautilus --check' on the 19.10 beta or on 18.04.3 prints:
running nautilus_self_check_file_utilities
running nautilus_self_check_file_operations
running nautilus_self_check_directory

  And then it just sits there. This is probably not intended.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
  Uname: Linux 5.3.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 23:33:12 2019
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-09-27 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  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/nautilus/+bug/1845732/+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 2042909] Re: keyboard backlight slider and automatic brightness causes gnome-shell to freeze (mostly on MacBooks)

2024-01-16 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/2042909

Title:
  keyboard backlight slider and automatic brightness causes gnome-shell
  to freeze (mostly on MacBooks)

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 23.10
  Gnome Shell 45.0
  I expect gdm and the shell to be responsive but they freeze forcing me to 
reboot. Sometimes I'm able to use them but it takes some time to load.

  After taking a look at the journal, I see lots of messages like this:
  #0   564c4df768c8 i   resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 
@ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to run a JS callback 
during garbage collection. This is most likely caused by destroying a Clutter 
actor or GTK widget with ::destroy signal connected, or using the destroy(), 
dispose(), or remove() vfuncs. Because it would crash the application, it has 
been blocked.
 The offending callback was 
AsyncReadyCallback().
 == Stack trace for context 
0x564c4deaab90 ==
 #0   564c4df768c8 i   
resource:///org/gnome/shell/ui/init.js:21 (1c387d470ba0 @ 48)
  nov 07 09:18:55 perseus gnome-shell[3600]: Attempting to call back into JSAPI 
during the sweeping phase of GC. This is most likely caused by not destroying a 
Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be 
caused by using the destroy(), dispose(), or remove() vfuncs. Because it would 
crash the application, it has been blocked and the JS callback not invoked.
 The offending signal was 
g-properties-changed on GDBusProxy 0x564c4fec8670.
 == Stack trace for context 
0x564c4deaab90 ==

  On successful boots this seems to auto resolve, being followed by this 
message:
  nov 07 09:21:56 perseus dbus-daemon[1758]: [session uid=1000 pid=1758] 
Successfully activated service 'org.freedesktop.impl.portal.desktop.gnome'
  nov 07 09:21:56 perseus systemd[1722]: Started 
xdg-desktop-portal-gnome.service - Portal service (GNOME implementation).

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/2042909/+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 2043915] Re: Booting into live session results in try/install page white screen

2024-01-16 Thread Bug Watch Updater
** Changed in: ubuntu-desktop-installer
   Importance: Undecided => Unknown

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 1779432] Re: [upstream] Libre Writer doesn't do duplex printing

2024-01-15 Thread Bug Watch Updater
** Changed in: df-libreoffice
   Status: Confirmed => Invalid

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

Title:
  [upstream] Libre Writer doesn't do duplex printing

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

Bug description:
  The Libre Writer print settings are set to two side printing, but
  program only prints single side. Is not HP Linux driver because both
  FireFox and Chrome print both sides.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libreoffice-core 1:6.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: ufsd
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Fri Jun 29 22:17:38 2018
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2018-06-15 (14 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  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/1779432/+subscriptions


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


  1   2   3   4   5   6   7   8   9   10   >