[Desktop-packages] [Bug 2048438] Re: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2048438 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2048438 Title: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop Status in xwayland package in Ubuntu: New Bug description: I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated GPU. I installed Ubuntu 23.10, and it defaults to using Wayland and connected it to an external Dell Dell P2720D monitor via HDMI. The UI under Settings > Displays then "Mirror", the default setting works, and I see the display duplicated as expected, with the large external monitor having a low resolution limited to that of the laptop. But if I switch to "Join" does not allow to Apply with message: > Changes Cannot be Applied. This could be due to hardware limitations. Logging off and changing to X allows "Join" to work, so it is a Wayland issue. Is there a way to make it work on Wayland? Mostly out of morbid curiosity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2048438/+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 2048441] Re: Firefox cannot save/read a credit card number
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2048441 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2048441 Title: Firefox cannot save/read a credit card number Status in firefox package in Ubuntu: New Bug description: Firefox has a functionality to save and auto-fill credit cards. Saving can be done when entering the information of a card in a web page, or in Settings/Privacy & Security/Saved Credit Cards. Currently, with Kubuntu's version of Firefox 118.0.2, nothing happens when saving. In the "Browser Console" of Firefox, when saving from the Settings menu, I get the following message: NS_ERROR_ABORT: User canceled OS unlock entry encrypt resource://gre/modules/OSKeyStore.sys.mjs:320 editDialog.js:232:15 If the same is done with the non-snap version downloaded from Mozilla, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048441/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
Does it seem correct to say that the general intention of irqbalance wrt to system performance is to improve throughput (translating in some cases to a more responsive system) at a cost of increased processing latency? If so, then it should be considered and tuned generally with regards to usage scenarios that consider latency vs throughput. Eg digital audio workstations and gaming machines might disable it. But as Steve says, we don't have any data on the tradeoffs. How much more throughput/responsiveness for what cost in latency under what configurations? All I can find is a recommendation not to use it on CPUs with 2 or fewer cores as the overhead is said to be too high (which acc to above would translate to "unreasonable amount of latency for relatively little or even no throughput gains"), but even then, are we talking physical or logical/virtual cores? It seems like the more cores a system has, the more trivial the overhead from running irqbalance per performance/responsiveness gain. Is there a threshold number of cores beyond which something like IRQ balance becomes strongly recommended for general computing applications? But even then just like power scaling I can imagine it might still add undesirable or even critical latency in applications that are highly latency sensitive (eg when milliseconds or fractions of milliseconds matter) This website gave me some clarity on the theory and purpose: https://www.baeldung.com/linux/irqbalance-modern-hardware There is another dimension, one related to one of the reasons why Apple became known as the "AV professional's workstation" for so long, is that (apparently for fascinating reasons of a historical accident) the multimedia system engineers gained enough influence in the company to allow them to tune the default system configuration to prioritize latency and then system responsiveness over throughput (and even some compromises in system security) to allow for minimal system config in applications requiring both low and consistent (eg low jitter) latency. As it turned out, they got away with doing this for so many years in part because the growing "AV professional wannabe" crowd who just used the system mostly for general (rather than low latency sensitive) applications didn't really notice or care about the hit to throughput or security vulnerability. Noticeable in benchmarks, but not in real life. My first point in saying this is that benchmarks don't necessarily tell us what will give the greatest benefit to the greatest number of users with minimal or no reconfiguration. Eg, who cares if it takes even 10% more milliseconds to transcode an AV file or compile code (on same hardware configred differently) if it means you could also run latency sensitive apps at a consistent (low jitter) amd low latency without having to reconfigure anything and maintaining a generally responsive system? People often just walk away from that anyway (either physically, eg smoke or coffee break, or figuratively, eg task switching, in which case a responsive system would be a higher priority than crunching the numbers slightly faster). My second point is I think obsession over benchmarking risks losing the forest through the trees and really often doesn't account for anything close to real world performance optimizations. But even then it could be argued this is only because we fail to consider important parameters in common performance benchmarks, such as "responsiveness" and "jitter" and "latency" alongside obsessing over throughput and to a lesser extent power management. For me, the core of this question means finally coming to clarity about what "optimal balance" means for the widest variety of desktop and server applications, just as Apple did accidentally a few decades ago with its client systems I think this requires considering a variety of factors instead of an unrealistically narrow idea of "performance" that does not factor in real world user experience. Eg the idea that most users often will appreciate improvements in latency and responsiveness without really much noticing the cost of throughput until someone starts obsessing over throughput benchmarks with relatively minute differences as far as our intuitive or subconscious experience is concerned. Less user frustration from fewer to no buffer overruns or perceived interface hiccups again draw on concepts such as "reliability" and "default breadth of utility" FWIW I think a lot of throughput obsession is about internalized and institutionalized planned obsolescence. It's the primary benchmark of OEM system performance, and a fairly lazy way to measure performance at that. 4min 30sec for a transcoded file would be considered hugely different than 5min 30sec on the same hardware, but for the average user who would just take a smoco break or switch tasks it doesn't matter as long as the system remains responsive and functional. And you'll never get to the transcoding in the first place if the system
[Desktop-packages] [Bug 2039866] Re: I cannot use two screens on the Ubuntu system.
[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/2039866 Title: I cannot use two screens on the Ubuntu system. Status in gnome-shell package in Ubuntu: Expired Bug description: I cannot use two screens on the Ubuntu system. It was very good, and there were no problems with it. Only three days ago, I received a new notification regarding an update. I updated, and since then, the second screen has stuck and I cannot interact with it in any way. As a temporary solution, I With it, I disconnect the screen and connect it again, it works for no more than 10 minutes, then it hangs again, and I have to restart it again. I am fed up, but there are many updates that I received after that, and I say that perhaps this time this problem will be fixed, but no Something is going on, please help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2039866/+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 2042931] Re: Crashing frequently
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/2042931 Title: Crashing frequently Status in nautilus package in Ubuntu: Expired Bug description: Crashing frequetnly ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 Uname: Linux 5.15.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 7 11:31:46 2023 GsettingsChanges: InstallationDate: Installed on 2022-09-07 (425 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=en_IN:en TERM=xterm-256color PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2042931/+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 1833322] Re: Consider removing irqbalance from default install on desktop images
Hi Christian, I see a lot of strong opinions being given, but aside from the "don't use it in KVM" guidance which appears to be based on GCE's engineering expertise, very little evidence that irqbalance is actually a problem. I think it's true that in the default config, irqbalance can interfere with putting CPUs into higher C states to conserve power. However, I don't see any indication of quantitative analysis showing the impact. Recent versions of irqbalance have a '--powerthresh' argument that can be used to tell irqbalance to rebalance across fewer cores when CPU load is low, to allow some of the cores to be put into a sleep state and conserve power. My own initial testing on my desktop shows that this gets used for all of about 10 seconds at a time every few hours, before the load increases and irqbalance wakes the core back up... I would want any decision to remove irqbalance from the desktop to be based on evidence, not conjecture. At a minimum, I think what I would like to see is output from powertop showing both power consumption and CPU idle stats over a reasonable amount of time (10 minutes?), on a representative client machine, for a 2x3 matrix of configurations: - idle vs normal desktop load - irqbalance disabled vs irqbalance enabled with defaults vs irqbalance enabled with IRQBALANCE_ARGS=--powerthresh=1 System should be rebooted between each of the irqbalance configurations, as I'm not sure what does or doesn't persist in the CPU config after irqbalance exits. I am specifically not going to try to rebut the various webpages referenced here, beyond saying that there's an awful lot of these pages pointing to one other as authoritative sources on irqbalance without there actually being evidence to back them up (and a heaping spoonful of misinformation / outdated information along the way). So if we're going to make a change, there should be due diligence to demonstrate a benefit, it should not be based on Internet hype. -- 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/1833322 Title: Consider removing irqbalance from default install on desktop images Status in irqbalance package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 2048448] [NEW] Problems with icons in the gnome dock.
Public bug reported: When i move a icon into the dock, this one overlaps another icons and sometimes doesn't move in the position that i want. The error is in Ubuntu 23.10 Steps for reporduce: 1 - Open some aplications 2 - Pin into the dock 3 - Try to move the aplication to another position. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jan 6 22:44:08 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-01-06 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Attachment added: "Bug screenshot" https://bugs.launchpad.net/bugs/2048448/+attachment/5737093/+files/Screenshot%20from%202024-01-06%2022-32-17.png ** Summary changed: - Problems with icons in the application dock. + Problems with icons in the gnome dock. -- 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/2048448 Title: Problems with icons in the gnome dock. Status in gnome-shell package in Ubuntu: New Bug description: When i move a icon into the dock, this one overlaps another icons and sometimes doesn't move in the position that i want. The error is in Ubuntu 23.10 Steps for reporduce: 1 - Open some aplications 2 - Pin into the dock 3 - Try to move the aplication to another position. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Jan 6 22:44:08 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-01-06 (0 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0 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/2048448/+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 2048447] [NEW] Stylus becomes non-functional quickly after first use with X.
Public bug reported: I believe this is a gnome shell or perhaps libmutter bug. I am having trouble using Krita, gimp, and xournalpp with my stylus pen on several laptops, a Lenovo Yoga 260, a couple of Fujitsu Lifebooks including the T935 and the U729X. It all seems to work fine under Wayland, but not on X. It works with lxde, and lxqt and kde just fine, but not Gnome Shell. This happened when I moved from Ubuntu 23.04 to 23.10. There was a recent update to libmutter that chaned the behavior and made it a tad better, but still broken (Now it works for the first stroke, but not thereafter.) There is a bug report I made for Xorg, when I thought it was maybe in Xorg here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input- libinput/+bug/2043215 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 [modified: usr/share/applications/org.gnome.Shell.desktop] ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 6 16:03:30 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-12-09 (394 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-14 (85 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2048447 Title: Stylus becomes non-functional quickly after first use with X. Status in gnome-shell package in Ubuntu: New Bug description: I believe this is a gnome shell or perhaps libmutter bug. I am having trouble using Krita, gimp, and xournalpp with my stylus pen on several laptops, a Lenovo Yoga 260, a couple of Fujitsu Lifebooks including the T935 and the U729X. It all seems to work fine under Wayland, but not on X. It works with lxde, and lxqt and kde just fine, but not Gnome Shell. This happened when I moved from Ubuntu 23.04 to 23.10. There was a recent update to libmutter that chaned the behavior and made it a tad better, but still broken (Now it works for the first stroke, but not thereafter.) There is a bug report I made for Xorg, when I thought it was maybe in Xorg here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input- libinput/+bug/2043215 ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.1-0ubuntu1 [modified: usr/share/applications/org.gnome.Shell.desktop] ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3 Uname: Linux 6.5.0-14-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 6 16:03:30 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-12-09 (394 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.2-0ubuntu2~really45.0 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-10-14 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2048447/+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 2043215] Re: Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in Xorg.
Okay, so this does not seem to be an xorg bug. I believe it is a Gnome
Shell bug. If I use lxqt it works fine. It should probably be moved
there. Perhaps the above fix to mutter did not completely fix it all,
but at least xorg seems to be off the hook. :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2043215
Title:
Since upgrading to Ubuntu 23.10, the stylus (pen) does not work in
Xorg.
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Bug description:
There is more information on this issue:
https://github.com/xournalpp/xournalpp/issues/5303
and the other bug report that is linked there.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 10 07:17:22 2023
DistUpgraded: 2023-11-06 20:32:35,715 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus:
virtualbox/7.0.10, 6.2.0-36-generic, x86_64: installed
virtualbox/7.0.10, 6.5.0-10-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA
controller])
Subsystem: Fujitsu Limited. HD Graphics 5500 [10cf:1898]
InstallationDate: Installed on 2021-05-25 (899 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-10-generic
root=UUID=ce1b5a3a-3fee-4143-a385-d16e7d44c53a ro i8042.notimeout i8042.nomux
quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to mantic on 2023-11-07 (3 days ago)
dmi.bios.date: 12/21/2015
dmi.bios.release: 1.15
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.15
dmi.board.name: FJNB288
dmi.board.vendor: FUJITSU
dmi.board.version: D2
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias:
dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.15:bd12/21/2015:br1.15:svnFUJITSU:pnLIFEBOOKT935:pvr:rvnFUJITSU:rnFJNB288:rvrD2:cvnFUJITSU:ct10:cvr:sku:
dmi.product.name: LIFEBOOK T935
dmi.sys.vendor: FUJITSU
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.17-2build1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/2043215/+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 2048441] [NEW] Firefox cannot save/read a credit card number
Public bug reported: Firefox has a functionality to save and auto-fill credit cards. Saving can be done when entering the information of a card in a web page, or in Settings/Privacy & Security/Saved Credit Cards. Currently, with Kubuntu's version of Firefox 118.0.2, nothing happens when saving. In the "Browser Console" of Firefox, when saving from the Settings menu, I get the following message: NS_ERROR_ABORT: User canceled OS unlock entry encrypt resource://gre/modules/OSKeyStore.sys.mjs:320 editDialog.js:232:15 If the same is done with the non-snap version downloaded from Mozilla, it works. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/2048441 Title: Firefox cannot save/read a credit card number Status in firefox package in Ubuntu: New Bug description: Firefox has a functionality to save and auto-fill credit cards. Saving can be done when entering the information of a card in a web page, or in Settings/Privacy & Security/Saved Credit Cards. Currently, with Kubuntu's version of Firefox 118.0.2, nothing happens when saving. In the "Browser Console" of Firefox, when saving from the Settings menu, I get the following message: NS_ERROR_ABORT: User canceled OS unlock entry encrypt resource://gre/modules/OSKeyStore.sys.mjs:320 editDialog.js:232:15 If the same is done with the non-snap version downloaded from Mozilla, it works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2048441/+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 2048438] [NEW] Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop
Public bug reported: I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated GPU. I installed Ubuntu 23.10, and it defaults to using Wayland and connected it to an external Dell Dell P2720D monitor via HDMI. The UI under Settings > Displays then "Mirror", the default setting works, and I see the display duplicated as expected, with the large external monitor having a low resolution limited to that of the laptop. But if I switch to "Join" does not allow to Apply with message: > Changes Cannot be Applied. This could be due to hardware limitations. Logging off and changing to X allows "Join" to work, so it is a Wayland issue. Is there a way to make it work on Wayland? Mostly out of morbid curiosity. ** Affects: xwayland (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2048438 Title: Dual monitor extend (join) not working with Wayland with p14s ThinkPad laptop Status in xwayland package in Ubuntu: New Bug description: I have a Lenovo ThinkPad P14s gen4 amd laptop, which has an integrated GPU. I installed Ubuntu 23.10, and it defaults to using Wayland and connected it to an external Dell Dell P2720D monitor via HDMI. The UI under Settings > Displays then "Mirror", the default setting works, and I see the display duplicated as expected, with the large external monitor having a low resolution limited to that of the laptop. But if I switch to "Join" does not allow to Apply with message: > Changes Cannot be Applied. This could be due to hardware limitations. Logging off and changing to X allows "Join" to work, so it is a Wayland issue. Is there a way to make it work on Wayland? Mostly out of morbid curiosity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2048438/+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 2002978] Re: sh[1111]: /bin/sh: 1: initctl: not found
I just stumbled onto this in Ubuntu 22.04, where this bug still seems to
be present. The issue seems to be in the file
/usr/lib/systemd/user/gnome-keyring-ssh.service which wants to use
initctl which is an Upstart command and no longer exists on systemd
enabled systems. This is the content of the file:
[Unit]
Description=Start gnome-keyring as SSH agent
Before=graphical-session-pre.target ssh-agent.service
PartOf=graphical-session-pre.target
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/sh -ec 'if [ -z "${SSH_AUTH_SOCK}" ] && \
! grep -s -q X-GNOME-Autostart-enabled=false
~/.config/autostart/gnome-keyring-ssh.desktop
/etc/xdg/autostart/gnome-keyring-ssh.desktop; then \
eval $$(/usr/bin/gnome-keyring-daemon --start --components ssh); \
dbus-update-activation-environment --verbose --systemd
SSH_AUTH_SOCK=$$SSH_AUTH_SOCK SSH_AGENT_LAUNCHER=gnome-keyring; \
initctl set-env --global SSH_AUTH_SOCK=$$SSH_AUTH_SOCK || true; \
fi'
ExecStopPost=/bin/sh -ec 'if [ "${SSH_AGENT_LAUNCHER}" = gnome-keyring ]; then \
dbus-update-activation-environment --systemd SSH_AUTH_SOCK=; \
initctl unset-env --global SSH_AUTH_SOCK || true; \
fi'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/2002978
Title:
sh[]: /bin/sh: 1: initctl: not found
Status in gnome-keyring package in Ubuntu:
Fix Released
Bug description:
Just an unexpected error logged, no further issues from this.
/usr/lib/systemd/user/gnome-keyring-ssh.service from
gnome-keyring=40.0-3ubuntu3 (22.04.1) calls initctl from a systemd user service.
Looks like 42.1-1 sets SSH_AUTH_SOCK without such user unit, so the problem
may be resolved in current versions (though not in LTS).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/2002978/+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 1116421] Re: Ethernet mac address resets when cable unplugged
This bug needs to be forwarded to, reported upstream against Network Manager (NM) otherwise chances that it will ever get fixed are even lower if it is only reported here. -- 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/1116421 Title: Ethernet mac address resets when cable unplugged Status in network-manager package in Ubuntu: Confirmed Bug description: I'm not exactly sure if this is a network-manager bug, but if not perhaps you could point me in the right direction (or tell me how to find out what the right direction is).. A friend running 12.10 and myself running 12.04.1 both experienced the same problem. Using the following series of commands to change the ethernet MAC address works fine under some specific circumstances: ifconfig eth0 down ifconfig eth0 hw ether xx:xx:xx:xx:xx:xx ifconfig eth0 up If there is a wired connection defined in the network-manager gui (click the wireless signal-> Edit Connections...) and there is a Cloned Mac Address defined in there, the MAC address of eth0 WILL REVERT to it's original (hardware) MAC address upon connection of an ethernet cable. This is very strange and frustrating. In order for the above MAC address changes to take effect, there needs to be nothing filled in with the GUI. Second issue (I guess it is related) is that if everything is working correctly, the MAC address WILL REVERT to it's original (hardware) MAC address upon DISconncetion of the ethernet cable. Perhaps I am doing something horribly, horribly wrong here, but it's frustrating and hours of searching the forums have not given me any indication of the correct place/time to change MAC address. If network-manager does not want to respect the changes I have requested, then it should at least provide a functioning, documented alternative method in order to make the same change. What I would expect: Changing the MAC address of eth0 using the network-manager gui will actually change the MAC address everytime the interface is brought up. Current workaround: In /etc/rc.local, run the above commands for changing hardware address In /etc/network/if-post-down.d/ create a script that will sleep for 5 seconds and then run the above commands. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu4.2 ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24 Uname: Linux 3.2.0-29-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Tue Feb 5 08:15:48 2013 IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) IpRoute: default via 192.168.1.254 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.65 metric 2 MarkForUpload: True NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-02-03T13:48:28.620664 nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH BattlecruiserOperational 61ddc2db-76fa-4c7e-9b11-fc68440e8a47 802-11-wireless 1360080712 Tue 05 Feb 2013 08:11:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/1 magiclab f1b348f9-ff96-4729-b690-dcdb69c729e5 802-11-wireless 1360014380 Mon 04 Feb 2013 01:46:20 PM PSTyes no /org/freedesktop/NetworkManager/Settings/7 ubcsecure a141ff8b-b47f-47a4-81be-c01335b9aa0a 802-11-wireless 1360034251 Mon 04 Feb 2013 07:17:31 PM PSTyes no /org/freedesktop/NetworkManager/Settings/6 Wired connection 1e54ce990-cd66-461c-8343-60f4f099b7ec 802-3-ethernet1360034239 Mon 04 Feb 2013 07:17:19 PM PSTyes no /org/freedesktop/NetworkManager/Settings/5 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled
[Desktop-packages] [Bug 2048433] [NEW] scanning from ADF on Epson WF-7710 has page offset
Public bug reported: Scanning from the ADF on my Epson WF-7710 produces images with a left margin about 4 times as large as when scanning from the flatbed, so that the right-hand side of the page is lost. Top and bottom margins are handled correctly. The scanner is connected via the local ethernet. Memory tells me that it used to scan ok from the ADF, and that the problem may have started sometime in 2023 - but memory is terribly fallible ... $ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 Synaptic gives the package version as 42.0-1, the latest available. ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/2048433 Title: scanning from ADF on Epson WF-7710 has page offset Status in simple-scan package in Ubuntu: New Bug description: Scanning from the ADF on my Epson WF-7710 produces images with a left margin about 4 times as large as when scanning from the flatbed, so that the right-hand side of the page is lost. Top and bottom margins are handled correctly. The scanner is connected via the local ethernet. Memory tells me that it used to scan ok from the ADF, and that the problem may have started sometime in 2023 - but memory is terribly fallible ... $ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 Synaptic gives the package version as 42.0-1, the latest available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/2048433/+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 2035076] Re: Can't enter capital accented letters with Caps Lock on Wayland
OK, it works I've tried version 45.2-0ubuntu3 and can regularly type ÒÀÙÈÉÌ in the text editor, terminal, etc. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-manti ** Tags removed: verification-done-manti ** Tags added: verification-done-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2035076 Title: Can't enter capital accented letters with Caps Lock on Wayland Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Mantic: Fix Committed Status in mutter package in Fedora: Unknown Bug description: Impact -- Capital accented letters can't be entered using CAPS LOCK in the Wayland session Test Case - Open a terminal and install basic French support: sudo apt install language-pack-gnome-fr Open the Settings app. In the sidebar, click Keyboard Click +, choose French (France), then choose the French (AZERTY) keyboard Close the Settings app In the top right of the screen, click en and switch the keyboard layout to French (AZERTY) In the text editor, type é (this is the number 2 key on a US English keyboard). Now, press the Caps Lock key to enable Caps Lock. Press the same key. You should get É What Could Go Wrong --- This fix is included in mutter 45.2 so see the master bug for this upstream update: LP: #2043000 Original bug report --- Most programs don't recognize Italian accented capital letters. When "Caps Lock" is on àèìòù should be written as ÀÈÌÒÙ... but for some reasons they are not capitalized. I've noticed that everything works fine using the Live session which still uses X11 session. It looks there's no problem with programs that use xwayland like Gimp and MarkText. WORKAROUND === In "Settings -> Keyboard" it's possible to set a "compose key". For example I've selected the [Super left] key. If I want to compose È I press and immediately release each key: [Super left] + [E] + [Alt Gr] + ['] If you want É: [Super left] + [E] + ['] Do the same for the other vowels. === ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-text-editor 45~beta-1 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 11 11:48:41 2023 InstallationDate: Installed on 2023-09-07 (4 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230906.3) ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-text-editor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2035076/+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 2048398] Re: Unable to change audio volume for the speakers
Hi @guiverc for your suggestion. I think this is indeed a bug since I searched extensively on the internet and I found several people with the same problem, but I haven't found any solution so far. Actually, some time ago I opened a question on askubuntu (link: https://askubuntu.com/questions/1485233/lenovo- yoga-7i-intel-i7-13700h-cannot-change-volume-on-the-speakers, https://askubuntu.com/questions/1466286/lenovo-yoga-slim-7-pro-volume- cannot-be-changed, ...) I've been using this PC since November, so it's not a fresh install. However, I encountered the problem since the first usage bet report here only now, so yeah, this "bug" is from a fresh installation of 23.04 The package in question is pulseaudio, I've updated the bug description. ** Package changed: ubuntu => pulseaudio (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2048398 Title: Unable to change audio volume for the speakers Status in pulseaudio package in Ubuntu: New Bug description: Hi everyone, from a fresh install of Ubuntu 23.04, I cannot change the audio volume for the speakers. Formally, the audio is either at minimum (lowest part of the volume control bar) or at maximum (every other part of the audio control bar). I can mute the speakers. However, audio works perfectly for headphones. The Bluetooth pairing is instant, and I can change the volume. HW information for the audio device is the following: Audio: Device-1: Intel vendor: Lenovo driver: sof-audio-pci-intel-tgl bus-ID: 00:1f.3 Sound API: ALSA v: k6.2.0-39-generic running: yes Sound Server-1: PulseAudio v: 16.1 running: no Sound Server-2: PipeWire v: 0.3.65 running: yes Other info: System: Kernel: 6.2.0-39-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 44.3 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: LENOVO product: 82Y7 v: Yoga Pro 7 14IRH8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2048398/+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 2048398] [NEW] Unable to change audio volume for the speakers
You have been subscribed to a public bug: Hi everyone, from a fresh install of Ubuntu 23.04, I cannot change the audio volume for the speakers. Formally, the audio is either at minimum (lowest part of the volume control bar) or at maximum (every other part of the audio control bar). I can mute the speakers. However, audio works perfectly for headphones. The Bluetooth pairing is instant, and I can change the volume. HW information for the audio device is the following: Audio: Device-1: Intel vendor: Lenovo driver: sof-audio-pci-intel-tgl bus-ID: 00:1f.3 Sound API: ALSA v: k6.2.0-39-generic running: yes Sound Server-1: PulseAudio v: 16.1 running: no Sound Server-2: PipeWire v: 0.3.65 running: yes Other info: System: Kernel: 6.2.0-39-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME v: 44.3 Distro: Ubuntu 23.04 (Lunar Lobster) Machine: Type: Laptop System: LENOVO product: 82Y7 v: Yoga Pro 7 14IRH8 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- Unable to change audio volume for the speakers https://bugs.launchpad.net/bugs/2048398 You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio 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
