[Desktop-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
For anyone looking for how to use this fix with the current Ubuntu 18.04
installation ISO, this page ( https://askubuntu.com/a/1040322/14601 )
has a good description how to use the patch produced above in Comment
37.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Fix Released
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
Fix Released
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions
--
[Desktop-packages] [Bug 1639520] Re: nvidia graphics drivers 367.57-0ubuntu0.14.04.1 prevents gnome from launching
Here's the apt log of the update being applied which caused the problem Log started: 2016-11-04 13:32:03 (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 358778 files and directories currently installed.) Preparing to unpack .../libcurl3-gnutls_7.35.0-1ubuntu2.10_amd64.deb ... Unpacking libcurl3-gnutls:amd64 (7.35.0-1ubuntu2.10) over (7.35.0-1ubuntu2.9) ... Preparing to unpack .../curl_7.35.0-1ubuntu2.10_amd64.deb ... Unpacking curl (7.35.0-1ubuntu2.10) over (7.35.0-1ubuntu2.9) ... Preparing to unpack .../libcurl3_7.35.0-1ubuntu2.10_amd64.deb ... Unpacking libcurl3:amd64 (7.35.0-1ubuntu2.10) over (7.35.0-1ubuntu2.9) ... Preparing to unpack .../keybase_1.0.18-20161104161546.6537940_amd64.deb ... Unpacking keybase (1.0.18-20161104161546.6537940) over (1.0.18-20161101160102.a862115) ... Selecting previously unselected package nvidia-367. Preparing to unpack .../nvidia-367_367.57-0ubuntu0.14.04.1_amd64.deb ... Unpacking nvidia-367 (367.57-0ubuntu0.14.04.1) ... Preparing to unpack .../libcuda1-352_367.57-0ubuntu0.14.04.1_amd64.deb ... Unpacking libcuda1-352 (367.57-0ubuntu0.14.04.1) over (352.63-0ubuntu0.14.04.1) ... Selecting previously unselected package libcuda1-367. Preparing to unpack .../libcuda1-367_367.57-0ubuntu0.14.04.1_amd64.deb ... Unpacking libcuda1-367 (367.57-0ubuntu0.14.04.1) ... Preparing to unpack .../nvidia-opencl-icd-352_367.57-0ubuntu0.14.04.1_amd64.deb ... Unpacking nvidia-opencl-icd-352 (367.57-0ubuntu0.14.04.1) over (352.63-0ubuntu0.14.04.1) ... dpkg: warning: unable to delete old directory '/etc/OpenCL/vendors': Directory not empty dpkg: warning: unable to delete old directory '/etc/OpenCL': Directory not empty Selecting previously unselected package nvidia-opencl-icd-367. Preparing to unpack .../nvidia-opencl-icd-367_367.57-0ubuntu0.14.04.1_amd64.deb ... Unpacking nvidia-opencl-icd-367 (367.57-0ubuntu0.14.04.1) ... Processing triggers for man-db (2.6.7.1-1ubuntu1) ... Processing triggers for hicolor-icon-theme (0.13-1) ... Processing triggers for mime-support (3.54ubuntu1.1) ... Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for ureadahead (0.100.0-16) ... Setting up libcurl3-gnutls:amd64 (7.35.0-1ubuntu2.10) ... Setting up libcurl3:amd64 (7.35.0-1ubuntu2.10) ... Setting up curl (7.35.0-1ubuntu2.10) ... Setting up keybase (1.0.18-20161104161546.6537940) ... Setting up nvidia-367 (367.57-0ubuntu0.14.04.1) ... update-alternatives: using /usr/lib/nvidia-367/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode update-alternatives: using /usr/lib/nvidia-367/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in auto mode update-alternatives: using /usr/lib/nvidia-367/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode update-alternatives: using /usr/lib/nvidia-367/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in auto mode update-alternatives: using /usr/share/nvidia-367/glamor.conf to provide /usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-367 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Adding system user `nvidia-persistenced' (UID 120) ... Adding new group `nvidia-persistenced' (GID 127) ... Adding new user `nvidia-persistenced' (UID 120) with group `nvidia-persistenced' ... Not creating home directory `/'. Loading new nvidia-367-367.57 DKMS files... First Installation: checking all kernels... Building only for 3.13.0-100-generic Building for architecture x86_64 Building initial module for 3.13.0-100-generic Done. nvidia_367: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/3.13.0-100-generic/updates/dkms/ nvidia_367_modeset.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to
[Desktop-packages] [Bug 1639520] [NEW] nvidia graphics drivers 367.57-0ubuntu0.14.04.1 prevents gnome from launching
Public bug reported: Release : Ubuntu 14.04.5 LTS Package Version : 367.57-0ubuntu0.14.04.1 nvidia graphics drivers version 367.57-0ubuntu0.14.04.1 was published 2 days ago on 11/3 ( https://launchpad.net/ubuntu/+source/nvidia- graphics-drivers-367/367.57-0ubuntu0.14.04.1 ). I installed the update on 11/4 (see apt log below). Today on 11/5 I rebooted my machine. Upon booting when the graphical UI is launched the screen is black. I knew that though I had no display I was at the graphical login prompt as I heard the ubuntu sound that's played when the login prompt is presented. I rebooted into an older kernel version and got the graphical UI to render such that I could log in. Upon logging in (as myself or as guest) an error message was flashed and I'm returned to the login prompt. In looking at /var/log/syslog each time this happens I'm getting the error gnome-session[4575]: CRITICAL: We failed, but the fail whale is dead. Sorry After attempting other fixes I found the fix. I removed the nvidia drivers from the command line with apt-get remove --purge nvidia* This resolved the problem. I then went into the graphical proprietary drivers UI and selected nvidia 367 which re-installed nvidia drivers 367.57-0ubuntu0.14.04.1 I rebooted and the black screen occurred again. At this point the cause/effect of the nvidia drivers was apparent. I again removed all nvidia drivers with the apt-get remove line above. I rebooted and again my system works correctly. Expected results : To be able to log into Ubuntu after accepting the upgraded nvidia drivers Actual results : The new version of nvidia drivers prevents the display from working or gnome-session from working. I'm happy to provide any additional diagnostic information that anyone would like, just ask for files or for me to run commands and get you output. ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/1639520 Title: nvidia graphics drivers 367.57-0ubuntu0.14.04.1 prevents gnome from launching Status in nvidia-graphics-drivers package in Ubuntu: New Bug description: Release : Ubuntu 14.04.5 LTS Package Version : 367.57-0ubuntu0.14.04.1 nvidia graphics drivers version 367.57-0ubuntu0.14.04.1 was published 2 days ago on 11/3 ( https://launchpad.net/ubuntu/+source/nvidia- graphics-drivers-367/367.57-0ubuntu0.14.04.1 ). I installed the update on 11/4 (see apt log below). Today on 11/5 I rebooted my machine. Upon booting when the graphical UI is launched the screen is black. I knew that though I had no display I was at the graphical login prompt as I heard the ubuntu sound that's played when the login prompt is presented. I rebooted into an older kernel version and got the graphical UI to render such that I could log in. Upon logging in (as myself or as guest) an error message was flashed and I'm returned to the login prompt. In looking at /var/log/syslog each time this happens I'm getting the error gnome-session[4575]: CRITICAL: We failed, but the fail whale is dead. Sorry After attempting other fixes I found the fix. I removed the nvidia drivers from the command line with apt-get remove --purge nvidia* This resolved the problem. I then went into the graphical proprietary drivers UI and selected nvidia 367 which re-installed nvidia drivers 367.57-0ubuntu0.14.04.1 I rebooted and the black screen occurred again. At this point the cause/effect of the nvidia drivers was apparent. I again removed all nvidia drivers with the apt-get remove line above. I rebooted and again my system works correctly. Expected results : To be able to log into Ubuntu after accepting the upgraded nvidia drivers Actual results : The new version of nvidia drivers prevents the display from working or gnome-session from working. I'm happy to provide any additional diagnostic information that anyone would like, just ask for files or for me to run commands and get you output. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1639520/+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 1498972] [NEW] Change icon to 256x256 version to support HiDPI
Public bug reported: Original bug : https://bugzilla.mozilla.org/show_bug.cgi?id=1193381 Please change the firefox packaging to use this icon browser/branding/official/default256.png instead of this icon browser/branding/official/mozicon128.png to prevent pixelation on HiDPI systems. ** Affects: firefox (Ubuntu) Importance: Undecided Assignee: Chris Coulson (chrisccoulson) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1498972 Title: Change icon to 256x256 version to support HiDPI Status in firefox package in Ubuntu: New Bug description: Original bug : https://bugzilla.mozilla.org/show_bug.cgi?id=1193381 Please change the firefox packaging to use this icon browser/branding/official/default256.png instead of this icon browser/branding/official/mozicon128.png to prevent pixelation on HiDPI systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1498972/+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 295961] Re: GUI doesn't show when list_visible is 0
I've also seen this occur twice and had to manually re-enable the buddy list in prefs.xml as described in this bug. Ubuntu 14.04 Pidgin 2.10.9 (libpurple 2.10.9) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pidgin in Ubuntu. https://bugs.launchpad.net/bugs/295961 Title: GUI doesn't show when list_visible is 0 Status in “pidgin” package in Ubuntu: Confirmed Bug description: Binary package hint: pidgin Sometimes, and it doesn't seem very predictable, the pidgin GUI fails to show on the screen. There's a pidgin process running on the machine. Am not sure if I'm visible online at that stage. Anyway, the fix is to go into ~/.purple/prefs.xml and change list_visible from 0 to 1. It always seems to be 0 when this problem occurs, and changing it to 1 fixes it. You have to kill the pidgin process first, as it re-writes the file on exit, so kill pidgin, edit prefs.xml, change list_visible from 0 to 1, save the file, start pidgin. Works fine - the GUI appears. In a note to myself, I also mentioned changing show_empty_groups to 0 - I haven't seen that at 1 recently, so not sure if that was a red herring. Anyway, it's setting list_visible from 0 to 1 which makes the GUI reappear and everything work fine again ProblemType: Bug Architecture: i386 Date: Sun Nov 9 14:30:52 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/bin/pidgin NonfreeKernelModules: nvidia Package: pidgin 1:2.5.0-0ubuntu2~hardy1 PackageArchitecture: i386 ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_GB.UTF-8 SourcePackage: pidgin Uname: Linux 2.6.24-21-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/295961/+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
