Bug 1461576
Summary: | [abrt] plasma-workspace: SNIProxy::SNIProxy(): xembedsniproxy killed by signal 11 | ||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Eugene Mah <eugenemah> | ||||||||||||||||||||||||||
Component: | plasma-workspace | Assignee: | KDE SIG <kde-sig> | ||||||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||||
Version: | 26 | CC: | anton.kochkov, billcrawford1970, bminish, ciptok, cunio, daramas444, davidjeremias82, e.ashrafinia, gggsartori, hunkdvj, icolle, jazzer2007, jgrulich, kaasboer, kde-sig, lonelywoolf, mail432, mattia.verga, me, phoxis, rdieter, redhatbugzilla, r.info, robinlee.sysu, s.kieske, tcarlin, than, thenscheid, thestonewell, tiaonmmn, vindicators | ||||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/f19df620ece363c0d63c2b57c2d6e7ec0614f2b7 | ||||||||||||||||||||||||||||
Whiteboard: | abrt_hash:163c0bc9ac3cc10107108187fab2918edf1556a9; | ||||||||||||||||||||||||||||
Fixed In Version: | plasma-workspace-5.10.4-1.fc26 | Doc Type: | If docs needed, set a value | ||||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||||
Last Closed: | 2017-08-07 17:26:22 UTC | Type: | --- | ||||||||||||||||||||||||||
Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||
Documentation: | --- | CRM: | |||||||||||||||||||||||||||
Verified Versions: | Category: | --- | |||||||||||||||||||||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||
Embargoed: | |||||||||||||||||||||||||||||
Bug Depends On: | |||||||||||||||||||||||||||||
Bug Blocks: | 1463252 | ||||||||||||||||||||||||||||
Attachments: |
|
Description
Eugene Mah
2017-06-14 20:09:49 UTC
Created attachment 1287809 [details]
File: backtrace
Created attachment 1287810 [details]
File: cgroup
Created attachment 1287811 [details]
File: core_backtrace
Created attachment 1287812 [details]
File: cpuinfo
Created attachment 1287813 [details]
File: dso_list
Created attachment 1287814 [details]
File: environ
Created attachment 1287815 [details]
File: exploitable
Created attachment 1287816 [details]
File: limits
Created attachment 1287817 [details]
File: maps
Created attachment 1287818 [details]
File: open_fds
Created attachment 1287819 [details]
File: proc_pid_status
Created attachment 1287820 [details]
File: var_log_messages
Similar problem has been detected: Logged into my computer and received a notification of a crash reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=ed9f3681ff464b67a92c4c569485a996;i=17ebc4;b=10d0355f827a4ade8f10ebea4d06eb84;m=126386cb;t=552047ac71947;x=b1988379c489b2f1 kernel: 4.11.4-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1462545 has been marked as a duplicate of this bug. *** This is now fixed in Plasma-5.10.3 Similar problem has been detected: When the session started reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=1bccb2952f6d4ba2a572e58accd3e975;i=10ec9;b=17550c5fd7114d079f6eaf7dec92006d;m=9811698;t=55335c8171003;x=3d098ec9b2c67e8f kernel: 4.11.7-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Similar problem has been detected: It happens on resume process. Whole plasma session is crashing closing all previously opened applications. Happened to me already few times. Machine is connected to Dell WD15 docking station with 1 external monitor connected. In this particular case I suspended with docking station connected and resumed without it. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=9ca301758fcc45b98ce9c4bc393c771c;i=11834;b=ba47b3ec0b1f445482c9b47ba4defe44;m=c3923613f;t=55340d594cea7;x=734ab6368ae2f652 kernel: 4.11.6-301.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1467043 has been marked as a duplicate of this bug. *** Similar problem has been detected: First time booting plasma desktop after install @kde-desktop. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=3e7774c320dc482e90611a53e0020bdd;i=206b21;b=f6f498ad9da248deb88aa6608a969a8e;m=36f5327;t=553b0f77230e1;x=e0bbdd3d7d63f7a kernel: 4.11.6-301.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: boot login to user session ge this error reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=3b94b4bf7d0046ee8adfc1012b1a1d39;i=7aa;b=46287819933e4273af2e6154f8159c5c;m=112b8747;t=553b50a3cb878;x=c424dfb534385325 kernel: 4.11.8-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1470075 has been marked as a duplicate of this bug. *** Similar problem has been detected: First boot after the upgrading Fedora 25 to 26. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=57177a814e3e4c3b9e8ae34f4a4d2ee1;i=892f0;b=16a3f62b5f6b4fb3bd0a3ac8681f675c;m=21abf88;t=5542ee220393d;x=ee496f28d8e2011f kernel: 4.11.9-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: Occurs right after login, before networks connect reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=6bdea796b4bd48ee9f3939a05322c75f;i=45215;b=9ddff63f7217458f94d95d500fba9f5d;m=532c4cb;t=5543699821004;x=f61e4d9b544a96de kernel: 4.11.9-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1470990 has been marked as a duplicate of this bug. *** Similar problem has been detected: It happens automatically, plasma freezes frequently after login. Nothing specific needs to be done. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=bcf5e4803292460aab97e3f45a1a255f;i=97a2;b=a25d287489774b00ba72c4c0e52fb07e;m=17bbff1;t=55446ef3674c2;x=a7aa6f36dbcf6aa7 kernel: 4.11.9-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1471208 has been marked as a duplicate of this bug. *** *** Bug 1471271 has been marked as a duplicate of this bug. *** Similar problem has been detected: After upgrading from F25 to F26 I get this crash on startup when logging in. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=427d70eb787c472ea42a2a89341e35c1;i=145f6;b=423e21d3bb464d6ea53d9fb5f2e385d4;m=1d30073;t=5546cda4b2d7d;x=30d63b17dbf188e4 kernel: 4.11.9-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Similar problem has been detected: Logging in to KDE desktop. reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=61305bffb1c541698cf8b9cede06c114;i=11438;b=9d30bb1197f54fea856031e2d59a7fe1;m=3a4a810a;t=554938fb54b18;x=bec052bf7ce5cf4a kernel: 4.11.10-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 1000 *** Bug 1474020 has been marked as a duplicate of this bug. *** *** Bug 1474501 has been marked as a duplicate of this bug. *** Similar problem has been detected: 1. I launched Plasma session 2. I launched Linphone 3. I closed Linphone 4. Plasma fell reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/xembedsniproxy crash_function: SNIProxy::SNIProxy executable: /usr/bin/xembedsniproxy journald_cursor: s=2a0eaf2cbdaf4b018499ca1666f43adb;i=1124a2;b=b8e8317b6ae74a60b76df051cff850ef;m=bf871e3;t=5551e6a60fa75;x=46fd2b134b10180 kernel: 4.11.11-300.fc26.x86_64 package: plasma-workspace-5.10.1-1.fc26 reason: xembedsniproxy killed by signal 11 rootdir: / runlevel: N 5 type: CCpp uid: 16777216 *** Bug 1476036 has been marked as a duplicate of this bug. *** per comment #32 , using latest plasma-workspace-5.10.3 from (stable) updates, I cannot reproduce any crash with start/quit of linphone Can anyone still reproduce this with 5.10.3? (I see all the reports here references 5.10.1) I didn't experienced this crash anymore and I can confirm I'm unable to reproduce the crash with linphone. I don't think I've encountered this bug since the update to 5.10.3 or 5.10.4 Thanks, closing. *** Bug 1484560 has been marked as a duplicate of this bug. *** *** Bug 1484939 has been marked as a duplicate of this bug. *** |