[Bug 1213098] New: Docky freezes when wifi can't connect.
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1213098
Bug ID: 1213098
Summary: Docky freezes when wifi can't connect.
Product: Fedora
Version: 21
Component: docky
Severity: medium
Assignee: i(a)cicku.me
Reporter: goedine(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i(a)cicku.me, mono(a)lists.fedoraproject.org
Description of problem: Docky freezes when my computer is unable to connect to
the internet or the wifi.
Version-Release number of selected component (if applicable): 2.2.0
How reproducible:Always
Steps to Reproduce:
1. Start the computer and connect it to a non-functioning wifi
2.Docky freezes so kill the docky process.
3. Connect to the wifi and re-start docky. Docky now works.
Actual results: Docky freezes if at startup wifi is not stable.
Expected results: Docky should not freeze.
Additional info:There are two docklets in my docky that require an internet
connection. One is weather, and the other one is gmail. I have a suspicion that
weather (the docklet) may cause the freezing.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=AftEZSlpXe&a=cc_unsubscribe
8 years, 3 months
Re: Mono 4 Alpha1
by Timotheus Pokorra
Moving this conversation back to the Fedora mono list...
On 13 April 2015 at 13:29, Claudio Rodrigo <elsupergomez(a)gmail.com> wrote:
> I think, Mono 3 and 4 must coexist like python 2 and python 3. Unless all
> software dependent on profiles 2, 3.5 and 4 migrate to profile 4.5. This is
> a huge task like I see, because many package depend on this profiles. What
> do you think?
I think the difference between Python2 and Python3 is much bigger,
because the API has changed. You need to completely rewrite software
from 2 to 3.
For profiles < 4.5, there are only minor issues I suspect.
Can we hold the package maintainers of the other packages responsible
for patching and fixing their packages for Mono 4?
I don't think we should maintain two different versions of Mono, if we
have trouble maintaining just one...
Alternatively, we could first focus on getting Mono 3.12.1 into
Fedora, before we start working on Mono 4 at all.
8 years, 11 months