I adopted libeio back when Node.js still bundled it to aid in the unbundling
effort, but upstream "fixed" the bundling problem here by no longer using
libeio for anything.
It's now conflicting with a different eio, used by Enlightenment. Since most
other distros ship the Enlightenment version as libeio.so.1 instead of this
libeio, and nothing in Fedora uses it anymore, I'd like to retire the libeio
package so Enlightenment packaging can proceed without gross unnecessary hacks.
Please shout if you need it for anything and would like to take it over,
otherwise I'll retire it in a week or so.
Am 22.09.2013 02:52, schrieb Ed Greshko:
> On 09/22/13 08:39, Timothy Murphy wrote:
>> Ed Greshko wrote:
>>>> I've been having a problem on my Thinkpad T61 for the last 2 days.
>>>> In fact since "yum update" installed kernel-PAE-3.11.1-200.fc19.i686,
>>>> though that is probably a coincidence.
>>> Would it be possible to boot into the previous kernel to verify if it is a
>> I'm afraid I'm not sure how to do that.
>> I'd be happy to try if someone could suggest the way.
> When you boot your system, don't you have a menu to select up to 3 kernels?
and that is why i cried on @devel about the idea to hide the GRUB menu as default
now we have exactly what i said will happen: users in trouble does not know how to
boot the still installed older kernel because they never learned that there are
more than one because they never faced it as all the years before
developers these days forgot how we learned things in the early days
and that wil always be the price if you give up good technical
solutions for a more shiny look which does only interest if
this are going well
First off congrats, each release gets better and better especially with
regards to the anaconda changes. Either I am getting better trained to
deal with the rough spots or they just have been fixed, I figure it is
So here are some of the issues I ran into, I will file bugs for these
but I reckoned I would chat about them with folks first:
Anaconda failed after all configuration was done and installation began.
I chose to do custom partitioning and was removing and reformatting my
existing partitions. Anaconda was attempting to wipe /dev/sda7 which
didn't exist, highest was sda6, on the system and so it crashed (off by
The new display manager for KDE, SDDM, doesn't seem to work so well in
an IPA environment. Even after adjusting the upper limit in
/etc/sddm.conf to include the insanely high UIDs that IPA hands out no
users appeared in the login box and as such I was unable to move past
that screen. Nor could I figure out how to login as 'Other' user and try
to futz with it as root or some such. I ended up switching to lightDM
and that did work with IPA users.
LightDM appears not to remember the last session used, as such every
time I log in I have to choose the session, or if I don't it will just
pass me past the login and no environment will come up which
precipitates going to another terminal and restarting the display manager.
Finally, and for some reason I can't figure out, F19 Alpha and F20 Alpha
seem to crash my wireless router. F19 Final didn't do this, but the
Alpha sure did and I don't have a clue as to why. My systems has an
Intel 6250 wireless card and the router is an Actiontec c1000a. If
anyone has suggestions or pointers on how to debug this it would be