remmina crashed with SIGSEGV in InterlockedIncrement()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
remmina (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
size: 6MiB
capacity: 6MiB
*-memory
physical id: 22
slot: System board or motherboard
size: 10GiB
*-bank:0
slot: ChannelA-DIMM0
size: 2GiB
width: 64 bits
clock: 1066MHz (0.9ns)
*-bank:1
slot: ChannelA-DIMM1
size: 4GiB
width: 64 bits
clock: 1066MHz (0.9ns)
*-bank:2
slot: ChannelB-DIMM0
size: 2GiB
width: 64 bits
clock: 1066MHz (0.9ns)
*-bank:3
slot: ChannelB-DIMM1
size: 2GiB
width: 64 bits
clock: 1066MHz (0.9ns)
*-cpu
product: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
vendor: Intel Corp.
physical id: 23
bus info: cpu@0
version: Intel(R) Core(TM) i5-2500 CPU @ 3.30GHz
slot: SOCKET 0
size: 2999MHz
capacity: 3800MHz
width: 64 bits
clock: 100MHz
*-pci
product: 2nd Generation Core Processor Family DRAM Controller
vendor: Intel Corporation
physical id: 100
bus info: pci@0000:00:00.0
version: 09
width: 32 bits
clock: 33MHz
*-pci:0
bus info: pci@0000:00:01.0
width: 32 bits
clock: 33MHz
bus info: pci@0000:01:00.0
bus info: pci@0000:01:00.1
*-display
bus info: pci@0000:00:02.0
width: 64 bits
clock: 33MHz
*-usb:0
bus info: pci@0000:00:14.0
width: 64 bits
clock: 33MHz
bus info: usb@3
bus info: usb@4
bus info: pci@0000:00:16.0
width: 64 bits
clock: 33MHz
bus info: pci@0000:00:16.3
width: 32 bits
clock: 66MHz
*-network
bus info: pci@0000:00:19.0
size: 1Gbit/s
width: 32 bits
clock: 33MHz
*-usb:1
bus info: pci@0000:00:1a.0
width: 32 bits
clock: 33MHz
bus info: usb@1
*-usb
bus info: pci@0000:00:1b.0
width: 64 bits
clock: 33MHz
*-pci:1
bus info: pci@0000:00:1c.0
width: 32 bits
clock: 33MHz
*-pci
bus info: pci@0000:02:00.0
*-usb:2
bus info: pci@0000:00:1d.0
width: 32 bits
clock: 33MHz
bus info: usb@2
*-usb
*-pci:2
bus info: pci@0000:00:1e.0
width: 32 bits
clock: 33MHz
*-isa
bus info: pci@0000:00:1f.0
width: 32 bits
clock: 33MHz
*-storage
bus info: pci@0000:00:1f.2
width: 32 bits
clock: 66MHz
*-serial UNCLAIMED
bus info: pci@0000:00:1f.3
width: 64 bits
clock: 33MHz
*-generic UNCLAIMED
bus info: pci@0000:00:1f.6
width: 64 bits
clock: 33MHz
*-scsi:0
physical id: 1
logical name: scsi2
*-disk
bus info: scsi@2:0.0.0
size: 465GiB (500GB)
bus info: scsi@2:0.0.0,1
bus info: scsi@2:0.0.0,2
bus info: scsi@2:0.0.0,3
*-scsi:1
physical id: 2
logical name: scsi3
*-disk
bus info: scsi@3:0.0.0
size: 298GiB (320GB)
bus info: scsi@3:0.0.0,1
bus info: scsi@3:0.0.0,2
*-power UNCLAIMED
description: To Be Filled By O.E.M.
product: To Be Filled By O.E.M.
vendor: To Be Filled By O.E.M.
physical id: 1
version: To Be Filled By O.E.M.
serial: To Be Filled By O.E.M.
capacity: 32768mWh
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: remmina 1.2.0-rcgit.
ProcVersionSign
Uname: Linux 4.15.0-13-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Apr 10 20:11:28 2018
ExecutablePath: /usr/bin/remmina
InstallationDate: Installed on 2018-04-10 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
ProcCmdline: /usr/bin/remmina
SegvAnalysis:
Segfault happened at: 0x7fdc7ad4bda5 <InterlockedInc
PC (0x7fdc7ad4bda5) ok
source "%eax" ok
destination "(%rdi)" (0x00000020) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: remmina
StacktraceTop:
InterlockedInc
EnterCriticalS
MessageQueue_
MessageQueue_Post () from /usr/lib/
?? () from /usr/lib/
Title: remmina crashed with SIGSEGV in InterlockedIncr
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
XsessionErrors:
mate-session[
(process:1765): indicator-
(nm-applet:1757): Gtk-WARNING **: 19:35:46.840: Can't set a parent on widget which has a parent
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1751324, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.