[Desktop-packages] [Bug 1766192] Re: [snap] cannot save file under $HOME
This issue also prevents importing CSV files stored in the user's home directory. You need to come up with a way to allow snap applications to do *any* action the user explicitly initiates. Only automated dotfile access should be blocked. -- 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/1766192 Title: [snap] cannot save file under $HOME Status in snapd: Triaged Status in firefox package in Ubuntu: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: (this was initially reported on the forum: https://forum.snapcraft.io/t/libreoffice-6-0-3-not-so-stable/5032) When trying to save a file under $HOME (not a subdirectory), the user is presented with an error dialog: --- Error --- Error saving the document Untitled 1: Object not accessible. The object cannot be accessed due to insufficient user rights. [OK] This is because libreoffice tries to create a lock file of the form: "$HOME/.~lock.Untitled 1.odt", and the home interface doesn't allow writing hidden files (those with a filename that starts with a dot) under $HOME. DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu Bionic Beaver (development branch)" DESKTOP_SESSION=ubuntu GTK_MODULES=gail:atk-bridge HOME=/home/osomon/snap/libreoffice/59 LANG=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 LC_NAME=fr_FR.UTF-8 LC_NUMERIC=fr_FR.UTF-8 LC_TIME=fr_FR.UTF-8 LD_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu::/snap/libreoffice/59/lib:/snap/libreoffice/59/usr/lib:/snap/libreoffice/59/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa-egl:/snap/libreoffice/59/usr/lib/x86_64-linux-gnu/mesa PATH=/snap/libreoffice/59/usr/sbin:/snap/libreoffice/59/usr/bin:/snap/libreoffice/59/sbin:/snap/libreoffice/59/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games SNAP=/snap/libreoffice/59 SNAP_ARCH=amd64 SNAP_COMMON=/var/snap/libreoffice/common SNAP_DATA=/var/snap/libreoffice/59 SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void SNAP_NAME=libreoffice SNAP_REEXEC= SNAP_REVISION=59 SNAP_USER_COMMON=/home/osomon/snap/libreoffice/common SNAP_USER_DATA=/home/osomon/snap/libreoffice/59 SNAP_VERSION=6.0.3.2 TEMPDIR=/tmp TMPDIR=/run/user/1000/snap.libreoffice XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc/xdg/xdg-ubuntu:/etc/xdg XDG_CURRENT_DESKTOP=ubuntu:GNOME XDG_DATA_DIRS=/usr/share/ubuntu:/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop XDG_RUNTIME_DIR=/run/user/1000/snap.libreoffice XDG_SESSION_DESKTOP=ubuntu XDG_SESSION_TYPE=x11 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1766192/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
** Description changed:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
- The real fix has been made in glib2.0, and the proposed updates in the
- below PPA will allow the IBus patch to be re-enabled.
-
- https://launchpad.net/~gunnarhj/+archive/ubuntu/glib2.0
+ The real fix has been made in glib2.0, and the updates in -proposed will
+ allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
-- Upgrade the glib2.0 packages from
- {eoan,disco,bionic,xenial}-proposed
+ - Upgrade the glib2.0 packages from
+ {eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
Consequently the changes have been reviewed by the glib maintainer, but also
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.
[Original description]
Kubuntu Release 18.04.3 LTS
Expected behavior:
ibus continues working as before after applying security update
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.
Observed behavior:
ibus is not usable anymore in Qt applications.
After updating ibus and the related packages ibus-gtk, ibus-gtk3,
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using
shift-space no longer changes the selected input method and even when i switch
to the mozc input method in a gtk application, i can not use it in any Qt
applications.
When starting qtconfig in a terminal, I also get the following message:
Bus::open: Connect ibus failed!
IBusInputContext::createInputContext: no connection to ibus-daemon
This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed
that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus
functionality in Qt applications.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ibus 1.5.17-3ubuntu5.1
ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat Sep 21 07:58:56 2019
InstallationDate: Installed on 2019-06-28 (84 days ago)
InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1844853
Title:
IBus no longer works in Qt applications after upgrade
Status in GLib:
Fix Released
Status in ibus:
Fix Released
Status in glib2.0 package in Ubuntu:
Fix Committed
Status in ibus package in Ubuntu:
Fix Released
Status in glib2.0 source package in Xenial:
In Progress
Status in glib2.0 source package in Bionic:
In Progress
Status in glib2.0 source package in Disco:
In Progress
Status in glib2.0 source package in Eoan:
In Progress
Status in glib2.0 source package in Focal:
Fix Committed
Status in ibus source package in Focal:
Fix Released
Status in glib2.0 package in Debian:
Fix Released
Bug description:
[Impact]
IBus was broken for Qt applications as a regression due to the fix of
CVE-2019-14822. As a result the IBus patch was disabled temporarily,
which fixed IBus from a usability POV.
The real fix has been made in glib2.0, and the updates in -proposed
will allow the IBus patch to be re-enabled.
[Test Case]
* On a standard Ubuntu {eoan,disco,bionic,xenial} installation
- Upgrade the glib2.0 packages from
{eoan,disco,bionic,xenial}-proposed
- Upgrade the ibus packages from
https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
- Install some IBus input method, e.g. ibus-libpinyin
- Install some Qt application, e.g. Kate
* Relogin (maybe reboot)
* Add the input method to the input sources
* Open the Qt app and try to input something using the IBus IM
=> Find that the transliteration works as expected
[Regression Potential]
The applicable patches origin from glib upstream:
https://gitlab.gnome.org/GNOME/glib/
[Desktop-packages] [Bug 1798840] Re: Night Light is not functioning
Night light stopped working for me from Disco to Eoan upgrade. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1798840 Title: Night Light is not functioning Status in gnome-control-center package in Ubuntu: Expired Bug description: Night Light is not shading/filtering the screen anymore after the update to Cosmic (Ubuntu 18.10) from Bionic (Ubuntu 18.04 LTS). It still appears as an option and all the settings work, but the feature itself isn't filtering out blue light from the screen. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 19 11:03:28 2018 InstallationDate: Installed on 2018-08-17 (63 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to cosmic on 2018-10-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798840/+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 1848186] Re: label escaping warnings
** Tags removed: verification-needed -- 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/1848186 Title: label escaping warnings Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Committed Bug description: * Impact When connecting to some access points warnings are printed in the log due to incorrect handling of special chars * Test case Connect to an AP with a '&' in its name, no warning should be displayed * Regression potential The code changes is the one building the label of APs, check that those are properly named in the applet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1848186/+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 1806269] Re: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed
** Bug watch removed: GNOME Bug Tracker #785674 https://gitlab.gnome.org/785674 ** Also affects: network-manager-applet (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865013 Importance: Unknown Status: Unknown ** Bug watch removed: Debian Bug tracker #883965 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883965 ** Changed in: network-manager-applet (Ubuntu Bionic) Importance: Undecided => Medium ** Tags removed: verification-needed -- 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/1806269 Title: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed Status in Network Manager Applet: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager-applet source package in Bionic: Fix Committed Status in network-manager-applet package in Debian: Unknown Bug description: * Impact the connection editor segfault when using without gnome-keyring * Test case uninstall gnome-keyring and try to edit a connection, it shouldn't segfault * Regression potential the fix changes an error handling case, it shouldn't impact normal use Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault. 0x77ba6b53 in modules_initialized (object=, res=0x56048a40, user_data=) at src/libnma/nma-cert-chooser-button.c:98 98 src/libnma/nma-cert-chooser-button.c: No such file or directory. This occurs when the package "gnome-keyring" is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1806269/+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 1851068] [NEW] laptop does not wakeup after suspend (when lid off). Need to had reset
Public bug reported: When lid off. The laptop goes to unusual suspend mode. When raising the lid. Cannot turn laptop on. Cannot even log remotely using ssh. My lap top is ho spectre-15, i7-9750h with nvidia gtx 1650 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 Uname: Linux 5.4.0-050400rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:14:29 2019 InstallationDate: Installed on 2019-10-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1851068 Title: laptop does not wakeup after suspend (when lid off). Need to had reset Status in pm-utils package in Ubuntu: New Bug description: When lid off. The laptop goes to unusual suspend mode. When raising the lid. Cannot turn laptop on. Cannot even log remotely using ssh. My lap top is ho spectre-15, i7-9750h with nvidia gtx 1650 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pm-utils 1.4.1-18 Uname: Linux 5.4.0-050400rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:14:29 2019 InstallationDate: Installed on 2019-10-31 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1851068/+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 1851067] Re: Unnecessary Delays Recovering from Screen Lock
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1851067 Title: Unnecessary Delays Recovering from Screen Lock Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: New Bug description: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off: https://gitlab.gnome.org/GNOME/gnome-control- center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png **Side-note:** this is bad terminology because your screen will still go into the exact same state that "Screen Lock: On" accomplishes (upon an inactivity timeout), but the only difference is that you won't have to enter your password to regain access to the desktop. I would have named this "Require Password Authentication After Inactivity Timeout" (to me wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of things. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press the "enter" key. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. Also, there should be separate setting for "blank screen x time", and "monitor power off after x time". My ideal settings would to make the screen go black after 5 minutes of inactively and to turn my monitors completely off after 15 minutes of inactively, and I'd like to control whether each of these requires password authentication or not. On the 5 minute one, I personally would note require a password, but I would require a password after monitor going off. However, on either of these, I expect the desktop to be fully functional immediately after coming out of these states. At the very least please remove these unnecessary delays. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+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 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Description changed: You can turn "Sreen Lock" off using gnome-control-center > Privacy > - Screen Lock : Off. + Screen Lock : Off: - However, this is bad terminology because you screen will still go into - the exact same "Screen Lock" state upon an inactivity timeout, but the - only difference is that you don't have to enter your password to regain - access to the desktop. + https://gitlab.gnome.org/GNOME/gnome-control- + center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png + + **Side-note:** this is bad terminology because your screen will still go + into the exact same state that "Screen Lock: On" accomplishes (upon an + inactivity timeout), but the only difference is that you won't have to + enter your password to regain access to the desktop. I would have named + this "Require Password Authentication After Inactivity Timeout" (to me + wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a - couple of behaviors. + couple of things. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press - enter. I want to be able to accomplish this also by moving my mouse. + the "enter" key. I want to be able to accomplish this also by moving my + mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. + Also, there should be separate setting for "blank screen x time", and + "monitor power off after x time". + + My ideal settings would to make the screen go black after 5 minutes of + inactively and to turn my monitors completely off after 15 minutes of + inactively, and I'd like to control whether each of these requires + password authentication or not. On the 5 minute one, I personally would + note require a password, but I would require a password after monitor + going off. However, on either of these, I expect the desktop to be fully + functional immediately after coming out of these states. At the very + least please remove these unnecessary delays. + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Screen Lock Recovery has Unnecessary Delays + Unnecessary Delays Recovering from Screen Lock -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1851067 Title: Unnecessary Delays Recovering from Screen Lock Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: New Bug description: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off: https://gitlab.gnome.org/GNOME/gnome-control- center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png **Side-note:** this is bad terminology because your screen will still go into the exact same state that "Screen Lock: On" accomplishes (upon an inactivity timeout), but the only difference is that you won't have to enter your password to regain access to the desktop. I would have named this "Require Password Authentication After Inactivity Timeout" (to me wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of things. 1) Afte
[Desktop-packages] [Bug 1790098] Re: vlan created on bond fails auto activation on updating parent network bond
** Changed in: network-manager (Ubuntu Bionic) Importance: Undecided => High ** Changed in: network-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1790098 Title: vlan created on bond fails auto activation on updating parent network bond Status in Ubuntu on IBM z Systems: Fix Committed Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Bionic: Fix Committed Bug description: Auto activation of Vlan created over network-bond fails if bond is deactivated and reactivated. Contact Information = Abhiram Kulkarni(abhir...@in.ibm.com), Mandar Deshpande(manda...@in.ibm.com) ---uname output--- Linux S36MANDAR 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:23 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = s390x ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Created a network bond with static IP address (and no IPv6 address); active backup mode; ARP polling; single slave. 2. Created a VLAN using said network bond with static IPv4 address (and no IPv6 address). 3. Can ping from the appliance to a target on both links (the parent bond and the VLAN). 4. Switched to another slave for the created bond 5. Can still ping from the appliance to a target via the parent bond; however, cannot ping to the target via the VLAN. = Detailed steps: 1. Initial setup: root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 2. Create Netwrok-bond with one slave: root@S36MANDAR:~# nmcli c add type bond con-name mybond1 ifname mybond1 ipv4.method disabled ipv6.method ignore Connection 'mybond1' (4b918a65-43a6-4ec3-b3c4-388ed52b116d) successfully added. root@S36MANDAR:~# nmcli con add type ethernet ifname enc1d40 master mybond1 Connection 'bond-slave-enc1d40' (cfe4b245-3dda-4f45-b7b4-6d40d144a02f) successfully added. root@S36MANDAR:~# nmcli con up bond-slave-enc1d40 Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/18) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 3. Create vlan over mybond1: === root@S36MANDAR:~# nmcli con add type vlan con-name vlanbond.100 ifname vlanbond.100 dev mybond1 id 100 ipv4.method disabled ipv6.method ignore Connection 'vlanbond.100' (e054df42-97a0-492b-b2c9-b9571077493e) successfully added. root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet enc1d40 enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan vlanbond.100 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet -- 4. Reactivate bond : = root@S36MANDAR:~# nmcli con up mybond1 Connection successfully activated (master waiting for slaves) (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/30) root@S36MANDAR:~# nmcli c s NAMEUUID TYPE DEVICE enc1a80 c3a2037d-60a3-3cb4-9234-45aed55f7093 ethernet enc1a80 enc1d40 ff2d70f8-130e-3dc6-ab24-1dba07563605 ethernet enc1d40 enc8f00 2423add6-1464-3765-877c-a214dc497492 ethernet enc8f00 mybond1 4b918a65-43a6-4ec3-b3c4-388ed52b116d bond mybond1 bond-slave-enc1d40 cfe4b245-3dda-4f45-b7b4-6d40d144a02f ethernet -- encw18104ddeb38e-d5f7-3814-abb7-be50b8da874e ethernet -- vlanbond.100e054df42-97a0-492b-b2c9-b9571077493e vlan -- As is seen, vlan(vlanbond.100) did not ge
[Desktop-packages] [Bug 1851067] Re: Screen Lock Recovery has Unnecessary Delays
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #757 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/issues/757 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1851067 Title: Unnecessary Delays Recovering from Screen Lock Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: New Bug description: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off: https://gitlab.gnome.org/GNOME/gnome-control- center/uploads/62e176ed49faf1defaf6e4a36ad86f77/ScreenLock.png **Side-note:** this is bad terminology because your screen will still go into the exact same state that "Screen Lock: On" accomplishes (upon an inactivity timeout), but the only difference is that you won't have to enter your password to regain access to the desktop. I would have named this "Require Password Authentication After Inactivity Timeout" (to me wordy is better than unclear). While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of things. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press the "enter" key. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. Also, there should be separate setting for "blank screen x time", and "monitor power off after x time". My ideal settings would to make the screen go black after 5 minutes of inactively and to turn my monitors completely off after 15 minutes of inactively, and I'd like to control whether each of these requires password authentication or not. On the 5 minute one, I personally would note require a password, but I would require a password after monitor going off. However, on either of these, I expect the desktop to be fully functional immediately after coming out of these states. At the very least please remove these unnecessary delays. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1851067/+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 1851067] [NEW] Screen Lock Recovery has Unnecessary Delays
Public bug reported: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off. However, this is bad terminology because you screen will still go into the exact same "Screen Lock" state upon an inactivity timeout, but the only difference is that you don't have to enter your password to regain access to the desktop. While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of behaviors. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press enter. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1851067 Title: Screen Lock Recovery has Unnecessary Delays Status in gnome-control-center package in Ubuntu: New Bug description: You can turn "Sreen Lock" off using gnome-control-center > Privacy > Screen Lock : Off. However, this is bad terminology because you screen will still go into the exact same "Screen Lock" state upon an inactivity timeout, but the only difference is that you don't have to enter your password to regain access to the desktop. While this accomplishes "not having to re-enter your password when coming back from an inactivity timeout", I'm very dissatisfied with a couple of behaviors. 1) After reaching an "inactivity timeout" that "locks" your screen, you cannot unlock your screen by simply moving your mouse; you have to press enter. I want to be able to accomplish this also by moving my mouse. 2) Even if you press the enter key, to come out of "lock mode", it takes too long before you can interact with the applications you had open. I expect this to be instantaneous! If I were coming out of a suspended state, I could understand some delay. However, I'm not coming out of a suspended state, I just coming out of a screen lock. I do not like how this works. The whole purpose of this, as far as I'm concerned, is to increase the lifespan of my display monitors. All I want this to do, when a inactivity timeout occurs, is turn off all my monitor, and the only delay I expect, when coming back to my desktop, is what ever delay my monitor causes; the desktop should be fully available even before my monitor starts to display the desktop again. Having to press Enter and waiting 5 or 10 seconds before I can start working is NOT something that anyone wants. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 16:58:25 2019 InstallationDate: Installed on 2019-10-30 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug
[Desktop-packages] [Bug 1850995] Re: gnome-shell: freeze and high CPU usage
I tried to start a session with "ubuntu wayland" on the VM and the problem is not there, the problem is only on the xorg session. I can't start "ubuntu wayland" on the host desktop with the NVIDIA GPU, of course I enable "nvidia-drm.modeset = 1", but that's another problem. -- 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/1850995 Title: gnome-shell: freeze and high CPU usage Status in gnome-shell package in Ubuntu: New Bug description: It's easy to reproduce: Put files on the desktop, select them, the selection remains and the whole shell crashes. I switch to a tty2 session and see the gnome-shell process with 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.34.1+git20191024-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 00:32:11 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (256 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191022-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1850995/+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 1624541] Re: blank screen with amdgpu on [AMD/ATI] Topaz XT [Radeon R7 M260/M265]
Possible duplicate of Bug #1848900 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1624541 Title: blank screen with amdgpu on [AMD/ATI] Topaz XT [Radeon R7 M260/M265] Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: The machine is still fully functioning but laptop screen is blank. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xserver-xorg-video-amdgpu 1.1.0-1 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Fri Sep 16 22:53:26 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:80b5] InstallationDate: Installed on 2016-09-09 (7 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Pavilion Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=9955b60d-5abe-40f5-b6b1-060b2a803731 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-video-amdgpu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.16 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 80B5 dmi.board.vendor: HP dmi.board.version: 81.29 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.16:bd11/27/2015:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B5:rvr81.29:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.sys.vendor: HP version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Sep 16 22:52:30 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.3-1ubuntu2.3 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1624541/+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 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
** Description changed: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 Fix: - Backport a patch from 1.20.4 + Backport a patch from 1.20.2 Regression potential: - None really, we've had this xserver version since 18.10 and in the HWE backport, this patch backport is for 18.04 stock xserver but should work the same. It just skips initializing glamor if the system is using software fallback. + None really, we've had this xserver version since 18.10 and in the HWE backport, this patch backport is for 18.04 stock xserver but should work the same. It just skips initializing glamor if the system is using software fallback. ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- 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/1792932 Title: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Incomplete Status in xorg-server source package in Cosmic: Fix Released Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39
[Desktop-packages] [Bug 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
** Description changed: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 + + Fix: + Backport a patch from 1.20.4 + + Regression potential: + none really, we've had this version since 18.10 and in the HWE backport, this is for 18.04 stock xserver but should work the same + ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Description changed: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 Fix: Backport a patch from 1.20.4 Regression potential: - none really, we've had this version since 18.10 and in the HWE backport, this is for 18.04 stock xserver but should work the same - + None really, we've had this xserver version since 18.10 and in the HWE backport, this patch backport is for 18.04 stock xserver but should work the same. It just skips initializing glamor if the system is using software fallback. ProblemType: Crash DistroRelease: Ubuntu 18.10
[Desktop-packages] [Bug 1851063] [NEW] EPSON XP-960 printer unusable since installation of 19.10 (worked OK with 19.04)
Public bug reported: [code] chris@chris-BlackTower:~$ lsmod | grep usb btusb 57344 0 btrtl 20480 1 btusb btbcm 16384 1 btusb btintel24576 1 btusb bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm snd_usb_audio 241664 4 snd_usbmidi_lib36864 1 snd_usb_audio snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec snd_rawmidi36864 2 snd_seq_midi,snd_usbmidi_lib usblp 24576 0 snd_pcm 106496 4 snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core snd86016 28 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi mc 53248 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common usb_storage77824 3 uas usbhid 57344 0 hid 126976 2 usbhid,hid_generic chris@chris-BlackTower:~$ tail -f /var/log/syslog Nov 2 17:51:20 chris-BlackTower dbus-daemon[1927]: [session uid=1000 pid=1927] Successfully activated service 'org.gnome.Terminal' Nov 2 17:51:20 chris-BlackTower systemd[1910]: Started GNOME Terminal Server. Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’ Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # watch_fast: "/org/gnome/terminal/legacy/" (establishing: 0, active: 0) Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # unwatch_fast: "/org/gnome/terminal/legacy/" (active: 0, establishing: 1) Nov 2 17:51:20 chris-BlackTower gnome-shell[2136]: # watch_established: "/org/gnome/terminal/legacy/" (establishing: 0) Nov 2 17:51:22 chris-BlackTower wpa_supplicant[1213]: wlp6s0: Reject scan trigger since one is already pending Nov 2 17:51:58 chris-BlackTower xdg-desktop-por[2074]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Nov 2 17:52:17 chris-BlackTower kernel: [ 5451.623104] usb 1-2: USB disconnect, device number 5 Nov 2 17:52:25 chris-BlackTower wpa_supplicant[1213]: wlp6s0: Reject scan trigger since one is already pending Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545188] audit: type=1400 audit(1572717167.836:71): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/sbin/route" pid=15859 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545588] audit: type=1400 audit(1572717167.836:72): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/bin/ip" pid=15860 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:47 chris-BlackTower kernel: [ 5481.545989] audit: type=1400 audit(1572717167.836:73): apparmor="DENIED" operation="exec" profile="snap.syncthing.syncthing" name="/bin/ip" pid=15861 comm="syncthing" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 Nov 2 17:52:58 chris-BlackTower xdg-desktop-por[2074]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: App introspection not allowed Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.424278] usb 1-2: new high-speed USB device number 6 using ehci-pci Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584559] usb 1-2: New USB device found, idVendor=04b8, idProduct=1109, bcdDevice= 1.00 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584565] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584568] usb 1-2: Product: XP-960 Series Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584570] usb 1-2: Manufacturer: EPSON Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.584573] usb 1-2: SerialNumber: 57355359303299 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.588547] usblp 1-2:1.1: usblp0: USB Bidirectional printer dev 6 if 1 alt 0 proto 2 vid 0x04B8 pid 0x1109 Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.588832] usb-storage 1-2:1.2: USB Mass Storage device detected Nov 2 17:53:29 chris-BlackTower kernel: [ 5523.589015] scsi host6: usb-storage 1-2:1.2 Nov 2 17:53:29 chris-BlackTower mtp-probe: checking bus 1, device 6: "/sys/devices/pci:00/:00:12.2/usb1/1-2" Nov 2 17:53:29 chris-BlackTower mtp-probe: bus: 1, device: 6 was not an MTP device Nov 2 17:53:29 chris-BlackTower systemd[1]: Starting Configure Plugged-In Printer... Nov 2 17:53:29 chris-BlackTower udev-configure-printer[15961]: add usb-001-006 Nov 2 17:53:29 chris-BlackTower mtp-probe: checking bus 1, device 6: "/sys/devices/pci:00/:00:12.2/usb1/1-2" Nov 2 17:53:29 chris-BlackTower mtp-probe: bus: 1
[Desktop-packages] [Bug 1851058] Re: Live session any mouse or keyboard command is ignored
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/1851058 ** Tags added: iso-testing -- 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/1851058 Title: Live session any mouse or keyboard command is ignored Status in xorg package in Ubuntu: New Bug description: The problem happens in the live session. Ubiquity starts ok, The default desktop is displayed, but any mouse or keyboard command is ignored. If instead of "Try Ubuntu" I select "install Ubuntu" the install runs fine but the new installed system has the problem described in bug #1850969. Same problem with ISO Alpha amd64 (20191101), 20191102, 20191030 and 20191031 also on a different hardware (HP laptop) and also selecting 'graphic failsafe' Now I'm working with Wayland session because X11 does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 17:36:01 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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+git20190815-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/1851058/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
I am also facing this issue in Ubuntu 19.10 Eoan Ermine -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu Bionic) Status: New => Confirmed -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1850069] Re: No sound output at chromium-browser 79.0.3941.4 dev channel
https://bugs.chromium.org/p/chromium/issues/detail?id=1018580#c18 None of the following specific Audio flags prefixed with --enable-features= AudioServiceLaunchOnStartup AudioServiceAudioStreams AudioServiceOutOfProcess have any affect. Launching Chromium with --no-sandbox is the only means that have tried so far which results in audio being output at Chromium 79.0.3941.4. Is that the expected result of the design and implementation of audio now? -- 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/1850069 Title: No sound output at chromium-browser 79.0.3941.4 dev channel Status in chromium-browser package in Ubuntu: New Bug description: Steps to reproduce the problem: 1. Play sounds (video, audio, speech synthesis) 2. 3. What is the expected behavior? 1. Sound should be output to headphones or speakers What went wrong? 1. No sound is output to headphones or speakers DOMException: Could not start audio source Did this work before? Yes 79.0.3921.0 Does this work in other browsers? Yes Chrome version: 79.0.3941.4 Channel: n/a ALSA lib pcm_direct.c:1722:(snd1_pcm_direct_parse_open_conf) The field ipc_gid must be a valid group (create group audio) [32691:32691:1027/165318.863140:ERROR:alsa_util.cc(204)] PcmOpen: default,Invalid argument https://bugs.chromium.org/p/chromium/issues/detail?id=1018580 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 79.0.3941.4-0ubuntu0.18.04.1 [origin: LP-PPA-chromium-team-dev] ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17 Uname: Linux 4.15.0-20-lowlatency i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 CasperVersion: 1.394 CrashDB: ubuntu CurrentDesktop: XFCE DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-eDP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAGrz0RABEXAQSVHxF4AoflpFZQniYNUFQBAQEBAQEBAQEBAQEBAQEBFDeAuHA4JEAQED4ANa0QAAAaFDeAuHA4JEAQED4ANa0QAAAa/gBYVFJZOYBCMTQwSEFOQQKeAAoBCiAgAHg= modes: 1920x1080 Date: Sun Oct 27 17:45:32 2019 Desktop-Session: 'ubuntustudio' '/etc/xdg/xdg-ubuntustudio:/etc/xdg:/etc/xdg' '/usr/share/ubuntustudio:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstalledPlugins: LiveMediaBuild: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 (20180426) Load-Avg-1min: 0.47 Load-Processes-Running-Percent: 0.1% MachineType: Dell Inc. Latitude E7440 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/ubuntustudio.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz SourcePackage: chromium-browser ThirdParty: True UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 03HFCG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd05/01/2014:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn03HFCG:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1850069/+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 1790608] Re: [snap] Libreoffice does not open files from thunderbird (more general: from /tmp)
This is also happening to me, but I don't have a snap version installed, I don't even know what that is. -- 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/1790608 Title: [snap] Libreoffice does not open files from thunderbird (more general: from /tmp) Status in libreoffice package in Ubuntu: Confirmed Bug description: I received a document via e-mail in Thunderbird. I have the Libreoffice snap package installed. When I want to open the document from Thunderbird, I see the Libreoffice splash screen, and then a dialog stating "/tmp/mozilla_0/.docx does not exist." The same dialog appears when I navigate to the folder in Files and want to open it. When I copy the file to my desktop, however, I can open it without problems. I guess the source of the issue is confinement, that the Libreoffice snap can only access files from $HOME. But this breaks the case where thunderbird creates a temporary copy in /tmp. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1790608/+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 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu Bionic) Status: New => Confirmed -- 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/1727908 Title: Software & Updates application does not permit changes on the "Other Software" tab Status in gnome-shell package in Ubuntu: Confirmed Status in software-properties package in Ubuntu: Confirmed Status in gnome-shell source package in Bionic: Confirmed Status in software-properties source package in Bionic: Confirmed Bug description: On the "Other Software" tab, I am unable to select "Canonical Partners". Similarly, the other checkboxes on the "Other Software" can not be clicked. Clicking on a checkbox has no effect, and a dialog requesting the admin password is not presented. However, activating or deactivating checkboxes on other tabs causes an authorization dialog to be presented to the user. I experience this bug in an an Xorg session. sources.list and sources.list.d have the following permissions: -rw-r--r-- 1 root root 2897 Oct 26 22:35 sources.list drwxr-xr-x 2 root root 4096 Oct 26 21:29 sources.list.d All files in sources.list.d have the following permissions as this example: -rw-r--r-- 1 root root 189 Oct 25 21:50 google-chrome.list $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 $ apt-cache policy software-properties-gtk software-properties-gtk: Installed: 0.96.24.17 Candidate: 0.96.24.17 Version table: *** 0.96.24.17 500 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: software-properties-gtk 0.96.24.17 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Oct 26 22:45:09 2017 InstallationDate: Installed on 2017-10-26 (1 days ago) InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark" PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1843984] Re: iubuntu dash truncate the name of all application searched - no way to see the complete name
*** This bug is a duplicate of bug 968213 ***
https://bugs.launchpad.net/bugs/968213
hank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 968213, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** Package changed: dash (Ubuntu) => gnome-shell (Ubuntu)
** This bug has been marked a duplicate of bug 968213
Too many icons in Gnome Shell Activities Overview require ellipses
--
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/1843984
Title:
iubuntu dash truncate the name of all application searched - no way to
see the complete name
Status in gnome-shell package in Ubuntu:
New
Bug description:
I installed avidemux, which installed two packages with the same initial part
of their names: avidemux2.7_jobs_qt5 and avidemux2.7_qt5.
By clicking SUPER, the Dash will appear. If I search for "avidemux" the two
elements appear but because of the name truncated, I can't differentiate them,
either are showed with the name "avidemux 2.7 (".
Right-clicking on one of these there is the "details" option but it bring me
to the "ubuntu software" application that does not recognize the application
saying "application not found".
I think that the choose to truncate the application name in the Dash is
simply a design bug.
This is very annoying: there is enough space to see the compllete name,
instead of truncate it to the preview image size...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dash 0.5.8-2.10
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 14 10:42:12 2019
InstallationDate: Installed on 2019-09-07 (6 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1843984/+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 1851058] [NEW] Live session any mouse or keyboard command is ignored
Public bug reported: The problem happens in the live session. Ubiquity starts ok, The default desktop is displayed, but any mouse or keyboard command is ignored. If instead of "Try Ubuntu" I select "install Ubuntu" the install runs fine but the new installed system has the problem described in bug #1850969. Same problem with ISO Alpha amd64 (20191101), 20191102, 20191030 and 20191031 also on a different hardware (HP laptop) and also selecting 'graphic failsafe' Now I'm working with Wayland session because X11 does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 17:36:01 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible ubuntu wayland-session -- 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/1851058 Title: Live session any mouse or keyboard command is ignored Status in xorg package in Ubuntu: New Bug description: The problem happens in the live session. Ubiquity starts ok, The default desktop is displayed, but any mouse or keyboard command is ignored. If instead of "Try Ubuntu" I select "install Ubuntu" the install runs fine but the new installed system has the problem described in bug #1850969. Same problem with ISO Alpha amd64 (20191101), 20191102, 20191030 and 20191031 also on a different hardware (HP laptop) and also selecting 'graphic failsafe' Now I'm working with Wayland session because X11 does not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 17:36:01 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa"
[Desktop-packages] [Bug 1847516] Re: Alt+Shift does not change layout
** Package changed: ubuntu => gnome-settings-daemon (Ubuntu) ** Tags added: eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1847516 Title: Alt+Shift does not change layout Status in gnome-settings-daemon package in Ubuntu: New Bug description: Ubuntu 19.10 Daily 09.10.2019 and older After settings in gnome tweaks I expect changing of keyboard layout, but it still super+space. Also , shortcut's "Set shortcut' ignores Alt+Shift. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1847516/+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 1843984] [NEW] iubuntu dash truncate the name of all application searched - no way to see the complete name
You have been subscribed to a public bug:
I installed avidemux, which installed two packages with the same initial part
of their names: avidemux2.7_jobs_qt5 and avidemux2.7_qt5.
By clicking SUPER, the Dash will appear. If I search for "avidemux" the two
elements appear but because of the name truncated, I can't differentiate them,
either are showed with the name "avidemux 2.7 (".
Right-clicking on one of these there is the "details" option but it bring me to
the "ubuntu software" application that does not recognize the application
saying "application not found".
I think that the choose to truncate the application name in the Dash is simply
a design bug.
This is very annoying: there is enough space to see the compllete name, instead
of truncate it to the preview image size...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dash 0.5.8-2.10
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Sep 14 10:42:12 2019
InstallationDate: Installed on 2019-09-07 (6 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: dash
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic third-party-packages
--
iubuntu dash truncate the name of all application searched - no way to see the
complete name
https://bugs.launchpad.net/bugs/1843984
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 1847516] [NEW] Alt+Shift does not change layout
You have been subscribed to a public bug: Ubuntu 19.10 Daily 09.10.2019 and older After settings in gnome tweaks I expect changing of keyboard layout, but it still super+space. Also , shortcut's "Set shortcut' ignores Alt+Shift. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Alt+Shift does not change layout https://bugs.launchpad.net/bugs/1847516 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon 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 1761606] Re: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session.
Thanks to Alkis Georgopoulos @alkisg for the hint, `Exec=nm-applet --indicator` indeed does work for me in LUbuntu 18.0.4. -- 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/1761606 Title: Two Wi-Fi network applets appear after logging back into live-usb Lubuntu 18.04 session. Status in network-manager-applet package in Ubuntu: Confirmed Bug description: Lubuntu 18.04 ISO version: 20180404 network-manager-applet version: 1.8.10-2ubuntu1 After logging into my Wi-Fi network then logging out then logging back into the Live-USB session Two Wi-Fi network applets appeared where One would be the expected outcome. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager-gnome 1.8.10-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CasperVersion: 1.392 CurrentDesktop: LXDE Date: Thu Apr 5 21:06:24 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.166 metric 600 LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash 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: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134 wifi 1522962221 Thu Apr 5 21:03:41 2018 yes 0 no /org/freedesktop/NetworkManager/Settings/2 yes wlp3s0 activated /org/freedesktop/NetworkManager/ActiveConnection/2 -- Wired connection 1 472b45a7-c95b-3638-b452-3f6720688df8 ethernet 1522961321 Thu Apr 5 20:48:41 2018 yes 4294966297no /org/freedesktop/NetworkManager/Settings/1 no -- -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Zero-Daya2f10fa9-551c-4a4f-93ba-5fe6c22c4134 /org/freedesktop/NetworkManager/ActiveConnection/2 enp0s25 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1761606/+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 1832426] Re: "Program" is not responding when debugging in gdb
I am also affected in Ubuntu 19.10 -- 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/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: Confirmed Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+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 1851046] [NEW] Enable Last.fm provider
Public bug reported: Since a while now GOA supports Last.fm accounts but for some reason this provider is excluded in the Ubuntu build parameters of this package. Is there a specific reason why this is not enabled? Would it be possible to enable this provider as well? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-online-accounts 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 2 16:07:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-26 (1437 days ago) InstallationMedia: It SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to eoan on 2019-10-20 (13 days ago) ** Affects: gnome-online-accounts (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1851046 Title: Enable Last.fm provider Status in gnome-online-accounts package in Ubuntu: New Bug description: Since a while now GOA supports Last.fm accounts but for some reason this provider is excluded in the Ubuntu build parameters of this package. Is there a specific reason why this is not enabled? Would it be possible to enable this provider as well? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-online-accounts 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Nov 2 16:07:05 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2015-11-26 (1437 days ago) InstallationMedia: It SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to eoan on 2019-10-20 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1851046/+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 1850529] Re: Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
I confirm the same issue on 16.04. Firefox is now entirely unusable.
--
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/1850529
Title:
Crash after update to 71.0~b5+build1-0ubuntu0.16.04.1
Status in firefox package in Ubuntu:
Confirmed
Bug description:
After update from: 70.0+build2-0ubuntu0.16.04.1 to
71.0~b5+build1-0ubuntu0.16.04.1 app is not starting. I got constantly
message that I can Refresh Firefox (crash) or Start in safe mode (also
crash).
Tech details:
Description: Ubuntu 16.04.6 LTS
Release: 16.04
package name: 71.0~b5+build1-0ubuntu0.16.04.1
Crash log details:
AdapterDeviceID: 0x1616
AdapterDriverVendor: mesa/i965
AdapterDriverVersion: 18.0.5.0
AdapterVendorID: 0x8086
BuildID: 20191028161640
ContentSandboxCapabilities: 119
ContentSandboxCapable: 1
ContentSandboxLevel: 4
CrashTime: 1572373123
DOMIPCEnabled: 1
FramePoisonBase: 9223372036600930304
FramePoisonSize: 4096
InstallTime: 1572364967
IsWayland: 0
IsWaylandDRM: 0
MozCrashReason: MOZ_RELEASE_ASSERT(len.isValid()) (Substring tuple length is
invalid)
Notes: Ubuntu 16.04.6 LTSFP(D00-L1000-W-T000) WR? WR- OMTP? OMTP-
ProductID: {ec8030f7-c20a-464f-9b0e-13a3a9e97384}
ProductName: Firefox
ReleaseChannel: beta
SafeMode: 1
SecondsSinceLastCrash: 816
StartupCrash: 0
StartupTime: 1572373025
TelemetryEnvironment:
{"build":{"applicationId":"{ec8030f7-c20a-464f-9b0e-13a3a9e97384}","applicationName":"Firefox","architecture":"x86-64","buildId":"20191028161640","version":"71.0","vendor":"Mozilla","displayVersion":"71.0b5","platformVersion":"71.0","xpcomAbi":"x86_64-gcc3","updaterAvailable":false},"partner":{"distributionId":null,"distributionVersion":null,"partnerId":null,"distributor":null,"distributorChannel":null,"partnerNames":[]},"system":{"memoryMB":15965,"virtualMaxMB":null,"cpu":{"count":4,"cores":2,"vendor":"GenuineIntel","family":6,"model":61,"stepping":4,"l2cacheKB":256,"l3cacheKB":3072,"speedMHz":2700,"extensions":["hasMMX","hasSSE","hasSSE2","hasSSE3","hasSSSE3","hasSSE4_1","hasSSE4_2","hasAVX","hasAVX2","hasAES"]},"os":{"name":"Linux","version":"4.15.0-66-generic","locale":"en-US"},"hdd":{"profile":{"model":null,"revision":null,"type":null},"binary":{"model":null,"revision":null,"type":null},"system":{"model":null,"revision":null,"type":null}},"gfx":{"D2DEnabled":null,"DWriteEnabled":null,"ContentBackend":"Skia","Headless":false,"adapters":[{"description":"Mesa
DRI Intel(R) HD Graphics 5500 (Broadwell GT2)
","vendorID":"0x8086","deviceID":"0x1616","subsysID":null,"RAM":3072,"driver":null,"driverVendor":"mesa/i965","driverVersion":"18.0.5.0","driverDate":null,"GPUActive":true}],"monitors":[{"screenWidth":1366,"screenHeight":768}],"features":{"compositor":"none","gpuProcess":{"status":"blocked"},"wrQualified":{"status":"blocked-release-channel-intel"},"webrender":{"status":"unavailable-in-safe-mode"}}},"appleModelId":null},"settings":{"blocklistEnabled":true,"e10sEnabled":true,"e10sMultiProcesses":8,"telemetryEnabled":true,"locale":"en-US","intl":{},"update":{"channel":"beta","enabled":true,"autoDownload":false},"userPrefs":{"app.shield.optoutstudies.enabled":false,"browser.cache.disk.capacity":1048576,"browser.newtabpage.enabled":false,"browser.shell.checkDefaultBrowser":true,"browser.search.region":"US","browser.search.suggest.enabled":false,"browser.search.widget.inNavBar":false,"browser.startup.homepage":"","browser.startup.page":3,"browser.urlbar.suggest.searches":false,"devtools.chrome.enabled":false,"devtools.debugger.remote-enabled":false,"extensions.blocklist.url":"https://blocklists.settings.services.mozilla.com/v1/blocklist/3/%20/%20/","extensions.formautofill.addresses.enabled":false,"extensions.formautofill.creditCards.enabled":false,"privacy.donottrackheader.enabled":true},"sandbox":{"effectiveContentProcessLevel":4},"addonCompatibilityCheckEnabled":true,"isDefaultBrowser":null},"profile":{}}
ThreadIdNameMapping: 7556:"Gecko_IOThread",7557:"JS Watchdog",7558:"JS
Helper",7559:"JS Helper",7560:"JS Helper",7561:"JS
Helper",7562:"Timer",7563:"Netlink Monitor",7564:"Socket Thread",7568:"Cache2
I/O",7569:"Cookie",7570:"StreamTrans #1",7571:"GMPThread",7572:"Worker
Launcher",7573:"SoftwareVsyncThread",7574:"Compositor",7575:"ImgDecoder
#1",7576:"ImageIO",7580:"ImageBridgeChild",7581:"IPDL Background",7582:"DOM
Worker",7584:"QuotaManager
IO",7587:"StyleThread#0",7589:"StyleThread#2",7588:"StyleThread#1",7593:"DOM
Worker",7630:"DataStorage",7631:"DNS Resolver #1",7632:"DNS Resolver
#2",7633:"StreamTrans #7",7646:"IndexedDB #2",7647:"StreamTrans
#8",7648:"StreamTrans #9",7649:"StreamTrans #10",
Throttleable: 1
UptimeTS: 98.30915265
Vendor: Mozilla
Version: 71.0
useragent_locale: en-US
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1850529/+subscriptions
--
Mai
[Desktop-packages] [Bug 1851041] Re: Occasionally, the keyboard cannot be input
19.04之前从未出现过类似情况 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1851041 Title: Occasionally, the keyboard cannot be input Status in ibus-libpinyin package in Ubuntu: New Bug description: 有时键盘无法输入文字，功能键正常，约几十秒后恢复正常，期间无法打开输入法设置 Sometimes the keyboard cannot input text and the function key is normal. It will return to normal after several tens of seconds. During this period, the input method setting cannot be opened ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus-libpinyin 1.11.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Sat Nov 2 22:00:06 2019 InstallationDate: Installed on 2019-10-18 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ibus-libpinyin UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.default.apport: 2019-10-18T23:13:49.837467 mtime.conffile..etc.logrotate.d.apport: 2019-10-29T22:06:09.766287 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1851041/+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 1851041] [NEW] Occasionally, the keyboard cannot be input
Public bug reported: 有时键盘无法输入文字，功能键正常，约几十秒后恢复正常，期间无法打开输入法设置 Sometimes the keyboard cannot input text and the function key is normal. It will return to normal after several tens of seconds. During this period, the input method setting cannot be opened ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus-libpinyin 1.11.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Sat Nov 2 22:00:06 2019 InstallationDate: Installed on 2019-10-18 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ibus-libpinyin UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.default.apport: 2019-10-18T23:13:49.837467 mtime.conffile..etc.logrotate.d.apport: 2019-10-29T22:06:09.766287 ** Affects: ibus-libpinyin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1851041/+attachment/5302279/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus-libpinyin in Ubuntu. https://bugs.launchpad.net/bugs/1851041 Title: Occasionally, the keyboard cannot be input Status in ibus-libpinyin package in Ubuntu: New Bug description: 有时键盘无法输入文字，功能键正常，约几十秒后恢复正常，期间无法打开输入法设置 Sometimes the keyboard cannot input text and the function key is normal. It will return to normal after several tens of seconds. During this period, the input method setting cannot be opened ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus-libpinyin 1.11.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 Date: Sat Nov 2 22:00:06 2019 InstallationDate: Installed on 2019-10-18 (15 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ibus-libpinyin UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] modified.conffile..etc.logrotate.d.apport: [modified] mtime.conffile..etc.default.apport: 2019-10-18T23:13:49.837467 mtime.conffile..etc.logrotate.d.apport: 2019-10-29T22:06:09.766287 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1851041/+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 1851015] Re: All LibreOffice applications not starting without an error message
Part of LibreOffice's core feature set is to allow remote content within documents. While this plug may be connected by default, you may disconnect if you wish: snap disconnect libreoffice:network ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1851015 Title: All LibreOffice applications not starting without an error message Status in libreoffice package in Ubuntu: Invalid Bug description: snap info libreoffice name:libreoffice summary: LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bugs?field.tag=snap license: unset description: | LibreOffice is a powerful and free office suite, used by millions of people around the world. Its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most versatile Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.filebug - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer snap-id: CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v tracking: stable refresh-date: today at 13:42 +03 channels: stable:6.3.2.2 2019-10-22 (154) 442MB - candidate: 6.3.2.2 2019-10-22 (154) 442MB - beta: ↑ edge: ↑ installed: 6.3.2.2(154) 442MB - uname -a Linux The-pc 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:19:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux State: Fresh snap install with only some connection tweak snap connections libreoffice audio-playbacklibreoffice:audio-playback :audio-playback - bluez libreoffice:bluez - - content[gnome-3-28-1804] libreoffice:gnome-3-28-1804 gnome-3-28-1804:gnome-3-28-1804 - content[gtk-3-themes] libreoffice:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] libreoffice:icon-themes gtk-common-themes:icon-themes- content[sound-themes] libreoffice:sound-themes gtk-common-themes:sound-themes - cups-control libreoffice:cups-control- - desktop libreoffice:desktop :desktop - gsettings libreoffice:gsettings :gsettings - home libreoffice:home:home - network libreoffice:network - - network-bind libreoffice:network-bind- - opengllibreoffice:opengl :opengl - pulseaudiolibreoffice:pulseaudio - - removable-media libreoffice:removable-media - - screen-inhibit-controllibreoffice:screen-inhibit-control :screen-inhibit-control - unity7libreoffice:unity7 :unity7 - wayland libreoffice:wayland :wayland - Only reason i'm using snap is i don't want any application that can access home to connect internet and i want a office application that can access to home but not internet since it is a absurd requirement for a office application to connect internet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1851015/+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 1851018] [NEW] xorg have some bugs.
Public bug reported: 1.When pasting, often I paste not the newest copied/cut text/image, but the previous one. Very annoying! It is the case in all programs (LibreOffice, Kate, Firefox etc.). 2.When a program has problems - e.g. because something takes a long time, and it offers to wait or close down, sometimes the whole computer becomes unresponsive - I can move the mouse, but not change to other running programs. In the end, I have to hard reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 19:49:35 2019 DistUpgraded: 2019-10-19 08:58:21,996 DEBUG install of snap core18 succeeded DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: mt7601, 3.0.0.4: added nvidia, 430.50, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:1131] InstallationDate: Installed on 2019-07-06 (119 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7850 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=41f99f54-13ee-4bc3-8dcd-bca83277990a ro quiet splash nomodeset video=uvesafb:mode_option=1366x7680-24,mtrr=3,scroll=ywrap vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-19 (14 days ago) dmi.bios.date: 02/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.11:bd02/16/2016:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnZ97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan possible-manual-nvidia-install ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1851018 Title: xorg have some bugs. Status in xorg package in Ubuntu: New Bug description: 1.When pasting, often I paste not the newest copied/cut text/image, but the previous one. Very annoying! It is the case in all programs (LibreOffice, Kate, Firefox etc.). 2.When a program has problems - e.g. because something takes a long time, and it offers to wait or close down, sometimes the whole computer becomes unresponsive - I can move the mouse, but not change to other running programs. In the end, I have to hard reboot. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 430.50 Thu Sep 5 22:36:31
[Desktop-packages] [Bug 1851015] [NEW] All LibreOffice applications not starting without an error message
Public bug reported: snap info libreoffice name:libreoffice summary: LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bugs?field.tag=snap license: unset description: | LibreOffice is a powerful and free office suite, used by millions of people around the world. Its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most versatile Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.filebug - libreoffice.impress - libreoffice - libreoffice.math - libreoffice.writer snap-id: CpUkI0qPIIBVRsjy49adNq4D6Ra72y4v tracking: stable refresh-date: today at 13:42 +03 channels: stable:6.3.2.2 2019-10-22 (154) 442MB - candidate: 6.3.2.2 2019-10-22 (154) 442MB - beta: ↑ edge: ↑ installed: 6.3.2.2(154) 442MB - uname -a Linux The-pc 4.15.0-15-generic #16~16.04.1-Ubuntu SMP Thu Apr 5 12:19:23 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux State: Fresh snap install with only some connection tweak snap connections libreoffice audio-playbacklibreoffice:audio-playback :audio-playback - bluez libreoffice:bluez - - content[gnome-3-28-1804] libreoffice:gnome-3-28-1804 gnome-3-28-1804:gnome-3-28-1804 - content[gtk-3-themes] libreoffice:gtk-3-themes gtk-common-themes:gtk-3-themes - content[icon-themes] libreoffice:icon-themes gtk-common-themes:icon-themes- content[sound-themes] libreoffice:sound-themes gtk-common-themes:sound-themes - cups-control libreoffice:cups-control- - desktop libreoffice:desktop :desktop - gsettings libreoffice:gsettings :gsettings - home libreoffice:home:home - network libreoffice:network - - network-bind libreoffice:network-bind- - opengllibreoffice:opengl :opengl - pulseaudiolibreoffice:pulseaudio - - removable-media libreoffice:removable-media - - screen-inhibit-controllibreoffice:screen-inhibit-control :screen-inhibit-control - unity7libreoffice:unity7 :unity7 - wayland libreoffice:wayland :wayland - Only reason i'm using snap is i don't want any application that can access home to connect internet and i want a office application that can access to home but not internet since it is a absurd requirement for a office application to connect internet. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1851015 Title: All LibreOffice applications not starting without an error message Status in libreoffice package in Ubuntu: New Bug description: snap info libreoffice name:libreoffice summary: LibreOffice is a powerful office suite including word processing and creation of spreadsheets, slideshows and databases publisher: Canonical✓ contact: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bugs?field.tag=snap license: unset description: | LibreOffice is a powerful and free office suite, used by millions of people around the world. Its clean interface and feature-rich tools help you unleash your creativity and enhance your productivity. LibreOffice includes several applications that make it the most versatile Free and Open Source office suite on the market: Writer (word processing), Calc (spreadsheets), Impress (presentations), Draw (vector graphics and flowcharts), Base (databases), and Math (formula editing). commands: - libreoffice.base - libreoffice.calc - libreoffice.draw - libreoffice.filebug - libreoffice.impress - libreoffice - libreoffice.math
[Desktop-packages] [Bug 1851011] Re: Chromium is now a snap package
** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu) -- 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/1851011 Title: Chromium is now a snap package Status in chromium-browser package in Ubuntu: New Bug description: Starting with Ubuntu Eoan, chromium-browser is shipped as snap package, instead of a regular .deb package. This is wasteful, since all dependencies have to duplicated. It also breaks apt, which no longer controls all the software on my system. I now have to deal with two tools to keep everything up-to-date. Please restrict snap packages to big, complimentary packages, which chromium definitely isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851011/+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 1730903] Re: Firefox has screen tearing on Intel Graphics with default setting
Affected in Firefox 70 (64-Bit) on Ubuntu 18.04.3. ** Tags added: bionic -- 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/1730903 Title: Firefox has screen tearing on Intel Graphics with default setting Status in firefox package in Ubuntu: Confirmed Bug description: Firefox has choppy scrolling/tearing on pretty much any web page with the default settings on Intel Graphics. Since the modesetting driver uses OpenGL, you have to force enable layers.acceleration (layers.acceleration.force-enabled) in about:config to remedy this. The other thing that works is to enable the Intel DDX driver with TearFree. This is on a fresh Ubuntu 17.10 install in the Xorg session but the same would apply to Wayland as well as Xwayland also uses the modesetting driver. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: firefox 56.0+build6-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: prashant 1605 F...m pulseaudio /dev/snd/controlC1: prashant 1605 F pulseaudio /dev/snd/controlC0: prashant 1605 F pulseaudio BuildID: 20171003222101 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Nov 8 13:36:53 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-11-03 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) IpRoute: default via 192.168.1.1 dev wlp6s0 proto static metric 600 192.168.1.0/24 dev wlp6s0 proto kernel scope link src 192.168.1.101 metric 600 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=56.0/20171003222101 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 05JF1T dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd10/15/2015:svnDellInc.:pnVostro3558:pvr01:rvnDellInc.:rn05JF1T:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Vostro 3558 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1730903/+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 1851011] [NEW] Chromium is now a snap package
You have been subscribed to a public bug: Starting with Ubuntu Eoan, chromium-browser is shipped as snap package, instead of a regular .deb package. This is wasteful, since all dependencies have to duplicated. It also breaks apt, which no longer controls all the software on my system. I now have to deal with two tools to keep everything up-to-date. Please restrict snap packages to big, complimentary packages, which chromium definitely isn't. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- Chromium is now a snap package https://bugs.launchpad.net/bugs/1851011 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 1792932] Re: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed.
Can't reproduce bug at Bionic, may be after some packege updates it's gone. -- 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/1792932 Title: Desktop fails to boot in vbox: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Bionic: Incomplete Status in xorg-server source package in Cosmic: Fix Released Bug description: https://errors.ubuntu.com/problem/4ffab1fb339140b2c39fa0d096293706399e7280 https://errors.ubuntu.com/problem/d18c1a21ca8ed1bb6cca06ddb5350187bed44f80 --- Test Case: Boot Ubuntu Cosmic Desktop 20180916 on Virtual Box Actual Result Black screen or dropped to the login screen if the user skips ubiquity-dm Workaround: Add nomodeset on the kernel command line or from the boot menu, press F6 then select nomodeset Possibly a duplicate of bug 1432137 ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 AssertionMessage: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. CasperVersion: 1.395 CompositorRunning: None Date: Mon Sep 17 12:42:24 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180916) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/999/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper initrd=/casper/initrd --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 __assert_fail_base (fmt=0x7f60fa1e3858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=) at assert.c:92 __GI___assert_fail (assertion=0x563dbf96db7d "!global_keys[type].created", file=0x563dbf96db38 "../../../../dix/privates.c", line=384, function=0x563dbf96dde0 "dixRegisterPrivateKey") at assert.c:101 dixRegisterPrivateKey () Title: Xorg assert failure: Xorg: ../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1792932/+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 1851007] Re: Login option 'GNOME + Remmina' not working
** Tags removed: wayland-session -- 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/1851007 Title: Login option 'GNOME + Remmina' not working Status in xorg package in Ubuntu: New Bug description: Selecting Login option 'GNOME + Remmina' I'm just returned to login panel with no message. corrado@corrado-p13-ff-1101:~$ inxi -Fx System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 19.2.1 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Sound Server: ALSA v: k5.3.0-18-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 5.30 GiB (0.6%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 15.62 GiB used: 5.30 GiB (33.9%) fs: ext4 dev: /dev/sda13 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 37.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 197 Uptime: 7m Memory: 7.49 GiB used: 1.00 GiB (13.4%) Init: systemd runlevel: 5 Compilers: gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 corrado@corrado-p13-ff-1101:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 08:17:56 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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:
[Desktop-packages] [Bug 1843392] Re: [snap] smart card reader no longer works
https://github.com/glasen/snap- ausweisapp2-ce/blob/master/snap/snapcraft.yaml This is another snap that supports smart card readers. It seems to package pcscd... -- 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/1843392 Title: [snap] smart card reader no longer works Status in chromium-browser package in Ubuntu: Confirmed Bug description: chromium uses the Netscape Cryptographic Module to access smartcards for authentication purposes. This stopped working when switching to the snap version. Chromium would normally access the setup in ~/.pki/nssdb/pkcs11.txt That file would refer to a library used to access the smart card. I.e /usr/lib/x86_64-linux-gnu/pkcs11/opensc- pkcs11.so The problem can be bypassed by manually launching chromium via: /snap/chromium/current/usr/lib/chromium-browser/chrome To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1843392/+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 1851007] [NEW] Login option 'GNOME + Remmina' not working
Public bug reported: Selecting Login option 'GNOME + Remmina' I'm just returned to login panel with no message. corrado@corrado-p13-ff-1101:~$ inxi -Fx System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial: UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31199 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 801 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 19.2.1 direct render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 Sound Server: ALSA v: k5.3.0-18-generic Network: Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:Local Storage: total: 931.51 GiB used: 5.30 GiB (0.6%) ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB Partition: ID-1: / size: 15.62 GiB used: 5.30 GiB (33.9%) fs: ext4 dev: /dev/sda13 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 Sensors: System Temperatures: cpu: 37.5 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 197 Uptime: 7m Memory: 7.49 GiB used: 1.00 GiB (13.4%) Init: systemd runlevel: 5 Compilers: gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 corrado@corrado-p13-ff-1101:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Nov 2 08:17:56 2019 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912] InstallationDate: Installed on 2019-11-01 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/11/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: H110M-G/M.2 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 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+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal reproducible ubuntu wayland-session -- 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/1851007 Title:
[Desktop-packages] [Bug 1844739] Re: Latest Firefox update freezing my system
** Attachment added: "log messages1" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+attachment/5302201/+files/log%20messages1 -- 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/1844739 Title: Latest Firefox update freezing my system Status in firefox package in Ubuntu: Incomplete Bug description: The latest updates of firefox renders my machine useless. I'm sending it as is hopefully before it freezes completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 69.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 BuildID: 20190828152935 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 01:22:17 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-05-01 (506 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=69.0/20190828152935 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+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 1844739] Re: Latest Firefox update freezing my system
Hello @Oliver Tilloy(osomon), The good news are that I can at least use the browser most of the time but not all the time... I'm adding log messages. I initiated oom to kill the processes instead of hard booting. I hope it will help you to see what's happening. Thank you, Paz -- 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/1844739 Title: Latest Firefox update freezing my system Status in firefox package in Ubuntu: Incomplete Bug description: The latest updates of firefox renders my machine useless. I'm sending it as is hopefully before it freezes completely. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 69.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 Uname: Linux 4.15.0-62-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: i386 BuildID: 20190828152935 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 01:22:17 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:997 DefaultProfileThemes: extensions.sqlite corrupt or missing InstallationDate: Installed on 2018-05-01 (506 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US SHELL=/bin/bash Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=69.0/20190828152935 (In use) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1844739/+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
