[Touch-packages] [Bug 2042763] Re: Keyboard navigation in the Show Applications menu

2023-11-05 Thread ChrisK5
** Description changed:

  Hello.
  
  My bug, if it is one, is in Wayland, or more likely in new desktop icon 
management thingy, which was introduced with one of the last Ubuntu versions.
- I can't navigate the "Show Applications" menu with the keyboard when I go 
into a subfolder. This means that I can navigate in "Show Applications" with 
the keyboard as long as I stay at the top level. But when I go to a folder that 
contains several programs, such as the "Utilities" folder, the keyboard 
navigation no longer works. The cursor will stuck no matter which arrow key I 
press. Even the Tab key is of no use. I've already searched for this problem on 
the Internet, but couldn't find it. Either I'm the only one who has this 
problem, or most others simply prefer to use the mouse to navigate. I only use 
the keyboard when possible. I am a heavy keyboard/hotkey user.
+ Maybe around ubuntu 22.04. I'm not sure if the problem came when Wayland was 
set as the window manager or if it came when the new "Desktop Icon Manager" 
thing came along. I think the two weren't too far apart in time. I'm only 
reporting my problem now because I always assumed it would be fixed in future 
updates. But my problem never changed with all the updates.
+ Here is my problem:
+ I can't navigate in the "Show Applications" menu with the keyboard when I go 
into a subfolder. This means that I can navigate in "Show Applications" with 
the keyboard as long as I stay at the top level. But when I go to a folder that 
contains several programs, such as the "Utilities" folder, the keyboard 
navigation no longer works. The cursor will stuck no matter which arrow key I 
press. Even the Tab key is of no use. I've already searched for this problem on 
the Internet, but couldn't find it. Either I'm the only one who has this 
problem, or most others simply prefer to use the mouse to navigate. I only use 
the keyboard when possible. I am a heavy keyboard/hotkey user.
  The problem has existed for me for a long time. It either came with the 
switch to Wayland or with the switch to the new desktop icon management thingy. 
It's just a small problem, but for a massive keyboard user, it's really 
annoying. And definitely also for people who can't use a mouse.
  
  Kind regards
  Chris
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 11:22:55 2023
  DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 
XT/6500M] [1002:743f] (rev c1) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M] 
[1043:05db]
  InstallationDate: Installed on 2021-09-16 (779 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: P35C-DS3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: P35C-DS3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042763

Title:
  Keyboard navigation in the Show Applications menu

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello.

  My bug, if it is one, is in 

[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

2023-11-05 Thread Gunnar Hjalmarsson
Ok.

This bug is focused on the UI for the upgrader itself. I would recommend
you to ask a question at Ask Ubuntu. That way you'll hopefully get help
to determine if it is a problem with your configuration or some kind of
bug.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


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


[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

2023-11-05 Thread BloodyIron
My upgrade for Ubuntu to 23.10 was a bunch of days ago. In that time I
have rebooted multiple times and no change observed for fonts (better or
worse). Still bad heh

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


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


[Touch-packages] [Bug 2042776] [NEW] [81VV, Realtek ALC257, Speaker, Internal] No sound at all

2023-11-05 Thread Joseph Vunanga
Public bug reported:

No sound whatsoever not even on external speakers. I suspected a
hardware problem at first and by the way drivers have been updated but
same issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joseph-vunanga   4569 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 20:04:21 2023
InstallationDate: Installed on 2023-03-30 (220 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [81VV, Realtek ALC257, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/15/2021
dmi.bios.release: 1.27
dmi.bios.vendor: LENOVO
dmi.bios.version: CUCN27WW(V1.16)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76446 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S340-14IIL
dmi.ec.firmware.release: 1.27
dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN27WW(V1.16):bd06/15/2021:br1.27:efr1.27:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0T76446WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL:skuLENOVO_MT_81VV_BU_idea_FM_IdeaPadS340-14IIL:
dmi.product.family: IdeaPad S340-14IIL
dmi.product.name: 81VV
dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL
dmi.product.version: Lenovo IdeaPad S340-14IIL
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2042776

Title:
  [81VV, Realtek ALC257, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound whatsoever not even on external speakers. I suspected a
  hardware problem at first and by the way drivers have been updated but
  same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joseph-vunanga   4569 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 20:04:21 2023
  InstallationDate: Installed on 2023-03-30 (220 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [81VV, Realtek ALC257, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN27WW(V1.16)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76446 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14IIL
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN27WW(V1.16):bd06/15/2021:br1.27:efr1.27:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0T76446WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL:skuLENOVO_MT_81VV_BU_idea_FM_IdeaPadS340-14IIL:
  dmi.product.family: IdeaPad S340-14IIL
  dmi.product.name: 81VV
  dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL
  dmi.product.version: Lenovo IdeaPad S340-14IIL
  dmi.sys.vendor: LENOVO

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


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

[Touch-packages] [Bug 1986444] Re: network-manager fails to detect usb internet adapter

2023-11-05 Thread Chucky
>From what I discovered, the USB device itself is not listed by lsusb
anymore although the driver ax88179_178a is available in
/lib/modules/...

Note : I've checked the device on another laptop where it works just fine with 
the very same cable. On that secondary laptopt, the device is listed by lsusb 
properly as follows :
  ASIX Electronics Corp. AX88179 Gigabit Ethernet

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

Title:
  network-manager fails to detect usb internet adapter

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to Ubuntu 22.04 from 20.04 several days ago, my ugreen 
network adapter is not detected even though the lights between the ethernet 
cable and the adapter are on.  I am using a 
  Dell G3 3500 that came with windows 10.  The adapter works ok on my Dell XPS 
and worked fine
  with Ubuntu 20.04 on the Dell G3.  Other devices are detected when plugged 
into the usb.  
  The wifi is working.  Any help with this would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 13 19:16:38 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-12-04 (617 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.4 metric 
600
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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


[Touch-packages] [Bug 1986444] Re: network-manager fails to detect usb internet adapter

2023-11-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  network-manager fails to detect usb internet adapter

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to Ubuntu 22.04 from 20.04 several days ago, my ugreen 
network adapter is not detected even though the lights between the ethernet 
cable and the adapter are on.  I am using a 
  Dell G3 3500 that came with windows 10.  The adapter works ok on my Dell XPS 
and worked fine
  with Ubuntu 20.04 on the Dell G3.  Other devices are detected when plugged 
into the usb.  
  The wifi is working.  Any help with this would be appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.6-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 13 19:16:38 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2020-12-04 (617 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  IpRoute:
   default via 192.168.0.1 dev wlp0s20f3 proto dhcp metric 600 
   169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.0.4 metric 
600
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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


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


[Touch-packages] [Bug 2042772] Re: Display corrupted/freeze

2023-11-05 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042772

Title:
  Display corrupted/freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  After latest updates login display is fine but after entering password
  display changes to black with random full width 1 pixel high white
  lines that move randomly vertically.  Must power off to recover.  Boot
  in recovery mode works OK.

  Send email if you need more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 07:09:04 2023
  DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
  InstallationDate: Installed on 2018-08-11 (1912 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Inspiron 5565
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
  dmi.bios.date: 10/18/2016
  dmi.bios.release: 5.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.5
  dmi.board.name: 0021CT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.0.5
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5565
  dmi.product.sku: 0769
  dmi.product.version: 1.0.5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2042772] [NEW] Display corrupted/freeze

2023-11-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After latest updates login display is fine but after entering password
display changes to black with random full width 1 pixel high white lines
that move randomly vertically.  Must power off to recover.  Boot in
recovery mode works OK.

Send email if you need more information.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 07:09:04 2023
DistUpgraded: 2022-12-21 11:25:42,433 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wani [Radeon R5/R6/R7 Graphics] 
[1002:9874] (rev c9) (prog-if 00 [VGA controller])
   Subsystem: Dell Wani [Radeon R5/R6/R7 Graphics] [1028:0769]
   Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 
530/535 / 620/625 Mobile] [1028:0769]
InstallationDate: Installed on 2018-08-11 (1912 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Inspiron 5565
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=54c49f2a-71f4-4c7f-b611-4f0af1922365 ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-12-21 (318 days ago)
dmi.bios.date: 10/18/2016
dmi.bios.release: 5.3
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.5
dmi.board.name: 0021CT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.0.5
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.5:bd10/18/2016:br5.3:svnDellInc.:pnInspiron5565:pvr1.0.5:rvnDellInc.:rn0021CT:rvrA00:cvnDellInc.:ct10:cvr1.0.5:sku0769:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5565
dmi.product.sku: 0769
dmi.product.version: 1.0.5
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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

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


** Tags: amd64 apport-bug freeze jammy ubuntu
-- 
Display corrupted/freeze
https://bugs.launchpad.net/bugs/2042772
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

2023-11-05 Thread Gunnar Hjalmarsson
@Bloodyiron: Does it help to reboot?

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


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


[Touch-packages] [Bug 2034986] Re: some text became unreadable during a distribution upgrade

2023-11-05 Thread BloodyIron
Not sure if I'm in the right thread, but after upgrading to Mantic
(23.10) a lot of fonts, namely in browsers, look like trash. There's
lots of overlapping and other font weirdness. I haven't really seen
boxes yet, but it was not present before doing do-release-upgrade.

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

Title:
  some text became unreadable during a distribution upgrade

Status in Cinnamon:
  New
Status in Ubuntu MATE:
  New
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Jammy:
  Fix Committed
Status in ubuntu-release-upgrader source package in Lunar:
  Fix Released
Status in ubuntu-meta source package in Mantic:
  Fix Released
Status in ubuntu-release-upgrader source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

   * On Ubuntu Mate with the Lunar series, when running
     ubuntu-release-upgrader, the displayed font of running
     applications (including the upgrader) becomes very corrupted.

   * This is not just a display problem, it is also a functional one.
     The release upgrader will have text corrupted to the point
     where a dialog asks a decision, and displays two buttons, but the
     text is unreadable and one has to guess which button is the one
     that carries out their desired action.

   * In the early parts of the upgrader tool, users are told in bold:
     "To prevent data loss close all open applications and documents."
     This is just before the "Start Upgrade" button is available.
     But they may not do so.  Many applications may have a corrupted
     font.

   * To address this, an additional environment variable is being
     passed along to pkexec, XDG_CURRENT_DESKTOP, as this is the
     critical criteria for making the Mate version of the fix work.

   * Also in the change are
     * an update to tests
 * from pre-build.sh
       * an update of the mirrors.cfg, adding and removing several
 mirrors
       * a refresh of the po files

  [ Test Plan ]

   * acquire an Ubuntu Mate environment running Ubuntu Lunar on amd64

   * as user, run "update-manager -d"

   * monitor the "Distribution Upgrade" screen.  During the "Installing
     the upgrades" step (and mind that this step will be long), observe
     the text of the "Distribution Upgrade" screen and verify that the
     font does not corrupt.

   * Repeat the above for Ubuntu Desktop

  [ Where problems could occur ]

   * We are changing, at release time, ubuntu-release upgrader.  If we
     are careless, we could regress upgrades for a wider group of users
     than just Ubuntu Mate.  That said, it is believed that passing the
     additional XDG_CURRENT_DESKTOP variable is relatively low risk.

  [ Other Info ]

   * TBD

  ---

  Original description:

  I was upgrading from Lunar to Mantic the other day and left a couple
  of applications open during the upgrade process. During the upgrade
  the text in audacious became unreadable (I'll attach a screenshot) and
  I seem to recall the title bar of Firefox being unreadable but the
  contents of web pages still being readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-release-upgrader-core 1:23.10.5
  ProcVersionSignature: Ubuntu 6.5.0-4.4-generic 6.5.0
  Uname: Linux 6.5.0-4-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  8 15:39:27 2023
  InstallationDate: Installed on 2018-08-10 (1855 days ago)
  InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to mantic on 2023-09-06 (2 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
126: Error executing command as another user: Request dismissed
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.meta-release:
  2021-05-27T16:30:16.970490

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinnamon-project/+bug/2034986/+subscriptions


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


[Touch-packages] [Bug 2015479] Re: gnome-shell crashed with SIGSEGV in verify_objects() from handle_array() from wl_resource_post_event_array()

2023-11-05 Thread Daniel van Vugt
** No longer affects: wayland (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2015479

Title:
  gnome-shell crashed with SIGSEGV in verify_objects() from
  handle_array() from wl_resource_post_event_array()

Status in gnome-shell package in Ubuntu:
  Confirmed

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

  ---

  after clicking the screenshot icon in the top panel right corner control 
centre, my google chrome window crashed and the screenshots were not taken.
  The system then automatically logged me out closing all my other windows.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  Uname: Linux 6.2.0-19-generic x86_64
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  6 19:35:53 2023
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1680272303
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ochego
  Signal: 11
  SourcePackage: gnome-shell
  UserGroups: adm cdrom dip lpadmin plugdev sudo users

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


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


[Touch-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

2023-11-05 Thread Daniel van Vugt
** Tags added: mantic

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2040450

Title:
  Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  When using keyboard layout Latvian (apostrophe), when writing accented 
  characters like "š", second character is outputed accented, too.

  When writing, for example, 'so, šō is outputted (should be šo)

  When testing keyboard during Ubuntu 23.10 installation and choosing 
  Latvian (apostrophe) layout, the behaviour was correct.

    affects ubuntu/mantic

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


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


[Touch-packages] [Bug 2041008] Re: wayland : no uppercase accented characters with capslock

2023-11-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 2035076 ***
https://bugs.launchpad.net/bugs/2035076

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

** This bug has been marked a duplicate of bug 2035076
   Wayland - Capital accented letters not recognized

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2041008

Title:
  wayland : no uppercase accented characters with capslock

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  Until Ubuntu 23.04, with the "french alternative" [français (variante)] 
keyboard, capslock gave you directly uppercase accented characters (like É È À) 
from the keys 2, 7 and 0 of the fifth row of the keyboard.
  With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it 
works like before if you connect with Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 13:36:26 2023
  DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:174b]
  InstallationDate: Installed on 2020-04-10 (1294 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (13 days ago)
  dmi.bios.date: 08/05/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: 970 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2040450] Re: Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

2023-11-05 Thread Sebastien Bacher
Could be similar to bug #2035076

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2040450

Title:
  Ubuntu 23.10 Latvian keyboard layout (apostrophe) broken

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  When using keyboard layout Latvian (apostrophe), when writing accented 
  characters like "š", second character is outputed accented, too.

  When writing, for example, 'so, šō is outputted (should be šo)

  When testing keyboard during Ubuntu 23.10 installation and choosing 
  Latvian (apostrophe) layout, the behaviour was correct.

    affects ubuntu/mantic

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


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


[Touch-packages] [Bug 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect

2023-11-05 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2040657

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  New

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

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


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


[Touch-packages] [Bug 2042767] [NEW] Crackling sound at random intervals while Virtualbox is running

2023-11-05 Thread Rick van den Bergh
Public bug reported:

Recently I'm having an issue where the audio playback from my HDMI
output starts crackling at random intervals in Ubuntu 22.04. It is not
sure if Virtualbox is causing this issue, but it's a possible cause. I
dug up a forum post from 2 years ago on AskUbuntu where someone implies
Virtualbox causes their issue. Since Virtualbox runs in the background
all the time for me, I cannot be certain about this. I run my Home
Asisstant server inside Virtualbox.

If any audio playback starts crackling,  executing pulseaudio -k always
fixes it. Then the applications producing sound need to be restarted in
order to get any sound out of them. After that the crackling will take
hours to show up again.

In that AskUbuntu forum post that I referred to earlier, the user fixed
this by setting resample-method = speex-float-10 in
/etc/pulse/daemon.conf. So I did the same thing just before filling this
bug report to see if that would fix it. I do not have enough data yet to
draw any conclusions.

I can be sure that the crackling is from the HDMI sound output and not
from malfunctioning speakers, since no other devices connected to the
same speakers/TV have this issue.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  rick  90340 F pulseaudio
 /dev/snd/controlC0:  rick  90340 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 14:01:41 2023
InstallationDate: Installed on 2023-10-28 (8 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/13/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.H0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: MAG B550M MORTAR WIFI (MS-7C94)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.H0:bd10/13/2023:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C94:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMAGB550MMORTARWIFI(MS-7C94):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C94
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
modified.conffile..etc.pulse.daemon.conf: [modified]
mtime.conffile..etc.pulse.daemon.conf: 2023-11-05T11:50:19.891182

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2042767

Title:
  Crackling sound at random intervals while Virtualbox is running

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Recently I'm having an issue where the audio playback from my HDMI
  output starts crackling at random intervals in Ubuntu 22.04. It is not
  sure if Virtualbox is causing this issue, but it's a possible cause. I
  dug up a forum post from 2 years ago on AskUbuntu where someone
  implies Virtualbox causes their issue. Since Virtualbox runs in the
  background all the time for me, I cannot be certain about this. I run
  my Home Asisstant server inside Virtualbox.

  If any audio playback starts crackling,  executing pulseaudio -k
  always fixes it. Then the applications producing sound need to be
  restarted in order to get any sound out of them. After that the
  crackling will take hours to show up again.

  In that AskUbuntu forum post that I referred to earlier, the user
  fixed this by setting resample-method = speex-float-10 in
  /etc/pulse/daemon.conf. So I did the same thing just before filling
  this bug report to see if that would fix it. I do not have enough data
  yet to draw any conclusions.

  I can be sure that the crackling is from the HDMI sound output and not
  from malfunctioning speakers, since no other devices connected to the
  same speakers/TV have this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  rick  90340 F pulseaudio
   /dev/snd/controlC0:  rick 

[Touch-packages] [Bug 2041008] Re: wayland : no uppercase accented characters with capslock

2023-11-05 Thread J-Paul BERARD
Additional information:

This issue depends on the application used ! You get it with Gnome-text-
editor or LO Writer but not in Firefox Web browser (snap). Because the
good libraries are embedded with the snap ?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2041008

Title:
  wayland : no uppercase accented characters with capslock

Status in wayland package in Ubuntu:
  Confirmed

Bug description:
  Until Ubuntu 23.04, with the "french alternative" [français (variante)] 
keyboard, capslock gave you directly uppercase accented characters (like É È À) 
from the keys 2, 7 and 0 of the fifth row of the keyboard.
  With 23.10 Mantic, it has disappeared with Wayland (you get é, è, à) BUT it 
works like before if you connect with Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 13:36:26 2023
  DistUpgraded: 2023-10-13 14:46:58,342 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
   virtualbox/7.0.10, 6.5.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Barts PRO [Radeon HD 6850] 
[1002:6739] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Barts PRO [Radeon HD 
6850] [174b:174b]
  InstallationDate: Installed on 2020-04-10 (1294 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-9-generic 
root=UUID=042824eb-95be-471e-bdb4-d7adf594a94a ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (13 days ago)
  dmi.bios.date: 08/05/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.80
  dmi.board.name: 970 Extreme4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd08/05/2015:br4.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2042764] [NEW] ICC profile has no effect in Wayland session

2023-11-05 Thread Tim Summerer
Public bug reported:

The color profile set either via the Gnome Control Center or colord has
no effect in the Wayland session.

I tested it with Firefox and can see no difference no matter what color profile 
is set in GNOME.
I also changed the color profile in Firefox via the about:config and tried to 
set the color management flag to 1 (to always enable color management to no 
effect).

I then tested eog vs. shotwell.
In the Gnome Wayland session the images I compared looked identical but both 
not in the ICC profile I selected.
In the Gnome Xorg session there was a visible difference between eog which 
displayed the image with the selected ICC profile and shotwell which ignored 
the ICC profile.

This bug might very well be an upstream issue.
I am reporting it because (without diving very deep into the system) I do not 
see anything else to try to remedy this issue.

Ubuntu version: Ubuntu 23.10
colord version: 1.4.6-3 (Maybe this is not the correct package to file this 
against)

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: colord 1.4.6-3
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 13:09:08 2023
InstallationDate: Installed on 2023-11-03 (2 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: colord
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to colord in Ubuntu.
https://bugs.launchpad.net/bugs/2042764

Title:
  ICC profile has no effect in Wayland session

Status in colord package in Ubuntu:
  New

Bug description:
  The color profile set either via the Gnome Control Center or colord
  has no effect in the Wayland session.

  I tested it with Firefox and can see no difference no matter what color 
profile is set in GNOME.
  I also changed the color profile in Firefox via the about:config and tried to 
set the color management flag to 1 (to always enable color management to no 
effect).

  I then tested eog vs. shotwell.
  In the Gnome Wayland session the images I compared looked identical but both 
not in the ICC profile I selected.
  In the Gnome Xorg session there was a visible difference between eog which 
displayed the image with the selected ICC profile and shotwell which ignored 
the ICC profile.

  This bug might very well be an upstream issue.
  I am reporting it because (without diving very deep into the system) I do not 
see anything else to try to remedy this issue.

  Ubuntu version: Ubuntu 23.10
  colord version: 1.4.6-3 (Maybe this is not the correct package to file this 
against)

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: colord 1.4.6-3
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 13:09:08 2023
  InstallationDate: Installed on 2023-11-03 (2 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: colord
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 2042763] Re: Keyboard navigation in the Show Applications menu

2023-11-05 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042763

Title:
  Keyboard navigation in the Show Applications menu

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello.

  My bug, if it is one, is in Wayland, or more likely in new desktop icon 
management thingy, which was introduced with one of the last Ubuntu versions.
  I can't navigate the "Show Applications" menu with the keyboard when I go 
into a subfolder. This means that I can navigate in "Show Applications" with 
the keyboard as long as I stay at the top level. But when I go to a folder that 
contains several programs, such as the "Utilities" folder, the keyboard 
navigation no longer works. The cursor will stuck no matter which arrow key I 
press. Even the Tab key is of no use. I've already searched for this problem on 
the Internet, but couldn't find it. Either I'm the only one who has this 
problem, or most others simply prefer to use the mouse to navigate. I only use 
the keyboard when possible. I am a heavy keyboard/hotkey user.
  The problem has existed for me for a long time. It either came with the 
switch to Wayland or with the switch to the new desktop icon management thingy. 
It's just a small problem, but for a massive keyboard user, it's really 
annoying. And definitely also for people who can't use a mouse.

  Kind regards
  Chris

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 11:22:55 2023
  DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 
XT/6500M] [1002:743f] (rev c1) (prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M] 
[1043:05db]
  InstallationDate: Installed on 2021-09-16 (779 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
  dmi.bios.date: 06/18/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F12
  dmi.board.name: P35C-DS3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
  dmi.product.name: P35C-DS3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.115-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


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


[Touch-packages] [Bug 2042763] [NEW] Keyboard navigation in the Show Applications menu

2023-11-05 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hello.

My bug, if it is one, is in Wayland, or more likely in new desktop icon 
management thingy, which was introduced with one of the last Ubuntu versions.
I can't navigate the "Show Applications" menu with the keyboard when I go into 
a subfolder. This means that I can navigate in "Show Applications" with the 
keyboard as long as I stay at the top level. But when I go to a folder that 
contains several programs, such as the "Utilities" folder, the keyboard 
navigation no longer works. The cursor will stuck no matter which arrow key I 
press. Even the Tab key is of no use. I've already searched for this problem on 
the Internet, but couldn't find it. Either I'm the only one who has this 
problem, or most others simply prefer to use the mouse to navigate. I only use 
the keyboard when possible. I am a heavy keyboard/hotkey user.
The problem has existed for me for a long time. It either came with the switch 
to Wayland or with the switch to the new desktop icon management thingy. It's 
just a small problem, but for a massive keyboard user, it's really annoying. 
And definitely also for people who can't use a mouse.

Kind regards
Chris

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Nov  5 11:22:55 2023
DistUpgraded: 2023-11-03 22:29:03,001 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] 
[1002:743f] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Navi 24 [Radeon RX 6400/6500 XT/6500M] 
[1043:05db]
InstallationDate: Installed on 2021-09-16 (779 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=UUID=da9b8938-71c1-4591-9b97-e052ca3ea1b2 ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-11-03 (2 days ago)
dmi.bios.date: 06/18/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F12
dmi.board.name: P35C-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF12:bd06/18/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35C-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35C-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:sku:
dmi.product.name: P35C-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.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-3
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

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


** Tags: amd64 apport-bug mantic ubuntu wayland-session
-- 
Keyboard navigation in the Show Applications menu
https://bugs.launchpad.net/bugs/2042763
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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


[Touch-packages] [Bug 412195] Re: ttf-tahoma-replacement makes some web-sites look ugly

2023-11-05 Thread Jaromir Obr
Just hit a similar issue with "fonts-wine 8.0.1~repack-3ubuntu2" in
Ubuntu 23.10.

Text on the web page https://www.virtualdub.org/altirra.html is rendered
by the font Tahoma and it looks ugly, see
https://i.imgur.com/KXC5DYq.png

I uninstalled the package "fonts-wine". Now the font Verdana is used on
that page and it looks well, see https://i.imgur.com/P7xO53r.png

I tested it in Chrome and Firefox, with the same result.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/412195

Title:
  ttf-tahoma-replacement makes some web-sites look ugly

Status in fontconfig package in Ubuntu:
  Invalid
Status in wine1.2 package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: wine1.2

  This font package is good for wine 1.2; however, it also makes sites
  look ugly in Firefox and other browsers. I had to manually remove the
  fonts from /usr/share/fonts/ to rectfiy this, because removing the
  package through apt would have made me remove wine 1.2 and I didn't
  want that.

  ProblemType: Bug
  Architecture: i386
  Date: Wed Aug 12 00:23:40 2009
  DistroRelease: Ubuntu 9.10
  Package: ttf-tahoma-replacement 1.1.27-0ubuntu1
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
  SourcePackage: wine1.2
  Uname: Linux 2.6.31-5-generic i686

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


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


[Touch-packages] [Bug 2042728] Re: No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336).

2023-11-05 Thread Yosha872
Note: after launching 'ubuntu-bug' from command line, pulseaudio did
crash and launched a automatic bug report, then I completed my manual
bug report.

** Summary changed:

- No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336).
+ No sound from speakers. Audio chip: Everest ESSX 8336 (ESSX8336, ES8336).

** Description changed:

- Similar to bug #1977685.
+ The laptop does not output sound from its speaker, just a loud 'click'
+ when launching a sound player (ie: audio file from Rhythm'box).
+ 
+ Issue similar to bug #1977685.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  joel905 F wireplumber
-  /dev/snd/seq:joel902 F pipewire
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  joel905 F wireplumber
+  /dev/snd/seq:joel902 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Nov  4 15:27:44 2023
  InstallationDate: Installed on 2023-11-03 (1 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  ProcEnviron:
-  LANG=fr_FR.UTF-8
-  LANGUAGE=fr_FR
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
+  LANG=fr_FR.UTF-8
+  LANGUAGE=fr_FR
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 0.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE
  dmi.board.asset.tag: Default string
  dmi.board.name: G8316
  dmi.board.vendor: THOMSON
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64:
  dmi.product.family: N14C4WH64
  dmi.product.name: N14C4WH64
  dmi.product.sku: N14C4WH64
  dmi.product.version: Default string
  dmi.sys.vendor: THOMSON

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2042728

Title:
  No sound from speakers. Audio chip: Everest ESSX 8336 (ESSX8336,
  ES8336).

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The laptop does not output sound from its speaker, just a loud 'click'
  when launching a sound player (ie: audio file from Rhythm'box).

  Issue similar to bug #1977685.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: pulseaudio 1:16.1+dfsg1-2ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joel905 F wireplumber
   /dev/snd/seq:joel902 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Nov  4 15:27:44 2023
  InstallationDate: Installed on 2023-11-03 (1 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2021
  dmi.bios.release: 0.5
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE
  dmi.board.asset.tag: Default string
  dmi.board.name: G8316
  dmi.board.vendor: THOMSON
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.ec.firmware.release: 1.2
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64:
  dmi.product.family: N14C4WH64
  dmi.product.name: N14C4WH64
  dmi.product.sku: N14C4WH64
  dmi.product.version: Default string