[Desktop-packages] [Bug 1858072] [NEW] Webdav is not python3 compatible
Public bug reported:
The webdav backend calls base64.encodestring, which (counterintuitively)
expects a bytes input in python3.
# duplicity incremental \
--asynchronous-upload \
--full-if-older-than 1M \
-v 9 \
--exclude='./Documents/google_drive/**' \
--include='./src/**' \
--exclude='**' \
'.' \
"$target_url"
Using archive dir:
/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f
Using backup name: 74043f3f63750b8654c846cb69e2833f
GPG binary is gpg, version (2, 2, 12)
Import of duplicity.backends.adbackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.jottacloudbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pcabackend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Using WebDAV protocol http
Using WebDAV host REDACTED port None
Using WebDAV directory /webdav/backup/
Main action: inc
Acquiring lockfile
b'/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f/lockfile'
duplicity $version ($reldate)
Args: /usr/bin/duplicity incremental --asynchronous-upload --full-if-older-than
1M -v 9 --exclude=./Documents/google_drive/** --include=./src/** --exclude=** .
webdavs://RED:ACT@ED/webdav/backup
Linux zenbook-k 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019
x86_64 x86_64
/usr/bin/python3 3.7.5 (default, Nov 20 2019, 09:21:52)
[GCC 9.2.1 20191008]
Using temporary directory /tmp/duplicity-7ypg8z7d-tempdir
Registering (mkstemp) temporary file
/tmp/duplicity-7ypg8z7d-tempdir/mkstemp-v33ewch5-1
Temp has 50636972032 available, backup will use approx 482344960.
WebDAV create connection on 'REDACTED'
WebDAV PROPFIND /remote.php/webdav/backup/ request with headers: {'Connection':
'keep-alive', 'Depth': '1'}
WebDAV data length: 95
WebDAV response status 401 with reason 'Unauthorized'.
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 371, in
inner_retry
return fn(self, *args)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 580, in list
return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 343, in _list
raise e
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 317, in _list
response = self.request(u"PROPFIND", self.directory, self.listbody)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 240, in request
self.headers[u'Authorization'] = self.get_authorization(response,
quoted_path)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 271, in get_authorization
return self.get_basic_authorization()
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 291, in get_basic_authorization
return u'Basic %s' % base64.encodestring(auth_string).strip()
File "/usr/lib/python3.7/base64.py", line 540, in encodestring
return encodebytes(s)
File "/usr/lib/python3.7/base64.py", line 527, in encodebytes
_input_type_check(s)
File "/usr/lib/python3.7/base64.py", line 513, in _input_type_check
raise TypeError(msg) from err
TypeError: expected bytes-like object, not str
Attempt 1 failed. TypeError: expected bytes-like object, not str
^CReleasing lockfile
b'/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f/lockfile'
Removing still remembered temporary file
/tmp/duplicity-7ypg8z7d-tempdir/mkstemp-v33ewch5-1
INT intercepted...exiting.
Releasing lockfile
b'/home/username/.cache/dupl
[Desktop-packages] [Bug 1856795] Re: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix
[Test case]
Connect to a x2go server on a session that has file sharing or audo-forwarding
enabled -> Error message "SCP: Warning: status code 1 received: scp:
~/.x2go/ssh: No such file or directory" needs to be clicked away with
"ok".
[Regression potential]
Very low as the patch removes "~" from the ssh string which is the same
as just using no path spec (":") as the default is the home dir of the logged
in remote user.
I have tested Graham's ppa packages and they work again as before the
libssh change and fix the bug reliably.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1856795
Title:
[SRU] X2Go Client broken by libssh CVE-2019-14889 fix
Status in libssh package in Ubuntu:
Invalid
Status in x2goclient package in Ubuntu:
Fix Released
Status in libssh source package in Xenial:
Invalid
Status in x2goclient source package in Xenial:
Confirmed
Status in libssh source package in Bionic:
Invalid
Status in x2goclient source package in Bionic:
Confirmed
Status in libssh source package in Disco:
Invalid
Status in x2goclient source package in Disco:
Confirmed
Status in libssh source package in Eoan:
Invalid
Status in x2goclient source package in Eoan:
Confirmed
Status in x2goclient package in Debian:
Fix Released
Bug description:
The recent CVE fix broke SCP support in libssh, which X2Go Client
(x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status
code 1 received: scp: ~username/.x2go/ssh: No such file or
directory\n". (Also note the literal "\n" there, but I guess we don't
really need to care about that.)
The previous version worked fine and rolling the libssh4 package back
fixes this issue, but also leaves users vulnerable to the fixed
security issue in its scp implementation.
I've been looking at the debdiff, but spotting the actual changes is very
difficult due to the reformatting that was done at the same time. This degraded
the patch(es) into one big blob.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+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 1856795] Re: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix
** Description changed:
+ [Test case]
+ Connect to a x2go server on a session that has file sharing or
audo-forwarding enabled -> Error message "SCP: Warning: status code 1 received:
scp: ~/.x2go/ssh: No such file or directory" needs to be clicked away
with "ok".
+
+ [Regression potential]
+ Very low as the patch removes "~" from the ssh string which is the same
as just using no path spec (":") as the default is the home dir of the logged
in remote user.
+
+ --
+
The recent CVE fix broke SCP support in libssh, which X2Go Client
(x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status code
1 received: scp: ~username/.x2go/ssh: No such file or directory\n".
(Also note the literal "\n" there, but I guess we don't really need to
care about that.)
The previous version worked fine and rolling the libssh4 package back
fixes this issue, but also leaves users vulnerable to the fixed security
issue in its scp implementation.
-
- I've been looking at the debdiff, but spotting the actual changes is very
difficult due to the reformatting that was done at the same time. This degraded
the patch(es) into one big blob.
+ I've been looking at the debdiff, but spotting the actual changes is
+ very difficult due to the reformatting that was done at the same time.
+ This degraded the patch(es) into one big blob.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1856795
Title:
[SRU] X2Go Client broken by libssh CVE-2019-14889 fix
Status in libssh package in Ubuntu:
Invalid
Status in x2goclient package in Ubuntu:
Fix Released
Status in libssh source package in Xenial:
Invalid
Status in x2goclient source package in Xenial:
Confirmed
Status in libssh source package in Bionic:
Invalid
Status in x2goclient source package in Bionic:
Confirmed
Status in libssh source package in Disco:
Invalid
Status in x2goclient source package in Disco:
Confirmed
Status in libssh source package in Eoan:
Invalid
Status in x2goclient source package in Eoan:
Confirmed
Status in x2goclient package in Debian:
Fix Released
Bug description:
[Test case]
Connect to a x2go server on a session that has file sharing or
audo-forwarding enabled -> Error message "SCP: Warning: status code 1 received:
scp: ~/.x2go/ssh: No such file or directory" needs to be clicked away
with "ok".
[Regression potential]
Very low as the patch removes "~" from the ssh string which is the same
as just using no path spec (":") as the default is the home dir of the logged
in remote user.
--
The recent CVE fix broke SCP support in libssh, which X2Go Client
(x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status
code 1 received: scp: ~username/.x2go/ssh: No such file or
directory\n". (Also note the literal "\n" there, but I guess we don't
really need to care about that.)
The previous version worked fine and rolling the libssh4 package back
fixes this issue, but also leaves users vulnerable to the fixed
security issue in its scp implementation.
I've been looking at the debdiff, but spotting the actual changes is
very difficult due to the reformatting that was done at the same time.
This degraded the patch(es) into one big blob.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+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 1858080] [NEW] ubuntu 19.10 - dock hides part of [full] screen hiding game function
Public bug reported: Ubuntu 19.10 'live' system * Steps to re-create 1. Boot 19.10 live system 2. enable 'universe' & `sudo apt update` 3. add "pingus' game 4. start game, change to fullscreen & exit 5, start game & play * Problem Ubuntu dock hides the select options (digger, float & lemmings functions) making game hard to play. * Expected behavior When game is started in full-screen mode, Ubuntu dock should not be visible. Note: I"ve not checked for duplicates properly, and this will be related to another bug report where Ubuntu-Dock appears when xscreensaver is running. (I'll do some more exploration & scanning when home) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 09:07:01 2020 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Screenshot from 2020-01-02 09-04-52.png" https://bugs.launchpad.net/bugs/1858080/+attachment/5316996/+files/Screenshot%20from%202020-01-02%2009-04-52.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1858080 Title: ubuntu 19.10 - dock hides part of [full] screen hiding game function Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 19.10 'live' system * Steps to re-create 1. Boot 19.10 live system 2. enable 'universe' & `sudo apt update` 3. add "pingus' game 4. start game, change to fullscreen & exit 5, start game & play * Problem Ubuntu dock hides the select options (digger, float & lemmings functions) making game hard to play. * Expected behavior When game is started in full-screen mode, Ubuntu dock should not be visible. Note: I"ve not checked for duplicates properly, and this will be related to another bug report where Ubuntu-Dock appears when xscreensaver is running. (I'll do some more exploration & scanning when home) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 09:07:01 2020 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1858080/+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 1856795] Re: [SRU] X2Go Client broken by libssh CVE-2019-14889 fix
** Changed in: x2goclient (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: x2goclient (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: x2goclient (Ubuntu Eoan)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/1856795
Title:
[SRU] X2Go Client broken by libssh CVE-2019-14889 fix
Status in libssh package in Ubuntu:
Invalid
Status in x2goclient package in Ubuntu:
Fix Released
Status in libssh source package in Xenial:
Invalid
Status in x2goclient source package in Xenial:
In Progress
Status in libssh source package in Bionic:
Invalid
Status in x2goclient source package in Bionic:
In Progress
Status in libssh source package in Disco:
Invalid
Status in x2goclient source package in Disco:
Confirmed
Status in libssh source package in Eoan:
Invalid
Status in x2goclient source package in Eoan:
In Progress
Status in x2goclient package in Debian:
Fix Released
Bug description:
[Test case]
Connect to a x2go server on a session that has file sharing or
audo-forwarding enabled -> Error message "SCP: Warning: status code 1 received:
scp: ~/.x2go/ssh: No such file or directory" needs to be clicked away
with "ok".
[Regression potential]
Very low as the patch removes "~" from the ssh string which is the same
as just using no path spec (":") as the default is the home dir of the logged
in remote user.
--
The recent CVE fix broke SCP support in libssh, which X2Go Client
(x2goclient) relies on.
Sessions now fail with error messages such as "SCP: Warning: status
code 1 received: scp: ~username/.x2go/ssh: No such file or
directory\n". (Also note the literal "\n" there, but I guess we don't
really need to care about that.)
The previous version worked fine and rolling the libssh4 package back
fixes this issue, but also leaves users vulnerable to the fixed
security issue in its scp implementation.
I've been looking at the debdiff, but spotting the actual changes is
very difficult due to the reformatting that was done at the same time.
This degraded the patch(es) into one big blob.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/1856795/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: Fix Released Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Released Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] Low, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. For the Bionic, This SRU also includes the fix of LP: #1556439, this fix is safe and is very low possible to introduce any regression too, because it just adds a sink-input/source-output state checking, if the sink-input/source-output is unlinking or unlinked, it is useless to move it to a new sink/source, furthermore it will trigger an assertion that make the pulseaudio crash, adding this check can fix this problem (LP: #1556439). [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1858080] Re: ubuntu 19.10 - dock hides part of [full] screen hiding game function
*** This bug is a duplicate of bug 1849787 *** https://bugs.launchpad.net/bugs/1849787 ** This bug has been marked a duplicate of bug 1849787 The dock is shown in front of full screen windows since 19.10 ** Description changed: Ubuntu 19.10 'live' system + dell inspiron 3470 (i5-8400, 8gb, i915) * Steps to re-create 1. Boot 19.10 live system 2. enable 'universe' & `sudo apt update` 3. add "pingus' game 4. start game, change to fullscreen & exit 5, start game & play * Problem Ubuntu dock hides the select options (digger, float & lemmings functions) making game hard to play. * Expected behavior When game is started in full-screen mode, Ubuntu dock should not be visible. Note: I"ve not checked for duplicates properly, and this will be related to another bug report where Ubuntu-Dock appears when xscreensaver is - running. (I'll do some more exploration & scanning when home) + running. Later marked this duplicate of + https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu- + dock/+bug/1849787 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 09:07:01 2020 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1858080 Title: ubuntu 19.10 - dock hides part of [full] screen hiding game function Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Ubuntu 19.10 'live' system dell inspiron 3470 (i5-8400, 8gb, i915) * Steps to re-create 1. Boot 19.10 live system 2. enable 'universe' & `sudo apt update` 3. add "pingus' game 4. start game, change to fullscreen & exit 5, start game & play * Problem Ubuntu dock hides the select options (digger, float & lemmings functions) making game hard to play. * Expected behavior When game is started in full-screen mode, Ubuntu dock should not be visible. Note: I"ve not checked for duplicates properly, and this will be related to another bug report where Ubuntu-Dock appears when xscreensaver is running. Later marked this duplicate of https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension- ubuntu-dock/+bug/1849787 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Thu Jan 2 09:07:01 2020 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1858080/+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 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer
In the event that you aren't sure what your Apple ID is, find it by entering the complete name and email address related with your Apple ID.* If you overlooked how to reset apple id password, we can assist you with discovering it or reset it. To deal with your Apple ID, including refreshing believed telephone numbers and gadgets or changing an installment technique, utilize the Settings application on your iPhone, iPad, or iPod contact, System Preferences on your Mac, or apple itunes login my account. create new apple id | apple customer support number -- 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/548891 Title: keyboard input broken due to invalid keyboard variant set by VMWare installer Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Lucid: Fix Released Status in xorg-server source package in Maverick: Fix Released Bug description: [Problem] /etc/default/console-setup has an invalid XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" [Workaround] For affected machines, run: sudo dpkg-reconfigure console-setup [Impact] Due to console-setup using invalid keyboard model and layout identifiers on certain (common) hardware, this can break the keyboard functionality in certain circumstances. For example, the vmware installer copies these invalid values and propagates them in a way that causes them to become the X defaults, thus confusing X and leaving the keyboard improperly set up. [Development] The fix has been committed to the main ubuntu-x git branch, which will be used once Maverick Meerkat is open for development, thus this fix will automatically copy over into it. [Patch] The xkb rules are modified to simply ignore the invalid values XKBMODEL="SKIP" and XKBLAYOUT="U.S. English" and use the default -evdev settings. [Test Case] 1. Set XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" in /etc/default/console-setup. 2. Install vmware 3. Reboot. When login box appears, verify password can be typed in properly [Regression Potential] Negligible. These days there are hardly any systems which aren't going to work fine with the default evdev settings, and anyway those cases would neither work with "SKIP" or "U.S. English" either. [Original Report] VMWare Player 3.0.1 build-227600 Host OS: Windows XP Guest OS: Ubuntu 10.04 Beta, Kernel 2.6.32-17-generic After installing a slew of Ubuntu updates on 3/26/2010 keyboard input at the gnome login prompt no longer works. The mouse does work and I am able to use the 'on-screen keyboard' accessibility tool to input my password and gain entry. After logging in, there does not seem to be any problems using the keyboard, I experience the problem only at the gnome login screen. I suspected that after updating that possibly some of the vmware drivers may not be working correctly, so I ran vmware-config-tools.pl to recompile the tools, which didn't work. I've tried a couple of cycles of rebooting the VM and restarting vmware player, which hasn't resolved the problem either. I've attached the portion of the apt history.log showing the packages that were applied during the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/548891/+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 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer
In the event that you aren't sure what your Apple ID is, find it by entering the complete name and email address related with your Apple ID.* If you overlooked [url=http://worldtechlife.com/how-to-log-into-my-apple-itunes-account/]how to reset apple id password[/url], we can assist you with discovering it or reset it. To deal with your Apple ID, including refreshing believed telephone numbers and gadgets or changing an installment technique, utilize the Settings application on your iPhone, iPad, or iPod contact, System Preferences on your Mac, or [url=http://worldtechlife.com/how-to-log-into-my-apple-itunes-account/]apple itunes login my account[/url]. [url=http://worldtechlife.com/how-to-log-into-my-apple-itunes-account/]create new apple id[/url] | [url=http://worldtechlife.com/how-to-log-into-my-apple-itunes-account/]apple customer support number[/url] -- 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/548891 Title: keyboard input broken due to invalid keyboard variant set by VMWare installer Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Lucid: Fix Released Status in xorg-server source package in Maverick: Fix Released Bug description: [Problem] /etc/default/console-setup has an invalid XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" [Workaround] For affected machines, run: sudo dpkg-reconfigure console-setup [Impact] Due to console-setup using invalid keyboard model and layout identifiers on certain (common) hardware, this can break the keyboard functionality in certain circumstances. For example, the vmware installer copies these invalid values and propagates them in a way that causes them to become the X defaults, thus confusing X and leaving the keyboard improperly set up. [Development] The fix has been committed to the main ubuntu-x git branch, which will be used once Maverick Meerkat is open for development, thus this fix will automatically copy over into it. [Patch] The xkb rules are modified to simply ignore the invalid values XKBMODEL="SKIP" and XKBLAYOUT="U.S. English" and use the default -evdev settings. [Test Case] 1. Set XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" in /etc/default/console-setup. 2. Install vmware 3. Reboot. When login box appears, verify password can be typed in properly [Regression Potential] Negligible. These days there are hardly any systems which aren't going to work fine with the default evdev settings, and anyway those cases would neither work with "SKIP" or "U.S. English" either. [Original Report] VMWare Player 3.0.1 build-227600 Host OS: Windows XP Guest OS: Ubuntu 10.04 Beta, Kernel 2.6.32-17-generic After installing a slew of Ubuntu updates on 3/26/2010 keyboard input at the gnome login prompt no longer works. The mouse does work and I am able to use the 'on-screen keyboard' accessibility tool to input my password and gain entry. After logging in, there does not seem to be any problems using the keyboard, I experience the problem only at the gnome login screen. I suspected that after updating that possibly some of the vmware drivers may not be working correctly, so I ran vmware-config-tools.pl to recompile the tools, which didn't work. I've tried a couple of cycles of rebooting the VM and restarting vmware player, which hasn't resolved the problem either. I've attached the portion of the apt history.log showing the packages that were applied during the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/548891/+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 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer
In the event that you aren't sure what your Apple ID is, find it by entering the complete name and email address related with your Apple ID.* If you overlooked http://worldtechlife.com/how-to-log- into-my-apple-itunes-account/">how to reset apple id password, we can assist you with discovering it or reset it. To deal with your Apple ID, including refreshing believed telephone numbers and gadgets or changing an installment technique, utilize the Settings application on your iPhone, iPad, or iPod contact, System Preferences on your Mac, or http://worldtechlife.com/how-to-log-into-my-apple-itunes- account/">apple itunes login my account. http://worldtechlife.com/how-to-log-into-my-apple-itunes- account/">create new apple id | http://worldtechlife.com /how-to-log-into-my-apple-itunes-account/">apple customer support number -- 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/548891 Title: keyboard input broken due to invalid keyboard variant set by VMWare installer Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Lucid: Fix Released Status in xorg-server source package in Maverick: Fix Released Bug description: [Problem] /etc/default/console-setup has an invalid XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" [Workaround] For affected machines, run: sudo dpkg-reconfigure console-setup [Impact] Due to console-setup using invalid keyboard model and layout identifiers on certain (common) hardware, this can break the keyboard functionality in certain circumstances. For example, the vmware installer copies these invalid values and propagates them in a way that causes them to become the X defaults, thus confusing X and leaving the keyboard improperly set up. [Development] The fix has been committed to the main ubuntu-x git branch, which will be used once Maverick Meerkat is open for development, thus this fix will automatically copy over into it. [Patch] The xkb rules are modified to simply ignore the invalid values XKBMODEL="SKIP" and XKBLAYOUT="U.S. English" and use the default -evdev settings. [Test Case] 1. Set XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" in /etc/default/console-setup. 2. Install vmware 3. Reboot. When login box appears, verify password can be typed in properly [Regression Potential] Negligible. These days there are hardly any systems which aren't going to work fine with the default evdev settings, and anyway those cases would neither work with "SKIP" or "U.S. English" either. [Original Report] VMWare Player 3.0.1 build-227600 Host OS: Windows XP Guest OS: Ubuntu 10.04 Beta, Kernel 2.6.32-17-generic After installing a slew of Ubuntu updates on 3/26/2010 keyboard input at the gnome login prompt no longer works. The mouse does work and I am able to use the 'on-screen keyboard' accessibility tool to input my password and gain entry. After logging in, there does not seem to be any problems using the keyboard, I experience the problem only at the gnome login screen. I suspected that after updating that possibly some of the vmware drivers may not be working correctly, so I ran vmware-config-tools.pl to recompile the tools, which didn't work. I've tried a couple of cycles of rebooting the VM and restarting vmware player, which hasn't resolved the problem either. I've attached the portion of the apt history.log showing the packages that were applied during the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/548891/+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 548891] Re: keyboard input broken due to invalid keyboard variant set by VMWare installer
In the event that you aren't sure what your Apple ID is, find it by entering the complete name and email address related with your Apple ID.* If you overlooked how to reset apple id password, we can assist you with discovering it or reset it. To deal with your Apple ID, including refreshing believed telephone numbers and gadgets or changing an installment technique, utilize the Settings application on your iPhone, iPad, or iPod contact, System Preferences on your Mac, or apple itunes login my account. create new apple id | apple customer support number http://worldtechlife.com/how-to-log-into-my-apple-itunes-account/ -- 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/548891 Title: keyboard input broken due to invalid keyboard variant set by VMWare installer Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Lucid: Fix Released Status in xorg-server source package in Maverick: Fix Released Bug description: [Problem] /etc/default/console-setup has an invalid XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" [Workaround] For affected machines, run: sudo dpkg-reconfigure console-setup [Impact] Due to console-setup using invalid keyboard model and layout identifiers on certain (common) hardware, this can break the keyboard functionality in certain circumstances. For example, the vmware installer copies these invalid values and propagates them in a way that causes them to become the X defaults, thus confusing X and leaving the keyboard improperly set up. [Development] The fix has been committed to the main ubuntu-x git branch, which will be used once Maverick Meerkat is open for development, thus this fix will automatically copy over into it. [Patch] The xkb rules are modified to simply ignore the invalid values XKBMODEL="SKIP" and XKBLAYOUT="U.S. English" and use the default -evdev settings. [Test Case] 1. Set XKBMODEL="SKIP" and/or XKBLAYOUT="U.S. English" in /etc/default/console-setup. 2. Install vmware 3. Reboot. When login box appears, verify password can be typed in properly [Regression Potential] Negligible. These days there are hardly any systems which aren't going to work fine with the default evdev settings, and anyway those cases would neither work with "SKIP" or "U.S. English" either. [Original Report] VMWare Player 3.0.1 build-227600 Host OS: Windows XP Guest OS: Ubuntu 10.04 Beta, Kernel 2.6.32-17-generic After installing a slew of Ubuntu updates on 3/26/2010 keyboard input at the gnome login prompt no longer works. The mouse does work and I am able to use the 'on-screen keyboard' accessibility tool to input my password and gain entry. After logging in, there does not seem to be any problems using the keyboard, I experience the problem only at the gnome login screen. I suspected that after updating that possibly some of the vmware drivers may not be working correctly, so I ran vmware-config-tools.pl to recompile the tools, which didn't work. I've tried a couple of cycles of rebooting the VM and restarting vmware player, which hasn't resolved the problem either. I've attached the portion of the apt history.log showing the packages that were applied during the update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/548891/+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 1794033] Re: i965: Failed to submit batchbuffer: Bad address
Just got this on 19.10 on a thinkpad t470s. $ uname -a Linux hostname 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I run ZFS. My first thought was OOM, but can't see any mentions of it. ... jan. 02 09:51:06 hostname gnome-shell[27297]: Usage of object.actor is deprecated for ArgosButton get@resource:///org/gnome/shell/ui/environment.js:249:29 _processOutput@/home/larsfp/.local/share/gnome-shell/extensions/argos@pew.worldwide wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _update/<@/home/larsfp/.local/share/gnome-shell/extensions/argos@pew.worldwidemann. spawnWithCallback/<@/home/larsfp/.local/share/gnome-shell/extensions/ar...@pew.worl readStream/<@/home/larsfp/.local/share/gnome-shell/extensions/argos@pew.worldwidema jan. 02 09:51:30 hostname /usr/lib/gdm3/gdm-x-session[27136]: i965: Failed to submit batchbuffer: Bad address jan. 02 09:51:30 hostname seahorse[8246]: seahorse: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. jan. 02 09:51:30 hostname firefox[986]: firefox: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. jan. 02 09:51:30 hostname gnome-shell[27297]: Gdk-Message: 09:51:30.655: /usr/lib/firefox/firefox: Fatal IO error 11 (Resource te jan. 02 09:51:30 hostname at-spi-bus-launcher[27266]: X connection to :0 broken (explicit kill or server shutdown). jan. 02 09:51:30 hostname pulseaudio[26437]: X connection to :0 broken (explicit kill or server shutdown). ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in Mesa: Fix Released Status in mesa package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Fedora: Unknown Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1794033/+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 1858072] Re: Webdav is not python3 compatible
** Also affects: duplicity
Importance: Undecided
Status: New
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => In Progress
** Changed in: duplicity
Milestone: None => 0.8.09
** Changed in: duplicity
Assignee: (unassigned) => Kenneth Loafman (kenneth-loafman)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1858072
Title:
Webdav is not python3 compatible
Status in Duplicity:
In Progress
Status in duplicity package in Ubuntu:
New
Bug description:
The webdav backend calls base64.encodestring, which
(counterintuitively) expects a bytes input in python3.
# duplicity incremental \
--asynchronous-upload \
--full-if-older-than 1M \
-v 9 \
--exclude='./Documents/google_drive/**' \
--include='./src/**' \
--exclude='**' \
'.' \
"$target_url"
Using archive dir:
/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f
Using backup name: 74043f3f63750b8654c846cb69e2833f
GPG binary is gpg, version (2, 2, 12)
Import of duplicity.backends.adbackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.jottacloudbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pcabackend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Using WebDAV protocol http
Using WebDAV host REDACTED port None
Using WebDAV directory /webdav/backup/
Main action: inc
Acquiring lockfile
b'/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f/lockfile'
duplicity $version ($reldate)
Args: /usr/bin/duplicity incremental --asynchronous-upload
--full-if-older-than 1M -v 9 --exclude=./Documents/google_drive/**
--include=./src/** --exclude=** . webdavs://RED:ACT@ED/webdav/backup
Linux zenbook-k 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019
x86_64 x86_64
/usr/bin/python3 3.7.5 (default, Nov 20 2019, 09:21:52)
[GCC 9.2.1 20191008]
Using temporary directory /tmp/duplicity-7ypg8z7d-tempdir
Registering (mkstemp) temporary file
/tmp/duplicity-7ypg8z7d-tempdir/mkstemp-v33ewch5-1
Temp has 50636972032 available, backup will use approx 482344960.
WebDAV create connection on 'REDACTED'
WebDAV PROPFIND /remote.php/webdav/backup/ request with headers:
{'Connection': 'keep-alive', 'Depth': '1'}
WebDAV data length: 95
WebDAV response status 401 with reason 'Unauthorized'.
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 371, in
inner_retry
return fn(self, *args)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 580, in
list
return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 343, in _list
raise e
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 317, in _list
response = self.request(u"PROPFIND", self.directory, self.listbody)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 240, in request
self.headers[u'Authorization'] = self.get_authorization(response,
quoted_path)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 271, in get_authorization
return self.get_basic_authorization()
File "/usr/lib/python3/dist-packages/duplicity/backends/we
[Desktop-packages] [Bug 1858093] [NEW] Display Driver Issue
Public bug reported: Not able to Suspend/Hibernate and facing issues in brightness controlling. Also screen don't turn off once it is locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 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: Thu Jan 2 17:30:41 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:096a] InstallationDate: Installed on 2019-12-25 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d0ddd98e-6672-461c-bb96-25092a84666e ro quiet splash acpi_backlight=vendor vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 0MNRJY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd06/25/2019:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn0MNRJY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages 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/1858093 Title: Display Driver Issue Status in xorg package in Ubuntu: New Bug description: Not able to Suspend/Hibernate and facing issues in brightness controlling. Also screen don't turn off once it is locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 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: Thu Jan 2 17:30:41 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:096a] InstallationDate: Installed on 2019-12-25 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:671e Microdia Bus 001 Device 002: ID 27c6:5301 Bus 001 Device 004: ID 0cf3:e009 Atheros Communications, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Vostro 3590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=d0ddd98e-6672-461c-bb96-25092a84666e ro quiet splash acpi_backlight=vendor vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.name: 0MNRJY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.0:bd06/25/2019:svnDellInc.:pnVostro3590:pvr:rvnDellInc.:rn0MNRJY:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 3590 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libg
[Desktop-packages] [Bug 1858072] Re: Webdav is not python3 compatible
This bug was fixed in rev 1344, current rev is 1533.
It looks like a case where duplicity was updated manually, not even
running 'setup.py install' or purging the repo's duplicity.
** Changed in: duplicity
Status: In Progress => Invalid
** Changed in: duplicity
Milestone: 0.8.09 => None
** Changed in: duplicity
Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1858072
Title:
Webdav is not python3 compatible
Status in Duplicity:
Invalid
Status in duplicity package in Ubuntu:
New
Bug description:
The webdav backend calls base64.encodestring, which
(counterintuitively) expects a bytes input in python3.
# duplicity incremental \
--asynchronous-upload \
--full-if-older-than 1M \
-v 9 \
--exclude='./Documents/google_drive/**' \
--include='./src/**' \
--exclude='**' \
'.' \
"$target_url"
Using archive dir:
/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f
Using backup name: 74043f3f63750b8654c846cb69e2833f
GPG binary is gpg, version (2, 2, 12)
Import of duplicity.backends.adbackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.jottacloudbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pcabackend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Using WebDAV protocol http
Using WebDAV host REDACTED port None
Using WebDAV directory /webdav/backup/
Main action: inc
Acquiring lockfile
b'/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f/lockfile'
duplicity $version ($reldate)
Args: /usr/bin/duplicity incremental --asynchronous-upload
--full-if-older-than 1M -v 9 --exclude=./Documents/google_drive/**
--include=./src/** --exclude=** . webdavs://RED:ACT@ED/webdav/backup
Linux zenbook-k 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019
x86_64 x86_64
/usr/bin/python3 3.7.5 (default, Nov 20 2019, 09:21:52)
[GCC 9.2.1 20191008]
Using temporary directory /tmp/duplicity-7ypg8z7d-tempdir
Registering (mkstemp) temporary file
/tmp/duplicity-7ypg8z7d-tempdir/mkstemp-v33ewch5-1
Temp has 50636972032 available, backup will use approx 482344960.
WebDAV create connection on 'REDACTED'
WebDAV PROPFIND /remote.php/webdav/backup/ request with headers:
{'Connection': 'keep-alive', 'Depth': '1'}
WebDAV data length: 95
WebDAV response status 401 with reason 'Unauthorized'.
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 371, in
inner_retry
return fn(self, *args)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 580, in
list
return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 343, in _list
raise e
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 317, in _list
response = self.request(u"PROPFIND", self.directory, self.listbody)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 240, in request
self.headers[u'Authorization'] = self.get_authorization(response,
quoted_path)
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 271, in get_authorization
return self.get_basic_authorization()
File "/u
[Desktop-packages] [Bug 1858095] [NEW] 'Automatic Date and Time' automatically disabled when trying to enable
Public bug reported: When enabling the "Automatic DateTime" in the gnome control center, it instantly turns off. The following is reported in syslog: Jan 2 12:10:58 ubuntu systemd[1]: Reloading. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/docker.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: Starting resolvconf-pull-resolved.service... Jan 2 12:10:58 ubuntu systemd[1]: resolvconf-pull-resolved.service: Succeeded. Jan 2 12:10:58 ubuntu systemd[1]: Started resolvconf-pull-resolved.service. Jan 2 12:10:58 ubuntu systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Jan 2 12:10:58 ubuntu systemd-timedated[10725]: Set NTP to enabled Jan 2 12:10:58 ubuntu systemd[1]: Reloading. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/docker.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly. Jan 2 12:10:59 ubuntu systemd[1]: Starting resolvconf-pull-resolved.service... Jan 2 12:10:59 ubuntu systemd[1]: resolvconf-pull-resolved.service: Succeeded. Jan 2 12:10:59 ubuntu systemd[1]: Started resolvconf-pull-resolved.service. Jan 2 12:10:59 ubuntu systemd-timedated[10725]: Set NTP to disabled Jan 2 12:11:03 ubuntu xdg-desktop-por[3204]: 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 $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.34.1-1ubuntu2 Candidate: 1:3.34.1-1ubuntu2 Version table: *** 1:3.34.1-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Description changed: When enabling the "Automatic DateTime" in the gnome control center, it - immediately turns off. + instantly turns off. The following is reported in syslog: - + Jan 2 12:10:58 ubuntu systemd[1]: Reloading. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/dbus.socket:4: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/docker.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/docker.sock → /run/docker.sock; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly. Jan 2 12:10:58 ubuntu systemd[1]: Starting resolvconf-pull-resolved.service... Jan 2 12:10:58 ubuntu systemd[1]: resolvconf-pull-resolved.service: Succeeded. Jan 2 12:10:58 ubuntu systemd[1]: Started resolvconf-pull-resolved.service.
[Desktop-packages] [Bug 1858092] [NEW] Network Manager not saving OpenVPN password
You have been subscribed to a public bug: Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kwallet manager network openvpn -- Network Manager not saving OpenVPN password https://bugs.launchpad.net/bugs/1858092 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager 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 1858092] Re: Network Manager not saving OpenVPN password
** Package changed: ubuntu => network-manager (Ubuntu) ** Tags added: eoan -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in network-manager package in Ubuntu: New Bug description: Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1858092/+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 1804285] Re: hplip Setting up python3 Errno2
My "solution": for i in `apt-get autoremove 2>&1|grep "o such" |cut -f 2 -d \'`; do touch $i; done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1804285 Title: hplip Setting up python3 Errno2 Status in hplip package in Ubuntu: Confirmed Bug description: This is Ubuntu 18.04.1 LTS (bionic beaver) mark@Lexington:~$ apt-cache policy hplip hplip: Installed: 3.17.10+repack0-5 Candidate: 3.17.10+repack0-5 Version table: *** 3.17.10+repack0-5 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status The extensive terminal output, posted below, can also be viewed here: https://pastebin.com/Zrv5AAZL After I could not repair the hplip causing the printer/scanner dialogue windows to take 5 minutes to come onscreen, I reinstalled Ubuntu 18.04. After running all updates on the OS, I reinstalled hplip (or so I thought). The hplip did install, the dialogue windows come onscreen almost instantly. There is no HP icon in the system tray and hplip throws an error/warning about this with each reboot. Today, I tried running: sudo apt-get update / upgrade. I was offered a list of upgradeable packages and said Yes to the upgrade. After running the terminal threw a long list of error messages all or almost all related to the hplip, specifically mutter, python3. Python repeatedly reports Errno2. What appeared in the terminal follows: mark@Lexington:~$ sudo aptitude upgrade The following packages will be upgraded: bind9-host dnsutils gir1.2-mutter-2 gnome-shell gnome-shell-common google-chrome-stable libbind9-160 libdns-export1100 libdns1100 libirs160 libisc-export169 libisc169 libisccc160 libisccfg160 liblwres160 libmutter-2-0 libpython3-stdlib mutter mutter-common python3 python3-distutils python3-gdbm python3-lib2to3 python3-minimal 24 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 60.9 MB of archives. After unpacking 128 kB will be used. Do you want to continue? [Y/n/?] Y Get: 1 http://dl.google.com/linux/chrome/deb stable/main amd64 google-chrome-stable amd64 70.0.3538.110-1 [55.9 MB] Get: 2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-minimal amd64 3.6.7-1~18.04 [23.7 kB] Get: 3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3 amd64 3.6.7-1~18.04 [47.2 kB] Get: 4 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libpython3-stdlib amd64 3.6.7-1~18.04 [7,240 B] Get: 5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libisc-export169 amd64 1:9.11.3+dfsg-1ubuntu1.3 [163 kB] Get: 6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdns-export1100 amd64 1:9.11.3+dfsg-1ubuntu1.3 [749 kB] Get: 7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 dnsutils amd64 1:9.11.3+dfsg-1ubuntu1.3 [145 kB] Get: 8 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 bind9-host amd64 1:9.11.3+dfsg-1ubuntu1.3 [53.5 kB] Get: 9 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libbind9-160 amd64 1:9.11.3+dfsg-1ubuntu1.3 [27.6 kB] Get: 10 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libisccfg160 amd64 1:9.11.3+dfsg-1ubuntu1.3 [48.4 kB] Get: 11 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libisccc160 amd64 1:9.11.3+dfsg-1ubuntu1.3 [17.9 kB] Get: 12 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libirs160 amd64 1:9.11.3+dfsg-1ubuntu1.3 [19.1 kB] Get: 13 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libdns1100 amd64 1:9.11.3+dfsg-1ubuntu1.3 [966 kB] Get: 14 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libisc169 amd64 1:9.11.3+dfsg-1ubuntu1.3 [237 kB] Get: 15 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 liblwres160 amd64 1:9.11.3+dfsg-1ubuntu1.3 [34.6 kB] Get: 16 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-gdbm amd64 3.6.7-1~18.04 [13.4 kB] Get: 17 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 mutter-common all 3.28.3-2~ubuntu18.04.2 [13.3 kB] Get: 18 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 gir1.2-mutter-2 amd64 3.28.3-2~ubuntu18.04.2 [139 kB] Get: 19 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 libmutter-2-0 amd64 3.28.3-2~ubuntu18.04.2 [1,207 kB] Get: 20 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 gnome-shell amd64 3.28.3-0ubuntu0.18.04.3 [665 kB] Get: 21 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 gnome-shell-common all 3.28.3-0ubuntu0.18.04.3 [183 kB] Get: 22 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 mutter amd64 3.28.3-2~ubuntu18.04.2 [15.4 kB] Get: 23 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python3-lib2to3 all 3.6.7-1
Re: [Desktop-packages] [Bug 1858072] Re: Webdav is not python3 compatible
Ubuntu is currently shipping a broken version (0.8.04). That's the bug
being reported.
This LP bugtracker tracks both duplicity and it's ubuntu packaging,
right?
On Thu, Jan 2, 2020 at 1:30 PM Kenneth Loafman
wrote:
> This bug was fixed in rev 1344, current rev is 1533.
>
> It looks like a case where duplicity was updated manually, not even
> running 'setup.py install' or purging the repo's duplicity.
>
> ** Changed in: duplicity
>Status: In Progress => Invalid
>
> ** Changed in: duplicity
> Milestone: 0.8.09 => None
>
> ** Changed in: duplicity
> Assignee: Kenneth Loafman (kenneth-loafman) => (unassigned)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1858072
>
> Title:
> Webdav is not python3 compatible
>
> Status in Duplicity:
> Invalid
> Status in duplicity package in Ubuntu:
> New
>
> Bug description:
> The webdav backend calls base64.encodestring, which
> (counterintuitively) expects a bytes input in python3.
>
>
> # duplicity incremental \
> --asynchronous-upload \
> --full-if-older-than 1M \
> -v 9 \
> --exclude='./Documents/google_drive/**' \
> --include='./src/**' \
> --exclude='**' \
> '.' \
> "$target_url"
> Using archive dir:
> /home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f
> Using backup name: 74043f3f63750b8654c846cb69e2833f
> GPG binary is gpg, version (2, 2, 12)
> Import of duplicity.backends.adbackend Succeeded
> Import of duplicity.backends.azurebackend Succeeded
> Import of duplicity.backends.b2backend Succeeded
> Import of duplicity.backends.botobackend Succeeded
> Import of duplicity.backends.cfbackend Succeeded
> Import of duplicity.backends.dpbxbackend Succeeded
> Import of duplicity.backends.gdocsbackend Succeeded
> Import of duplicity.backends.giobackend Succeeded
> Import of duplicity.backends.hsibackend Succeeded
> Import of duplicity.backends.hubicbackend Succeeded
> Import of duplicity.backends.imapbackend Succeeded
> Import of duplicity.backends.jottacloudbackend Succeeded
> Import of duplicity.backends.lftpbackend Succeeded
> Import of duplicity.backends.localbackend Succeeded
> Import of duplicity.backends.mediafirebackend Succeeded
> Import of duplicity.backends.megabackend Succeeded
> Import of duplicity.backends.multibackend Succeeded
> Import of duplicity.backends.ncftpbackend Succeeded
> Import of duplicity.backends.onedrivebackend Succeeded
> Import of duplicity.backends.par2backend Succeeded
> Import of duplicity.backends.pcabackend Succeeded
> Import of duplicity.backends.pydrivebackend Succeeded
> Import of duplicity.backends.rsyncbackend Succeeded
> Import of duplicity.backends.ssh_paramiko_backend Succeeded
> Import of duplicity.backends.ssh_pexpect_backend Succeeded
> Import of duplicity.backends.swiftbackend Succeeded
> Import of duplicity.backends.sxbackend Succeeded
> Import of duplicity.backends.tahoebackend Succeeded
> Import of duplicity.backends.webdavbackend Succeeded
> Using WebDAV protocol http
> Using WebDAV host REDACTED port None
> Using WebDAV directory /webdav/backup/
> Main action: inc
> Acquiring lockfile
> b'/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f/lockfile'
>
>
> duplicity $version ($reldate)
> Args: /usr/bin/duplicity incremental --asynchronous-upload
> --full-if-older-than 1M -v 9 --exclude=./Documents/google_drive/**
> --include=./src/** --exclude=** . webdavs://RED:ACT@ED/webdav/backup
> Linux zenbook-k 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
> 2019 x86_64 x86_64
> /usr/bin/python3 3.7.5 (default, Nov 20 2019, 09:21:52)
> [GCC 9.2.1 20191008]
>
>
> Using temporary directory /tmp/duplicity-7ypg8z7d-tempdir
> Registering (mkstemp) temporary file
> /tmp/duplicity-7ypg8z7d-tempdir/mkstemp-v33ewch5-1
> Temp has 50636972032 available, backup will use approx 482344960.
> WebDAV create connection on 'REDACTED'
> WebDAV PROPFIND /remote.php/webdav/backup/ request with headers:
> {'Connection': 'keep-alive', 'Depth': '1'}
> WebDAV data length: 95
> WebDAV response status 401 with reason 'Unauthorized'.
> Backtrace of previous error: Traceback (innermost last):
> File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 371,
> in inner_retry
> return fn(self, *args)
> File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 580,
> in list
> return [tobytes(x) for x in self.backend._list()]
> File
> "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py", line
> 343, in _list
> raise e
> File
> "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py", line
> 317, in _list
> response = self.request(u"PROPFIND", self.di
[Desktop-packages] [Bug 1858105] [NEW] chromium-browser hangs on startup without gnome-keyring
Public bug reported: Ubuntu 16.04.6 LTS chromium-browser 79.0.3945.79-0ubuntu0.16.04. (and some older ones) amd64 Ive used chromium-browser since a while but in the recent months it sometimes after exiting cannot be started again, it just hangs with no window opened and no meaningful error message. First I thought some corrupt profile was the cause as a restore of the profile from backup resolves this. But as it kept happening on a 100% stable system which runs 24/7 this is unlikely. Debugging this was a bit delayed as the -dbg package is outdated the -dbgsym package does not work with the gdb version i have from xenial and rebuilding chromium-browser strips debug symbols even when is_debug is enabled and it takes over 12h for a build. Either way, backtraces of the relevant threads are below. A workaround of this issue is to install gnome-keyring, start chromium-browser, cancel the gazillion of password requests and uninstall gnome-keyring and gcr, after that chromium-browser launches normal again. Another workaround is to use --single-process (which is a dumb idea security wise) I do not know why its doing that, i did not investigate further, but this is not normal or acceptable behavior of a browser even if I did something stupid which no doubt is possible. What i expect is well the browser should not hang and not do funny things with packages it doesnt have any dependancy/recommand/suggests on. And it should not grow tentacles that grab into keyrings without explanation to the user. info threads Id Target Id Frame * 1Thread 0x77f1dac0 (LWP 23428) "chromium-browse" __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 2Thread 0x7fffe85bd700 (LWP 23433) "sandbox_ipc_thr" 0x7144074d in poll () at ../sysdeps/unix/syscall-template.S:84 3Thread 0x7fffe7dbc700 (LWP 23438) "chromium-browse" 0x772d7f7b in __waitpid (pid=23435, stat_loc=0x7fffe7dbbb04, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:29 4Thread 0x7fffe6207700 (LWP 23439) "ThreadPoolServi" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 6Thread 0x7fffe5205700 (LWP 23441) "Chrome_IOThread" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 8Thread 0x7fffc700 (LWP 23443) "inotify_reader" 0x714425d3 in select () at ../sysdeps/unix/syscall-template.S:84 9Thread 0x7fffcf38f700 (LWP 23444) "gmain" 0x7144074d in poll () at ../sysdeps/unix/syscall-template.S:84 10 Thread 0x7fffceb8e700 (LWP 23445) "gdbus" 0x7144074d in poll () at ../sysdeps/unix/syscall-template.S:84 11 Thread 0x7fffce38d700 (LWP 23446) "Bluez D-Bus thr" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 12 Thread 0x7fffe413d700 (LWP 23447) "CrShutdownDetec" 0x772d751d in read () at ../sysdeps/unix/syscall-template.S:84 15 Thread 0x7fffccb8a700 (LWP 23450) "ThreadPoolForeg" pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 17 Thread 0x7fffabfff700 (LWP 23451) "ThreadPoolForeg" __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 18 Thread 0x7fffaaffd700 (LWP 23453) "CompositorTileW" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 19 Thread 0x7fffaa7fc700 (LWP 23454) "ThreadPoolSingl" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 20 Thread 0x7fffa9ffb700 (LWP 23455) "VideoCaptureThr" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 21 Thread 0x7fffa8ff9700 (LWP 23457) "gpu-process_cra" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 22 Thread 0x7fffa97fa700 (LWP 23456) "CacheThread_Blo" 0x7144ca13 in epoll_wait () at ../sysdeps/unix/syscall-template.S:84 23 Thread 0x7fff87fff700 (LWP 23459) "utility_crash_u" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 24 Thread 0x7fff877fe700 (LWP 23461) "ThreadPoolSingl" pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 25 Thread 0x7fff86ffd700 (LWP 23463) "Chrome_HistoryT" pthread_cond_timedwait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:225 bt #0 __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x772d0dbd in __GI___pthread_mutex_lock (mutex=0x5ef8b1a8 <(anonymous namespace)::g_cache+40>) at ../nptl/pthread_mutex_lock.c:80 #2 0x565b734c in Lock () at ../../base/synchronization/lock_impl_posix.cc:102 #3 0x5a6c1135 in Acquire () at ../../base/synchronization/lock.h:31 #4 BasicAutoLock () at ../../base/synchronization/lock_impl.h:84 #5 Ge
[Desktop-packages] [Bug 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
I can confirm that applying the patch from #30 in 18.04 does seem to fix the problem when using WH-1000XM3. -- 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/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+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 1773114] Re: Cannot copy file using 'cp' on a gvfs mount
Ubuntu 18.04.3 LTS here. Tried to cp a file from local storage to a GVFS mounted Android Phone. copy /home/user/example.file /run/user/1000/gvfs/mtp\:host\=%5Busb%3A001%2C004%5D/Phone/SomeDir/ Results in error: operation not supported. Browsing the dir tree via CLI was working , though. Via GUI in nautilus is working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1773114 Title: Cannot copy file using 'cp' on a gvfs mount Status in gvfs package in Ubuntu: Confirmed Bug description: On Ubuntu 18.04, I can't anymore copy a file using the 'cp' command on a gvfs smb mount. For example, If I try to copy the file test.odp on a SMB shared folder, like this: cp -v test.odp /run/user/1000/gvfs/smb- share:domain=X,server=x,share=xxx,user=x/ I get the following error: cp: cannot fstat '/run/user/1000/gvfs/smb- share:domain=X,server=x,share=xxx,user=x//test.odp': Invalid argument A file 'test.odp' is created, but with size 0. I can delete any file on the shared folder using the 'rm' command. If I copy the file using the command 'gio copy', then it works as expected. This used to work in Ubuntu 16.04. Of course, I don't know if the problem is in the gvfs package or in some underlying component... System: Ubuntu 18.04 LTS (Bionic Beaver) 64-bit Kernel: 4.15.0-22-generic x86_64 Package: gvfs 1.36.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1773114/+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 1858072] Re: Webdav is not python3 compatible
It's a long standing problem. I can fix all the bugs and release a new
version, but that will not get them to update the base to the new
version.
Please upgrade to the current version of duplicity. This will assure
that any bugs fixed since your release are available and may fix your
issue. Please read and follow NOTE below!
There are three options:
* Release tarball Install - https://launchpad.net/duplicity/+download
* Daily duplicity builds -
https://launchpad.net/~duplicity-team/+archive/ubuntu/daily-dev-trunk
* Stable snap builds - “sudo snap install duplicity —classic"
* Latest snap builds - “sudo snap install duplicity —classic —edge"
NOTE: UNinstall duplicity first if it was installed via the distribution
repository. For Ubuntu, that would be "sudo apt-get purge duplicity".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/1858072
Title:
Webdav is not python3 compatible
Status in Duplicity:
Invalid
Status in duplicity package in Ubuntu:
New
Bug description:
The webdav backend calls base64.encodestring, which
(counterintuitively) expects a bytes input in python3.
# duplicity incremental \
--asynchronous-upload \
--full-if-older-than 1M \
-v 9 \
--exclude='./Documents/google_drive/**' \
--include='./src/**' \
--exclude='**' \
'.' \
"$target_url"
Using archive dir:
/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f
Using backup name: 74043f3f63750b8654c846cb69e2833f
GPG binary is gpg, version (2, 2, 12)
Import of duplicity.backends.adbackend Succeeded
Import of duplicity.backends.azurebackend Succeeded
Import of duplicity.backends.b2backend Succeeded
Import of duplicity.backends.botobackend Succeeded
Import of duplicity.backends.cfbackend Succeeded
Import of duplicity.backends.dpbxbackend Succeeded
Import of duplicity.backends.gdocsbackend Succeeded
Import of duplicity.backends.giobackend Succeeded
Import of duplicity.backends.hsibackend Succeeded
Import of duplicity.backends.hubicbackend Succeeded
Import of duplicity.backends.imapbackend Succeeded
Import of duplicity.backends.jottacloudbackend Succeeded
Import of duplicity.backends.lftpbackend Succeeded
Import of duplicity.backends.localbackend Succeeded
Import of duplicity.backends.mediafirebackend Succeeded
Import of duplicity.backends.megabackend Succeeded
Import of duplicity.backends.multibackend Succeeded
Import of duplicity.backends.ncftpbackend Succeeded
Import of duplicity.backends.onedrivebackend Succeeded
Import of duplicity.backends.par2backend Succeeded
Import of duplicity.backends.pcabackend Succeeded
Import of duplicity.backends.pydrivebackend Succeeded
Import of duplicity.backends.rsyncbackend Succeeded
Import of duplicity.backends.ssh_paramiko_backend Succeeded
Import of duplicity.backends.ssh_pexpect_backend Succeeded
Import of duplicity.backends.swiftbackend Succeeded
Import of duplicity.backends.sxbackend Succeeded
Import of duplicity.backends.tahoebackend Succeeded
Import of duplicity.backends.webdavbackend Succeeded
Using WebDAV protocol http
Using WebDAV host REDACTED port None
Using WebDAV directory /webdav/backup/
Main action: inc
Acquiring lockfile
b'/home/username/.cache/duplicity/74043f3f63750b8654c846cb69e2833f/lockfile'
duplicity $version ($reldate)
Args: /usr/bin/duplicity incremental --asynchronous-upload
--full-if-older-than 1M -v 9 --exclude=./Documents/google_drive/**
--include=./src/** --exclude=** . webdavs://RED:ACT@ED/webdav/backup
Linux zenbook-k 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019
x86_64 x86_64
/usr/bin/python3 3.7.5 (default, Nov 20 2019, 09:21:52)
[GCC 9.2.1 20191008]
Using temporary directory /tmp/duplicity-7ypg8z7d-tempdir
Registering (mkstemp) temporary file
/tmp/duplicity-7ypg8z7d-tempdir/mkstemp-v33ewch5-1
Temp has 50636972032 available, backup will use approx 482344960.
WebDAV create connection on 'REDACTED'
WebDAV PROPFIND /remote.php/webdav/backup/ request with headers:
{'Connection': 'keep-alive', 'Depth': '1'}
WebDAV data length: 95
WebDAV response status 401 with reason 'Unauthorized'.
Backtrace of previous error: Traceback (innermost last):
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 371, in
inner_retry
return fn(self, *args)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 580, in
list
return [tobytes(x) for x in self.backend._list()]
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 343, in _list
raise e
File "/usr/lib/python3/dist-packages/duplicity/backends/webdavbackend.py",
line 317, in _list
response = sel
[Desktop-packages] [Bug 1858120] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1858120/+attachment/5317143/+files/GsettingsChanges.txt -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in gnome-shell package in Ubuntu: New Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858120/+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 1858120] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1858120/+attachment/5317144/+files/ProcCpuinfoMinimal.txt -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in gnome-shell package in Ubuntu: New Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858120/+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 1858120] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1858120/+attachment/5317145/+files/ShellJournal.txt -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in gnome-shell package in Ubuntu: New Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858120/+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 1858120] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1858120/+attachment/5317142/+files/Dependencies.txt -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in gnome-shell package in Ubuntu: New Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858120/+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 1796928] Re: Fast Double-tap Treated as Single Click
should be fixed since 19.04 ** Changed in: libinput (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1796928 Title: Fast Double-tap Treated as Single Click Status in libinput package in Ubuntu: Fix Released Bug description: https://gitlab.freedesktop.org/libinput/libinput/issues/158 --- Fast double-taps get treated as a single click. Behavior is present in Ubuntu 18.04 (libinput 1.10.4-1) but not in 17.10 (libinput 1.8.2-1ubuntu2). Still present in 18.10 daily downloaded 2018.10.08 (libinput 1.12.0-1). I think this is similar to https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1762536 with different hardware. I'm trying to run Ubuntu 18.04 in a VMware Fusion guest on a Macbook host. If I double-tap the trackpad fast, it gets treated as a single- click in Ubuntu. If I double-tap slow (but not too slow) it gets treated as a double-click. Hitting the narrow window is hard! This makes it tough to run X in a VM on a Macbook. I suspect that the host hardware+software delivers a synthesized double-click to the guest, and that the time between the clicks is very small. evemu-record shows two "VirtualPS/2 VMware Virtual Mouse" devices and a "VMware VMware Virtual USB Mouse". Capture of the first of these is attached. It looks to me like the second tap comes 8 ms after the first, and I'm betting that is treated as bounce. Bug report also created at https://bugs.freedesktop.org/show_bug.cgi?id=108306 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2018-10-09 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: VMware, Inc. VMware Virtual Platform Package: libinput (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=a0e790b4-4632-4de9-aa52-4dff4fc9fe4f ro find_preseed=/preseed.cfg auto noprompt priority=critical locale=en_US quiet ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic ubuntu Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/19/2017 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/19/2017:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1796928/+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 1858120] [NEW] Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode
Public bug reported: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal wayland-session ** Tags added: apport-collected focal wayland-session ** Description changed: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: - This is likely a bug in GS 3.34, fixed by - https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and - https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included - in 3.34.2 which should arrive soon in Ubuntu 19.10. + This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu15 + Architecture: amd64 + CurrentDesktop: GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-01-01 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) + Package: gnome-shell 3.34.1+git20191024-1ubuntu1 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 + RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 + Tags: focal wayland-session + Uname: Linux 5.3.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in gnome-shell package in Ubuntu: New Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Va
[Desktop-packages] [Bug 1858120] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1858120/+attachment/5317146/+files/monitors.xml.txt -- 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/1858120 Title: Graphical corruption Intel HD Graphics 630 when using Firefox nightly in Wayland mode Status in gnome-shell package in Ubuntu: New Bug description: Also tracked in: https://bugzilla.mozilla.org/show_bug.cgi?id=1604948 Once every few starts of Firefox on my machine ends up corrupting the display of my Wayland session badly - what looks like a lot of stray marks on my display are seen overlaid on top of all windows, not just Firefox. Logging out and logging back in resolves the issue, but there is a chance that it recurs on next launch. Steps to reproduce: 1. Start Gnome session in Wayland mode. 2. Start Firefox Nightly with MOZ_ENABLE_WAYLAND=1 What happens: Various issues, including "unknown" application appearing in task switcher, stray marks on screen, and dead/inactive windows that persist over other windows even when switching virtual desktops. Response from Firefox bugzilla says: This is likely a bug in GS 3.34, fixed by https://gitlab.gnome.org/GNOME/mutter/merge_requests/924 and https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/815, included in 3.34.2 which should arrive soon in Ubuntu 19.10. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-01 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) Package: gnome-shell 3.34.1+git20191024-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: mutter-common 3.34.2-2ubuntu1 Tags: focal wayland-session Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1858120/+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 1845046] Re: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected
Applying the patch fixed my problem with my Sony WH-H900N headphones. Probably a different bug but if I open Sound Settings -> Input and change the input from "Internal Microphone Built-in Audio" to "Headset WH-H900N (h.ear)" the quality degrades and the Output profile changes to "Headset Head Unit (HSP/HFP)". If I change the Output profile back to "High Fidelity Playback (A2DP Sink)" I get high quality audio again but the Input changes back to "Internal Microphone Built-in Audio". Or is it that you can't use the headset microphone and get high quality audio at the same time? -- 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/1845046 Title: Bluetooth headphones/speaker such as Sony WH-1000XM3 default to low quality headset mode and fails to switch to A2DP when selected Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1845046/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
When will the fix be released? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1858130] [NEW] cups-browsed assert failure: corrupted size vs. prev_size
Public bug reported: after turn on pc. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CrashCounter: 1 CupsErrorLog: Date: Wed Jan 1 23:08:16 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-22 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) Lpstat: device for HP_LaserJet_Pro_MFP_M127fs_67477B_: implicitclass://HP_LaserJet_Pro_MFP_M127fs_67477B_/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: HP_LaserJet_Pro_MFP_M127fs_67477B_: HP LaserJet Pro MFP M127fs, driverless, cups-filters 1.26.0 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7a96217c-8f39-491f-8b1e-b4af01f6ca40 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5a995f93a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f5a995f74b6 "corrupted size vs. prev_size") at malloc.c:5332 unlink_chunk (p=p@entry=0x55e4d3a5ab10, av=0x7f5a9962ab80 ) at malloc.c:1454 _int_malloc (av=av@entry=0x7f5a9962ab80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer separator: ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace ** Information type changed from Private to Public Security ** Information type changed from Public Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1858130 Title: cups-browsed assert failure: corrupted size vs. prev_size Status in cups-filters package in Ubuntu: New Bug description: after turn on pc. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CrashCounter: 1 CupsErrorLog: Date: Wed Jan 1 23:08:16 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-22 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) Lpstat: device for HP_LaserJet_Pro_MFP_M127fs_67477B_: implicitclass://HP_LaserJet_Pro_MFP_M127fs_67477B_/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: HP_LaserJet_Pro_MFP_M127fs_67477B_: HP LaserJet Pro MFP M127fs, driverless, cups-filters 1.26.0 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7a96217c-8f39-491f-8b1e-b4af01f6ca40 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5a995f93a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f5a995f74b6 "corrupted size vs. prev_size") at malloc.c:5332 unlink_chunk (p=p@entry=0x55e4d3a5ab10, av=0x7f5a9962ab80 ) at malloc.c:1454 _int_malloc (av=av@entry=0x7f5a9962ab80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi
[Desktop-packages] [Bug 1858130] cups-browsed assert failure: corrupted size vs. prev_size
StacktraceTop: raise () from /tmp/apport_sandbox_7u00eqqw/lib/x86_64-linux-gnu/libc.so.6 abort () from /tmp/apport_sandbox_7u00eqqw/lib/x86_64-linux-gnu/libc.so.6 ?? () from /tmp/apport_sandbox_7u00eqqw/lib/x86_64-linux-gnu/libc.so.6 ?? () from /tmp/apport_sandbox_7u00eqqw/lib/x86_64-linux-gnu/libc.so.6 ?? () from /tmp/apport_sandbox_7u00eqqw/lib/x86_64-linux-gnu/libc.so.6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1858130 Title: cups-browsed assert failure: corrupted size vs. prev_size Status in cups-filters package in Ubuntu: New Bug description: after turn on pc. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CrashCounter: 1 CupsErrorLog: Date: Wed Jan 1 23:08:16 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-22 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) Lpstat: device for HP_LaserJet_Pro_MFP_M127fs_67477B_: implicitclass://HP_LaserJet_Pro_MFP_M127fs_67477B_/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: HP_LaserJet_Pro_MFP_M127fs_67477B_: HP LaserJet Pro MFP M127fs, driverless, cups-filters 1.26.0 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7a96217c-8f39-491f-8b1e-b4af01f6ca40 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5a995f93a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f5a995f74b6 "corrupted size vs. prev_size") at malloc.c:5332 unlink_chunk (p=p@entry=0x55e4d3a5ab10, av=0x7f5a9962ab80 ) at malloc.c:1454 _int_malloc (av=av@entry=0x7f5a9962ab80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1858130/+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 1858130] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1858130/+attachment/5317177/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1858130 Title: cups-browsed assert failure: corrupted size vs. prev_size Status in cups-filters package in Ubuntu: New Bug description: after turn on pc. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CrashCounter: 1 CupsErrorLog: Date: Wed Jan 1 23:08:16 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-22 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) Lpstat: device for HP_LaserJet_Pro_MFP_M127fs_67477B_: implicitclass://HP_LaserJet_Pro_MFP_M127fs_67477B_/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: HP_LaserJet_Pro_MFP_M127fs_67477B_: HP LaserJet Pro MFP M127fs, driverless, cups-filters 1.26.0 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7a96217c-8f39-491f-8b1e-b4af01f6ca40 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5a995f93a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f5a995f74b6 "corrupted size vs. prev_size") at malloc.c:5332 unlink_chunk (p=p@entry=0x55e4d3a5ab10, av=0x7f5a9962ab80 ) at malloc.c:1454 _int_malloc (av=av@entry=0x7f5a9962ab80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1858130/+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 1858130] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1858130/+attachment/5317176/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1858130 Title: cups-browsed assert failure: corrupted size vs. prev_size Status in cups-filters package in Ubuntu: New Bug description: after turn on pc. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CrashCounter: 1 CupsErrorLog: Date: Wed Jan 1 23:08:16 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-22 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) Lpstat: device for HP_LaserJet_Pro_MFP_M127fs_67477B_: implicitclass://HP_LaserJet_Pro_MFP_M127fs_67477B_/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: HP_LaserJet_Pro_MFP_M127fs_67477B_: HP LaserJet Pro MFP M127fs, driverless, cups-filters 1.26.0 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7a96217c-8f39-491f-8b1e-b4af01f6ca40 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5a995f93a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f5a995f74b6 "corrupted size vs. prev_size") at malloc.c:5332 unlink_chunk (p=p@entry=0x55e4d3a5ab10, av=0x7f5a9962ab80 ) at malloc.c:1454 _int_malloc (av=av@entry=0x7f5a9962ab80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1858130/+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 1858130] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1858130/+attachment/5317178/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-filters in Ubuntu. https://bugs.launchpad.net/bugs/1858130 Title: cups-browsed assert failure: corrupted size vs. prev_size Status in cups-filters package in Ubuntu: New Bug description: after turn on pc. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: cups-browsed 1.26.0-1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 AssertionMessage: corrupted size vs. prev_size CrashCounter: 1 CupsErrorLog: Date: Wed Jan 1 23:08:16 2020 ExecutablePath: /usr/sbin/cups-browsed InstallationDate: Installed on 2019-12-22 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) Lpstat: device for HP_LaserJet_Pro_MFP_M127fs_67477B_: implicitclass://HP_LaserJet_Pro_MFP_M127fs_67477B_/ MachineType: System manufacturer System Product Name Papersize: letter PpdFiles: HP_LaserJet_Pro_MFP_M127fs_67477B_: HP LaserJet Pro MFP M127fs, driverless, cups-filters 1.26.0 ProcAttrCurrent: /usr/sbin/cups-browsed (enforce) ProcCmdline: /usr/sbin/cups-browsed ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=7a96217c-8f39-491f-8b1e-b4af01f6ca40 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups-filters StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f5a995f93a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f5a995f74b6 "corrupted size vs. prev_size") at malloc.c:5332 unlink_chunk (p=p@entry=0x55e4d3a5ab10, av=0x7f5a9962ab80 ) at malloc.c:1454 _int_malloc (av=av@entry=0x7f5a9962ab80 , bytes=bytes@entry=184) at malloc.c:4041 __libc_calloc (n=, elem_size=) at malloc.c:3428 Title: cups-browsed assert failure: corrupted size vs. prev_size UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3805 dmi.board.asset.tag: Default string dmi.board.name: Z170-P dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1858130/+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 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libpciaccess (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: Confirmed Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: Confirmed Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83] (EE) 9: /usr/lib/xorg/Xorg (0x55a9687bf000+0x581a6) [0x55a9
[Desktop-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pciutils (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: Confirmed Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: Confirmed Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83] (EE) 9: /usr/lib/xorg/Xorg (0x55a9687bf000+0x581a6) [0x55a96881
[Desktop-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower
I'm hitting this issue on some new server hardware when trying to use lspci from pciutils with a 16.04 installation. I'm wondering of there has there been any progress on getting this fix released for Xenial? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libpciaccess in Ubuntu. https://bugs.launchpad.net/bugs/1818816 Title: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower Status in libpciaccess package in Ubuntu: Fix Released Status in linux package in Ubuntu: Invalid Status in nvidia-graphics-drivers package in Ubuntu: Invalid Status in pciutils package in Ubuntu: Fix Released Status in libpciaccess source package in Xenial: Confirmed Status in linux source package in Xenial: Invalid Status in nvidia-graphics-drivers source package in Xenial: Invalid Status in pciutils source package in Xenial: Confirmed Bug description: Hello Team, I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower over UEFI installation. I'm using Display port monitor, inorder to get proper display I need to download nvidia driver from ppa:graphics- drivers/ppa After install nvidia-384 and did a reboot, still no display, but can able to see the PCI modules conflicted #lspci -v lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or directory There is no issue with Ubuntu 18.04 , which is works perfectly on the same machine. Ubuntu 16.04 having issue. Please let me know id there is some issue with the running kernel or any package? Below is the environment details. = Ubuntu 16.04.4 LTS Xenial Kernel - 4.15.0-46-generic NVIDIA Quadro P4000 $lshw -C Display WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: NVIDIA Corporation vendor: NVIDIA Corporation physical id: 0 bus info: pci@:65:00.0 version: a1 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:29 memory:d700-d7ff memory:c000-cfff memory:d000-d1ff ioport:b000(size=128) memory:d800-d807 #dpkg -l | grep xserver-xorg-core-hwe-16.04 ii xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 $dpkg -l | grep nvid ii nvidia-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA binary driver - version 384.130 ii nvidia-opencl-icd-384 384.130-0ubuntu0.16.04.1 amd64NVIDIA OpenCL ICD ii nvidia-prime0.8.2 amd64Tools to enable NVIDIA's Prime ii nvidia-settings 415.27-0ubuntu0~gpu16.04.1 amd64Tool for configuring the NVIDIA graphics driver #startx xauth: file /root/.Xauthority does not exist X.Org X Server 1.19.5 Release Date: 2017-10-12 X Protocol Version 11, Revision 0 Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic #49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64 Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7 Build Date: 24 November 2017 09:44:25AM xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see http://www.ubuntu.com/support) Current version of pixman: 0.33.6 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 6 15:14:19 2019 (==) Using system config directory "/usr/share/X11/xorg.conf.d" (EE) (EE) Backtrace: (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e] (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) [0x7fe81649c390] (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) [0x7fe817ae4a38] (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) [0x7fe817ae4abb] (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) [0x7fe817ae67af] (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9] (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62] (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83]
[Desktop-packages] [Bug 1694926] Re: Boost.Context and Boost.Coroutine not built on s390x
** Also affects: boost1.71 (Ubuntu) Importance: Undecided Status: New ** Also affects: boost-defaults (Ubuntu) Importance: Undecided Status: New ** Also affects: boost1.67 (Ubuntu) Importance: Undecided Status: New ** No longer affects: boost (Ubuntu) ** Changed in: boost-defaults (Ubuntu) Status: New => Confirmed ** Changed in: boost1.67 (Ubuntu) Status: New => Won't Fix ** Changed in: boost1.71 (Ubuntu) Status: New => Fix Committed ** Changed in: boost-defaults (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to boost-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1694926 Title: Boost.Context and Boost.Coroutine not built on s390x Status in Ubuntu on IBM z Systems: Triaged Status in boost-defaults package in Ubuntu: Triaged Status in boost1.67 package in Ubuntu: Won't Fix Status in boost1.71 package in Ubuntu: Fix Committed Status in ceph package in Ubuntu: Triaged Bug description: The Boost packaging currently excludes s390x support for Boost.Context and Boost.Coroutine; These are required to support Ceph >= 12.0.3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1694926/+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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10
Addition: neither #42 nor #58 doesn't help. The problem persists in 19.10 too. This laptop had the same issue in Win10. I reinstalled it from Microsoft's ISO (to exclude potential bugs in Dell soft) and problem was gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1798961 Title: Random unrecoverable freezes on Ubuntu 18.10 Status in Linux: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Invalid Status in linux source package in Bionic: Triaged Status in xserver-xorg-video-intel source package in Bionic: Invalid Status in linux source package in Cosmic: Triaged Status in xserver-xorg-video-intel source package in Cosmic: Invalid Status in linux source package in Disco: Triaged Status in xserver-xorg-video-intel source package in Disco: Invalid Bug description: First thing I notice is that the mouse cursor freezes as I'm using it, then I hit the CAPS LOCK key and the LED indicator doesn't respond. Then I try the "REISUB" command, but it doesn't do anything either. Only a hard reset works, pressing down the power button for a few seconds. How to reproduce? I couldn't figure out a consistent method. It is still random to me. Version: Ubuntu 4.18.0-10.11-generic 4.18.12 System information attached. Also happens under Arch Linux and Fedora. I've talked to another user on IRC who seems to be having the same freezes. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-10-generic 4.18.0-10.11 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dsilva 1213 F pulseaudio /dev/snd/controlC0: dsilva 1213 F pulseaudio CurrentDesktop: XFCE Date: Sat Oct 20 09:54:50 2018 InstallationDate: Installed on 2018-10-20 (0 days ago) InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Dell Inc. Inspiron 5458 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-10-generic N/A linux-backports-modules-4.18.0-10-generic N/A linux-firmware 1.175 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 09WGNT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 5458 dmi.product.sku: Inspiron 5458 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1798961/+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 1765888] Re: Please revert to debian-alternatives based prime-select
** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1765888 Title: Please revert to debian-alternatives based prime-select Status in nvidia-prime package in Ubuntu: Fix Released Bug description: The new prime-select has some problems. It is very slow to switch, since it does initramfs -u each time It leaves my two optimus laptops without graphics if you leave it in prime-select intel but boot with discrete nvidia. Previously this would load nvidia drivers. These are both two bad 'regressions' in the user experience, the first for everyone, the second for those how have a hardware mux. I know there is bug in logind meaning that a restart is required to poweroff the nvidia card. But this is not new, right? What has happened between 17.10 and 18.04 that has required this dramatic change? Is it now broken to use debian alternatives? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.7 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 21 12:25:58 2018 Dependencies: InstallationDate: Installed on 2017-10-19 (183 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: Upgraded to bionic on 2018-03-09 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765888/+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 1857252] Re: chromium 79 remote display broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1857252 Title: chromium 79 remote display broken Status in chromium-browser package in Ubuntu: Confirmed Status in chromium package in Fedora: Unknown Bug description: Chromium 78 worked and things broke in version 79. With chromium 79 when using the remote display (ssh for x forward) I get the display forward but only a blank (white) window. Chromiumn does not render anything into the window. If I am at the console then every thing work normal. Also Firefox does work for remote display. It just chromium 79 that has this problem. Every thing worked with version 78. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.36 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Sun Dec 22 14:57:30 2019 InstallationDate: Installed on 2016-07-24 (1246 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to bionic on 2018-09-03 (475 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1857252/+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 1857252] Re: chromium 79 remote display broken
** Bug watch added: Red Hat Bugzilla #1786306 https://bugzilla.redhat.com/show_bug.cgi?id=1786306 ** Also affects: chromium (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1786306 Importance: Unknown Status: Unknown -- 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/1857252 Title: chromium 79 remote display broken Status in chromium-browser package in Ubuntu: Confirmed Status in chromium package in Fedora: Unknown Bug description: Chromium 78 worked and things broke in version 79. With chromium 79 when using the remote display (ssh for x forward) I get the display forward but only a blank (white) window. Chromiumn does not render anything into the window. If I am at the console then every thing work normal. Also Firefox does work for remote display. It just chromium 79 that has this problem. Every thing worked with version 78. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.36 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Sun Dec 22 14:57:30 2019 InstallationDate: Installed on 2016-07-24 (1246 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to bionic on 2018-09-03 (475 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1857252/+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 211966] Re: nautilus-share report a warning about missing /var/lib/samba/usershares
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/211966 Title: nautilus-share report a warning about missing /var/lib/samba/usershares Status in Apache2 Web Server: Invalid Status in OEM Priority Project: New Status in nautilus-share package in Ubuntu: Fix Released Status in samba package in Ubuntu: Won't Fix Bug description: Binary package hint: nautilus-share if you start nautilus from console you can see this error message: Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Aucun fichier ou dossier de ce type Please ask your system administrator to enable user sharing. I assume it needs to create /var/lib/samba/usershares in the package To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/211966/+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 211966] Re: nautilus-share report a warning about missing /var/lib/samba/usershares
** Tags added: oem-priority ** Tags added: originate-from-1856685 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/211966 Title: nautilus-share report a warning about missing /var/lib/samba/usershares Status in Apache2 Web Server: Invalid Status in OEM Priority Project: New Status in nautilus-share package in Ubuntu: Fix Released Status in samba package in Ubuntu: Won't Fix Bug description: Binary package hint: nautilus-share if you start nautilus from console you can see this error message: Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error Aucun fichier ou dossier de ce type Please ask your system administrator to enable user sharing. I assume it needs to create /var/lib/samba/usershares in the package To manage notifications about this bug go to: https://bugs.launchpad.net/apache2/+bug/211966/+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 1858164] [NEW] libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates
Public bug reported: 1) The release of Ubuntu you are using: $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 2) The version of the package you are using: $ dpkg -l | grep libpulse ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries ii libpulse0:i3861:11.1-1ubuntu7.5 i386 PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio OSS pre-load library 3) What you expected to happen "sudo apt install libpulse-dev" should installed libpulse-dev. 4) What happened instead $ sudo apt install libpulse-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed E: Unable to correct problems, you have held broken packages. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1858164 Title: libpulse-dev needs a rebuild for libpulse0-1:11.1-1ubuntu7.5 on bionic-updates Status in pulseaudio package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using: $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 2) The version of the package you are using: $ dpkg -l | grep libpulse ii libpulse-mainloop-glib0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries (glib support) ii libpulse0:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio client libraries ii libpulse0:i3861:11.1-1ubuntu7.5 i386 PulseAudio client libraries ii libpulsedsp:amd64 1:11.1-1ubuntu7.5 amd64PulseAudio OSS pre-load library 3) What you expected to happen "sudo apt install libpulse-dev" should installed libpulse-dev. 4) What happened instead $ sudo apt install libpulse-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies. libpulse-dev : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed Depends: libpulse-mainloop-glib0 (= 1:11.1-1ubuntu7.4) but 1:11.1-1ubuntu7.5 is to be installed E: Unable to correct problems, you have held broken packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1858164/+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 1858165] [NEW] Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available.
Public bug reported: I'm working on Ubuntu 18.04 LTS x86_64 fully patched. I have LibreOffice Base installed. I am trying to open a MS Access database. I open LibreOffice Base. At Step (1) I select "Connect to an existing database". At Step (2), which is the File Open dialog, I click browse: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available. At this point I am browsing to the *.mdb file. No database is selected. This is a drag. I am working with a company that specializes in fresh water wells. I'm trying to get them to convert from Windows to Linux for all the right reasons. Obviously they cannot convert if Linux software cannot open the database. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic $ libreoffice --version LibreOffice 6.0.7.3 00m0(Build:3) $ apt-cache show libreoffice Package: libreoffice Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/editors Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 103 ... $ apt-cache show libreoffice-base Package: libreoffice-base Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/database Source: libreoffice Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8928 ... ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: libreoffice libreoffice-base odbc ** Attachment added: "Screen capture of LibreOffice error" https://bugs.launchpad.net/bugs/1858165/+attachment/5317283/+files/libreoffice-base.png -- 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/1858165 Title: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available. Status in libreoffice package in Ubuntu: New Bug description: I'm working on Ubuntu 18.04 LTS x86_64 fully patched. I have LibreOffice Base installed. I am trying to open a MS Access database. I open LibreOffice Base. At Step (1) I select "Connect to an existing database". At Step (2), which is the File Open dialog, I click browse: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available. At this point I am browsing to the *.mdb file. No database is selected. This is a drag. I am working with a company that specializes in fresh water wells. I'm trying to get them to convert from Windows to Linux for all the right reasons. Obviously they cannot convert if Linux software cannot open the database. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic $ libreoffice --version LibreOffice 6.0.7.3 00m0(Build:3) $ apt-cache show libreoffice Package: libreoffice Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/editors Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 103 ... $ apt-cache show libreoffice-base Package: libreoffice-base Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/database Source: libreoffice Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8928 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1858165/+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 1858165] Re: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available.
My bad, this may be helpful: $ find /usr/lib -name libodbc.so $ find /lib -name libodbc.so $ sudo find / -name libodbc.so 2>/dev/null $ -- 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/1858165 Title: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available. Status in libreoffice package in Ubuntu: New Bug description: I'm working on Ubuntu 18.04 LTS x86_64 fully patched. I have LibreOffice Base installed. I am trying to open a MS Access database. I open LibreOffice Base. At Step (1) I select "Connect to an existing database". At Step (2), which is the File Open dialog, I click browse: Could not load the program library libodbc.so or it is corrupted. The ODBC data source selection is not available. At this point I am browsing to the *.mdb file. No database is selected. This is a drag. I am working with a company that specializes in fresh water wells. I'm trying to get them to convert from Windows to Linux for all the right reasons. Obviously they cannot convert if Linux software cannot open the database. $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.3 LTS Release: 18.04 Codename: bionic $ libreoffice --version LibreOffice 6.0.7.3 00m0(Build:3) $ apt-cache show libreoffice Package: libreoffice Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/editors Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 103 ... $ apt-cache show libreoffice-base Package: libreoffice-base Architecture: amd64 Version: 1:6.0.7-0ubuntu0.18.04.10 Priority: optional Section: universe/database Source: libreoffice Origin: Ubuntu Maintainer: Ubuntu Developers Original-Maintainer: Debian LibreOffice Maintainers Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 8928 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1858165/+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 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]
I get this all the time after resuming from sleep, unfortunately with wayland it's not possible to reload gnome-shell so I have to log out/in to get rid of it. -- 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/1824874 Title: undismissable, unclickable authentication dialog left on screen (top- left corner) after policykit authentication [pushModal: invocation of begin_modal failed] Status in gnome-shell package in Ubuntu: Confirmed Bug description: In disco, when policykit prompted me for a password in order for update-manager to dispatch instructions to aptdaemon to perform package updates, the password dialog remained on the screen after I clicked 'authenticate'. The window is not clickable, it appears not to even be a window - mouse presses are received by the window underneath. The exception is that the 'cancel' button is active and receives mouse events - but clicking it does nothing. This may be a gnome-shell issue rather than policykit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: policykit-1 0.105-25 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 15 13:14:33 2019 InstallationDate: Installed on 2010-09-24 (3125 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) SourcePackage: policykit-1 UpgradeStatus: Upgraded to disco on 2019-04-11 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1824874/+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 1858181] [NEW] Xorg freeze with bluetooth mouse plugin, 19.10
Public bug reported: Release: 19.10 Xorg Version: 1:7.7_19ubuntu12 Problem: After powering on my computer, grub's menu shows the options for starting Ubuntu, advanced Ubuntu options, etc. If I have my bluetooth mouse receiver plugged into the usb port, the menu freezes and a hard reboot is necessary as I cannot move my cursor; however, this continues only as long as the receiver is plugged in. Once it is removed and a hard reboot is done (reboot necessary to unfreeze), the menu allows me to select "Ubuntu" and access the OS. Plugging back in in the OS lets me use the mouse without problem, but relapses if I restart/shut down. Environment Details: New HP Spectre x360, 15-inch, freshly wiped from Windows 10 Home and installed with Ubuntu 19.10 Eoan Ermine after failing to dual-boot. My boot order in HP's bios is by usb drive first followed by the system boot option, the order of which does not seem to have an effect on the problem. The mouse is a Jelly Comb 2.4GHz wireless rechargeable mouse (not sure if important). There is no legacy mode, and safeboot is currently disabled; however, the parity of the option has not affected the problem. The mouse is solely what seems to cause the issue. I plan on testing with other USB dongles for debugging if you want more data on if it's all wireless mice, all usb dongles or what have you. Steps to replicate: 0 Put wireless mouse receiver in USB slot (Spectre has only 1 so test all of them) 1 Turn on computer with ubuntu 2 Try to select any option on the grub menu. Should be frozen and unresponsive 3 Unplugging mouse should not affect frozen state 4 Restart computer with free USB slots 5 Grub should be responsive ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..3b.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:3b: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 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 3 01:51:02 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:863f] Subsystem: Hewlett-Packard Company GP108M [GeForce MX250] [103c:863f] InstallationDate: Installed on 2020-01-03 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP Spectre x360 Convertible 15t-df100 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2019 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 863F dmi.board.vendor: HP dmi.board.version: 54.13 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.10:bd07/25/2019:svnHP:pnHPSpectrex360Convertible15t-df100:pvr:rvnHP:rn863F:rvr54.13:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15t-df100 dmi.product.sku: 5ZV31AV dmi.sys.vendor: HP 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.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 freeze 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/1858181 Title: Xorg f
[Desktop-packages] [Bug 1858035] Re: Xorg freeze (Ubuntu 19.10 stuck on splash screen)
Hey, quick question. I'm running into similar problems, but on grub right before the splash screen. After removing your drive, did you happen to have anything else like a charging cable or wired/wireless mouse in your ports? -- 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/1858035 Title: Xorg freeze (Ubuntu 19.10 stuck on splash screen) Status in xorg package in Ubuntu: New Bug description: Yesterday I had just installed Ubuntu 19.10 and after my third or fourth reboot it would not start, it just got stuck on the splash screen. I didn't know what to do, but I still had the USB from which I had installed Ubuntu, so I plugged it in and booted up from the USB, and then I pressed the shutdown button, and before it shut down Ubuntu asked me to remove the installation media and press OK, I did, the laptop shut down, and now I booted up my laptop as usual, not from the USB, and this time it did not get stuck on the splash screen. So I left it at that, but just now, I booted up my laptop,and again it got stuck again, and so again I did the boot up from the USB, shut down, remove USB, and reboot as usual from the laptops HDD. Now it works again. This problem seems to happen on a random basis. I hope this helps to solve this problem. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jan 1 18:58:18 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Core Processor Integrated Graphics Controller [1028:0410] InstallationDate: Installed on 2019-12-30 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Latitude E4310 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=6e8b1021-3bce-4fb7-a48b-eb93e408c4d4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.name: 0XG3JF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd05/12/2017:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn0XG3JF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. 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.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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1858035/+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
