[SRU] Mirage segfaults immediately when run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mirage |
Fix Released
|
Unknown
|
|||
mirage (Ubuntu) |
Fix Released
|
Undecided
|
Graham Inggs | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Opinion
|
Undecided
|
Unassigned | ||
Mantic |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[ Impact ]
mirage is completely unusable as it will always segfault if any user tries to run the application.
Debugger showed that it is causing segfault when it is tryig to import the module xmouse. And then the coredump showed that the segfault is when Python is trying to check the flags for the methods while importing the module.
The upstream Python developers helped and the issue was found to be a missing sentinel value which caused "PyModule_Create" to access memory beyond the end of the array.
[ Test Plan ]
* Execute the command "mirage", which will segfault if it's not fixed.
* With the fixed package, the "mirage" window will be displayed.
[ Where problems could occur ]
* This is not changing any part of the code and is only adding a sentinel value to terminate the array.
* It is already completely unusable for users, and this will not cause any more regression than what user experiences now.
[ Other Info ]
* All versions from Jammy are affected by this.
* More info at https:/
[ Original Bug Description ]
Newly installed mirage segfaults immediately when run.
Last few lines of strace:
mmap(NULL, 4096, PROT_READ|
newfstatat(
newfstatat(
openat(AT_FDCWD, "/usr/lib/
read(13, "\177ELF\
newfstatat(13, "", {st_mode=
mmap(NULL, 16720, PROT_READ, MAP_PRIVATE|
mmap(0x7f04e7f0
mmap(0x7f04e7f0
mmap(0x7f04e7f0
close(13) = 0
mprotect(
newfstatat(
newfstatat(
openat(AT_FDCWD, "/usr/lib/
read(13, "\177ELF\
newfstatat(13, "", {st_mode=
mmap(NULL, 16560, PROT_READ, MAP_PRIVATE|
mmap(0x7f04e400
mmap(0x7f04e400
mmap(0x7f04e400
close(13) = 0
mprotect(
--- SIGSEGV {si_signo=SIGSEGV, si_code=
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mirage 0.11.1-1build4
ProcVersionSign
Uname: Linux 5.15.0-48-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 25 08:30:56 2022
InstallationDate: Installed on 2022-03-03 (235 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: mirage
UpgradeStatus: Upgraded to jammy on 2022-06-30 (116 days ago)
Changed in mirage (Ubuntu): | |
status: | Confirmed → In Progress |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in mirage: | |
status: | Unknown → New |
Changed in mirage (Ubuntu Jammy): | |
status: | New → In Progress |
Changed in mirage (Ubuntu Lunar): | |
status: | New → In Progress |
Changed in mirage (Ubuntu Mantic): | |
status: | New → In Progress |
Changed in mirage (Ubuntu Jammy): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in mirage (Ubuntu Lunar): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in mirage (Ubuntu Mantic): | |
assignee: | nobody → Sudip Mukherjee (sudipmuk) |
Changed in mirage (Ubuntu): | |
assignee: | nobody → Graham Inggs (ginggs) |
status: | Confirmed → In Progress |
Changed in mirage: | |
status: | New → Fix Released |
description: | updated |
description: | updated |
Version: 0.11.1-1build4 amd64