[Desktop-packages] [Bug 1721401] Re: eog fails to open png: Failed to register: Timeout was reached
Just for reference, i ran into this problem once again tonight (2021-07-30) on one of my xubuntu 20.04 systems. In this particular case it was due to running another copy of eog under gdb (which somehow made it out-of-reach to killall, and which i had forgotten about). I don't think this is what happened on 2021-05-25, because i didn't have the need to really hack into eog at that time. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1721401 Title: eog fails to open png: Failed to register: Timeout was reached Status in eog package in Ubuntu: Confirmed Bug description: eog fails to open PNG file. After about 25 seconds, it gives up and says: Failed to register: Timeout was reached You can find the relevant image at: https://www.dropbox.com/s/psrm3wj1n480ocx/FIDUCEO_FCDR_L1C_HIRS2_noaa14_2101144729_2101162929_easy_v0.7_fv0.4.png?dl=0 Ubuntu 16.04.2 LTS, GNOME Image Viewer 3.18.2. I expect it to display the image. Instead it fails with the above message. Image Magicks "display" utility shows the image fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1721401/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Do you need to update the sof-firmware apart from changing the kernel? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1930119] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1930119 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Expired Bug description: i am install chromium browser but show some unwanted error ProblemType: Package DistroRelease: Ubuntu 21.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.11.0-1008.8-raspi 5.11.12 Uname: Linux 5.11.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: chromium-browser:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 25 19:57:47 2021 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 ImageMediaBuild: 20210421 Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1930119/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
So, the overall steps would be make a clone of https://github.com/thesofproject/linux.git and run following commands ``` sudo apt install build-essential sudo apt-get build-dep linux-image-`uname -r` #(the running kernel) ``` and after that copied over current cofig Removed --> #CONFIG_SYSTEM_TRUSTED_KEYS sudo make menuconfig sudo make clean sudo make deb-pkg LOCALVERSION=-custom KDEB_PKGVERSION=$(make kernelversion) -1 Will this be sufficient -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1892454] Re: [MIR] libostree-1-1
I reviewed ostree 2020.8-2 as checked into hirsute. This shouldn't be considered a full audit but rather a quick gauge of maintainability. I didn't make any effort to find which portion of the sources correspond with the exact binary package that is under discussion. ostree is a tool to manage giant farms of hardlinks and boot configurations with a goal of providing transactional system updates, complete with chain-of-trust using gpg. I did not inspect ostree from this perspective at all -- the security team is not interested in supporting ostree as a system management tool. - CVE History: None in our database - Build-Depends? Includes gpg, libgpgme-dev, among others - pre/post inst/rm scripts? The ostree and ostree-boot package maintainer scripts have some dracut and grub configuration file handling, systemd service management, and will update the initrams - init scripts? None - systemd units? Not inspected, only in ostree-boot and ostree-tests - dbus services? None - setuid binaries? None - sudo fragments? None - polkit files? None - udev rules? None - unit tests / autopkgtests? Some tests run during the build, not inspected - cron jobs? None - Build logs: A lot of doc warnings; nothing code-related stood out - Processes spawned? A lot of process spawning; some using arrays, some using strings with quoted filenames (presumably so the user could put pipelines into EDITOR or VISUAL environment variables) - Memory management? Stack allocation is used a lot more often than I'd like. Because it's C, there's necessarily a lot of memory management and some of it is very fiddly. I'm pretty sure I found bugs, though maybe they just lead to crashes and memory leaks. - File IO? Extensive file IO -- some file operations rely upon umask having a sane value for the files to have sane permissions. File paths come from packages. A lot of operations are done on files as instructed by whatever is the equivalent of packages -- xattrs, setuid/setgid bits, etc. It's basically a full package manager tool. The inputs must be safe. - Logging? Extensive logging; I did spot-checks and didn't find errors. - Environment variable usage? Moderate use, some are validated and some are used as-is without any verification at all. Probably fine. - Use of privileged functions? Extensive. ostree is a general system management tool. Spot checks of calls looked careful but I did not do full call hierarchy checks to see if all inputs to privileged functions were properly sanitized. - Use of cryptography / random number sources etc? Uses an embedded soup to do some https validation. It wasn't obvious that it's correct but it did go to effort to pass the system CA store, so someone at least tried. - Use of temp files? I'm slightly worried about the random number use for XX files; it is using non-cryptographic tool. It's probably fine and I'm a worry-wart. - Use of networking? Yes, some, I didn't closely inspect it. What I did see looked primarily client-oriented rather than server-oriented - Use of WebKit? None - Use of PolicyKit? None - Any significant cppcheck results? None - Any significant Coverity results? Some issues, maybe just crashes, but might be worse. A lot of false positives. - Any significant shellcheck results? None - Any significant bandit results? None Security team ACK for promoting strictly libostree-1-1 to main and with the understanding that we're not supporting the ostree system management in any way. I've elided the notes I made while reading this, pending feedback from Red Hat's security team. I don't like that there's no listed way to report security issues. Thanks ** Changed in: ostree (Ubuntu) Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned) ** Changed in: ostree (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1892454 Title: [MIR] libostree-1-1 Status in ostree package in Ubuntu: In Progress Bug description: Many applications have Flatpak integration using libflatpak. The Ubuntu desktop team would like libflatpak in main so we can easily build such applications (LP: #1812456). libostree-1-1 is a dependency of this, so it would also need to be in main. We don't need OSTree functionality, and do not expect any other OSTree packages to be installed by default. Availability In Universe, builds for all architectures and in sync with Debian. Rationale = Required for libflatpak0 being in main (LP: #1812456) Security This will need a Security review. Quality Assurance = Should be subscribed to by Ubuntu Desktop Bugs. Contains a single .so and doesn't have any debconf prompts. Package is maintained in Debian. No major bugs in Debian or Ubuntu.
[Desktop-packages] [Bug 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
Since I hadn't yet added the extra dependencies to gnome-shell- extension-desktop-icons, I set "verification-failed-focal" and "verification-failed-hirsute" for now, so they don't get accidentally moved to -updates. (It doesn't mean there is anything wrong with the -ng package in hirsute-proposed, but there is no tag available to specify the package...) I'll upload gnome-shell-extension-desktop-icons to experimental/impish again with the extra dependencies, and propose new SRUs for hirsute and focal. ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-failed-focal verification-failed-hirsute ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: Fix Committed => In Progress ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: Fix Committed => In Progress ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Impish) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: In Progress Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Impish: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1923845] Re: Please compress packages with zstd by default
This bug was fixed in the package diffoscope - 179 --- diffoscope (179) unstable; urgency=medium * Ensure that various LLVM tools are installed, even when testing whether a MacOS binary has zero differences when compared to itself. (Closes: reproducible-builds/diffoscope#270) -- Chris Lamb Fri, 30 Jul 2021 09:05:01 +0100 ** Changed in: diffoscope (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream-glib in Ubuntu. https://bugs.launchpad.net/bugs/1923845 Title: Please compress packages with zstd by default Status in appstream-glib package in Ubuntu: New Status in apt package in Ubuntu: Fix Released Status in aptly package in Ubuntu: New Status in boinc package in Ubuntu: New Status in busybox package in Ubuntu: New Status in cdebootstrap package in Ubuntu: New Status in cdist package in Ubuntu: New Status in debdelta package in Ubuntu: New Status in debian-el package in Ubuntu: New Status in debootstrap package in Ubuntu: Fix Released Status in debsig-verify package in Ubuntu: New Status in debsigs package in Ubuntu: New Status in diffoscope package in Ubuntu: Fix Released Status in dpkg package in Ubuntu: Fix Released Status in dpkg-sig package in Ubuntu: New Status in file package in Ubuntu: New Status in hello package in Ubuntu: Fix Released Status in libsolv package in Ubuntu: New Status in lintian package in Ubuntu: Fix Released Status in lutris package in Ubuntu: New Status in obs-build package in Ubuntu: New Status in osc package in Ubuntu: New Status in radare2 package in Ubuntu: New Status in reprepro package in Ubuntu: Fix Released Status in vim-scripts package in Ubuntu: New Status in zeroinstall-injector package in Ubuntu: New Status in reprepro source package in Focal: Fix Released Status in reprepro source package in Groovy: Fix Released Status in reprepro source package in Hirsute: Fix Released Status in debian-el package in Debian: New Bug description: https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built on Hirsute having both data and control members of the .deb being compressed with zstd. It can be handy for testing various tools. [dpkg] Decompression support in dpkg landed first in Bionic and is being SRUd to Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the zstd-compressed binary packages. From dpkg's perspective the upgrade path is cleared. The original plan was compressing only the internal data.tar .deb member, but dpkg uses uniform compression by default since dpkg 1.19.0 thus I'm collecting all the changes to support control.tar.zst, too, in this bug. Reviewed packages from: https://codesearch.debian.net/search?q=data.tar.xz=1=1 https://codesearch.debian.net/search?q=control.tar.xz=1=1 appstream-glib - needs fix: libappstream-builder/asb-package-deb.c aptly - needs fix: deb/deb.go boinc - needs fix: debian/fetch_example_applications.sh busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c cdebootstrap- needs fix: src/package.c cdist - may need fix, can use dpkg-deb: cdist/preos/debootstrap/files/devuan-debootstrap/functions debdelta- needs fix: debdelta debpatch.sh debian-el - needs fix: deb-view.el debian-handbook - needs fix, maybe later, for Debian debootstrap - needs fix, https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54 debsigs - needs fix, debsigs debsig-verify - needs fix, src/debsig-verify.c diffoscope - needs fix, diffoscope/comparators/deb.py dpkg- needs fix, change default dpkg-sig- needs fix, dpkg-sig dpmb- needs fix, maybe later, for Debian elfutils- may need fix, uses dpkg-deb if it is available, does not handle .gz either file- needs fix, magic/Magdir/archive libsolv - needs fix, ext/repo_deb.c lintian - needs fix malformed-deb-archive lutris - needs fix, lutris/util/extract.py obs-build - needs fix Build/Deb.pm osc - needs fix osc/util/debquery.py control.tar.zst only python-apt - needs fix apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall() radare2 - needs fix reprepro- needs fix, debfile.c vim-scripts - needs fix debPlugin/autoload/deb.vim winetricks - needs fix when Debian switches src/winetricks zeroinstall-injector - needs fix src/zeroinstall/archive.ml acr - skip, does not _have to_ be fixed, just creates packages, see dist/deb_hand.mak alien - skip, uses dpkg-deb to extract .deb ansible - not affected, just test data in dbdata.tar.xz anthy - not affected, just changelog entry apt - seems fixed
[Desktop-packages] [Bug 1938596] Re: Always on top windows obscure context menus and tooltips
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 1938596 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. A screen capture, ideally also highlighted with your issue, may have helped explain and thus help us to better understand your issue. I've changed package to gnome-shell based on your last line. ** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1938596 Title: Always on top windows obscure context menus and tooltips Status in gnome-shell package in Ubuntu: New Bug description: "Always on top" windows are meant to be on top of other non-transient windows (its peers), but they're also on top of other windows' transient GUI components like context menus and tooltips. It is not constructive to obscure menus and tooltips with always on top windows any more than it is helpful to obscure the actual mouse cursor with AOT windows. They are short lived. Users can't decide where to place them. They will disappear by themselves when the user is done with them. A hidden tooltip or context menu helps no one. ubuntu 21.04 gnome wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1938596/+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 1938596] [NEW] Always on top windows obscure context menus and tooltips
You have been subscribed to a public bug: "Always on top" windows are meant to be on top of other non-transient windows (its peers), but they're also on top of other windows' transient GUI components like context menus and tooltips. It is not constructive to obscure menus and tooltips with always on top windows any more than it is helpful to obscure the actual mouse cursor with AOT windows. They are short lived. Users can't decide where to place them. They will disappear by themselves when the user is done with them. A hidden tooltip or context menu helps no one. ubuntu 21.04 gnome wayland ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- Always on top windows obscure context menus and tooltips https://bugs.launchpad.net/bugs/1938596 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
Hello jeremyszu, or anyone else affected, Accepted gnome-shell-extension-desktop-icons into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/20.04.0-3~ubuntu20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
Hello jeremyszu, or anyone else affected, Accepted gnome-shell-extension-desktop-icons into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons/20.04.0+git20200908-5ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
Hello jeremyszu, or anyone else affected, Accepted gnome-shell-extension-desktop-icons-ng into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-shell-extension-desktop- icons-ng/0.15.0-0ubuntu4.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: Fix Committed Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
Per https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging the preferred version number here is 20.04.0+git20200908-5ubuntu0.1, not 20.04.0+git20200908-6~ubuntu21.04.1, despite the contents being equivalent to the 20.04.0+git20200908-6 in impish. I am reuploading with a fixed-up changelog for cleanliness. Also, please do not point Vcs-Git for Ubuntu packages at repositories that are not writable by everyone who has upload rights to the package. There are many schemas you can use to host such branches in launchpad, writable by ~ubuntu-dev. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Focal: In Progress Status in gnome-shell-extension-desktop-icons source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons-ng source package in Hirsute: In Progress Status in gnome-shell-extension-desktop-icons source package in Impish: Fix Released Status in gnome-shell-extension-desktop-icons-ng source package in Impish: Fix Released Bug description: == SRU Justification == [Impact] Double tap desktop icons on a touchscreen barely works. [Fix] Because tapping isn't as precise as clicking, ignore the double click distance as long as the icon is tapped. [Test] Roughly double tap the desktop icon and nothing happens. After applying the fix, double tap can 100% open the app or directory. [racb] Since single click code is also being adjusted, please also test that single clicking behaviour has not changed. [racb] Since clicking with modifiers (holding Shift and/or Ctrl) is also being adjusted, please also test that modifier clicking behaviour has not changed. [Where problems could occur] If the new code throws any exception, clicking can also be affected. == Original Bug Report == Double-clicks touchscreen on HiDPI system, sometime it will not be detected. Here is a related patch on upstream https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1487 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1917010/+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 1938588] Re: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
** Package changed: linux (Ubuntu) => ubuntu-meta (Ubuntu) ** Tags added: rls-ii-incoming -- 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/1938588 Title: Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata Status in ubuntu-meta package in Ubuntu: New Bug description: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1938588/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Thanks @mblack154 its working now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1938588] [NEW] Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata
You have been subscribed to a public bug: We have several factory-fresh Mitac industrial motherboards (https://www.mitacmct.com/IndustrialMotherboard_PH13FEI_PH13FEI) that we are unable to install Ubuntu Server 18.04.5 on. When we boot from the installation media we get the following error and the installation hangs (see attached screenshot, I've transcribed the error below too) ``` [0.00] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x52 (or later) [0.157025] ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-241) ``` Googling the microcode bug, the normal advice appears to be "boot into an older, functioning kernel, update the `intel-microcode` package, and then reboot." But in this situation there is no older kernel to boot into; there is no OS installed _at all_ on these boards yet. I'm booting from a USB drive loaded with the latest version of Ubuntu Server 18.04. The only work-around I've found that works so far is to install Ubuntu Desktop 18.04, which can boot successfully on these boards, perform the minimal desktop installation, then use the desktop install to update the `intel-microcode` package, reboot, and then finally install Ubuntu Server. This is obviously not convenient needing to install a complete desktop OS just so I can update the microcode, and then immediately wiping it to install what I wanted in the first place. I have not tried Ubuntu 20.x or 21.x; I need to use Ubuntu 18.04 because these motherboards are being installed into robots that will be running ROS Melodic (ROS Noetic runs on 20.04, but these robots don't have Noetic support yet). I have tried the following to modify the Ubuntu Server ISO, without success: 1- Adding the microcode to initrd --- I unpacked the contents of the Ubuntu Server ISO, decompressed install/initrd.gz, and used the bash script here https://www.kernel.org/doc/html/latest/x86/microcode.html to add the intel-microcode firmware to the image. Then I recompressed initrd.gz, and rebuild the ISO using xorisso. This did not have any effect: Ubuntu Server still encountered the same error when trying to install. 2- Using initrd from Ubuntu Desktop 18.04.5 -- I downloaded & unpacked Ubuntu Desktop 18.04.5 and replaced Ubuntu Server's install/initrd.gz with Ubuntu Desktop's casper/initrd (updating txt.cfg and grub.cfg to load the uncompressed initrd instead of the .gz that Ubuntu Server normally uses). Then I rebuilt the Ubuntu Server with xorisso again. The resulted in the system booting, but immediately dropping into an initramfs busybox shell, saying boot files were missing. I assume this is because Ubuntu Server uses the `boot=casper` flag in order to boot into the live desktop session. At this point I'm running out of ideas for how to be able to make Ubuntu Server's installation media work with these boards. Ubuntu Desktop has no problem booting on them, so it's obviously something specific to the Ubuntu Server image, but I'm not sure exactly what or how to fix it. If you need any additional information/logs/etc... please let me know and I'll be happy to provide them. Thanks! ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment intel-microcode kernel-bug ubuntu-server -- Ubuntu Server 18.04.5 install fails: TSC_DEADLINE disabled due to errata https://bugs.launchpad.net/bugs/1938588 You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
yes i did. I am doing it all over again just in case if i miss anything. Thank you for the advise @mblack154 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1938584] Re: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card
I just checked it: I could show a newscast from France 24. Both audio and video worked * with firefox * with an alternatively snap-installed Chromium browser. On my trials mentioned above, I also used Version 92.0.4515.107 (Offizieller Build) snap (64-Bit). I thought to have installed it the apt install way, but possibly this is also just another way to really get a snap packet. I was not aware of that. What I could not test that way: On my target system, I uninstalled firefox since I only need one browser. Installing something else is possible on a live system (albeit the installation is only present until shutdown). However, it is only possible as installing does not alter any kernel component which apparently happens sometimes when updating requires a reboot. Anyway: Would it make sense to copy system files from the live system (via a USB stick or directly by mounting the Linux system partition)? -- 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/1938584 Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: This problem came up after installing Xubuntu 20.04.02 on this computer, which used Xubuntu 18.04 before. Ifter installing the system, I installed some programs, among them Sound Switcher Indicator 2.3.6 and I unistalled firefox after I had installed Chromium instead. My first test of Audio/Video: When streaming e.g. from https://www.france24.com/fr/direct, I can see the video part but I hear nothing. I am sure that the loudspeaker is not muted. pavucontrol shows me a blue slider switch. Its tab "playback" shows a varying Chromium playback indicator and the associated fader has influence on the amplitude of the shown intensity. (Note: I am using a German version so my transaltions of the items might be off a bit, still I hpe that it can be understood). I have no HDMI cable connected to the computer and no USB-sound device is plugged into it. The laptop has an internal microphone and an internal loudspeaker. In pavucontrol's tab "output devices" it shows something like "no output devices available" when "only hardware devices" are selected there. In pavucontrol's tab "configuration" I can select nothing. I am quite confident that this is not a hardware bug, because the audio system worked before I upgraded to Xubuntu 20.04.02. I also tried alsamixer. in F2 it offers two cards: 0: PCH and 1: HDMI. When I type 0 there to select the PCH one, nothing happens. If I type 1, nothing happens either (I expected the latter since there is no HDMI-device connected). In the levels above, one of the offered items is highlighted and the selection can be moved by up or down. Most of the files in /proc/asound are empty: $ ls -l /proc/asound insgesamt 0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 cards -r--r--r-- 1 root root 0 2021-07-30 17:46 devices lrwxrwxrwx 1 root root 5 2021-07-30 17:46 HDMI -> card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 hwdep -r--r--r-- 1 root root 0 2021-07-30 17:46 modules dr-xr-xr-x 4 root root 0 2021-07-30 17:46 oss lrwxrwxrwx 1 root root 5 2021-07-30 17:46 PCH -> card0 -r--r--r-- 1 root root 0 2021-07-30 17:46 pcm dr-xr-xr-x 6 root root 0 2021-07-30 17:46 seq -r--r--r-- 1 root root 0 2021-07-30 17:46 timers -r--r--r-- 1 root root 0 2021-07-30 17:46 version Probably this will give a hint (perhaps it is also visible from the automatically collected information). I think I had tried the sound system with the live stick before installation. But I'll repeat that test again and tell you the outcome. Kind regards melolontha ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 30 17:08:50 2021 InstallationDate: Installed on 2021-07-28 (1 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2011
Re: [Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Did you clone the src files from here? https://github.com/thesofproject/linux.git On 7/30/21 1:34 PM, Raish khaitu wrote: > I am getting this error @mblack154: > > BTF: .tmp_vmlinux.btf: pahole (pahole) is not available > Failed to generate BTF for vmlinux > Try to disable CONFIG_DEBUG_INFO_BTF > make[3]: *** [Makefile:1177: vmlinux] Error 1 > make[2]: *** [debian/rules:7: build-arch] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 2 > make: *** [Makefile:1560: deb-pkg] Error 2 > > > Any advise would be helpful. should i just try and disable BTF? > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
I am getting this error @mblack154: BTF: .tmp_vmlinux.btf: pahole (pahole) is not available Failed to generate BTF for vmlinux Try to disable CONFIG_DEBUG_INFO_BTF make[3]: *** [Makefile:1177: vmlinux] Error 1 make[2]: *** [debian/rules:7: build-arch] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 2 make: *** [Makefile:1560: deb-pkg] Error 2 Any advise would be helpful. should i just try and disable BTF? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1938584] [NEW] [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card
Public bug reported: This problem came up after installing Xubuntu 20.04.02 on this computer, which used Xubuntu 18.04 before. Ifter installing the system, I installed some programs, among them Sound Switcher Indicator 2.3.6 and I unistalled firefox after I had installed Chromium instead. My first test of Audio/Video: When streaming e.g. from https://www.france24.com/fr/direct, I can see the video part but I hear nothing. I am sure that the loudspeaker is not muted. pavucontrol shows me a blue slider switch. Its tab "playback" shows a varying Chromium playback indicator and the associated fader has influence on the amplitude of the shown intensity. (Note: I am using a German version so my transaltions of the items might be off a bit, still I hpe that it can be understood). I have no HDMI cable connected to the computer and no USB-sound device is plugged into it. The laptop has an internal microphone and an internal loudspeaker. In pavucontrol's tab "output devices" it shows something like "no output devices available" when "only hardware devices" are selected there. In pavucontrol's tab "configuration" I can select nothing. I am quite confident that this is not a hardware bug, because the audio system worked before I upgraded to Xubuntu 20.04.02. I also tried alsamixer. in F2 it offers two cards: 0: PCH and 1: HDMI. When I type 0 there to select the PCH one, nothing happens. If I type 1, nothing happens either (I expected the latter since there is no HDMI- device connected). In the levels above, one of the offered items is highlighted and the selection can be moved by up or down. Most of the files in /proc/asound are empty: $ ls -l /proc/asound insgesamt 0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card0 dr-xr-xr-x 6 root root 0 2021-07-30 17:46 card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 cards -r--r--r-- 1 root root 0 2021-07-30 17:46 devices lrwxrwxrwx 1 root root 5 2021-07-30 17:46 HDMI -> card1 -r--r--r-- 1 root root 0 2021-07-30 17:46 hwdep -r--r--r-- 1 root root 0 2021-07-30 17:46 modules dr-xr-xr-x 4 root root 0 2021-07-30 17:46 oss lrwxrwxrwx 1 root root 5 2021-07-30 17:46 PCH -> card0 -r--r--r-- 1 root root 0 2021-07-30 17:46 pcm dr-xr-xr-x 6 root root 0 2021-07-30 17:46 seq -r--r--r-- 1 root root 0 2021-07-30 17:46 timers -r--r--r-- 1 root root 0 2021-07-30 17:46 version Probably this will give a hint (perhaps it is also visible from the automatically collected information). I think I had tried the sound system with the live stick before installation. But I'll repeat that test again and tell you the outcome. Kind regards melolontha ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.11 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 30 17:08:50 2021 InstallationDate: Installed on 2021-07-28 (1 days ago) InstallationMedia: Xubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2011 dmi.bios.release: 21.0 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2100V2 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 21.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2100V2:bd08/24/2011:br21.0:efr21.0:svnSonyCorporation:pnVPCCA3S1E:pvrC609VVH0:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCCA3S1E dmi.product.sku: N/A dmi.product.version: C609VVH0 dmi.sys.vendor: Sony Corporation ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1938584 Title: [VPCCA3S1E, Realtek ALC269, Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: New Bug description: This problem came up after installing Xubuntu 20.04.02 on this computer, which used Xubuntu 18.04 before. Ifter installing the system, I installed some programs, among them Sound Switcher Indicator 2.3.6 and I unistalled firefox after I had
Re: [Desktop-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Had to compile with: copied over current cofig Removed --> #CONFIG_SYSTEM_TRUSTED_KEYS sudo make menuconfig sudo make clean sudo make deb-pkg LOCALVERSION=-custom KDEB_PKGVERSION=$(make kernelversion)-1 Then installed the deb files. Let me know if this works. Michael On 7/30/21 10:17 AM, Raish khaitu wrote: > @mblack154 How did you resolve this issue: > arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support > sed: can't read modules.order: No such file or directory > make: *** [Makefile:1485: __modinst_pre] Error 2 > > i am still stuck here even after running these: > sudo apt install build-essential > sudo apt-get build-dep linux-image- (the running kernel) > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
@mblack154 How did you resolve this issue: arch/x86/Makefile:148: CONFIG_X86_X32 enabled but no binutils support sed: can't read modules.order: No such file or directory make: *** [Makefile:1485: __modinst_pre] Error 2 i am still stuck here even after running these: sudo apt install build-essential sudo apt-get build-dep linux-image- (the running kernel) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1935850/+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 1938040] Re: "Run command as a login shell" is enabled even with custom command in Gnome Terminal
** Package changed: ubuntu => gnome-terminal (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1938040 Title: "Run command as a login shell" is enabled even with custom command in Gnome Terminal Status in gnome-terminal package in Ubuntu: New Bug description: When I write custom command instead (in Command tab) to execute non- default shell or pass some extra parameters to it "Run command as a login shell" is still enabled but doesn't affects on custom command. I think it's better to disable "Run command as a login shell" checkbox to avoid any confusions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1938040/+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 1938040] [NEW] "Run command as a login shell" is enabled even with custom command in Gnome Terminal
You have been subscribed to a public bug: When I write custom command instead (in Command tab) to execute non- default shell or pass some extra parameters to it "Run command as a login shell" is still enabled but doesn't affects on custom command. I think it's better to disable "Run command as a login shell" checkbox to avoid any confusions. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- "Run command as a login shell" is enabled even with custom command in Gnome Terminal https://bugs.launchpad.net/bugs/1938040 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1920813 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1920813 Title: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session requiredpam_loginuid.so" for compatibility with user applications Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.04 2. Launch MATE Terminal 3. Execute `cat /proc/self/loginuid` Expected results: * above command returned 1000 Actual results: * above command returned 4294967295 Remediation: * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment session requiredpam_loginuid.so for compatibility with user applications. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 22 22:41:05 2021 InstallationDate: Installed on 2021-03-21 (1 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1920813/+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 1920813] Re: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session required pam_loginuid.so" for compatibility with user applications
** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1920813 Title: /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin should have uncommented "session requiredpam_loginuid.so" for compatibility with user applications Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 21.04 2. Launch MATE Terminal 3. Execute `cat /proc/self/loginuid` Expected results: * above command returned 1000 Actual results: * above command returned 4294967295 Remediation: * edit /etc/pam.d/lightdm and /etc/pam.d/lightdm-autologin to uncomment session requiredpam_loginuid.so for compatibility with user applications. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: lightdm 1.30.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CurrentDesktop: MATE Date: Mon Mar 22 22:41:05 2021 InstallationDate: Installed on 2021-03-21 (1 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1920813/+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 1938548] Re: screen capture broken; ImageMagick "import" command fails
** Description changed: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. + + This bug is mirrored here: + + https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1938556 + + Most likely ImageMagick is the culprit. -- 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/1938548 Title: screen capture broken; ImageMagick "import" command fails Status in xwayland package in Ubuntu: New Bug description: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. This bug is mirrored here: https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/1938556 Most likely ImageMagick is the culprit. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1938548/+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 1901263] Re: I cant open any Chromium based browser
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1901263 Title: I cant open any Chromium based browser Status in Ubuntu MATE: Incomplete Status in chromium-browser package in Ubuntu: Incomplete Bug description: I've just installed Unbuntu Mate 20.10 from a bootable USB stick. The process was very simple (congratulations!) but the only browser I can open is the built-in Firefox. All other Chromium based browsers I've installed ( Chromium, Opera and Vivaldi) freeze the computer and I have do shut it down manually. My PC is a AMD-64 Dell Inspiron with 4 GB RAM. Thanks for any help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1901263/+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 1934941] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1934941 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: hello developers when I start my ubantu after entering passward somentimes when I open the screen divided into 4 screen and starts blinking for that I have to restart the computer. It does not happens daily but it sucks when happens. I have also problem in my blutooth it disconnect after sometimes of connect and once disconnect you can not connect again . ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 8 02:47:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2021-07-03 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=20708d08-341d-4530-803a-7e28abc56637 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2014 dmi.bios.release: 15.109 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 33.71 dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/23/2014:br15.109:efr33.71:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.sku: D7Z60PC#ACJ dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1934941/+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 1931388] Re: Firefox disaplayerror after Update on last version 89
** Tags removed: groovy ** Tags added: hirsute ** Changed in: firefox (Ubuntu) Status: Incomplete => Confirmed -- 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/1931388 Title: Firefox disaplayerror after Update on last version 89 Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Confirmed Bug description: After the last Update from Firefox Browser to Version 89 Firefox is unsuable. The Program starts but the window is somehow transparent and white. I removed and reinstalled Firefox but the problem is the same. My computer is an Amd Mashine running Ubuntu Mate 20.10 Mate 1.24.1 I took a Screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1931388/+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 1938548] [NEW] screen capture broken; ImageMagick "import" command fails
Public bug reported: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. ** 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/1938548 Title: screen capture broken; ImageMagick "import" command fails Status in xwayland package in Ubuntu: New Bug description: When running Xorg+xwayland+wayland+sway, the ImageMagick "import" command was executed on the commandline. The pointer was then dragged across an Ungoogled Chromium window. I should have drawn a rectangle to show the area being snapshot'd, but no box appeared. When the mouse button was released, this error was printed in the terminal: import-im6.q16: unable to read X window image `': Resource temporarily unavailable @ error/xwindow.c/XImportImage/4977. import-im6.q16: missing an image filename `/tmp/sample.png' @ error/import.c/ImportImageCommand/1276. No image file was produced. Chromium only works in Wayland for some people and only with some special parameters passed to it. I could not get Ungoogled Chromium to run in Wayland, so I had to run it like normal on Xwayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1938548/+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 1938053] Re: HDMI Problem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1938053 Title: HDMI Problem Status in xorg package in Ubuntu: New Bug description: Cannot connect second monitor with hdmi after update. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-63-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 26 17:49:36 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics [1462:12c1] InstallationDate: Installed on 2021-06-05 (50 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Micro-Star International Co., Ltd. Modern 14 B10MW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-63-generic root=UUID=375930f6-29d7-4278-861a-7bf26f514a10 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2020 dmi.bios.release: 1.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E14D1IMS.10B dmi.board.asset.tag: Default string dmi.board.name: MS-14D1 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE14D1IMS.10B:bd12/22/2020:br1.11:svnMicro-StarInternationalCo.,Ltd.:pnModern14B10MW:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-14D1:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: Modern dmi.product.name: Modern 14 B10MW dmi.product.sku: 14D1.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1938053/+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 1938249] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1938249 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: my system very frequently hang or crash when i establish internet connection. please ubuntu support help me to fix this problem. thanks in advance. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-142-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.30 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 28 10:05:05 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610/M74 [Mobility Radeon HD 2400 XT] [1002:94c8] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] RV610/M74 [Mobility Radeon HD 2400 XT] [1025:012f] MachineType: Acer Volvi ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-142-generic root=UUID=3517ff6d-a96d-4899-96e2-8dfde5a99c61 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/05/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: V1.14 dmi.board.name: Volvi dmi.board.vendor: Acer dmi.board.version: Rev dmi.chassis.asset.tag: None dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.14:bd11/05/2007:svnAcer:pnVolvi:pvr0100:rvnAcer:rnVolvi:rvrRev:cvnAcer:ct10:cvrN/A: dmi.product.name: Volvi dmi.product.version: 0100 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jul 28 09:57:43 2021 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1938249/+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 1776391] Re: Wifi Icon disappeared after upgrading to 4.15.0-23-generic
** Changed in: network-manager-applet (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-mate Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1776391 Title: Wifi Icon disappeared after upgrading to 4.15.0-23-generic Status in Ubuntu MATE: Incomplete Status in linux package in Ubuntu: Incomplete Status in network-manager-applet package in Ubuntu: Incomplete Bug description: After updating to Ubuntu Mate 4.15.0-23-generic the wifi icon disappeared from the task bar. I have no problems connecting to networks or anything (by going to Network Connections in Control Panel ). I was using the 4.13.something -generic version before. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1776391/+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 1873236] Re: 20.04 - 2 network icons displayed
** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1873236 Title: 20.04 - 2 network icons displayed Status in Ubuntu MATE: New Status in network-manager-applet package in Ubuntu: New Bug description: Ubuntu MATE daily since start of Alpha. No changes to system or network since installation, only testing apps and compiz. This morning, after several suspend/resume I have 2 network indicators displaying, which has not previously occurred. (At same time power management indicator - it is a laptop - disappeared. See separate report #1871854) Using default theme with icons just changed in colour to orange with the new applet back at start of beta test when it became available. 1 network icon is the correct one of 2 small arrows (1 up, 1 down) and left click displays network info, and right click displays About, help etc. As expected. About info displays Indicator Applet Complete 1.24.0. 2nd, new, icon is same but larger, and both left and right click display the same network info, so no way to access the About info. I do have MATE Netspeed indicator active, but it has been throughout my testing. Returns to 1 network indicator (the smaller correct one) after logout/login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1873236/+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 1884303] Re: LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??)
** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1884303 Title: LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??) Status in Ubuntu MATE: New Status in cups package in Ubuntu: New Bug description: Hello, I have been experiencing this problem for at least 2 LTS versions I believe and it concerns and issue with a LAN printer. I am still not quite too sure if it involves a happy mix-up of TCPvsmDNSvsuPnP and|or if it's a lpstat VS GUI binary setting and|or ?? Anyways, when using 20.04 fully patched(and also possibly not) while using a LAN printer there seems to be a "duplicated-corrupted entry" that ends up somewhat generated in the system. For example: $ lpstat -p printer Samsung_C460_Series_SEC30CDA7A49F15_ now printing Samsung_C460_Series_SEC30CDA7A49F15_-12. enabled since Fri 19 Jun 2020 01:09:47 PM $ And MATE agrees with that (See attachment "1.jpg") But when using Atril (See "2.jpg") or LOWriter (See "3.jpg") (or any other binary such as firefox) the story isn't so clear. That brought me back to this: $ lpstat -p lpstat: No destinations added. $ And MATE still agrees with that (See "4.jpg") Yet LOWriter (and co) seemed a bit still challenged (See "5.jpg") Anyways, time to delete everything and readd. But why are there 2x choices? (See "6.jpg") Looking carefully at both entries, I believe that one is the TCP socket (See "7.jpg") while the 2nd one is via SSDP/UPnP (See "8.jpg"). But anyways, I always go for the TCP entry and that's done (See "9.jpg"). $ lpstat -p 1 ↵ printer Samsung-C460 is idle. enabled since Fri 19 Jun 2020 02:36:42 PM $ And MATE again agrees (See "10.jpg") Yaaay! Time to print out that SOB, so let's go back into Atril and print it (See "11.jpg") Nothing surprising there: the old ghosted/MAC addressed profile still shows. But did printing on the newly added via TCP one actually worked? YES! This time it did. Why this time? Because in other times it will just die in the spoiler and have me started back at the very beginning of this ticket. Also, a major point of interest is: after having readded the printer, notice how lpstat named it, it was "Samsung-C460". Well, if/when I'll reboot the system, that simple name will be gone and will have been changed to "Samsung-C460-Series-SEC30CDA7A49F15" while still showing this "Samsung_C460_Series_SEC30CDA7A49F15_" ghost. From the printer's perspective, here is what's opened on it: PORT STATE SERVICE VERSION 80/tcpopen httpSamsung SyncThru Web Service |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9 | http-methods: |_ Supported Methods: GET POST | http-robots.txt: 1 disallowed entry |_* |_http-title: Site doesn't have a title (text/html; charset=utf-8). 427/tcp open svrloc? 515/tcp open printer? | fingerprint-strings: | TerminalServerCookie: |_PortThru lpd: No Jobs on this queue 631/tcp open httpSamsung SyncThru Web Service |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9 | http-methods: |_ Supported Methods: GET POST |_http-title: Site doesn't have a title (text/html; charset=utf-8). 5200/tcp open targus-getdata? | fingerprint-strings: | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LDAPSearchReq, LPDString, RPCCheck, RTSPRequest, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServerCookie, X11Probe: | HTTP/1.1 405 Method Not Allowed | Connection: close |_Server: ESWeb/0.5 9100/tcp open jetdirect? 10001/tcp open scp-config? Here's what /var/log/cups/error_log as to say about all of this: E [19/Jun/2020:00:00:00 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [19/Jun/2020:13:02:02 -0400] [Job 10] File \'\' not found E [19/Jun/2020:13:05:58 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [19/Jun/2020:13:08:09 -0400] [Job 11] No destination host name supplied by cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is cups-browsed running? E [19/Jun/2020:13:08:39 -0400] [Job 12] No destination host name supplied by cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is cups-browsed running? E [19/Jun/2020:13:09:58 -0400] [Client 2371] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from localhost. E [19/Jun/2020:13:09:58 -0400] [Client 2493] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from localhost. E
[Desktop-packages] [Bug 1888042] Re: Qualcomm Atheros QCA6174
** Changed in: ubuntu-mate Status: New => Incomplete ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1888042 Title: Qualcomm Atheros QCA6174 Status in Ubuntu MATE: Incomplete Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: On Ubuntu Mate 20 (and also Linux Mint 20) Ping over lan wireless result: icmp_seq=1 Destination Host Unreachable Network card Wireless Qualcomm Atheros QCA6174 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1888042/+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 1898771] Re: suspend does not lock screen Fresh Ubuntu Mate 20.04.1
** Tags removed: lightdm lock security suspend unlock ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1898771 Title: suspend does not lock screen Fresh Ubuntu Mate 20.04.1 Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: New Bug description: When suspending my freshly installed 20.04.1 system I noticed that on waking a password is not required. lightdm does not have locking enabled on suspend. A workaround I found from pszafer on archlinux blog. Quoted below: create lockscreen.sh file somewhere in your home directory with: #!/bin/sh XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" dm-tool lock - I've prefer just for sure creating dmlock.service file in home dir and create symlink to /etc/systemd/system. File has to be in /etc/systemd/system/dmlock.service [Unit] Description=DM Lock before sleep Before=sleep.target [Service] ExecStart=/home/user/dir/lockscreen.sh [Install] WantedBy=sleep.target For your needs, you probably need hibernate.target. Next run following commands: systemctl daemon-reload systemctl enable dmlock.service Just for sure it is working you could run: systemctl list-unit-files systemctl start dmlock.service Hope it helps you a little To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1898771/+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 1901263] Re: I cant open any Chromium based browser
** Also affects: chromium (Ubuntu) Importance: Undecided Status: New ** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu) ** Changed in: ubuntu-mate Status: New => Incomplete ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1901263 Title: I cant open any Chromium based browser Status in Ubuntu MATE: Incomplete Status in chromium-browser package in Ubuntu: Incomplete Bug description: I've just installed Unbuntu Mate 20.10 from a bootable USB stick. The process was very simple (congratulations!) but the only browser I can open is the built-in Firefox. All other Chromium based browsers I've installed ( Chromium, Opera and Vivaldi) freeze the computer and I have do shut it down manually. My PC is a AMD-64 Dell Inspiron with 4 GB RAM. Thanks for any help. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1901263/+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 1901349] Re: Rhythmbox, first song played doesn't start at beginning
** Also affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1901349 Title: Rhythmbox, first song played doesn't start at beginning Status in Ubuntu MATE: New Status in rhythmbox package in Ubuntu: New Bug description: After updating from Ubuntu-MATE 20.04 to 20.10, the first song played after opening Rhythmbox doesn't start at the beginning. All other songs work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1901349/+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 1904794] Re: Graphical error in Disks app
** Changed in: ubuntu-mate Status: New => Incomplete ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1904794 Title: Graphical error in Disks app Status in Ubuntu MATE: Incomplete Status in gnome-disk-utility package in Ubuntu: Incomplete Bug description: When loading the disks app I see the close item missing. I am enclosing a screenshot. I am using Mate 20.10 on a Raspberry Pi 4B 4Gb Ram. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1904794/+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 1901263] [NEW] I cant open any Chromium based browser
You have been subscribed to a public bug: I've just installed Unbuntu Mate 20.10 from a bootable USB stick. The process was very simple (congratulations!) but the only browser I can open is the built-in Firefox. All other Chromium based browsers I've installed ( Chromium, Opera and Vivaldi) freeze the computer and I have do shut it down manually. My PC is a AMD-64 Dell Inspiron with 4 GB RAM. Thanks for any help. ** Affects: ubuntu-mate Importance: Undecided Status: New ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: groovy -- I cant open any Chromium based browser https://bugs.launchpad.net/bugs/1901263 You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914891] Re: Wi-Fi "connect to new network" goes AWOL when changing geolocalisation
** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1914891 Title: Wi-Fi "connect to new network" goes AWOL when changing geolocalisation Status in Ubuntu MATE: New Status in network-manager-applet package in Ubuntu: New Bug description: If/when you install 20.04.1 and during setup you choose a BSSID + finish installation + fully patched system and everything ok, then if you take your laptop over to a different geolocalisation that has different wifi equipment, it becomes fairly hard/impossible for a simple end user to then connect to a new equipment in this new location because there exists no list of found access points. To state this differently: 1. I installed 20.04.1 ISO on my laptop; 2. During installation there was a "wizard" that found a bunch of APs and I connected to one, did the installation, everything went well; 3. Everytime I am physically located where this AP I connected to during installation is: my Internet works no problem. 4. Everytime I take this system and go elsewhere that has different APs, all that MATE gives me at TTY7 launch is that yellow pop-up at the right-hand upper portion of the screen saying that there are other APs nearby. -> The problem with that is: I need to manually go under Control Center -> Advanced Network Configuration -> click on green "+" -> select Wi-Fi -> Fill in all of those informations. This is no problem when you actually know where to connect to. But that is not always the case. My expectations: Instead of MATE telling me it found APs around me (Point #4) is that I would like for that same auto-discovery of APs that was launched during installation to also be available somewhere in MATE so I actually see a list of which APs are around me. That is not currently the case, we need to guess, and this is frustrating. <3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1914891/+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 1932005] Re: nm-applet not showing in system tray
** Also affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1932005 Title: nm-applet not showing in system tray Status in Ubuntu MATE: New Status in network-manager-applet package in Ubuntu: New Bug description: Hello all, I noticed this morning that the network options (i am not sure if it suppose to be nm-applet) is no longer showing in system tray and for a while now that KDE Connect indicator is not showing in the system tray. I am currently Ubuntu Mate 20.04 on a raspberry PI400 uname -a Linux pi400 5.4.0-1036-raspi #39-Ubuntu SMP PREEMPT Wed May 12 17:37:51 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal apt policy network-manager network-manager: Installed: 1.22.10-1ubuntu2.2 Candidate: 1.22.10-1ubuntu2.2 Version table: *** 1.22.10-1ubuntu2.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages Does anyone else have a similar issue? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1932005/+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 1781810] Re: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it
** Tags added: bionic ** Also affects: bamf (Ubuntu) Importance: Undecided Status: New ** Also affects: plank (Ubuntu) Importance: Undecided Status: New ** Changed in: bamf Status: New => Incomplete ** Changed in: plank Status: New => Incomplete ** Changed in: bamf (Ubuntu) Status: New => Incomplete ** Changed in: plank (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1781810 Title: Plank dock is not showing an indicator when a certain application is open anymore and when an application that is open is clicked on the dock, a new instance of it is opened Status in BAMF: Incomplete Status in Plank: Incomplete Status in bamf package in Ubuntu: Incomplete Status in plank package in Ubuntu: Incomplete Bug description: Plank version: 0.11.4 Distribution: Ubuntu MATE 18.04 DE: MATE Desktop Window manager: Marco Video card: Intel HD Graphics 4000 Plank comes installed with the system by default When i used Ubuntu MATE 16.04 it didn't happen. I had an indicator that the application i was clicking on was open and when i clicked it, it would be restored if it was minimized and it will be minimized if it was maximized or just being shown on the screen but on this version, even if the application is minimized or maximized, when i click on its icon, first of all, i can't see that "application open" indicator below its icon anymore(Only below the Plank icon) and second of all, Plank will open a new instance of that same application. I recorded a video showing you what i am talking about. And also, sometimes when i click on the icons on the dock, i won't have that visual feedback, that "little jump" of the icon i click. That's very important as well otherwise, i think nothing happened. That's all. I really like Plank and it is a great application. Thanks for it. Best wishes To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1781810/+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 1799856] Re: Software Boutique crashes after applying fixes
** Changed in: ubuntu-mate Status: New => Incomplete ** Changed in: ubuntu-mate-welcome (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1799856 Title: Software Boutique crashes after applying fixes Status in Ubuntu MATE: Incomplete Status in gnome-software package in Ubuntu: Invalid Status in ubuntu-mate-welcome package in Ubuntu: Incomplete Bug description: After Software Boutique installed the software I selected I clicked "fixes". After checking for incomplete and broken packages, I clicked "More Software". What I got was a list of "Software" and "Synaptic Package Manager" repeated 3 times. (Before installing apps, the list occurred only once.) Ubuntu 18.04.1 LTS (just reinstalled when 18.10 went into meltdown). AMD 64-bit ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: python3.6-minimal 3.6.6-1~18.04 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Wed Oct 24 21:56:10 2018 ExecutablePath: /usr/bin/python3.6 InstallationDate: Installed on 2018-10-25 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 SourcePackage: python3.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1799856/+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 1782473] Re: "Software" opens window missing a search widget
** No longer affects: ubuntu-mate ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1782473 Title: "Software" opens window missing a search widget Status in gnome-software package in Ubuntu: Incomplete Bug description: The window opened from Menu->All->Software shows the software stores available. When I alunch the first, I get a window showing all applications; but the window is missing a search widget. To look for a specific app I have to step through every app in every category. If there were only a dozen or so apps for Ubuntu that would be ok. Forgetting to add a search feature is a major design error! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: ufsd ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Wed Jul 18 22:29:19 2018 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-07-06 (13 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.1 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1782473/+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 1754458] Re: nm-applet symbol not displayed on mate (18.04)
** Changed in: mate-indicator-applet (Ubuntu) Status: Confirmed => Incomplete ** Changed in: ubuntu-mate-settings (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1754458 Title: nm-applet symbol not displayed on mate (18.04) Status in indicator-application package in Ubuntu: Invalid Status in mate-indicator-applet package in Ubuntu: Incomplete Status in network-manager-applet package in Ubuntu: Invalid Status in ubuntu-mate-settings package in Ubuntu: Incomplete Bug description: After upgrading to Ubuntu 18.04, the network manager applet symbol isn't displayed any longer. The other functionality (asking for credentials) is working. I also see other symbols. aptitude show network-manager-gnome Paket: network-manager-gnome Version: 1.8.10-2ubuntu1 Neu: ja Zustand: Installiert stdout/stderr: Gtk-Message: 21:28:14.411: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "topmenu-gtk-module" Gtk-Message: 21:28:14.431: Failed to load module "appmenu-gtk-module" Gtk-Message: 21:28:14.432: Failed to load module "topmenu-gtk-module" ** (nm-applet:29524): WARNING **: 21:28:14.668: Couldn't register with accessibility bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (nm-applet:29524): nm-applet-WARNING **: 21:28:15.987: Cannot grab information for modem at /org/freedesktop/ModemManager1/Modem/6: No ModemManager support (nm-applet:29524): nm-applet-WARNING **: 21:28:16.124: ModemManager is not available for modem at /org/freedesktop/ModemManager1/Modem/6 (nm-applet:29524): Gtk-WARNING **: 21:28:16.127: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:16.141: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:16.171: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:21.500: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:21.570: Can't set a parent on widget which has a parent (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-CRITICAL **: 21:28:24.517: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed (nm-applet:29524): Gtk-WARNING **: 21:28:24.655: Can't set a parent on widget which has a parent ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: MATE Date: Thu Mar 8 21:27:56 2018 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) WpaSupplicantLog: nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.4 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1754458/+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 1739908] Re: Ubuntu Software Center has low contrast with some themes
** Changed in: gtk2-engines (Ubuntu) Status: New => Incomplete ** Changed in: human-theme (Ubuntu) Status: New => Incomplete ** Changed in: mate-themes (Ubuntu) Status: New => Incomplete ** Changed in: software-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk2-engines in Ubuntu. https://bugs.launchpad.net/bugs/1739908 Title: Ubuntu Software Center has low contrast with some themes Status in gtk2-engines package in Ubuntu: Incomplete Status in human-theme package in Ubuntu: Incomplete Status in mate-themes package in Ubuntu: Incomplete Status in software-center package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. Install Ubuntu 16.04 LTS with MATE DE 2. Set theme which you like (for example, BlackMATE, DarkRoom, High Contrast Inverse, High Contrast, Human Clearlooks, Human) 3. Launch Ubuntu Software Center and start search for application Expected results: Ubuntu Software Center is usable, its interface has normal contrast (user can read text, click buttons and so on) Actual results: Ubuntu Software Center is unusable, its interface has very low contrast (user can not read text, click buttons and so on) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: software-center 16.01+16.04.20160420 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CurrentDesktop: MATE Date: Sat Dec 23 22:46:18 2017 JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk2-engines/+bug/1739908/+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 1578487] Re: Unable to mount disk drives in computer://
** Tags added: xenial ** Changed in: caja (Ubuntu) Status: Confirmed => Incomplete ** Changed in: gvfs (Ubuntu) Status: Confirmed => Incomplete -- 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/1578487 Title: Unable to mount disk drives in computer:// Status in caja package in Ubuntu: Incomplete Status in gvfs package in Ubuntu: Incomplete Bug description: Ubuntu Mate 16.04 Places/Computer -Disk images (SSD and File Systems) state "unknown" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1578487/+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 1616168] Re: package libpeas-1.0-0 1.16.0-1ubuntu2 failed to install/upgrade: Versuch, »/usr/lib/libpeas-1.0/loaders/libpython3loader.so« zu überschreiben, welches auch in Pake
** Changed in: libpeas (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpeas in Ubuntu. https://bugs.launchpad.net/bugs/1616168 Title: package libpeas-1.0-0 1.16.0-1ubuntu2 failed to install/upgrade: Versuch, »/usr/lib/libpeas-1.0/loaders/libpython3loader.so« zu überschreiben, welches auch in Paket libpeas-1.0-0-python3loader 1.16.0-1ubuntu2 ist Status in libpeas package in Ubuntu: Incomplete Bug description: i have this bug at startup ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libpeas-1.0-0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Tue Aug 23 20:19:28 2016 ErrorMessage: Versuch, »/usr/lib/libpeas-1.0/loaders/libpython3loader.so« zu überschreiben, welches auch in Paket libpeas-1.0-0-python3loader 1.16.0-1ubuntu2 ist InstallationDate: Installed on 2016-03-28 (148 days ago) InstallationMedia: Ubuntu-MATE 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libpeas Title: package libpeas-1.0-0 1.16.0-1ubuntu2 failed to install/upgrade: Versuch, »/usr/lib/libpeas-1.0/loaders/libpython3loader.so« zu überschreiben, welches auch in Paket libpeas-1.0-0-python3loader 1.16.0-1ubuntu2 ist UpgradeStatus: Upgraded to xenial on 2016-04-23 (122 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libpeas/+bug/1616168/+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 1460347] Re: B43 did not offer channel 11-13
** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1460347 Title: B43 did not offer channel 11-13 Status in network-manager package in Ubuntu: Incomplete Bug description: Ubuntu Mate 15.04 i386 / Lenovo ideapad S10-2 / Broadcom 4312 After install simple login and take a look at available wlans in the area. You will see all between 1 and 10, but none in the 11-13 range. It's also not possible to connect them as hidden network. In physical this machine was shipped with windows and it can use full range in Europe / Germany Under ubuntu we see: eric@selene:~$ iwlist chan wlan0 32 channels in total; available frequencies : Channel 01 : 2.412 GHz Channel 02 : 2.417 GHz Channel 03 : 2.422 GHz Channel 04 : 2.427 GHz Channel 05 : 2.432 GHz Channel 06 : 2.437 GHz Channel 07 : 2.442 GHz Channel 08 : 2.447 GHz Channel 09 : 2.452 GHz Channel 10 : 2.457 GHz Channel 11 : 2.462 GHz Channel 12 : 2.467 GHz Channel 13 : 2.472 GHz Full range but network-manager is in denial of that. eric@selene:~$ iw reg get country DE: DFS-ETSI (2400 - 2483 @ 40), (N/A, 20), (N/A) (5150 - 5250 @ 40), (N/A, 20), (N/A), NO-OUTDOOR (5250 - 5350 @ 40), (N/A, 20), (0 ms), NO-OUTDOOR, DFS (5470 - 5725 @ 40), (N/A, 26), (0 ms), DFS (57240 - 65880 @ 2160), (N/A, 40), (N/A), NO-OUTDOOR ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic i686 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.1 Architecture: i386 CurrentDesktop: MATE Date: Sat May 30 23:17:24 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-05-30 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release i386 (20150422.1) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 1024 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.101 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Elysion20 30f1d787-c4d3-4652-950f-e656990cbe9d 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- Kabelnetzwerkverbindung 1 aae849bd-3bcc-49fb-bd6c-8aff25c05e51 802-3-ethernet 1433020571 Sa 30 Mai 2015 23:16:11 CEST yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/2 nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/1 Kabelnetzwerkverbindung 1 aae849bd-3bcc-49fb-bd6c-8aff25c05e51 /org/freedesktop/NetworkManager/ActiveConnection/2 wlan0wifi disconnected /org/freedesktop/NetworkManager/Devices/2 -- ---- ttyACM1 gsm unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1460347/+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 1432824] Re: package cups-browsed 1.0.61-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: cups-filters (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1432824 Title: package cups-browsed 1.0.61-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups-filters package in Ubuntu: Incomplete Bug description: I removed cups because I was getting "Entity was too large" error messages when trying to configure through the web interface, and I was getting other errors when I tried configuring using the command line interface (I forget which errors, but it has to do with my printer, an Epson Stylus Photo 890), So I removed cups with apt-get and tried installing it from source code from the cups website. That didn't work either, What I am going to do now is remove the open source version of cups and try again with Ubuntu's version to see what happens. Ubuntu 14.10 jeffs@jeffs-desktop:~$ apt-cache policy cups cups: Installed: (none) Candidate: 1.7.5-3ubuntu3.1 Version table: 1.7.5-3ubuntu3.1 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ utopic-security/main amd64 Packages 100 /var/lib/dpkg/status 1.7.5-3ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages jeffs@jeffs-desktop:~$ I am currently running /usr/sbin/cupsd 2.0.2 When I try to print something, the printer gets no data (there is a light on the printer that blinks when it gets data, and it remains off), I expect the printer to get some data. Even if I use the wrong filter, I still expect to get something. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: cups-browsed 1.0.61-0ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 Architecture: amd64 CupsErrorLog: Date: Mon Mar 16 13:27:20 2015 DuplicateSignature: package:cups-browsed:1.0.61-0ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-01-30 (45 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - amd64 (20141023) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor Papersize: letter PpdFiles: /etc/cups/ppd/stphoto.ppd:*NickName: EPSON Stylus Photo Series CUPS v1.1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic root=UUID=c9a29661-91d8-4d1e-9a24-ac86a1835d7b ro quiet splash vt.handoff=7 SourcePackage: cups-filters Title: package cups-browsed 1.0.61-0ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/21/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: EBH7710H.86A.0075.2012.0521.1400 dmi.board.name: DH77EB dmi.board.vendor: Intel Corporation dmi.board.version: AAG39073-304 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrEBH7710H.86A.0075.2012.0521.1400:bd05/21/2012:svn:pn:pvr:rvnIntelCorporation:rnDH77EB:rvrAAG39073-304:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1432824/+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 1420589] Re: Wacom Intuos2 stops working at boot after installing Nvidia drivers.
** Changed in: xf86-input-wacom (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1420589 Title: Wacom Intuos2 stops working at boot after installing Nvidia drivers. Status in xf86-input-wacom package in Ubuntu: Incomplete Bug description: My Wacom Intuos2 6x8 tablet works out the box on an Ubuntu 14.04 install. After installing the Nvidia drivers and running updates, the tablet stops responding/moving. The only way to get the stylus working again is to add "blacklist wacom" to the /etc/modprobe.d/blacklist file. And after reboot re-enable the wacom module with: sudo modprobe wacom This is a problem in Ubuntu 14.04 64bit, as well as, Debian Jessie. It seems something is getting confused with udev. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-wacom 1:0.23.0-0ubuntu2 [modified: usr/share/X11/xorg.conf.d/50-wacom.conf] ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Tue Feb 10 21:25:51 2015 InstallationDate: Installed on 2015-01-05 (36 days ago) InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xf86-input-wacom UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1420589/+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 1410559] Re: 14.10 - Taking Screenshots stops working after an app is opened
** Changed in: gnome-screenshot (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1410559 Title: 14.10 - Taking Screenshots stops working after an app is opened Status in gnome-screenshot package in Ubuntu: Incomplete Bug description: This may or not be a gnome-screenshot issue, to me it seems to be a system issue: Fresh install of Ubuntu 14.10, Dell D630 Core 2Duo, 2.6Ghz. 240G SSD, Intel 965 Video. Taking screenshots works when first logged in but afterwards every screenshot becomes distorted. Seems to happen right after opening an app, Firefox, or Geary for an example. Installed Shutter, same exact problem, tried with Gimp, same thing. Installed Mate Desktop, works perfect, no issues whatsoever. http://ubuntuforums.org/showthread.php?t=2057426=ubuntu+14.10+screenshot+issue I can't seem to find a bug report anywhere, how can I fix this? Ubuntu 14.10 Memory: 3.9GiB Processor: Intel® Core™2 Duo CPU T7800 @ 2.60GHz × 2 Graphics: Intel® 965GM OS Type: 64-bit Disk 241.8GB ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gnome-screenshot 3.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 13 14:11:58 2015 InstallationDate: Installed on 2015-01-09 (3 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-screenshot UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1410559/+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 1335211] Re: Config details of networked printer aren't saved
** Changed in: system-config-printer (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1335211 Title: Config details of networked printer aren't saved Status in cups-filters package in Ubuntu: Fix Released Status in system-config-printer package in Ubuntu: Incomplete Bug description: Mint 17 64 bit. When I run the printer configuration application (system-config-printer) it detects my network printer. If I then access Priner properties I can set the manufacturer and model number in the usual way and the printer works. However the settings don't survive a reboot. The workround is to make a change to the Description field: the Apply button is then enabled and I can save the changes. Evidently the application doesn't register the changes to the printer's properties as a change requiring saving, and so leaves the Apply button greyed out. This behaviour is consistent and repeatable under Mate and Xfce. While the workround is simple the behaviour is confusing particularly to a new user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1335211/+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 1355994] Re: nm-applet periodically crashes in MATE desktop
** Changed in: network-manager-applet (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1355994 Title: nm-applet periodically crashes in MATE desktop Status in network-manager-applet package in Ubuntu: Incomplete Bug description: I have nm-applet connected to a WIFI network every day. It disappears from the panel every now and then, perhaps 1-4 times a day. I am not sure if this happens on all desktops of 14.04, or just MATE. It also happens on my Linux Mint computer running MATE and network-manager, so I am inclined to believe it happens with network-manager-applet. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager-gnome 0.9.8.8-0ubuntu4.3 ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 21:47:57 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-05-17 (86 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 88.113.44.1 dev wlan0 proto static 88.113.44.0/22 dev wlan0 proto kernel scope link src 88.113.47.79 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: network-manager-applet UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH Kissa ja Pupu 47ac40c7-690b-4b67-bf87-f99824f53178 802-11-wireless 1407869185 ti 12. elokuuta 2014 21.46.25 yes no /org/freedesktop/NetworkManager/Settings/2 HIIT 90a87b2c-3dcf-4d93-8303-0446c9cace9b vpn 0never nono /org/freedesktop/NetworkManager/Settings/1 HY47f3a09b-443f-4896-bd78-85dd7b553d68 vpn 1401524490 la 31. toukokuuta 2014 11.21.30nono /org/freedesktop/NetworkManager/Settings/0 Wired connection 1216ecad8-227f-4913-814c-d15603d6569a 802-3-ethernet1407856886 ti 12. elokuuta 2014 18.21.26 yes no /org/freedesktop/NetworkManager/Settings/3 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth1 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1355994/+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 1365232] Re: Xorg crashed (logging out and back in)
** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1365232 Title: Xorg crashed (logging out and back in) Status in xorg-server package in Ubuntu: Incomplete Bug description: Xorg (xserver-xorg 1:7.7+1ubuntu8) crashed on an Ubuntu MATE (Utopic) amd64 system. Apport informed me of the crash when I logged in. I had just logged out and back in. At the time I was using this system to verify the correct behavior of pam_env.so against another system on which it is not working. I had set unimportant environment variables (FOO and BAR) in ~/.pam_environment, changed them, and removed the file (which was otherwise empty). I did this across a few graphical sessions, all within a few minutes of one another. I suspect that is not what triggered this crash but I'm not sure. Recently I have some kernel messages which may or may not be related to whatever triggered this crash: [ 853.112643] systemd-logind[1038]: New session c10 of user lightdm. [ 858.538808] init: tty1 main process ended, respawning [ 858.554498] systemd-logind[1038]: Failed to abandon scope session-c2.scope [ 858.554583] systemd-logind[1038]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 1118.816570] systemd-logind[1038]: Failed to abandon scope session-c10.scope [ 1118.816582] systemd-logind[1038]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc10_2escope [ 1118.826320] systemd-logind[1038]: New session c11 of user ek. [ 1689.808829] audit: type=1400 audit(1409798550.085:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6369 comm="apparmor_parser" [ 1689.808841] audit: type=1400 audit(1409798550.085:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6369 comm="apparmor_parser" I've attached the full output of 'dmesg' (dmesg.txt). ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: xserver-xorg-core 2:1.15.1-0ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-12.18-generic 3.16.1 Uname: Linux 3.16.0-12-generic x86_64 ApportVersion: 2.14.7-0ubuntu1 Architecture: amd64 Date: Wed Sep 3 22:28:32 2014 ExecutablePath: /usr/bin/Xorg InstallationDate: Installed on 2014-08-19 (15 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha amd64 (20140731) ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: Signal: 6 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1365232/+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 1367098] Re: Pulseaudio doesn't start at boot
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1367098 Title: Pulseaudio doesn't start at boot Status in pulseaudio package in Ubuntu: Incomplete Bug description: It's been happening for a week now. When I log in, I hear no sound, and when I check the sound setup and it shows no sound card. I tried to kill pulseaudio and then restart it, but sometimes it can't even be killed. The most embarrasing thing about this is that the system cannot be shut down properly. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mate 1947 F pulseaudio /dev/snd/controlC0: mate 1947 F pulseaudio CurrentDesktop: Unity Date: Tue Sep 9 06:43:45 2014 InstallationDate: Installed on 2014-04-20 (141 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 6.20 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Pumori dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvr6.20:bd10/24/2012:svnTOSHIBA:pnSATELLITEC855D-15V:pvrPSKD6E-005004HU:rvnAMD:rnPumori:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: SATELLITE C855D-15V dmi.product.version: PSKD6E-005004HU dmi.sys.vendor: TOSHIBA modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified] mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2014-06-08T06:32:23.092640 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1367098/+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 1399854] Re: Hangs at logoff or shutdown
** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1399854 Title: Hangs at logoff or shutdown Status in lightdm package in Ubuntu: Incomplete Bug description: I use a desktop environment MATE. When I try to shut down the computer or log off the screen freezes for 30 seconds, then turns black. The computer does not respond to keyboard and mouse, I can turn it off only with the aid of keys Alt + SysRq + O. After installing the kernel http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.17.1-utopic/ problem disappeared. If you are using the latest kernel from the repository or http://kernel.ubuntu.com/~kernel- ppa/mainline/v3.16.7-ckt2-utopic/ problem exists. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.2-0ubuntu1 Uname: Linux 3.17.1-031701-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sat Dec 6 05:57:38 2014 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.lightdm.conf: [modified] mtime.conffile..etc.init.lightdm.conf: 2014-11-12T21:32:04.127872 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1399854/+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 1369958] Re: indicator-keyboard crashes in Ubuntu MATE live installer
** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1369958 Title: indicator-keyboard crashes in Ubuntu MATE live installer Status in lightdm package in Ubuntu: Incomplete Bug description: I am the maintainer of Ubuntu MATE Remix, we are currently working towards being an official Ubuntu flavour. While trying to resolve an issue with lightdm crashing (https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1369952) I noticed .xsession-errors was complaining indicators were not available in the live installer. I have recently added the following indicators to the live installer: * indicator-application * indicator-datetime * indicator-keyboard * indicator-power * indicator-session The others appear to be working correctly but I just found crash dump in /var/crash for indicator-keyboard. You can download a Ubuntu MATE iso image that exhibits this issue from https://ubuntu- mate.org/1369958/ ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: indicator-keyboard 0.0.0+14.10.20140620.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CasperVersion: 1.344 Date: Tue Sep 16 09:06:58 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service LiveMediaBuild: Ubuntu MATE 14.10 "Utopic Unicorn" - pre-beta2.25818 amd64 (20140915) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 XDG_RUNTIME_DIR= Signal: 5 SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1369958/+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 1395599] Re: xset r off fails after hitting num-lock key
** Changed in: x11-xserver-utils (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to x11-xserver-utils in Ubuntu. https://bugs.launchpad.net/bugs/1395599 Title: xset r off fails after hitting num-lock key Status in x11-xserver-utils package in Ubuntu: Incomplete Bug description: In a terminal, after you enter the following command: xset r off It turns off key auto-repeat, as it should. You can press and hold a key, and only one such key will be displayed. If you then press the num-lock key (in the numeric key-pad), then press and hold a key, it is repeatedly displayed, and the command: xset q outputs information showing that auto-repeat has been turned back on. I expected that after doing the "xset r off" command, auto-repeat would remain off, regardless which key is pressed. Yet when I pressed the num-lock key (in the numeric key-pad), auto- repeat got turned back on. It did not do this on Ubuntu 14.04. This causes problems for an application which turns-off key-repeat by using the "xset r off" system command. I have observed this happening in both the ubuntuMATE and Lubuntu distributions. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: x11-xserver-utils 7.7+2ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Sun Nov 23 23:11:47 2014 InstallationDate: Installed on 2014-10-27 (28 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - i386 (20141023) SourcePackage: x11-xserver-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/x11-xserver-utils/+bug/1395599/+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 1405976] Re: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it
** Changed in: jackd2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1405976 Title: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in jackd2 package in Ubuntu: Incomplete Bug description: I was loading the Mate desktop through the terminal while browsing with Chromium when eventoccurred. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 Date: Sat Dec 27 11:30:18 2014 DuplicateSignature: package:libjack-jackd2-0:i386:1.9.9.5+20130622git7de15e7a-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-08-19 (130 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: i386 SourcePackage: jackd2 Title: package libjack-jackd2-0:i386 1.9.9.5+20130622git7de15e7a-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1405976/+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 1927063] Re: Terminal prompt got strangely replicated when resizing terminal horizontally
** Tags removed: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1927063 Title: Terminal prompt got strangely replicated when resizing terminal horizontally Status in bash package in Ubuntu: Confirmed Status in gnome-terminal package in Ubuntu: Confirmed Status in mate-terminal package in Ubuntu: Confirmed Status in tilix package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu installed 2. Launch MATE Terminal 3. Navigate to some folder with long name - `cd /usr/share/doc/ayatana-indicator-application` 4. Resize terminal horizontally Expected results: * terminal shows the same "user@host:/usr/share/doc/ayatana-indicator-application$" with single occurrence Actual results: * terminal shows multiple occurrencies of "user@host:/usr/share/doc/ayatana-indicator-application$" (see attached screencast) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue May 4 10:54:59 2021 InstallationDate: Installed on 2021-04-23 (10 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1927063/+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 1936966] Re: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards
** Tags removed: groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1936966 Title: Libreoffice 7.1 from PPA uses wrong desktop/panel/window icons for Template wizards Status in LibreOffice: New Status in bamf package in Ubuntu: New Status in libreoffice package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with Unity and MATE desktops 2. Add LO PPA, install full LO by sudo add-apt-repository ppa:libreoffice/ppa sudo apt-get update sudo apt-get install libreoffice 3a. Launch Libreoffice Impress, wait the Select a Template window to appear on task bar/window list 3b. Launch Libreoffice Writer, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list 3c. Launch Libreoffice Calc, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list 3d. Launch Libreoffice Draw, click on File → Templates → Manage templates, wait Templates window to appear on task bar/window list Expected results: * all Template windows use correct desktop/panel/window icons on task bar/window list Actual results: * all Template windows use wrong desktop/panel/window icons on task bar/window list Details: libreoffice1:7.1.4~rc2-0ubuntu0.18.04.1~lo1 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1936966/+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 1069964] Re: Two processes attempt to mount blank optical discs
** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity-settings-daemon (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1069964 Title: Two processes attempt to mount blank optical discs Status in OEM Priority Project: Won't Fix Status in glib2.0 package in Ubuntu: Incomplete Status in unity-settings-daemon package in Ubuntu: Incomplete Bug description: This behavior can be reproduced using either a live USB or an installed version of the effected flavors. Simply insert a blank optical disc in the drive. The behavior differs slightly in Ubuntu GNOME as the notification to either Open with CD/DVD Creator or Eject is displayed twice - that is after simply clicking on the X to close that notification it closes but a new duplicate notification appaers immediately. The GNOME Classic session is not effected at all. In all other effected flavors and/or desktop environments a notification appears stating "Unable to mount Blank disc. Location is already mounted". Effected flavors and DE's include Ubuntu w/Unity, gnome-session-flashback, and Ubuntu MATE. Versions effected include Trusty, Utopic, and Vivid. I assume that two separate processes are actually attempting to mount the blank optical media, rather than just the file manager attemting to do so, because both Nautilus and Caja are effected (based on some of the comments below possibly also Nemo). While purely cosmetic in nature I'd certainly be willing to try and troubleshoot this if someone more tech savvy would provide some debugging instructions. Original content begins below: This error message comes up, while still able to burn, read/write etc. It occurs in quantal when inserting a CD/DVD into the drive, but it did not happen in precice. Screenshot: http://i47.tinypic.com/4v0aj6.png Burner: LG HL-DT-ST DVDRAM GH24NS90 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-settings-daemon 3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 22 19:50:35 2012 ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1583849] Re: Firefox > 44 is broken on all big-endian architectures
** Changed in: firefox (Ubuntu) Status: Confirmed => Incomplete -- 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/1583849 Title: Firefox > 44 is broken on all big-endian architectures Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Incomplete Bug description: OK, the reason I'm posting back here, running Lu 16.04 on an PPC iBook, and MATE/XFCE 16.04 on a PM ST. . . did a dist-upgrade today, so it now running the new "22" kernel and saw in the list of upgrades new updates to FF and T-bird . . . on both machines after reboot FF window frame loads . . . and then crashes . . . no data is ever filled into the browser window. The iBook error says it "doesn't have enough memory to report the problem" . . . and on the PM . . . apparently it says the error report was "corrupted" . . . no launchpad window opened in the browser when I clicked on the "report the problem." Tried to revert to the old kernel in the iBook several times, seemingly failed to boot the old one . . . shut it down. I went to the PM running 16.04 U-MATE and tried the same dist-upgrade via console there, that upgrade was much larger than the Lu system, but subsequently FF also then failed to launch w/o crashing . . . installed Midori to make an apple user post, but when I tried to start a new thread there Midori crashed as well. I ran "apt-get -f install" in both the iBook & the PM . . . nothing showed up. No "comment" in the terminal during the upgrade asking any questions or reporting "problems" . . . but FF is kaput I'm back in OSX 10.5 side until things cool down for the browsers in 16.04 PPC Lu & U-MATE/XFCE. e... To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1583849/+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 1555331] Re: crash in g_slist_remove_all from gtk_rc_clear_realized_style
** Changed in: gtk+2.0 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1555331 Title: crash in g_slist_remove_all from gtk_rc_clear_realized_style Status in gtk+2.0 package in Ubuntu: Incomplete Status in mate-panel package in Ubuntu: Won't Fix Bug description: Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: mate-panel 1.12.2-1 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: MATE Date: Wed Mar 9 22:49:55 2016 ExecutablePath: /usr/bin/mate-panel InstallationDate: Installed on 2016-02-25 (12 days ago) InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) ProcCmdline: mate-panel SegvAnalysis: Segfault happened at: 0x7f4fa6439b1c :cmp %rbp,(%rdi) PC (0x7f4fa6439b1c) ok source "%rbp" ok destination "(%rdi)" (0x160016) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: mate-panel StacktraceTop: g_slist_remove_all () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 g_hash_table_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_rc_reset_styles () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 Title: mate-panel crashed with SIGSEGV in g_slist_remove_all() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1555331/+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 1561573] Re: No slides are displayed in Ubiquity Slideshow while installing on Lubuntu or Ubuntu MATE PowerPC
** Changed in: webkit2gtk (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1561573 Title: No slides are displayed in Ubiquity Slideshow while installing on Lubuntu or Ubuntu MATE PowerPC Status in webkit2gtk package in Ubuntu: Incomplete Bug description: While installing Lubuntu or Ubuntu MATE 16.04 Beta 2 on PowerPC now slides are displayed in Ubiquity Slideshow. After sometime apprt catches the attached crash. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: libwebkit2gtk-4.0-37 2.10.8-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-15.31-powerpc-smp 4.4.6 Uname: Linux 4.4.0-15-powerpc-smp ppc ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CasperVersion: 1.368 Date: Thu Mar 24 14:30:49 2016 ExecutablePath: /usr/lib/powerpc-linux-gnu/webkit2gtk-4.0/WebKitWebProcess LiveMediaBuild: Lubuntu 16.04 LTS "Xenial Xerus" - Beta powerpc (20160323) ProcCmdline: /usr/lib/powerpc-linux-gnu/webkit2gtk-4.0/WebKitWebProcess 23 ProcEnviron: PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash LANGUAGE=en_GB.UTF-8 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: webkit2gtk UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1561573/+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 1638833] Re: at-spi-bus-launcher crashed with SIGSEGV in strlen()
** Changed in: at-spi2-core (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1638833 Title: at-spi-bus-launcher crashed with SIGSEGV in strlen() Status in at-spi2-core package in Ubuntu: Incomplete Bug description: Pops up shortly after starting the desktop. ProblemType: Crash DistroRelease: Ubuntu 17.04 Package: at-spi2-core 2.22.0-3 ProcVersionSignature: Ubuntu 4.8.0-26.28-powerpc-smp 4.8.0 Uname: Linux 4.8.0-26-powerpc-smp ppc ApportVersion: 2.20.3-0ubuntu8 Architecture: powerpc Date: Thu Nov 3 08:36:20 2016 ExecutablePath: /usr/lib/at-spi2-core/at-spi-bus-launcher InstallationDate: Installed on 2016-11-03 (0 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha powerpc (20161103) ProcCmdline: /usr/lib/at-spi2-core/at-spi-bus-launcher ProcEnviron: SHELL=/bin/false XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=de_AT:de LANG=de_AT.UTF-8 Signal: 11 SourcePackage: at-spi2-core StacktraceTop: strlen () at ../sysdeps/powerpc/powerpc32/strlen.S:98 g_variant_is_object_path () from /lib/powerpc-linux-gnu/libglib-2.0.so.0 g_dbus_proxy_new_for_bus () from /usr/lib/powerpc-linux-gnu/libgio-2.0.so.0 ?? () ?? () Title: at-spi-bus-launcher crashed with SIGSEGV in strlen() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1638833/+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 1490171] Re: Orca doesn't work properly with Ubuntu installer
** Changed in: gnome-orca (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1490171 Title: Orca doesn't work properly with Ubuntu installer Status in gnome-orca package in Ubuntu: Incomplete Bug description: Ubuntu MATE 15.10 Daily 20150829: When you get to the "Who are you?" portion of the installer, it does not read you what tab location you are in, so I have no way of knowing whether I am typing in my name, computer name, username, password, or password confirmation. It just says "Tab". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-orca/+bug/1490171/+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 1887216] Re: /usr/share/foo2zjs/hplj10xx_gui.tcl: /usr/bin/wish: bad interpreter: No such file or directory
Blacklisted on MATE level. ** Changed in: foo2zjs (Ubuntu) Status: New => Invalid ** Tags removed: eoan groovy ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to foo2zjs in Ubuntu. https://bugs.launchpad.net/bugs/1887216 Title: /usr/share/foo2zjs/hplj10xx_gui.tcl: /usr/bin/wish: bad interpreter: No such file or directory Status in foo2zjs package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Boot Ubuntu MATE 20.10 2. Open Caja 3. Navigate to /usr/share/applications/ 4. Click on *Reactivate HP LaserJet 1018/1020 after reloading paper* Expected results: * some application launched Actual results: * the application is not launched, the ~/.xsession-errors contain the following line: sh: 1: exec: /usr/share/foo2zjs/hplj10xx_gui.tcl: not found Note: manual launch of the above tcl file ends with: /usr/share/foo2zjs/hplj10xx_gui.tcl bash: /usr/share/foo2zjs/hplj10xx_gui.tcl: /usr/bin/wish: bad interpreter: No such file or directory Seems to be dependency issue. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: printer-driver-foo2zjs-common 20200505dfsg0-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: MATE Date: Sat Jul 11 07:28:44 2020 LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200711) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: LENOVO 27463ZG PackageArchitecture: all Papersize: a4 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- SourcePackage: foo2zjs UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2010 dmi.bios.vendor: LENOVO dmi.bios.version: 6AET64WW dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 27463ZG dmi.board.vendor: LENOVO dmi.board.version: LENOVO 6AET64WW dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: LENOVO 6AET64WW dmi.modalias: dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn27463ZG:pvrThinkPadSL500:rvnLENOVO:rn27463ZG:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW: dmi.product.name: 27463ZG dmi.product.version: ThinkPad SL500 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/foo2zjs/+bug/1887216/+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 1890569] Re: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed.
** Changed in: libreoffice (Ubuntu) Status: New => Confirmed ** Tags removed: groovy ** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1890569 Title: javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. Status in libreoffice package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Boot Ubuntu 20.10 daily ISO 2. Launch libreoffice-calc from its desktop file 3. Monitor the output of error-log by `tail -f ~/.xsession-errors` Expected results: * error log is empty Actual results: * error log contains lines: ``` javaldx: Could not find a Java Runtime Environment! Please ensure that a JVM and the package libreoffice-java-common is installed. If it is already installed then try removing ~/.config/libreoffice/4/user/config/javasettings_Linux_*.xml Warning: failed to read path from javaldx ``` Note: also happens for Draw, Impress, Math, StartCenter, Writer, xsltfilter. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: libreoffice-calc 1:6.4.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 CasperMD5CheckMismatches: ./casper/filesystem.squashfs CasperMD5CheckResult: skip CasperVersion: 1.452 CurrentDesktop: MATE Date: Thu Aug 6 10:10:47 2020 LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200806) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1890569/+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 1923052] Re: screen reader does not read ubiquity window
** Tags added: impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Confirmed Status in orca package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+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 1918855] Re: Xorg xserver got signal 6 to abort
** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1918855 Title: Xorg xserver got signal 6 to abort Status in OEM Priority Project: Triaged Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: == SRU Justification == [Impact] When the system is under memory pressure, the entire desktop session may crash. [Fix] Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if kernel can't allocate memory") [Test] Run memory stress and the session crashed in less than 5 minutes. With the fix applied, run memory stress for 24 hours and the desktop session is still alive. [Where problems could occur] Doing a reset might make the system even more sluggish when under memory pressure. == Original bug report == I run checkbox job com.canonical.certification::memory/memory_stress_ng on focal, and the xserver stops unexpectedly with the following stacktrace: /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x5619f3a4d59c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7fae476a418b] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7fae47683859] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) [0x7fae46529c9c] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) [0x7fae47007480] /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind info found [-10] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: /usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg (BlockHandler+0xa5) [0x5619f38f0995] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg (WaitForSomething+0x122) [0x5619f3a46c12] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x5619f38ebcf7] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5619f38effc4] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fae476850b3] /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) [0x5619f38d9a2e] More info: I searched the Internet and got a bug with the same stacktrace: https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468 https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
Resolving supertuxkart issue, actually it was a mesa issue now fixed. ** Changed in: supertuxkart (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Fix Released Status in supertuxkart package in Ubuntu: Invalid Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1 amd64Miscellaneous Mesa utilies (opengles, egl) ii mesa-va-drivers:amd64 19.0.8-0ubuntu0~18.04.1 amd64Mesa VA-API video
[Desktop-packages] [Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915
This issue should be fixed by this mesa commit https://cgit.freedesktop.org/mesa/mesa/commit/?id=3199172eaa703ac4c1fc3830c8e49c367725c3b8 which should be included since Ubuntu 20.04/focal. Please reopen this issue if you still have this problem. ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1841953 Title: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915 Status in mesa package in Ubuntu: Fix Released Status in supertuxkart package in Ubuntu: Invalid Bug description: Hi, for few weeks now, I've noticed a big change in graphic performance while playing famous SuperTuxKart on ubuntu bionic : shadows are flickering, all over the screen, it's a big pain for eyes ( and wonder what would happen for epileptic people ). My computer is : Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz with 16Go ram and Haswell integrated graphics. coeur-noir@asgard:~$ lspci -k | grep -A 2 -i "VGA" 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller Kernel driver in use: i915 coeur-noir@asgard:~$ sudo lshw -c video *-display description: VGA compatible controller produit: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller fabriquant: Intel Corporation identifiant matériel: 2 information bus: pci@:00:02.0 version: 06 bits: 64 bits horloge: 33MHz fonctionnalités: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 ressources: irq:26 mémoire:f780-f7bf mémoire:e000-efff portE/S:f000(taille=64) mémoire:c-d coeur-noir@asgard:~$ My Ubuntu Budgie 18.04 is : coeur-noir@asgard:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 coeur-noir@asgard:~$ uname -a Linux asgard 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux coeur-noir@asgard:~$ mesa packages are : coeur-noir@asgard:~$ dpkg -l | grep mesa ii libegl-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the EGL API -- Mesa vendor library ii libegl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-dri:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-dri:i38619.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- DRI modules ii libgl1-mesa-glx:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libgl1-mesa-glx:i38619.0.8-0ubuntu0~18.04.1 i386 transitional dummy package ii libglapi-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the GL API -- shared library ii libglapi-mesa:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the GL API -- shared library ii libgles2-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii libglu1-mesa:amd64 9.0.0-2.1build1 amd64Mesa OpenGL utility library (GLU) ii libglu1-mesa:i386 9.0.0-2.1build1 i386 Mesa OpenGL utility library (GLU) ii libglx-mesa0:amd64 19.0.8-0ubuntu0~18.04.1 amd64free implementation of the OpenGL API -- GLX vendor library ii libglx-mesa0:i386 19.0.8-0ubuntu0~18.04.1 i386 free implementation of the OpenGL API -- GLX vendor library ii libosmesa6:amd6419.0.8-0ubuntu0~18.04.1 amd64Mesa Off-screen rendering extension ii libosmesa6:i386 19.0.8-0ubuntu0~18.04.1 i386 Mesa Off-screen rendering extension ii libwayland-egl1-mesa:amd64 19.0.8-0ubuntu0~18.04.1 amd64transitional dummy package ii mesa-utils 8.4.0-1 amd64Miscellaneous Mesa GL utilities ii mesa-utils-extra8.4.0-1
[Desktop-packages] [Bug 1429222] Re: lightdm fails to start on boot of ubuntu mate but starts when restarted
** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1429222 Title: lightdm fails to start on boot of ubuntu mate but starts when restarted Status in lightdm package in Ubuntu: Incomplete Bug description: boot March 6th daily ubuntu mate installation went fine restarted got to grub started up and did not load any further switched to tty and no gui or splash screen came up. I switched to tty 1 and was able to login. lightdm: Installed: 1.13.1-0ubuntu2 Candidate: 1.13.1-0ubuntu2 Version table: *** 1.13.1-0ubuntu2 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 to reproduce install ubuntu-mate using manaul partitioning using an ext4 / partition and reusing an xfs /home. I expected lightdm to come up and display a GUI and I could get it to start by restarting it. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lightdm 1.13.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 CurrentDesktop: MATE Date: Fri Mar 6 09:45:52 2015 InstallationDate: Installed on 2015-03-06 (0 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha amd64 (20150306) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1429222/+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 1938505] [NEW] 1/4 screenshot issue in ubuntu cinnamon remix
Public bug reported: hello, i am reporting 1/4 screenshot issue in ubuntu cinnamon remix in 20.4 & 21.04 my laptop is dell 14 7400 , i5 11gen , gpu intel gpu , i am not able to use mx350 gpu in my dell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Fri Jul 30 11:47:16 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:09d9] Subsystem: Dell GP107M [GeForce MX350] [1028:09d9] InstallationDate: Installed on 2021-07-13 (16 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210422) MachineType: Dell Inc. Inspiron 7400 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-25-generic root=UUID=4afa5195-02a4-45d3-84e1-df9f5bade23a ro rootflags=subvol=@ quiet splash resume=UUID=1b62aa58-2234-4ada-bf43-f19e45ece46a vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 068X1V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd10/27/2020:br1.3:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn068X1V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7400 dmi.product.sku: 09D9 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.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-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu ** Attachment added: "Screenshot from 2021-07-30 11-42-12.png" https://bugs.launchpad.net/bugs/1938505/+attachment/5514711/+files/Screenshot%20from%202021-07-30%2011-42-12.png -- 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/1938505 Title: 1/4 screenshot issue in ubuntu cinnamon remix Status in xorg package in Ubuntu: New Bug description: hello, i am reporting 1/4 screenshot issue in ubuntu cinnamon remix in 20.4 & 21.04 my laptop is dell 14 7400 , i5 11gen , gpu intel gpu , i am not able to use mx350 gpu in my dell ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Fri Jul 30 11:47:16 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Xe Graphics [1028:09d9] Subsystem: Dell GP107M [GeForce MX350] [1028:09d9] InstallationDate: Installed on 2021-07-13 (16 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210422) MachineType: Dell Inc. Inspiron 7400 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.11.0-25-generic root=UUID=4afa5195-02a4-45d3-84e1-df9f5bade23a ro rootflags=subvol=@ quiet splash resume=UUID=1b62aa58-2234-4ada-bf43-f19e45ece46a vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2020 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 068X1V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd10/27/2020:br1.3:svnDellInc.:pnInspiron7400:pvr:rvnDellInc.:rn068X1V:rvrA00:cvnDellInc.:ct10:cvr: