Public bug reported:

I got this crash report after I rebooted my PC, but I'm sorry that I
don't know how to reproduce it.

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: plymouth 0.9.3-1ubuntu10
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Tue Feb 19 10:57:23 2019
DefaultPlymouth: /usr/share/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
Disassembly: => 0x21:   Cannot access memory at address 0x21
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-06-18 (245 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: ASUSTeK COMPUTER INC. K30AD_M31AD_M51AD
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a9094983-e022-4542-9e83-2c6f4fe4d612 ro quiet splash vt.handoff=1
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=/run/plymouth/pid 
--attach-to-session
ProcEnviron:
 LANG=it_IT.UTF-8
 PATH=(custom, no user)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=a9094983-e022-4542-9e83-2c6f4fe4d612 ro quiet splash vt.handoff=1
SegvAnalysis:
 Segfault happened at: 0x21:    Cannot access memory at address 0x21
 PC (0x00000021) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
 ?? ()
 ply_keyboard_stop_watching_for_input () from 
/lib/x86_64-linux-gnu/libply-splash-core.so.4
 ply_device_manager_deactivate_keyboards () from 
/lib/x86_64-linux-gnu/libply-splash-core.so.4
 ?? ()
 ?? ()
TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
Title: plymouthd crashed with SIGSEGV in ply_keyboard_stop_watching_for_input()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 11/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0402
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K30AD_M31AD_M51AD
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0402:bd11/29/2013:svnASUSTeKCOMPUTERINC.:pnK30AD_M31AD_M51AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnK30AD_M31AD_M51AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: K30AD_M31AD_M51AD
dmi.product.sku: All
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.apport.crashdb.conf: 2018-10-22T09:50:20.732763

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


** Tags: amd64 apport-crash cosmic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  plymouthd crashed with SIGSEGV in
  ply_keyboard_stop_watching_for_input()

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

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

Reply via email to