[Desktop-packages] [Bug 2018455] [NEW] gnome-shell exits after screen lock / unlock & login segfault libmutter-12.so.0.0.0 in Ubuntu 23.04 on Lenovo X1 Carbon Gen10
Public bug reported: The issue is happening 9 out of 10 times. It is hard to get a crash dump in /var/crash during this error though, but I found one from few days ago. Looks like should be relevant. I've reported it, see OOPS ID: b68253a2-ea4c-11ed-af33-fa163e55efd0 Laptop: Lenovo ThinkPad X1 Carbon Gen 10, model 21CB007WCK root@x1:~# uname -a Linux x1 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux To reproduce: 1. Win+L to lock the session 2. Screen turns black as expected 3. Login back to your session 4. Welcome to the new & clean session... all unsaved work is lost! 5. see gnome-shell segfault in libmutter-12.so in dmesg root@x1:~# dmesg -T |grep segf [Thu May 4 17:45:04 2023] gnome-shell[2554]: segfault at ff78 ip 7f3d10961115 sp 7ffd72b85f78 error 5 in libmutter-12.so.0.0.0[7f3d1084a000+13d000] likely on CPU 0 (core 0, socket 0) [Fri May 5 14:09:43 2023] gnome-shell[24568]: segfault at 11 ip 7f4c14161119 sp 7ffd4590de28 error 4 in libmutter-12.so.0.0.0[7f4c1404a000+13d000] likely on CPU 9 (core 17, socket 0) Logs from "ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash" command May 04 09:24:31 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Using lock path: /var/lock/whoopsie/lock May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Parsing /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:31 x1 whoopsie[54307]: [09:24:31] Uploading /var/crash/_usr_bin_gnome-shell.1000.crash. May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Sent; server replied with: No error May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Response code: 200 May 04 09:24:32 x1 whoopsie[54307]: [09:24:32] Reported OOPS ID b68253a2-ea4c-11ed-af33-fa163e55efd0 It was difficult to figure how to send the report in Ubuntu 23.04, previously it was just working... but with Ubuntu 23.04 there was this error: May 04 09:21:33 x1 systemd[1]: Starting apport-autoreport.service - Process error reports when automatic reporting is enabled... May 04 09:21:33 x1 systemd[1]: Started whoopsie.service - crash report submission. May 04 09:21:33 x1 whoopsie[53709]: [09:21:33] Using lock path: /var/lock/whoopsie/lock May 04 09:21:33 x1 systemd[1]: whoopsie.service: Deactivated successfully. May 04 09:21:33 x1 whoopsie-upload-all[53708]: ERROR: whoopsie.path is not enabled May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Main process exited, code=exited, status=1/FAILURE May 04 09:21:33 x1 systemd[1]: apport-autoreport.service: Failed with result 'exit-code'. May 04 09:21:33 x1 systemd[1]: Failed to start apport-autoreport.service - Process error reports when automatic reporting is enabled. Fixed by changing "Send error reports to Canonical" (in gnome control panel -> "Privacy" -> "Diagnostics") from "Automatic" to "Never" and re-running the `ubuntu-bug` command again. gnome-shell 44.0-2ubuntu3 intel-media-va-driver:amd64 23.1.2+dfsg1-1 root@x1:~# lshw -class display *-display description: VGA compatible controller product: Alder Lake-P Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 logical name: /dev/fb0 version: 0c width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom fb configuration: depth=32 driver=i915 latency=0 mode=1920x1200 resolution=1920,1200 visual=truecolor xres=1920 yres=1200 resources: iomemory:600-5ff iomemory:400-3ff irq:199 memory:603d00-603dff memory:40-400fff ioport:2000(size=64) memory:c-d memory:401000-4016ff memory:402000-40 root@x1:~# lshw -class multimedia *-multimedia:0 UNCLAIMED description: Multimedia controller product: Intel Corporation vendor: Intel Corporation physical id: 5 bus info: pci@:00:05.0 version: 02 width: 64 bits clock: 33MHz capabilities: pciexpress pm cap_list configuration: latency=0 resources: iomemory:600-5ff memory:603c00-603cff *-multimedia:1 description: Audio device product: Alder Lake PCH-P High Definition Audio Controller vendor: Intel Corporation physical id: 1f.3 bus info: pci@:00:1f.3 logical name: card0 logical name: /dev/snd/controlC0 logical name: /dev/snd/hwC0D0 logical name: /dev/snd/hwC0D2 logical name: /dev/snd/pcmC0D0c logical name: /dev/snd/pcmC0D0p logical name: /dev/snd/pcmC0D31p logical name: /dev/snd/pcmC0D3p logical name: /dev/snd/pcmC0D4p logical name: /dev/snd/pcmC0D5p logical name: /dev/snd/pcmC0D6c logical name: /dev/snd/pcmC0D7c version: 01 width: 64 bits clock: 33MHz capabilities: pm msi
[Desktop-packages] [Bug 1939592] Re: Login screen (gdm3) is purple blank after switching userA -> userB -> userA again
** Description changed:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
## Workaround 2
To not use gdm3. There are alternatives such as sddm or ligthdm:
sudo apt install sddm
OR
sudo apt install lightdm
-
Ctrl+Alt+F5 (drop to a console)
sudo systemctl stop gdm3
exec sudo systemctl start display-manager
-
## Details
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-===--=
ii gdm3 3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager
arno@z390-linux:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.11.0-25-generic
root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7
arno@z390-linux:~$ nvidia-smi
Wed Aug 11 16:42:07 2021
+-+
| NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2
|
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC
|
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M.
|
| | | MIG M.
|
|===+==+==|
| 0 GeForce RTX 207... Off | :01:00.0 On | N/A
|
| 0% 37CP817W / 215W |473MiB / 7979MiB | 1% Default
|
| | | N/A
|
+---+--+--+
+-+
| Processes:
|
| GPU GI CIPID Type Process name GPU Memory
|
|ID ID Usage
|
|=|
|0 N/A N/A 2211 G /usr/lib/xorg/Xorg 35MiB
|
|0 N/A N/A 10496 G /usr/lib/xorg/Xorg106MiB
|
|0 N/A N/A 10626 G /usr/bin/gnome-shell 157MiB
|
|0 N/A N/A 16828 G /usr/lib/xorg/Xorg 35MiB
|
|0 N/A N/A 38063 G ...A= --shared-files 80MiB
|
+-+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 11 16:37:35 2021
InstallationDate: Installed on 2020-09-26 (318 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
## Workaround 2
To not use gdm3. There are alternatives such as sddm or ligthdm:
-
- sudo apt install sddm
-
- OR
sudo apt install lightdm
Ctrl+Alt+F5 (drop to a console)
sudo systemctl stop gdm3
exec sudo systemctl start display-manager
## Details
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
|
[Desktop-packages] [Bug 1939592] [NEW] Login screen (gdm3) is purple blank after switching userA -> userB -> userA again
Public bug reported:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==-===--=
ii gdm3 3.36.3-0ubuntu0.20.04.4 amd64GNOME Display Manager
arno@z390-linux:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-5.11.0-25-generic
root=UUID=a39515ec-3bed-493b-8286-3904a4aac9de ro quiet splash vt.handoff=7
arno@z390-linux:~$ nvidia-smi
Wed Aug 11 16:42:07 2021
+-+
| NVIDIA-SMI 460.91.03Driver Version: 460.91.03CUDA Version: 11.2 |
|---+--+--+
| GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|===+==+==|
| 0 GeForce RTX 207... Off | :01:00.0 On | N/A |
| 0% 37CP817W / 215W |473MiB / 7979MiB | 1% Default |
| | | N/A |
+---+--+--+
+-+
| Processes: |
| GPU GI CIPID Type Process name GPU Memory |
|ID ID Usage |
|=|
|0 N/A N/A 2211 G /usr/lib/xorg/Xorg 35MiB |
|0 N/A N/A 10496 G /usr/lib/xorg/Xorg106MiB |
|0 N/A N/A 10626 G /usr/bin/gnome-shell 157MiB |
|0 N/A N/A 16828 G /usr/lib/xorg/Xorg 35MiB |
|0 N/A N/A 38063 G ...A= --shared-files 80MiB |
+-+
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.36.3-0ubuntu0.20.04.4
ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 11 16:37:35 2021
InstallationDate: Installed on 2020-09-26 (318 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: gdm3 (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1939592
Title:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again
Status in gdm3 package in Ubuntu:
New
Bug description:
Login screen (gdm3) is purple blank after switching userA -> userB ->
userA again.
Sometimes need to switch 5 times.. but definitely after around 5 times
gdm3 breaks (it shows just a blank purple screen with the cursor).
## Workaround
Ctrl+Alt+F3 (or F4.. F5...) until I get to the user I need to (and unlock the
screensaver there).
OR: switch to the console and run "exec sudo systemctl restart gdm3". ("exec"
is not necessary but highly desirable from the security point of view, so there
won't be a logged in session).
arno@z390-linux:~$ dpkg -l gdm3
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
[Desktop-packages] [Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Just got the same, shortly after I logged in, I opened VirtualBox (haven't started the VM yet), then Google Chrome -> went to my mails and ... just got logged out of my session! Ubuntu 18.04; gnome-session-bin 3.28.1-0ubuntu3. Logs: Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry Jan 08 10:21:27 REDACTED virtualbox.desktop[5400]: ICE default IO error handler doing an exit(), pid = 5400, errno = 11 Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSource Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSink Jan 08 10:21:27 REDACTED kernel: rfkill: input handler enabled Jan 08 10:21:27 REDACTED gnome-shell[4958]: gnome-shell: Fatal IO error 0 (Success) on X server :1. Jan 08 10:21:27 REDACTED polkitd(authority=local)[2802]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.100, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_U Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1" Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: after 145 requests (145 known processed) with 0 events remaining. Jan 08 10:21:27 REDACTED gsd-power[5096]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-wacom[5117]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-xsettings[5118]: gsd-xsettings: Fatal IO error 104 (Connection reset by peer) on X server :1. Jan 08 10:21:27 REDACTED gsd-color[5141]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-clipboard[5137]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-media-keys[5149]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gnome-terminal-[5507]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Jan 08 10:21:27 REDACTED gsd-color[4623]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_BenQ_Corporation_ZOWIE_XL_LCD_BCH00737SL0_arno_1000 Jan 08 10:21:27 REDACTED systemd[4821]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE Jan 08 10:21:27 REDACTED systemd[4821]: gnome-terminal-server.service: Failed with result 'exit-code'. Jan 08 10:21:28 REDACTED acpid[2618]: client 4841[0:0] has disconnected Jan 08 10:21:28 REDACTED acpid[2618]: client connected from 3353[0:0] Jan 08 10:21:28 REDACTED acpid[2618]: 1 client rule loaded Jan 08 10:21:31 REDACTED gnome-shell[3400]: JS ERROR: TypeError: this._currentWindow is null _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13 Jan 08 10:21:31 REDACTED gnome-shell[3400]: JS ERROR: TypeError: this._currentWindow is null _setCurrentRect@resource:///org/gnome/shell/ui/keyboard.js:536:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _init/<@resource:///org/gnome/shell/ui/keyboard.js:503:13 Jan 08 10:21:32 REDACTED gnome-shell[3400]: g_array_unref: assertion 'array' failed Jan 08 10:21:32 REDACTED gnome-shell[3400]: g_array_unref: assertion 'array' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I've had this happen a couple of times now
[Desktop-packages] [Bug 1779871] [NEW] Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user.
Public bug reported: To reproduce: 1. Install Ubuntu 18.04 on a laptop 2. Create two user accounts 3. Login to the first account and switch to the second account 4. Disconnect the power plug and work (while on the battery) from one (or the other) account for some time (more than 20 minutes which is default according to the "gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout" CLI command) 5. When switching a user back to the other account, it will automatically suspend the laptop. Workaround: For each(!) user disable "Automatic suspend" in the Power settings or same with the CLI command: gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' Bug? I think it is as having the multiuser session, switching back to the background user it should not immediately force the laptop sleep due to the background user inactivity. How to solve it? gnome-settings-daemon should probably not take into account the inactivity timer (or rather reset it) when there are other foreground users are using Ubuntu. ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: bionic xenial ** Summary changed: - Ubuntu automatically suspends the laptop for the background user when switching back to it from the other user. + Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1779871 Title: Ubuntu automatically suspends the laptop for the background user when switching back to it from the foreground user. Status in gnome-settings-daemon package in Ubuntu: New Bug description: To reproduce: 1. Install Ubuntu 18.04 on a laptop 2. Create two user accounts 3. Login to the first account and switch to the second account 4. Disconnect the power plug and work (while on the battery) from one (or the other) account for some time (more than 20 minutes which is default according to the "gsettings get org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout" CLI command) 5. When switching a user back to the other account, it will automatically suspend the laptop. Workaround: For each(!) user disable "Automatic suspend" in the Power settings or same with the CLI command: gsettings set org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'nothing' Bug? I think it is as having the multiuser session, switching back to the background user it should not immediately force the laptop sleep due to the background user inactivity. How to solve it? gnome-settings-daemon should probably not take into account the inactivity timer (or rather reset it) when there are other foreground users are using Ubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1779871/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
The patch
https://code.launchpad.net/~azzar1/ubiquity/+git/ubiquity/+merge/345056
did work for me on my mid-2017 MacBookPro (HW, not VM).
Thank you, Andrea!
--
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:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
In Progress
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
In Progress
Bug description:
The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although
it was working some weeks/months ago, so this is a recent regression.
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
--
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 1603600] Re: NetworkManager ignores pushed openvpn routes
The same issue :-/ Ubuntu 16.04.4 LTS network-manager-openvpn 1.1.93-1ubuntu1.1 network-manager-openvpn-gnome 1.1.93-1ubuntu1.1 I am usually setting: VPN connection settings -> IPv4 Settings -> Routes... -> [x] Use this connection only for resources on its network. So that my default GW is not changed as I need only the VPN routes. Except that with this bug, the VPN routes are not really applied on my system. When running openvpn on its own, everything is working. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1603600 Title: NetworkManager ignores pushed openvpn routes Status in network-manager-openvpn package in Ubuntu: Confirmed Bug description: Relevant information that may or may not have been included by ubuntu- bug: Ubuntu release 16.04 Package network-manager 1.2.0-0ubuntu0.16.04.2 Package network-manager-openvpn 1.1.93-1ubuntu1 NetworkManager ignores pushed openvpn routes when "Use this connection only for resources on its network" is checked. This is a behavior change since 14.04. To repeat: 1) Use an OpenVpn server that pushes routes. I suggest using a server that pushes several routes since this makes their absence obvious. Set up a NetworkManager VPN of type OpenVpn to this server. Select "Use this connection only for resources on its network" in the "Routes" section of the IPV4 options. 2) Set up a raw OpenVpn connection to the same server. 3) Connect to the server using the raw OpenVpn connection. The pushed routes are all there. 4) Connect to the server using NetworkManager. The only route added is a n interface level route to the tunnel device network. Using the same setup on 14.04, all pushed routes are added. The missing routes are also "Resources on the VPN network", and should be added in the absence of further direction. Ignoring pushed routes should be controlled by the "Ignore automatically obtained routes" checkbox. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jul 15 23:12:55 2016 InstallationDate: Installed on 2016-05-04 (72 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1603600/+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
