[Desktop-packages] [Bug 2004095] [NEW] Unimplemented action: POPPLER_ACTION_JAVASCRIPT
Public bug reported: evince gives me a warning message : ** (evince:158186): WARNING **: 22:24:40.458: Unimplemented action: POPPLER_ACTION_JAVASCRIPT, please post a bug report in Evince issue tracker (https://gitlab.gnome.org/GNOME/evince/issues) with a testcase. a whole bunch of times when i open the pdf of the following paper: DOI:10.1161/CIRCULATIONAHA.122.061025 evince: 3.36.0-2 ubuntu: 20.04 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 28 22:24:51 2023 InstallationDate: Installed on 2017-04-18 (2111 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-04-25 (1008 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal -- 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/2004095 Title: Unimplemented action: POPPLER_ACTION_JAVASCRIPT Status in evince package in Ubuntu: New Bug description: evince gives me a warning message : ** (evince:158186): WARNING **: 22:24:40.458: Unimplemented action: POPPLER_ACTION_JAVASCRIPT, please post a bug report in Evince issue tracker (https://gitlab.gnome.org/GNOME/evince/issues) with a testcase. a whole bunch of times when i open the pdf of the following paper: DOI:10.1161/CIRCULATIONAHA.122.061025 evince: 3.36.0-2 ubuntu: 20.04 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 Uname: Linux 6.0.7-gnulibre-squashfix x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 28 22:24:51 2023 InstallationDate: Installed on 2017-04-18 (2111 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-04-25 (1008 days ago) mtime.conffile..etc.apport.crashdb.conf: 2020-06-07T21:16:26.397404 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2004095/+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 1995236] Re: Xsessions has_option code error with fix
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1995236 Title: Xsessions has_option code error with fix Status in xorg package in Ubuntu: Expired Bug description: Jammy Jellyfish 22.04.1 LTS and others. There have been numerous bug reports and failed fixes for this over several years and releases. There are a couple of problems in /etc/X11/Xsessions where it fails to handle options, causing bogus error messages and, doubtless, many errors. The first bug is that the entire options file, including comments, is read into a variable. Where the variable "OPTIONS" is assigned; Replacing "cat" with "grep" strips out comments and blank lines; $ diff Xsession Xsession.orig 65c65 < grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" --- > cat "$OPTIONFILE" The second problem is that checking for a non-existent directory inside a command substitution does not work. It just appends garbage onto the output string. That is probably a bug in BASH, but I defer to your opinion there. The immediate work around is to create an empty directory so that the test does not fail. Better still, force the creation of the directory and remove the test. eg. change this; OPTIONS="$( if [ -r "$OPTIONFILE" ]; then cat "$OPTIONFILE" fi if [ -d /etc/X11/Xsession.options.d ]; then run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat fi )" to this; OPTIONSDIR=/etc/X11/Xsession.options.d mkdir --parents ${OPTIONSDIR} OPTIONS="$( if [ -r "$OPTIONFILE" ]; then grep -v "^\s*\#\|^\s*$" "$OPTIONFILE" fi run-parts --list --regex '\.conf$' /etc/X11/Xsession.options.d | xargs -d '\n' cat )" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 31 16:33:14 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: virtualbox/6.1.38, 5.15.0-362206031516-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-52-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2022-10-20 (11 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. MS-7B89 ProcKernelCmdLine: ro root=PARTUUID=1c70e394-574c-46cc-a65e-a402f0e077d4 fbcon=rotate:2 initrd=\initrd.img SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/01/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 2.C0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450M MORTAR MAX (MS-7B89) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr2.C0:bd02/01/2021:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B89:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB450MMORTARMAX(MS-7B89):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B89 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1 version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1997142] Re: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started
[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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: Expired Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997252] Re: the default DESKTOP ICONS NG doesn’t work as it doesn’t show Desktop Icons/folder
[Expired for gnome-shell-extension-desktop-icons-ng (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1997252 Title: the default DESKTOP ICONS NG doesn’t work as it doesn’t show Desktop Icons/folder Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Expired Bug description: As of today i was installing some pulseaudio package but due to some error it failed and i landed in the Text interface of ubuntu . But after installing GDM3 i was back on the desktop. then i had seen that all the extensions were working but not the default desktop icons. Then i had to install other extension name "desktop icons :neo" . . After this the whole gjs error occured.kindly review it.If there is any way to use the "desktop icons :ng" then also please inform ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 21 20:14:57 2022 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1997252/+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 2004063] Re: mouse pointer becomes laggy after some time and progressively gets worse
I have been watching journalctl log for clues and saw this Jan 28 19:57:49 tesla gnome-shell[455040]: libinput error: event4 - Logitech M585/M590: client bug: event processing lagging behind by 32ms, your system is too slow -- 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/2004063 Title: mouse pointer becomes laggy after some time and progressively gets worse Status in gnome-shell package in Ubuntu: New Bug description: Over some period of time after logging in the mouse becomes laggy and eventually unusable. I generally have a lot of Chrome tabs open. The time period can be minutes to maybe an hour. I am not sure if Chrome is required to cause the problem yet but I have experimented with changed Chrome versions and enable/disable hardware acceleration in Chrome and that did not make a difference. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jan 27 23:12:58 2023 DisplayManager: gdm3 InstallationDate: Installed on 2018-12-28 (1492 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 42.5-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-22 (219 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2004063/+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 1958084] Re: Please apply the upstream commit to drop Bitstream Vera fonts
Fixed also in Ubuntu. ** Changed in: fontconfig (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1958084 Title: Please apply the upstream commit to drop Bitstream Vera fonts Status in fontconfig package in Ubuntu: Fix Released Status in fontconfig package in Debian: Fix Released Bug description: Upstream dropped Bitstream Vera fonts, please apply that fix in the Ubuntu package. https://gitlab.freedesktop.org/fontconfig/fontconfig/-/commit/fcb042028126d79ea5a5fa015b2b034b98656e73 Rationale: DejaVu font extends the Bitstream Vera font, and is already installed by default. Besides, the Bitstream Vera font is very obsolete, looks worse than DejaVu and sometimes as a negative side effect it takes over as a default font when installed (without DejaVu). After applying the upstream fix, this Ubuntu patch becomes obsolete (03_prefer_dejavu.patch): https://git.launchpad.net/ubuntu/+source/fontconfig/tree/debian/patches/03_prefer_dejavu.patch You may also think about updating the whole package to an up-to-date snapshot, since the last Debian/Ubuntu version update was in 2018. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1958084/+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 1980080] Re: Unable to eject SDcard -getting remounted immediately
Is ther any reason that impish was removed if the bug is valid both for jammy and impish ? Also do you need any more debug info to properly triage this and change "New" status to something meaninfgul after 6 months ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1980080 Title: Unable to eject SDcard -getting remounted immediately Status in gvfs package in Ubuntu: New Bug description: THe problem is on Dell XPS13 9310 and built-in microSD card reader(without adapter). When I plug the card it's visiible in file manager, with little 'eject' icon. I can read/write to it. After finishing and using eject button. THe card it's still present in gnome along with 'eject' button. But when clicking eject it says 'No object for D-bus interface' and both the device and partition blockdevices are still present. I can't also eject from command line: nusch@xps13:~$ LANG="en" eject -v /dev/mmcblk0 eject: device name is `/dev/mmcblk0' eject: /dev/mmcblk0: not mounted eject: /dev/mmcblk0: is whole-disk device eject: /dev/mmcblk0: trying to eject using CD-ROM eject command eject: CD-ROM eject command failed eject: /dev/mmcblk0: trying to eject using SCSI commands eject: not an sg device, or old sg driver eject: SCSI eject failed eject: /dev/mmcblk0: trying to eject using floppy eject command eject: floppy eject command failed eject: /dev/mmcblk0: trying to eject using tape offline command eject: tape offline command failed eject: unable to eject ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.10.0-1057.61-oem 5.10.83 Uname: Linux 5.10.0-1057-oem x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu71.2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 28 13:31:39 2022 DisplayManager: gdm3 InstallationDate: Installed on 2015-05-08 (2608 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to impish on 2022-02-21 (126 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1980080/+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
Re: [Desktop-packages] [Bug 1983794] Please test proposed package
On Fri, 2023-01-27 at 17:06 +, Timo Aaltonen wrote: > Please help us by testing this new package. On first look, it does the Right Things in Evolution here with regard to autosave files. Don't know about the system sounds since I don't pay attention to these. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files Status in Evolution: Fix Released Status in evolution package in Ubuntu: Invalid Status in libcanberra package in Ubuntu: Fix Released Status in libcanberra source package in Jammy: Fix Committed Status in evolution source package in Kinetic: New Status in libcanberra source package in Kinetic: Fix Committed Bug description: [ Impact ] Autosave files are not removed from evolution local state directories (and windows leaked) [ Test case ] 1. Open evolution, and start to compose a new email 2. Write enough text and wait few minutes so that this command returns a file ls -l ~/.local/share/evolution/.evolution-composer.autosave-* 3. Close the email composer window, hitting "Do not save" 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list no files 5. Opening and closing again evolution should not ask to restore the previous email [ Regression potential ] No sounds could be performed during some UI actions --- Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1983794/+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 1916640] Re: Nvidia 340.108 driver provided by Butterfly (kelebek333) works very well till kernel 5.17.x but not beyond
@Kevin K (stafio) Thank you very much. That worked for me on Kubuntu 22.10, kernel 6.1.8 and GeForce 9800 GT. Could you please provide a bash script to help newbies? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1916640 Title: Nvidia 340.108 driver provided by Butterfly (kelebek333) works very well till kernel 5.17.x but not beyond Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Bug description: As usual I have opened this (no more) new bug report... As ALWAYS happened in the past, EVERY TWO MONTHS new patches are needed for old Nvidia 340.108 drivers, that is, with each release of a new kernel... Nvidia 340.108 fails to install with kernels 5.11.x - new patches needeed Just to inform develepers that a new patch for Nvidia 340.108 and kernel 5.11 is not yet available here: https://github.com/warpme/minimyth2/blob/master/script/nvidia/nvidia-340.108/files/ Anyway thanks for your great contribution to community and hope you publish new patched drivers without having to always report the same bug... Good day to all the developers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1916640/+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 2004081] [NEW] Setting power saving mode always reverts to balanced, and the laptop loses power quickly, even when suspended
Public bug reported: 1- I'm using Asus Vivobook 15 (i7) I tried to contact Asus support but they do not support Ubuntu. Hardware model: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EAN_K513EA Memory:16,0 GiB Processor: 11th Gen Intel® Core™ i7-1165G7 × 8 Graphics: Mesa Intel® Xe Graphics (TGL GT2) Disk capacity: 1,0 TB (SSD) OS Name: Ubuntu 22.10 OS Type: 64-bit Gnome version 43.1 Windowing system: Wayland 2- Package gnome-power-manager 43.0-1 3-Expectd that when I set power mode to Power Saver that it stays there, and when I suspend or put to sleep the laptop, battery level drops very slowly 4- If I manually set the power-saving mode, it reverts to balanced within less than a minute. This is reproducible every time and does not dependent on whether there's a power supply or on battery. while using the laptop with simple office work (no video, no audio), it drains the battery in less than 5 hours while the vendor claims 7 hours of heavy duty. even in sleep or suspend mode it drains the battery quickly. Almost half of normal consumption while used. At startup I can see error messages related to ACPI (see the screen shot). No idea if this can explain. the laptop is on dual boot Windows 11/Ubuntu 22.10 latest updates and I do not notice the same problem under windows 11. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Attachment added: "20230123_162017.jpg" https://bugs.launchpad.net/bugs/2004081/+attachment/5643751/+files/20230123_162017.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/2004081 Title: Setting power saving mode always reverts to balanced, and the laptop loses power quickly, even when suspended Status in gnome-power-manager package in Ubuntu: New Bug description: 1- I'm using Asus Vivobook 15 (i7) I tried to contact Asus support but they do not support Ubuntu. Hardware model: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X513EAN_K513EA Memory:16,0 GiB Processor: 11th Gen Intel® Core™ i7-1165G7 × 8 Graphics: Mesa Intel® Xe Graphics (TGL GT2) Disk capacity: 1,0 TB (SSD) OS Name: Ubuntu 22.10 OS Type: 64-bit Gnome version 43.1 Windowing system: Wayland 2- Package gnome-power-manager 43.0-1 3-Expectd that when I set power mode to Power Saver that it stays there, and when I suspend or put to sleep the laptop, battery level drops very slowly 4- If I manually set the power-saving mode, it reverts to balanced within less than a minute. This is reproducible every time and does not dependent on whether there's a power supply or on battery. while using the laptop with simple office work (no video, no audio), it drains the battery in less than 5 hours while the vendor claims 7 hours of heavy duty. even in sleep or suspend mode it drains the battery quickly. Almost half of normal consumption while used. At startup I can see error messages related to ACPI (see the screen shot). No idea if this can explain. the laptop is on dual boot Windows 11/Ubuntu 22.10 latest updates and I do not notice the same problem under windows 11. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/2004081/+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 2004080] [NEW] package ubuntu-minimal 1.481 failed to install/upgrade: problemas de dependência - deixando desconfigurado
Public bug reported: I was installing ubuntu 22.04 and on the final step, I've pressed the ctrl + C button in order to copy one information. Unfortunately, the update process stoped, and I got an error saying I have something to do about dpkg or something. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ubuntu-minimal 1.481 ProcVersionSignature: Ubuntu 5.14.0-1056.63-oem 5.14.21 Uname: Linux 5.14.0-1056-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jan 28 14:43:25 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2023-01-25 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: ubuntu-meta Title: package ubuntu-minimal 1.481 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to jammy on 2023-01-28 (0 days ago) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2004080 Title: package ubuntu-minimal 1.481 failed to install/upgrade: problemas de dependência - deixando desconfigurado Status in ubuntu-meta package in Ubuntu: New Bug description: I was installing ubuntu 22.04 and on the final step, I've pressed the ctrl + C button in order to copy one information. Unfortunately, the update process stoped, and I got an error saying I have something to do about dpkg or something. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: ubuntu-minimal 1.481 ProcVersionSignature: Ubuntu 5.14.0-1056.63-oem 5.14.21 Uname: Linux 5.14.0-1056-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jan 28 14:43:25 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2023-01-25 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: ubuntu-meta Title: package ubuntu-minimal 1.481 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: Upgraded to jammy on 2023-01-28 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2004080/+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 1998344] Re: Night Light doesn't alter screen display colour temperature
I see the same behaviour with Fedora gnome desktop on this machine. It does therefore seem to be related to gnome desktop and this hardware. -- 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/1998344 Title: Night Light doesn't alter screen display colour temperature Status in gnome-control-center package in Ubuntu: New Bug description: Night light turns on and off correctly (manually and automatically at sunset/sunrise), but it has no effect on screen colour temperature. Altering the colour temperature slider makes no difference. Changing display temperature in dconf-editor didn't have any effect either. Behaviour is the same in Wayland and Xorg sessions. (Note that 22.10 is the first ubuntu release where graphics have worked at all with this machine (Intel® Core™ i3-10100 CPU Intel CometLake-S GT2 [UHD Graphics 630]) With kernels before 5.19 the i915 driver module wouldn't load.) I have raised the issue on ubuntu forums, https://ubuntuforums.org/showthread.php?t=2481261 with no indication of it being a problem also reported by other 22.10 users, so it may be specific to this CPU. It also appears to be specific to gnome desktop. I have tried a Kubuntu liveUSB and night light worked correctly. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-control-center 1:43.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 30 14:47:25 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-10-27 (33 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1998344/+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 1999300] Re: crash in global constructor
** Changed in: libcamera (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcamera in Ubuntu. https://bugs.launchpad.net/bugs/1999300 Title: crash in global constructor Status in libcamera package in Ubuntu: Confirmed Bug description: An application built with libcamera-dev crashes instantly on start in a global constructor. This can be reproduced by the 'cam' example in package libcamera-tools (run 'cam -l') or via this simple example; #include int main(int argc, char **argv) { libcamera::CameraManager camera_manager; } ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libcamera0 0~git20200629+e7aa92a-9 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Dec 10 01:21:46 2022 InstallationDate: Installed on 2022-06-25 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: libcamera UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/1999300/+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 1983794] Re: Evolution not deleting autosave files
I am using Ubuntu 22.04.1 LTS Best wishes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files Status in Evolution: Fix Released Status in evolution package in Ubuntu: Invalid Status in libcanberra package in Ubuntu: Fix Released Status in libcanberra source package in Jammy: Fix Committed Status in evolution source package in Kinetic: New Status in libcanberra source package in Kinetic: Fix Committed Bug description: [ Impact ] Autosave files are not removed from evolution local state directories (and windows leaked) [ Test case ] 1. Open evolution, and start to compose a new email 2. Write enough text and wait few minutes so that this command returns a file ls -l ~/.local/share/evolution/.evolution-composer.autosave-* 3. Close the email composer window, hitting "Do not save" 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list no files 5. Opening and closing again evolution should not ask to restore the previous email [ Regression potential ] No sounds could be performed during some UI actions --- Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1983794/+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 1992255] Re: Cant upload files from remote folders : Firefox and Chrome
Any news about this? -- 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/1992255 Title: Cant upload files from remote folders : Firefox and Chrome Status in firefox package in Ubuntu: New Bug description: I dont know if this is really a Nautilus bug. In windows when we attach file in a webserver it opens "explorer" so I think in Linux is more or less the same. Problem: Upload file from a remote share to a Browser it does nothing, no error nothing. If I upload from the same share to Thunderbird and it uploads normally. I noticed one thing, apparently the browsers uses a different "Nautilus" than Thunderbird. Please see the screenshots attached ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60 Uname: Linux 5.15.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 8 21:15:39 2022 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.3-0ubuntu2 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992255/+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 2004074] [NEW] package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 2
Public bug reported: E: Sub-process /usr/bin/dpkg returned an error code (1) Sat Jan 28 09:02:32 AM EST 2023 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tex-common 6.17 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jan 28 09:02:22 2023 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-06-07 (234 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tex-common Title: package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to jammy on 2022-08-16 (165 days ago) ** Affects: tex-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tex-common in Ubuntu. https://bugs.launchpad.net/bugs/2004074 Title: package tex-common 6.17 failed to install/upgrade: installed tex- common package post-installation script subprocess returned error exit status 2 Status in tex-common package in Ubuntu: New Bug description: E: Sub-process /usr/bin/dpkg returned an error code (1) Sat Jan 28 09:02:32 AM EST 2023 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: tex-common 6.17 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sat Jan 28 09:02:22 2023 ErrorMessage: installed tex-common package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2022-06-07 (234 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: tex-common Title: package tex-common 6.17 failed to install/upgrade: installed tex-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to jammy on 2022-08-16 (165 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/2004074/+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 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on u
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer1.0 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Bionic: Confirmed Status in gstreamer1.0 source package in Focal: Confirmed Bug description: Following gstreamer critical warning observed on gstreamer version 1.16 on ubuntu-20.04 with nvidia specific gst-v4l2 decoder pipeline: "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" It seems fix for the issue is already incorporated on gstreamer version 1.18 with below: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a1b41b2b2493069365a8274c6a544e6799a5a8df We need to backport above fix on top of gst-1.16 on ubuntu-20.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+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 1962134] Re: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on u
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer1.0 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1962134 Title: Resolve "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" warning on gstreamer version 1.16 on ubuntu-20.04 Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gstreamer1.0 source package in Bionic: Confirmed Status in gstreamer1.0 source package in Focal: Confirmed Bug description: Following gstreamer critical warning observed on gstreamer version 1.16 on ubuntu-20.04 with nvidia specific gst-v4l2 decoder pipeline: "GStreamer-CRITICAL **: 13:33:23.770: gst_buffer_resize_range: assertion 'bufmax >= bufoffs + offset + size' failed" It seems fix for the issue is already incorporated on gstreamer version 1.18 with below: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/a1b41b2b2493069365a8274c6a544e6799a5a8df We need to backport above fix on top of gst-1.16 on ubuntu-20.04 in order to have out-of-box fix available with default gstreamer-1.0 version 1.16 on ubuntu-20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1962134/+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 1983794] Re: Evolution not deleting autosave files
You shouldn't build the package from source; it is already built in the proposed updates repository. miguelquiros, please specify what version of Ubuntu you are using. There are proposed packages for both Ubuntu 22.04 LTS and Ubuntu 22.10 available now to fix this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files Status in Evolution: Fix Released Status in evolution package in Ubuntu: Invalid Status in libcanberra package in Ubuntu: Fix Released Status in libcanberra source package in Jammy: Fix Committed Status in evolution source package in Kinetic: New Status in libcanberra source package in Kinetic: Fix Committed Bug description: [ Impact ] Autosave files are not removed from evolution local state directories (and windows leaked) [ Test case ] 1. Open evolution, and start to compose a new email 2. Write enough text and wait few minutes so that this command returns a file ls -l ~/.local/share/evolution/.evolution-composer.autosave-* 3. Close the email composer window, hitting "Do not save" 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list no files 5. Opening and closing again evolution should not ask to restore the previous email [ Regression potential ] No sounds could be performed during some UI actions --- Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1983794/+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 2003957] Re: Appearance set to dark but menus are the default
** Description changed: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. + + If I chose another item in the gnome settings and open "Appearance" + again, it will also trigger this bug. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: - + InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2003957 Title: Appearance set to dark but menus are the default Status in gnome-shell package in Ubuntu: New Bug description: Appearance is set to "dark" but sometimes background color for right- click menu, clock and other apps like Hexchat change to "default as shown in the screenshots. If I chose another item in the gnome settings and open "Appearance" again, it will also trigger this bug. The only solution is to change the "Color" setting in Settings -> Appearance and it will make it dark again. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jan 26 16:57:15 2023 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2023-01-04 (21 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell 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/2003957/+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 1987178] Re: package sgml-base 1.30 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sgml-base (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sgml-base in Ubuntu. https://bugs.launchpad.net/bugs/1987178 Title: package sgml-base 1.30 failed to install/upgrade: triggers looping, abandoned Status in sgml-base package in Ubuntu: Confirmed Bug description: 1. Ubuntu 20.04.1 2. sgml-base 1.30 3. It should be installed along with the rest of the 22.04.1 upgrade. 4. Didn't install. Stopped the upgrade. :( ProblemType: Package DistroRelease: Ubuntu 22.04 Package: sgml-base 1.30 ProcVersionSignature: Ubuntu 5.15.0-46.49~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: aufs ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Aug 21 00:33:56 2022 DuplicateSignature: package:sgml-base:1.30 Processing triggers for libgl1-amdgpu-mesa-dri:i386 (1:20.0.5-1098277) ... dpkg: error processing package libgl1-amdgpu-mesa-dri:i386 (--configure): installed libgl1-amdgpu-mesa-dri:i386 package post-installation script subprocess returned error exit status 1 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2021-05-23 (454 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: sgml-base Title: package sgml-base 1.30 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to jammy on 2022-08-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sgml-base/+bug/1987178/+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 2004070] Re: ayatana-indicator-messages-service crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1992477 *** https://bugs.launchpad.net/bugs/1992477 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 #1992477, 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/2004070/+attachment/5643717/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/2004070/+attachment/5643719/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2004070/+attachment/5643722/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2004070/+attachment/5643723/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/2004070/+attachment/5643724/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2004070/+attachment/5643725/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2004070/+attachment/5643726/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1992477 ** Information type changed from Private Security to Public Security ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ayatana-indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/2004070 Title: ayatana-indicator-messages-service crashed with SIGSEGV in g_type_check_instance_cast() Status in ayatana-indicator-messages package in Ubuntu: New Bug description: on installing and updating system ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: ayatana-indicator-messages 22.9.0-1 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Sat Jan 28 10:10:04 2023 ExecutablePath: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service InstallationDate: Installed on 2023-01-28 (0 days ago) InstallationMedia: Ubuntu-MATE 23.04 "Lunar Lobster" - Alpha amd64 (20221204) ProcCmdline: /usr/libexec/ayatana-indicator-messages/ayatana-indicator-messages-service ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7415c47547 : mov(%rax),%r12 PC (0x7f7415c47547) ok source "(%rax)" (0x55ad0002) not located in a known VMA region (needed readable region)! destination "%r12" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ayatana-indicator-messages StacktraceTop: g_type_check_instance_cast () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libaccountsservice.so.0 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ayatana-indicator-messages-service crashed with SIGSEGV in g_type_check_instance_cast() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ayatana-indicator-messages/+bug/2004070/+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 1983794] Re: Evolution not deleting autosave files
Updated packages from proposed repository. In a quick first test, the bug has not shown up. If it does not appear next days, we may consider the issue as solved. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcanberra in Ubuntu. https://bugs.launchpad.net/bugs/1983794 Title: Evolution not deleting autosave files Status in Evolution: Fix Released Status in evolution package in Ubuntu: Invalid Status in libcanberra package in Ubuntu: Fix Released Status in libcanberra source package in Jammy: Fix Committed Status in evolution source package in Kinetic: New Status in libcanberra source package in Kinetic: Fix Committed Bug description: [ Impact ] Autosave files are not removed from evolution local state directories (and windows leaked) [ Test case ] 1. Open evolution, and start to compose a new email 2. Write enough text and wait few minutes so that this command returns a file ls -l ~/.local/share/evolution/.evolution-composer.autosave-* 3. Close the email composer window, hitting "Do not save" 4. ls -l ~/.local/share/evolution/.evolution-composer.autosave-* should list no files 5. Opening and closing again evolution should not ask to restore the previous email [ Regression potential ] No sounds could be performed during some UI actions --- Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1 was installed with the distribution on a new system and received settings imported from an earlier version on another computer. When composing an email, if the process takes long enough an autosave file is created as ~/.local/share/evolution/.evolution- composer.autosave-xx ("xx" is a random 6 character string). When the email is successfully sent, the autosave file SHOULD be deleted. It's not. When evolution is shut down and restarted I'm asked if I want to recover an unfinished email. Answering No to this will delete the autosave file, but otherwise it persists and the recovery query recurs the next time I open evolution. Other people are having the same issue, see https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome people aren't dealing with it, perhaps considering it a distro- specific bug. On a system used by many people this is a potential security issue. To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1983794/+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