Public bug reported:

Filebot tried to write to network storage, chrashed nautilus and the

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-13-generic 4.15.0-13.14
ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
Uname: Linux 4.15.0-13-generic x86_64
Annotation: Your system might become unstable now and might need to be 
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
Date: Sat Apr  7 15:55:03 2018
Failure: oops
HibernationDevice: RESUME=UUID=16b94b21-aecc-4d2e-93f5-13640ea3517b
InstallationDate: Installed on 2014-04-20 (1448 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
 lo        no wireless extensions.
 eth0      no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. GA-790XT-USB3
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic 
root=UUID=2e3a0b23-1dde-4570-aa78-bd8253bbd52a ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
Title: general protection fault: 0000 [#1] SMP NOPTI
UpgradeStatus: No upgrade log present (probably fresh install) 05/13/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F4 GA-790XT-USB3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd05/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-790XT-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-790XT-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: GA-790XT-USB3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

** Tags: amd64 apport-kerneloops bionic kernel-oops

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  general protection fault: 0000 [#1] SMP NOPTI

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to