[Desktop-packages] [Bug 1990891] Re: after today's Kinetic updates, WiFi no longer working, so laptop basically useless
Since this only seems to happen on dist upgrades (or it would after 22.10 is released) and we have a workaround, it doesn't need to be Critical anymore. ** Tags added: regression-upgrade ** Changed in: network-manager (Ubuntu) Importance: Critical => High -- 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/1990891 Title: after today's Kinetic updates, WiFi no longer working, so laptop basically useless Status in network-manager package in Ubuntu: Confirmed Bug description: ThinkPad X1 Carbon 6th Gen WiFi was working fine. Installed today's batch of Kinetic updates. Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB dongle and plug into my router to be able to submit this bug report). ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: network-manager 1.40.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 17:09:25 2022 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-08-16 (1137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.4.1 dev enp0s31f6 proto dhcp src 192.168.4.158 metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.4.0/24 dev enp0s31f6 proto kernel scope link src 192.168.4.158 metric 100 SourcePackage: network-manager UpgradeStatus: Upgraded to kinetic on 2022-09-24 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.40.0 connected started full enabled enabled enabled missing enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1990891/+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 1991480] Re: Second video device not accessible in Cheese
** Package changed: linux (Ubuntu) => cheese (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1991480
Title:
Second video device not accessible in Cheese
Status in cheese package in Ubuntu:
Confirmed
Bug description:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second
device, /dev/video2), both working in applications such as guvcview,
vlc, OBS or webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the
menu to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1
[Desktop-packages] [Bug 1991480] [NEW] Second video device not accessible in Cheese
You have been subscribed to a public bug:
I have two USB video devices, a Logitech Webcam (first device,
/dev/video0) and a CZUR book scanner (basically a camera, second device,
/dev/video2), both working in applications such as guvcview, vlc, OBS or
webcamoid:
v4l2-ctl --list-devices
UVC Camera (046d:0825) (usb-:00:14.0-1.3.1):
/dev/video0
/dev/video1
/dev/media0
CZUR (usb-:00:14.0-1.4.2):
/dev/video2
/dev/video3
/dev/media1
However, in Cheese I cannot access the CZUR book scanner: In the GUI, the menu
to choose a device is greyed out showing only the UVC camera, on the
commandline cheese -d CZUR falls back to the UVC camera I obtained the device
name with
udevadm info /sys/class/video4linux/video2 | grep ID_V4L_PRODUCT
E: ID_V4L_PRODUCT=CZUR
and when I replace the device name with dconf editor Cheese falls back to the
UVC device again.
This is the output of gst-device-monitor-1.0 with respect to the first and
second video device:
gst-device-monitor-1.0 Video
Probing devices...
Device found:
name : UVC Camera (046d:0825)
class : Video/Source
caps : video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)960, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1280,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/2,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1184,
height=(int)656, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)720, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)1024,
height=(int)576, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 10/1,
5/1 };
video/x-raw, format=(string)YUY2, width=(int)960,
height=(int)544, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 15/1,
10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)600, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)864,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)800,
height=(int)448, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 20/1,
15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)752,
height=(int)416, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 25/1,
20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)480, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)640,
height=(int)360, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)544,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)432,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)352,
height=(int)288, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)240, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)320,
height=(int)176, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)176,
height=(int)144, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
video/x-raw, format=(string)YUY2, width=(int)160,
height=(int)120, pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1,
25/1, 20/1, 15/1, 10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)960,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1280, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)1184, height=(int)656,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
image/jpeg, width=(int)960, height=(int)720,
pixel-aspect-ratio=(fraction)1/1, framerate=(fraction){ 30/1, 25/1, 20/1, 15/1,
10/1, 5/1 };
[Desktop-packages] [Bug 1491249] Re: Regression: Visual new email notification no longer working in 38.2.0
[Expired for thunderbird (Ubuntu) because there has been no activity for
60 days.]
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => Expired
--
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/1491249
Title:
Regression: Visual new email notification no longer working in 38.2.0
Status in thunderbird package in Ubuntu:
Expired
Bug description:
One feature of Thunderbird is a notification through the system
notification system whenever a new email arrives in the inbox. With
the recent update to version 38.2 this notification no longer works.
The "new email" sound plays, but the visual notification is no longer
displayed.
This is clearly a regression, since it worked with the previous
versions of Thunderbird.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: thunderbird 1:38.2.0+build1-0ubuntu0.15.04.1
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
AddonCompatCheckDisabled: False
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/pcmC1D0p: jan2434 F...m pulseaudio
/dev/snd/controlC1: jan2434 F pulseaudio
/dev/snd/controlC0: jan2434 F pulseaudio
BuildID: 20150818212443
Channel: Unavailable
CurrentDesktop: GNOME
Date: Wed Sep 2 08:35:06 2015
EcryptfsInUse: Yes
Extensions: extensions.sqlite corrupt or missing
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
IncompatibleExtensions: Unavailable (corrupt or non-existant
compatibility.ini or extensions.sqlite)
InstallationDate: Installed on 2015-01-30 (214 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
IpRoute:
default via 192.168.1.1 dev eth0 proto static metric 1024
169.254.0.0/16 dev eth0 scope link metric 1000
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.30
IwConfig:
eth0 no wireless extensions.
lono wireless extensions.
Locales: extensions.sqlite corrupt or missing
MostRecentCrashID: bp-90222358-6460-4247-96c9-9500e2150311
Plugins: Gnome Shell Integration -
/usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so (gnome-shell)
PrefSources:
prefs.js
[Profile]/extensions/{847b3a00-7ab1-11d4-8f02-006008948af5}/defaults/preferences/enigmail.js
[Profile]/extensions/{e2fda1a4-762b-4020-b5ad-a41df1933103}/defaults/preferences/lightning.js
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
Profiles: Profile0 (Default) - LastVersion=38.2.0/20150818212443 (In use)
RelatedPackageVersions: gnome-shell 3.14.4-0ubuntu1
RfKill:
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
RunningIncompatibleAddons: False
SourcePackage: thunderbird
SubmittedCrashIDs: bp-90222358-6460-4247-96c9-9500e2150311
Themes: extensions.sqlite corrupt or missing
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0310JH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1491249/+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 1981880] Re: Screen scrolling up on its own
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1981880 Title: Screen scrolling up on its own Status in firefox package in Ubuntu: Expired Bug description: Once Ive taken the sidebar to the bottom of the page, using my mouse on the right hand side. The screen is sticking and not allowing me to scroll up to the top of the page again. Also their is flickering on the screen when attempting to type information ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 102.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paul 1353 F pulseaudio BuildID: 20220623063721 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sat Jul 16 08:54:15 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:304 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2022-05-20 (56 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IpRoute: default via 192.168.0.1 dev enp4s0 proto dhcp metric 100 169.254.0.0/16 dev enp4s0 scope link metric 1000 192.168.0.0/24 dev enp4s0 proto kernel scope link src 192.168.0.15 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:304 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=102.0/20220623063721 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to focal on 2022-05-21 (55 days ago) dmi.bios.date: 03/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 GK dmi.board.asset.tag: Default string dmi.board.name: H310M H 2.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11GK:bd03/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnH310MH2.0:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnH310MH2.0:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: H310M H 2.0 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1981880/+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 1982001] Re: Snap-based Firefox spams apparmor messages in journal
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- 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/1982001 Title: Snap-based Firefox spams apparmor messages in journal Status in firefox package in Ubuntu: Expired Bug description: The current awfully-slow firefox package which is provided via snap has an excessive log spamming bug: On various system interactions (not only in the browser but for example by using the media-next button) a lot of apparmor notifications are triggered: Jul 18 16:32:05 UML033 kernel: audit: type=1400 audit(1658154725.146:718): apparmor="DENIED" operation="open" profile="snap.firefox.firefox" name="/home/[private]/.xsession-errors" pid=3300 comm="pool-firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [REPEATS] Jul 18 16:32:06 UML033 audit[3300]: AVC apparmor="DENIED" operation="open" profile="snap.firefox.firefox" name="/home/[private]/.xsession-errors" pid=3300 comm="pool-firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 [REPEATS] This is particular annoying for all users who are actively using apparmor in combination with aa-notify: It floods the whole desktop. There is also no obvious way to access the apparmor configuration file of the snapped firefox. There are also other reports on the internet that the apparmor configuration in this version of firefox fails to provide the targeted security. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1982001/+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 1983449] Re: Screen does not get turned of after 1 minute of inactivity even though it is configured to do so in Settings->Power->Power Saving->Blank Screen
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1983449 Title: Screen does not get turned of after 1 minute of inactivity even though it is configured to do so in Settings->Power->Power Saving->Blank Screen Status in gnome-shell package in Ubuntu: Expired Bug description: Started happening immediately after an upgrade from 18.04 to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gdm3 3.36.3-0ubuntu0.20.04.4 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Aug 3 09:48:40 2022 InstallationDate: Installed on 2017-02-18 (1991 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) SourcePackage: gdm3 UpgradeStatus: Upgraded to focal on 2022-08-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983449/+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 1991461] Re: Please add icon for .aup3 Audacity mime type
** Bug watch added: github.com/ubuntu/yaru/issues #3749 https://github.com/ubuntu/yaru/issues/3749 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3749 Importance: Unknown Status: Unknown ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Paul (jupiter007) ** Changed in: yaru-theme (Ubuntu) Status: New => In Progress ** Changed in: yaru-theme (Ubuntu) Status: In Progress => Triaged ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1991461 Title: Please add icon for .aup3 Audacity mime type Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Triaged Bug description: Audacity 3 has a new file extension .aup3. The Debian package adds the mime type application/x-audacity-project+sqlite3 for it. Yaru already ships the application-x-audacity-project.png. Please add application-x-audacity-project+sqlite3.png as symlink to it. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1991461/+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 1991452] Re: Kinetic boots to black screen
The default VirtualBox settings only give 16MB of graphics memory so the screen will start to fail/turn black around 2K resolution. Please try turning off the virtual machine and changing Video Memory to 64MB. ** Tags added: virtualbox vmwgfx ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991452 Title: Kinetic boots to black screen Status in Ubuntu: Incomplete Bug description: I installed the kinetic beta this morning in VirtualBox VM (6.1.38-dfsg-3). On the first boot after install, it got as far as the Ubuntu logo and then the screen went black and I couldn't do anything. I tried to reboot it a few times to no avail. Eventually, I rebooted it into recovery mode and used the 'repair broken packages' option and that changed around some packages. The system resumed from recovery mode and brought me to the normal desktop. I used it stably for a while and I rebooted it twice in the normal course of what I was doing with it. It booted to the desktop fine both times. However, when I rebooted it a third time, it booted to the black screen again. I rebooted it into recovery mode and ran the 'repair' again. It didn't change any packages, but resuming from recovery booted me into a usable system. I filed this bug from the terminal directly after that reboot. Expected Result: Consistent boot to desktop Actual Result: Inconsistent boot to a black screen; seemingly fixed by entering and exiting recovery mode lsb_release -rd: Description: Ubuntu Kinetic Kudu (development branch) Release: 22.10 apt policy xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 1 13:26:51 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2022-10-01 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox 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.19.0-15-generic root=UUID=2628bb97-3fa1-41ab-92ca-3d98c5e16424 ro recovery nomodeset dis_ucode_ldr SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-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-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/+bug/1991452/+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 1960417] Re: Show applications in alphabetical order
Automatically sorting icons would only make sense at install time. Thereafter we have to assume the user has dragged and reordered them manually, so automatic sorting should not be used. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Opinion -- 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/1960417 Title: Show applications in alphabetical order Status in gnome-shell package in Ubuntu: Opinion Bug description: *** *** Please change package to the appropriate one *** In Ubuntu 22.04, the "Show Applications" icon at the bottom of the launcher gives the apps in undesired order. This needs to be sorted in ascending order. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gedit 40.1-3 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 9 09:52:54 2022 InstallationDate: Installed on 2022-02-06 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960417/+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 1728342] Re: Some applications disable "Night Light" and it is not reenabled upon exiting application
Sounds like the "old" night light implementation in gnome-settings- daemon is losing track of the gamma state. Perhaps the new implementation (where it was rewritten and moved into mutter for GNOME 43) will solve it? ** Tags added: focal -- 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/1728342 Title: Some applications disable "Night Light" and it is not reenabled upon exiting application Status in gnome-shell package in Ubuntu: Confirmed Bug description: Some applications disable "Night Light" and it is not reenabled upon exiting application. Examples: Minecraft Nvidia Settings World of Warcraft via Wine. You can go into settings and manually toggle "Night Light" off and back on in order to get the blue light reduction to take effect again. Not all application/games will cause this. Rocket League, Civilization 5 are examples that do not. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu4 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 29 00:50:51 2017 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-10-19 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1728342/+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 1991494] Re: dark mode sometimes works
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1991494 Title: dark mode sometimes works Status in gnome-shell package in Ubuntu: New Bug description: the dark mode sometimes works and sometimes doesn't work. If i open Ubuntu Software store dark mode doesn't work and i have to go back to turn it back on again then it work's, its like it doesn't went to be in dark mode when i open Ubuntu Software store. it doesn't matter that must to me i just want you guys to know about it. this problem in on Ubuntu 22.10 Kinetic Kudu ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 20:18:36 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e] InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: ASUSTeK COMPUTER INC. X541UVK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UVK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UVK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: X dmi.product.name: X541UVK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-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-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/gnome-shell/+bug/1991494/+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 1990456] Re: xorg reports bogus 1600x1024 resolution
** Tags added: originate-from-1991347 ** Changed in: oem-priority Assignee: (unassigned) => Yao Wei (medicalwei) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Fix Committed -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution Status in OEM Priority Project: Fix Committed Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Jammy: Fix Committed Bug description: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Fix ] Drop 001_fedora_extramodes.patch which was dropped from Fedora since xserver 1.5.0. [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1991497] [NEW] When opening gnome-control-center my screen flashes black
Public bug reported: (gnome-control-center:4740): Clutter-WARNING **: 19:49:01.750: Whoever translated default:LTR did so wrongly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 19:51:46 2022 InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1991497 Title: When opening gnome-control-center my screen flashes black Status in gnome-control-center package in Ubuntu: New Bug description: (gnome-control-center:4740): Clutter-WARNING **: 19:49:01.750: Whoever translated default:LTR did so wrongly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.5 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 19:51:46 2022 InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1991497/+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 1989989] Re: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1989989 Title: Microphone not working on Lenovo Yoga 7 Gen 7 AMD (14ARB7) Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Yoga 7 Gen 7 AMD (14ARB7), the microphone doesn't work. I'm not familiar with the area, but I think that there is no recognized input device at all. When I try to record with any program, no sound is recorded. I think that this problem affects other Lenovo Yoga laptops. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 Uname: Linux 6.0.0-06rc3-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Fri Sep 16 18:15:09 2022 InstallationDate: Installed on 2022-09-15 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04.1-6.0rc3 "Custom Jammy Jellyfish" (20220910) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 8 3 1 : a u d i o o p e n e r r o r : N o s u c h f i l e o r d i r e c t o r y Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: saverio1949 F pulseaudio /dev/snd/controlC0: saverio1949 F pulseaudio Symptom_Type: No sound at all Title: [HDA-Intel - HD-Audio Generic, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2022 dmi.bios.release: 1.27 dmi.bios.vendor: LENOVO dmi.bios.version: K5CN27WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76463 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 7 14ARB7 dmi.ec.firmware.release: 1.27 dmi.modalias: dmi:bvnLENOVO:bvrK5CN27WW:bd05/08/2022:br1.27:efr1.27:svnLENOVO:pn82QF:pvrYoga714ARB7:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct31:cvrYoga714ARB7:skuLENOVO_MT_82QF_BU_idea_FM_Yoga714ARB7: dmi.product.family: Yoga 7 14ARB7 dmi.product.name: 82QF dmi.product.sku: LENOVO_MT_82QF_BU_idea_FM_Yoga 7 14ARB7 dmi.product.version: Yoga 7 14ARB7 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2022-09-15T11:39:08.571662 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1989989/+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 1991293] Re: sane-backends 1.1.1-5 FTBFS
** Changed in: sane-backends (Debian) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1991293 Title: sane-backends 1.1.1-5 FTBFS Status in sane-backends: New Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends package in Debian: Fix Released Bug description: FTBFS[1]: ---> minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const std::vector’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::Pixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::RawPixel’) minigtest.h:43:29: error: no match for ‘operator<<’ (operand types are ‘std::basic_ostream’ and ‘const genesys::PixelFormat’) <--- Since this happens in testsuite/, my suggested workaround is to simply disable the offending call, responsible for a diagnostic message. [1]: https://launchpadlibrarian.net/625442428/buildlog_ubuntu-kinetic- amd64.sane-backends_1.1.1-5_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/sane-backends/+bug/1991293/+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 1991496] [NEW] Permission denied when trying to open a pdf file form Google Drive
Public bug reported: I logged into Google Drive on Gnome Online Accounts, and I can access my Google Drive files from nautilus. However, when I try to open a pdf file from said folder, I can't open it. I get a "permission denied". Other files open fine. Okular is also able to open the pdf file. See attached screenshot with the error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: evince 43.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 17:27:12 2022 InstallationDate: Installed on 2022-02-02 (242 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: evince UpgradeStatus: Upgraded to kinetic on 2022-09-29 (3 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session ** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/1991496/+attachment/5620621/+files/Captura%20desde%202022-10-02%2017-27-03.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1991496 Title: Permission denied when trying to open a pdf file form Google Drive Status in evince package in Ubuntu: New Bug description: I logged into Google Drive on Gnome Online Accounts, and I can access my Google Drive files from nautilus. However, when I try to open a pdf file from said folder, I can't open it. I get a "permission denied". Other files open fine. Okular is also able to open the pdf file. See attached screenshot with the error. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: evince 43.0-1 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 17:27:12 2022 InstallationDate: Installed on 2022-02-02 (242 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: evince UpgradeStatus: Upgraded to kinetic on 2022-09-29 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1991496/+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 1991494] Re: dark mode sometimes works
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1991494 Title: dark mode sometimes works Status in xorg package in Ubuntu: New Bug description: the dark mode sometimes works and sometimes doesn't work. If i open Ubuntu Software store dark mode doesn't work and i have to go back to turn it back on again then it work's, its like it doesn't went to be in dark mode when i open Ubuntu Software store. it doesn't matter that must to me i just want you guys to know about it. this problem in on Ubuntu 22.10 Kinetic Kudu ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 20:18:36 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e] InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: ASUSTeK COMPUTER INC. X541UVK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UVK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UVK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: X dmi.product.name: X541UVK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-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-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/1991494/+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 1991494] [NEW] dark mode sometimes works
You have been subscribed to a public bug: the dark mode sometimes works and sometimes doesn't work. If i open Ubuntu Software store dark mode doesn't work and i have to go back to turn it back on again then it work's, its like it doesn't went to be in dark mode when i open Ubuntu Software store. it doesn't matter that must to me i just want you guys to know about it. this problem in on Ubuntu 22.10 Kinetic Kudu ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 20:18:36 2022 DistUpgraded: Fresh install DistroCodename: kinetic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:135e] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 920MX] [1043:135e] InstallationDate: Installed on 2022-10-02 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Beta amd64 (20220927.1) MachineType: ASUSTeK COMPUTER INC. X541UVK ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-15-generic root=UUID=70e3626f-9c69-4f70-9d86-7021fd38f8a6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541UVK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541UVK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541UVK.308:bd01/30/2018:br5.12:svnASUSTeKCOMPUTERINC.:pnX541UVK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541UVK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: X dmi.product.name: X541UVK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.112-3ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-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-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 kinetic ubuntu -- dark mode sometimes works https://bugs.launchpad.net/bugs/1991494 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1724876] Re: libreoffice soffice.bin using 100% cpu
** Changed in: df-libreoffice Importance: Medium => Unknown ** Changed in: df-libreoffice Remote watch: Document Foundation Bugzilla #128406 => Document Foundation Bugzilla #121963 -- 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/1724876 Title: libreoffice soffice.bin using 100% cpu Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Incomplete Bug description: With literally every action in libreoffice Calc, CPU usage goes to 100% due to soffice.bin, and stays on 100% for minutes. To the extend that libreoffice calc is UNUSABLE for anything that has to do with spreadsheets. As far as I am concerned, this is a critical bug because it makes the program unusable, and often even the complete computer due to the high cpu load. - 'Every action' includes typing as much as one single letter in a cell. Or opening the file. - the file I am working on is only 1.1Mb in size - the same file used to open fine in previous versions of libreoffice. what I've tried so far - without any improvement in speed: - under tools, options, assigned memory 256 Mb for Libreoffice, and 20Mb per object (no solution) - automatic calculation has been turned off (no solution) - libreoffice-gnome and libreoffice-gtk have been removed (no solution) - purged and reinstalled libreoffice. (no solution) - created new user profile - also no resolve System: Ubuntu 16.04 LTS on AMD A8 with 8Gb ram and running on an SSD. Libreoffice: Version: 5.1.6.2 Build ID: 1:5.1.6~rc2-0ubuntu1~xenial2 CPU Threads: 4; OS Version: Linux 4.4; UI Render: default To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1724876/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
Hello, I have the following installed: xdg-desktop-portal-gnome is already the newest version (42.1-0ubuntu1). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. It is still happening and I selected Ubuntu.Xorg for my desktop environment. Chrome completely froze and I had to do a hard reboot. Please advise. Thanks -- 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/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1991493] Re: Data ciphers are not properly configured with openvpn 2.6
** Changed in: network-manager-openvpn
Status: Unknown => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
New
Status in network-manager-openvpn package in Ubuntu:
Triaged
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1991493] [NEW] Data ciphers are not properly configured with openvpn 2.6
Public bug reported:
OPTIONS ERROR: failed to negotiate cipher with server. Add the server's
cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because unsupported
'--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
** Affects: network-manager-openvpn
Importance: Unknown
Status: Unknown
** Affects: network-manager-openvpn (Ubuntu)
Importance: High
Assignee: Jeremy Bicha (jbicha)
Status: Triaged
** Tags: rls-kk-incoming
** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues #97
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/97
** Also affects: network-manager-openvpn via
https://gitlab.gnome.org/GNOME/NetworkManager-openvpn/-/issues/97
Importance: Unknown
Status: Unknown
** Summary changed:
- Data ciphers are not properly configured with opevpn 2.6
+ Data ciphers are not properly configured with openvpn 2.6
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1991493
Title:
Data ciphers are not properly configured with openvpn 2.6
Status in NetworkManager-OpenVPN:
Unknown
Status in network-manager-openvpn package in Ubuntu:
Triaged
Bug description:
OPTIONS ERROR: failed to negotiate cipher with server. Add the
server's cipher ('AES-256-CBC') to --data-ciphers (currently
'AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305') if you want to connect to
this server.
So basically some servers won't be supported anymore because
unsupported '--cipher' option is used instead of '--data-ciphers'
A fix is available at https://gitlab.gnome.org/GNOME/NetworkManager-
openvpn/-/merge_requests/46
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-openvpn/+bug/1991493/+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 1991492] [NEW] Upgrade to version 1.1.0
Public bug reported: Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding support. It would be great if the version here could be updated. ** Affects: libsndfile (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libsndfile in Ubuntu. https://bugs.launchpad.net/bugs/1991492 Title: Upgrade to version 1.1.0 Status in libsndfile package in Ubuntu: New Bug description: Version 1.1.0 (released in March 2022) brings MP3 encoding/decoding support. It would be great if the version here could be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libsndfile/+bug/1991492/+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 1991448] Re: evince hangs when print requested on Ubuntu 22.04.1
There is a Debian fix, https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1870625.html Apparently the problem occurs under Cinnamon, but not under Gnome- Desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1991448 Title: evince hangs when print requested on Ubuntu 22.04.1 Status in evince package in Ubuntu: New Bug description: evince /tmp/royalt*pdf sh: 1: /usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings: Permission denied Killed Evince does not respond at all, and has to be stopped ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Sat Oct 1 16:11:51 2022 InstallationDate: Installed on 2017-03-09 (2031 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-12 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1991448/+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 1975487] Re: zsys not installed during Kinetic ISO install with ZFS option
commit 50fcd6bcd34ea7b4f73438ff2db3e2487641bb29 (HEAD -> main, origin/main) Author: Brian Murray Date: Tue Sep 27 14:09:21 2022 -0700 zsysctl is no longer seeded diff --git a/definitions/basic_installation.xml b/definitions/basic_installation.xml index 4996e4b..f4eb8b7 100644 --- a/definitions/basic_installation.xml +++ b/definitions/basic_installation.xml @@ -184,22 +184,6 @@ rpool/ROOT/ubuntu_UUID/var/lib/apt /var/lib/apt rpool/ROOT/ubuntu_UUID/var/lib/dpkg /var/lib/dpkg -$ zsysctl show -Name: rpool/ROOT/ubuntu_UUID -ZSys: true -Last Used: current -History: - - Name: rpool/ROOT/ubuntu_UUID@autozsys_SNAPID -Created on: 2020-04-14 16:37:10 -Users: - - Name:root -History: - - rpool/USERDATA/root_0y7dio@autozsys_SNAPID (2020-04-14 16:37:10) - - Name:u -History: - - rpool/USERDATA/u_0y7dio@autozsys_SNAPID (2020-04-14 16:37:10) - - rpool/USERDATA/u_0y7dio@autozsys_SNAPID (2020-04-14 16:34:41) - ** Changed in: ubuntu-manual-tests Status: In Progress => Fix Released ** Changed in: zsys (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1975487 Title: zsys not installed during Kinetic ISO install with ZFS option Status in Ubuntu Manual Tests: Fix Released Status in zsys package in Ubuntu: Invalid Bug description: After following the instructions at: http://iso.qa.ubuntu.com/qatracker/milestones/433/builds/248685/testcases/1716/results on the 20220523 daily build of Kinetic, I used the command zsysctl show and was met with the message: ~$ zsysctl show Command 'zsysctl' not found, but can be installed with: sudo apt install zsys ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: zsys (not installed) ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 23 12:33:24 2022 InstallationDate: Installed on 2022-05-23 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220522) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1975487/+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 1991484] Re: nautilus crashed with SIGSEGV in g_list_store_find_with_equal_func_full()
*** This bug is a duplicate of bug 1991422 *** https://bugs.launchpad.net/bugs/1991422 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1991422, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1991484/+attachment/5620545/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1991484/+attachment/5620547/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1991484/+attachment/5620550/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1991484/+attachment/5620551/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1991484/+attachment/5620552/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1991484/+attachment/5620553/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1991484/+attachment/5620554/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1991422 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1991484 Title: nautilus crashed with SIGSEGV in g_list_store_find_with_equal_func_full() Status in nautilus package in Ubuntu: New Bug description: Browsed the filesystem, searched for kodi files. Kodi was installed as an ubuntu deb package. ProblemType: Crash DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-1003.3-lowlatency 5.19.0 Uname: Linux 5.19.0-1003-lowlatency x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 2 14:54:18 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1181, 847)' InstallationDate: Installed on 2022-08-13 (50 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220813) JournalErrors: -- No entries -- ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f14cd9c48af :mov0x0(%rbp),%rax PC (0x7f14cd9c48af) ok source "0x0(%rbp)" (0x) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: g_list_store_find_with_equal_func_full () from /lib/x86_64-linux-gnu/libgio-2.0.so.0 ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_list_store_find_with_equal_func_full() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.1-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1991484/+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 1772520] Re: [upstream] Font metrics mixed up when selecting Arabic characters in Writer
Launchpad has imported 30 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=30731.
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 2010-10-09T07:21:20+00:00 Rgb-mldc wrote:
Steps to reproduce the problem:
1- Install Linux Libertine G font from here: http://numbertext.org/linux/
2- Open a Writer document and type the following text
Some text \prime Some text fi more text
3- Modify the paragraph style to use the Linux Libertine G font with "tex mode"
enablesd (on the font name box type: Linux Libertine G:texm=1)
"\prime" will change into ' and fi will be replaced with proper typographical
ligature.
4- Put the cursor on the end of the paragraph and use the cursor arrows to go
to the left one character at a time.
Actual result:
While the cursor behaviour is OK on the fi ligature (and this is an improvement
respect OOo 3.2.x), when you arrive to the "prime" the cursor will jump to the
right, possible going to the position where the text \prime should be if "tex
mode" were not enabled.
This behaviour is confusing because the cursor jump to a text position,
but if you press "back space" the text deleted is the one "hidden" by
the Graphite replacement, not the one where cursor is shown.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772520/comments/0
On 2011-02-17T19:34:32+00:00 mhosken wrote:
This bug exemplifies a couple of problems.
Bug 34420 addresses most of the needs here. But there is also something
wrong with the font. When creating ligatures it is necessary to
associate the ligature with all (well the first and last) of the
underlying glyphs. Thus a rule (taken from MagyarLinLibertineG) like:
unicode(0x005C) p("a") p("l") p("p") p("h") p("a") > _ _ _ _ _
unicode(0x03B1);
needs to become:
unicode(0x005C) p("a") p("l") p("p") p("h") p("a") > _ _ _ _ _
unicode(0x03B1):(1 6);
This then tells the engine that the whole string \alpha is associated
with the one output glyph rather than saying that it is deleting \alph
and associating the alpha with the final a only.
Bug 34420 removes the most egregious problems with not specifying
appropriately, but doesn't solve everything.
In addition there is the issue that people don't really want to have to
right arrow 6 times to get past the alpha, which the current cursor
tracking algorithm, which is based on a purely codepoint based (UAX#29)
model, requires.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772520/comments/1
On 2011-10-27T22:33:10+00:00 Libreoffice-z wrote:
Modified Version due to report date.
@RGB:
Still a problem for you?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772520/comments/2
On 2011-10-28T17:01:52+00:00 Rgb-mldc wrote:
(In reply to comment #2)
> @RGB:
> Still a problem for you?
Yes. Same behavior as described on initial entry with LibO 3.4.2.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772520/comments/3
On 2011-12-23T11:35:38+00:00 Björn Michaelsen wrote:
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2
prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1
more detail on this bulk operation:
http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-
tp3607474p3607474.html
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772520/comments/4
On 2011-12-23T16:53:26+00:00 Rgb-mldc wrote:
The problem is present on 3.5 beta2.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772520/comments/5
On 2012-01-03T20:19:19+00:00 mhosken wrote:
did you fix the font?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1772520/comments/6
On 2014-06-25T17:38:02+00:00 Qa-admin-q wrote:
Please read this message in its entirety before responding.
Your bug was confirmed at least 1 year ago and has not had any activity
on it for
[Desktop-packages] [Bug 1991333] Re: Night light is not available in gnome-control-center despite being enabled in quick settings
** This bug is no longer a duplicate of bug 1990207 "Night Light unavailable" in Settings (but the quick settings toggle for it works) -- 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/1991333 Title: Night light is not available in gnome-control-center despite being enabled in quick settings Status in gnome-control-center package in Ubuntu: New Bug description: In the gnome-control-center, under Monitors->Night light, there is a banner saying that night light is not available and "that may be the result of the graphics driver or that you are using remote desktop" (loosely translated from Spanish, see screenshot). None of that is true and Night light worked fine before updating to 22.10 beta. Moreover, night light was setup to activate at dusk before updating and that seems to be working. It can even be toggled using the quick settings. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-15.15-generic 5.19.0 Uname: Linux 5.19.0-15-generic x86_64 ApportVersion: 2.23.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Sep 29 18:17:51 2022 InstallationDate: Installed on 2022-02-02 (239 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to kinetic on 2022-09-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1991333/+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 1772520] Re: [upstream] Font metrics mixed up when selecting Arabic characters in Writer
** Bug watch added: Document Foundation Bugzilla #30731 https://bugs.documentfoundation.org/show_bug.cgi?id=30731 ** Changed in: df-libreoffice Importance: Medium => Unknown ** Changed in: df-libreoffice Status: Invalid => Unknown ** Changed in: df-libreoffice Remote watch: Document Foundation Bugzilla #119347 => Document Foundation Bugzilla #30731 -- 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/1772520 Title: [upstream] Font metrics mixed up when selecting Arabic characters in Writer Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Confirmed Bug description: In most fonts, many characters in the Arabic script change their width and height as typing progresses. For example the letter ب (U+0628) is reduced to about a half or even a third of its width if it's followed by another character such as ا (U+0627): با. Usually LibreOffice understands the changes in font metrics pretty well but not always. See the attached screenshot where I've written the sentence "مرحبا يا صديقي العزيز" in Writer and started selecting letters from the beginning of the line. The selection shown in the screenshot looks like the whole first word plus the following space but actually it only covers the first 4 letters of the first word out of 5 total: مرحب. From a user's point of view, this is very confusing, as I can't tell how far I've already selected without counting the characters in my mind. Even more surprisingly, LibreOffice Calc shows the selection as expected, i.e. different from Writer, so this does not feel like a font problem per se, although only some fonts display this behavior. The font I'm using in this example is Scheherazade, available through a third-party repository at packages.sil.org. The font is designed to cover a very wide variety of characters used for Arabic-script minority languages in both Asia and Africa, and in many cases it's the only professionally made font available for people working on many of these languages. Description: Ubuntu 17.10 Release: 17.10 libreoffice-writer: Installed: 1:5.4.6-0ubuntu0.17.10.1 Candidate: 1:5.4.6-0ubuntu0.17.10.1 Version table: *** 1:5.4.6-0ubuntu0.17.10.1 500 500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:5.4.5-0ubuntu0.17.10.5 500 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 1:5.4.1-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 21:03:43 2018 InstallationDate: Installed on 2017-02-13 (462 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 artful on 2017-11-05 (197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772520/+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 1772520]
Same underling issue as bug 30731, and fixed with the same fix. *** This bug has been marked as a duplicate of bug 30731 *** -- 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/1772520 Title: [upstream] Font metrics mixed up when selecting Arabic characters in Writer Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Bug description: In most fonts, many characters in the Arabic script change their width and height as typing progresses. For example the letter ب (U+0628) is reduced to about a half or even a third of its width if it's followed by another character such as ا (U+0627): با. Usually LibreOffice understands the changes in font metrics pretty well but not always. See the attached screenshot where I've written the sentence "مرحبا يا صديقي العزيز" in Writer and started selecting letters from the beginning of the line. The selection shown in the screenshot looks like the whole first word plus the following space but actually it only covers the first 4 letters of the first word out of 5 total: مرحب. From a user's point of view, this is very confusing, as I can't tell how far I've already selected without counting the characters in my mind. Even more surprisingly, LibreOffice Calc shows the selection as expected, i.e. different from Writer, so this does not feel like a font problem per se, although only some fonts display this behavior. The font I'm using in this example is Scheherazade, available through a third-party repository at packages.sil.org. The font is designed to cover a very wide variety of characters used for Arabic-script minority languages in both Asia and Africa, and in many cases it's the only professionally made font available for people working on many of these languages. Description: Ubuntu 17.10 Release: 17.10 libreoffice-writer: Installed: 1:5.4.6-0ubuntu0.17.10.1 Candidate: 1:5.4.6-0ubuntu0.17.10.1 Version table: *** 1:5.4.6-0ubuntu0.17.10.1 500 500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:5.4.5-0ubuntu0.17.10.5 500 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 1:5.4.1-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 21:03:43 2018 InstallationDate: Installed on 2017-02-13 (462 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 artful on 2017-11-05 (197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772520/+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 1772520] Re: [upstream] Font metrics mixed up when selecting Arabic characters in Writer
** 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/1772520 Title: [upstream] Font metrics mixed up when selecting Arabic characters in Writer Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Bug description: In most fonts, many characters in the Arabic script change their width and height as typing progresses. For example the letter ب (U+0628) is reduced to about a half or even a third of its width if it's followed by another character such as ا (U+0627): با. Usually LibreOffice understands the changes in font metrics pretty well but not always. See the attached screenshot where I've written the sentence "مرحبا يا صديقي العزيز" in Writer and started selecting letters from the beginning of the line. The selection shown in the screenshot looks like the whole first word plus the following space but actually it only covers the first 4 letters of the first word out of 5 total: مرحب. From a user's point of view, this is very confusing, as I can't tell how far I've already selected without counting the characters in my mind. Even more surprisingly, LibreOffice Calc shows the selection as expected, i.e. different from Writer, so this does not feel like a font problem per se, although only some fonts display this behavior. The font I'm using in this example is Scheherazade, available through a third-party repository at packages.sil.org. The font is designed to cover a very wide variety of characters used for Arabic-script minority languages in both Asia and Africa, and in many cases it's the only professionally made font available for people working on many of these languages. Description: Ubuntu 17.10 Release: 17.10 libreoffice-writer: Installed: 1:5.4.6-0ubuntu0.17.10.1 Candidate: 1:5.4.6-0ubuntu0.17.10.1 Version table: *** 1:5.4.6-0ubuntu0.17.10.1 500 500 http://mr.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:5.4.5-0ubuntu0.17.10.5 500 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 1:5.4.1-0ubuntu1 500 500 http://mr.archive.ubuntu.com/ubuntu artful/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice-writer 1:5.4.6-0ubuntu0.17.10.1 ProcVersionSignature: Ubuntu 4.13.0-41.46-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon May 21 21:03:43 2018 InstallationDate: Installed on 2017-02-13 (462 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 artful on 2017-11-05 (197 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1772520/+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 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
Not only the resolution is wrong for the USB-C display but also the order is different. Unplugging and plugging the connector seems to fix the issue (Ubuntu 22 LTS). -- 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/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000BMC dmi.product.sku:
