Bug 744965 - could not create ICE listening socket fedora
Summary: could not create ICE listening socket fedora
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: libICE
Version: 15
Hardware: i686
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-11 01:57 UTC by Ryein
Modified: 2018-04-11 11:05 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-29 02:06:45 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
from this incident (22.28 KB, text/x-log)
2013-02-02 16:15 UTC, rmknox
no flags Details
ditto (21.63 KB, application/x-trash)
2013-02-02 16:16 UTC, rmknox
no flags Details
ditto (55.25 KB, application/octet-stream)
2013-02-02 16:17 UTC, rmknox
no flags Details

Description Ryein 2011-10-11 01:57:59 UTC
Description of problem:
When I reboot I some times see an error message "could not create ICE listening socket"

Version-Release number of selected component (if applicable):
Unknown

How reproducible:
 I haven't been able to reproduce it, but it does happen often.

Steps to Reproduce:
1. reboot

Actual results:
could not create ICE listening socket

Expected results:
no errors

Additional info:

Comment 1 Haïkel Guémar 2011-10-11 06:09:21 UTC
You picked the wrong ice, buddy. In Fedora:
* package "ice" relates to the "Internet Communication Engine" middleware (a CORBA-like framework which i bet you don't even have installed on your box ;) )
* package "libICE" to X11 "Inter-Client Exchange" protocol which is probably the one you're looking for.

I reassigned the ticket to libICE, though i'm not 100% sure that they're the right guys for your issue (at least, they may be able to do a better triaging than me here)

Comment 2 Matěj Cepl 2011-10-12 19:01:06 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log*; check with grep Backtrace /var/log/Xorg* which logs might be the most interesting ones, send us at least Xorg.0.log)
* output of the dmesg command, and
* output of the command (run as root)
ausearch -m AVC -ts today
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 3 Ryein 2011-10-29 02:06:45 UTC
An updated fixed the issue.  I will just close it. Thanks.

Comment 4 cornel panceac 2012-05-28 07:07:48 UTC
Hmm, this happens often in fedora 16 (i686) and i've just seen it first time in fedora 17 x86_64 (which is supposed to be released tomorrow). Matej, if you're still in charge with this, please let me know if i should open a new bug report.

Comment 5 Dave Allan 2012-06-06 13:27:34 UTC
(In reply to comment #4)
> Hmm, this happens often in fedora 16 (i686) and i've just seen it first time
> in fedora 17 x86_64 (which is supposed to be released tomorrow). Matej, if
> you're still in charge with this, please let me know if i should open a new
> bug report.

I asked Matej about this, and he recommended filing a new BZ, which I have against F17, bug 829324

Comment 6 rmknox 2013-02-02 16:15:22 UTC
Created attachment 691999 [details]
from this incident

Comment 7 rmknox 2013-02-02 16:16:00 UTC
Created attachment 692000 [details]
ditto

Comment 8 rmknox 2013-02-02 16:17:05 UTC
Created attachment 692001 [details]
ditto

Comment 9 rmknox 2013-02-02 16:20:57 UTC
Happened to me today on fedora 17 3.7.3-101.fc17.i686

I attached var/log/Xorg.0.log and var/log/Xorg.0.log and dmesg.lst

When I closed the graphical window system went black for a moment and then offered me a login which worked. Thus at this moment I am on the session where it occurred.

Comment 10 rmknox 2013-02-02 16:22:25 UTC
Should I open a new bug report ? It is my impression that you want to minimize them.


Note You need to log in before you can comment on or make changes to this bug.