[Bug 1899362] [NEW] System crashes on install. Gets almost to the end though.

2020-10-11 Thread John Manning
Public bug reported:

OS ISO loaded from DVD and crashes when almost complete.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 11 18:01:11 2020
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet 
splash --- maybe-ubiquity
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899362

Title:
  System crashes on install. Gets almost to the end though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1899362/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

RE: [Bug 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT

2015-01-02 Thread John Manning
Hi

Thanks for the update, however I'm not sure how to read these reports.
It appears from the details below that I'm running Ubunutu 13.10, when
I'm actually running 14.10 (are the details below related to the
original fault found?)

Anyway I think I've cure the problem by going back a version with my
kernel. Now on 3.16. No problems so far.

I was getting a couple of other spurious messages on boot, prior to the
desktop appearing, and they have gone as well. They were related to USB
something not found or busy.

Regards
John M

 Date: Fri, 2 Jan 2015 05:11:11 +
 From: 1235...@bugs.launchpad.net
 To: fandjmann...@hotmail.co.uk
 Subject: [Bug 1235567] Re: ibus-ui-gtk3 crashed with SIGABRT
 
 From upstream bug :
 It seems you have a bug from the previous internal patch.
 Please run 'ibus reset-config' and 'ibus restart' command.
 
 At least it looks like this fixed the bug for me.
 
 (also this may be fixed upstream, see
 https://github.com/ibus/ibus/commit/bb818e438599f080a0cffb0b7573d9a646cf3b1a)
 
 -- 
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1235567
 
 Title:
   ibus-ui-gtk3 crashed with SIGABRT
 
 Status in IBus:
   Unknown
 Status in ibus package in Ubuntu:
   Triaged
 
 Bug description:
   Restarted system after installing updates was greeting me with that
   message
 
   ProblemType: Crash
   DistroRelease: Ubuntu 13.10
   Package: ibus 1.5.3-6ubuntu2
   ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3
   Uname: Linux 3.11.0-11-generic x86_64
   ApportVersion: 2.12.5-0ubuntu1
   Architecture: amd64
   Date: Sat Oct  5 08:17:10 2013
   Disassembly: = 0x7f62f38f4f77: Cannot access memory at address 
 0x7f62f38f4f77
   ExecutablePath: /usr/lib/ibus/ibus-ui-gtk3
   InstallationDate: Installed on 2013-06-12 (114 days ago)
   InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)
   MarkForUpload: True
   ProcCmdline: /usr/lib/ibus/ibus-ui-gtk3
   ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
   Signal: 6
   SourcePackage: ibus
   StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
   Title: ibus-ui-gtk3 crashed with SIGABRT
   UpgradeStatus: Upgraded to saucy on 2013-08-11 (55 days ago)
   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
 
 To manage notifications about this bug go to:
 https://bugs.launchpad.net/ibus/+bug/1235567/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235567

Title:
  ibus-ui-gtk3 crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1235567/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 1366351] Re: compiz crashed with SIGSEGV in g_closure_invoke()

2014-10-10 Thread John Manning
Hi


Nothing out of the ordinary going on here and it doesn’t happen every time. 
Don’t you just love intermittent faults.




Sent from Windows Mail



From: Brandon Schaefer
Sent: ‎Thursday‎, ‎9‎ ‎October‎ ‎2014 ‎22‎:‎11
To: ICE - Fran



Hmm i just cant reproduce this issue :(.

Do you have multi monitors? Do you still get the crash when you have a
password? Anything else you have set up that is different then a default
install?

We have some ideas, but we cant really confirm a fix at all until we
have someone who can reproduce it!

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1368807).
https://bugs.launchpad.net/bugs/1366351

Title:
  compiz crashed with SIGSEGV in g_closure_invoke()

Status in Compiz:
  Confirmed
Status in “compiz” package in Ubuntu:
  Triaged

Bug description:
  Issue on booting into unity

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: compiz-core 1:0.9.12+14.10.20140812-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-13.19-generic 3.16.1
  Uname: Linux 3.16.0-13-generic x86_64
  NonfreeKernelModules: fglrx
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Sep  6 10:48:43 2014
  Disassembly: = 0x0:  Cannot access memory at address 0x0
  DistUpgraded: 2014-09-01 18:03:23,330 DEBUG enabling apt cron job
  DistroCodename: utopic
  DistroVariant: ubuntu
  ExecutablePath: /usr/bin/compiz
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Curacao XT [Radeon R9 270X] 
[1002:6810] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:04a1]
  InstallationDate: Installed on 2014-03-24 (166 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  MachineType: MSI MS-7640
  ProcCmdline: compiz
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LD_LIBRARY_PATH=set
   LANG=en_US.UTF-8
   XDG_RUNTIME_DIR=set
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-13-generic 
root=UUID=2696ea28-d88b-431c-a1fa-1e0f297ee664 ro quiet splash vt.handoff=7
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: compiz
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: compiz crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: Upgraded to utopic on 2014-09-01 (4 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 10/31/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.15
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: 890FXA-GD70 (MS-7640)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.15:bd10/31/2012:svnMSI:pnMS-7640:pvr1.0:rvnMSI:rn890FXA-GD70(MS-7640):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7640
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12+14.10.20140812-0ubuntu1
  version.fglrx-installer: fglrx-installer N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.6-1ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.6-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sat Sep  6 10:48:05 2014
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   AIGLX error: failed to open /usr/X11R6/lib64/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib64/modules/dri/fglrx_dri.so: cannot open shared object 
file: No such file or directory]
   AIGLX error: failed to open /usr/lib64/dri/fglrx_dri.so, 
error[/usr/lib64/dri/fglrx_dri.so: cannot open shared object file: No such file 
or directory]
   AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, 
error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot