| Summary: | avahi-daemon drops remote entries after 4500 sec | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Dag Nygren <dag> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | doktor5000, lewyssmith, marja11 |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | avahi-0.6.31-16.mga5 | CVE: | |
| Status comment: | |||
|
Description
Dag Nygren
2016-03-15 22:10:07 CET
Have to add to this that the "transplanted" avahi-daemon also failed in the same way after some time (did probably not wait long enough), so disregard that part of the report. The same binary does work in a Fedora setup, so there is still a difference somewhere. And the original problem persists. Will test a fresh Ubuntu tomorrow.
David Walser
2016-03-17 21:17:38 CET
Assignee:
bugsquad =>
shlomif
Florian Hubold
2016-03-18 08:55:20 CET
CC:
(none) =>
doktor5000 Does this happen with an avahi-daemon built from source? It may be an upstream problem. Haven't tried, and the Ubuntu behaviour does indicate upstream. On the other hand Fedora works quite fine... All the same avahi version. Also the fact that moving the working avahi-daemon from a Fedora installation to Mageia makes it fail actually points to the environment (conifg? Systemd? Other helpers?) more that the daemon itself. Always hard to figure out the weird logic in Pottering generated programs, complicated design and poor documentation generally.... I would also like to point out that the printserver runs Fedora FC23 if it makes a difference. Hi Dag Nygren, Thank you for having taken the needed time to report this issue! Did this bug get fixed? If so, please change its status to RESOLVED - FIXED If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues. If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard. Thanks, Marja CC:
(none) =>
marja11 Still a problem. Chaning version to Mageia 6, Version:
5 =>
6 (In reply to Dag Nygren from comment #6) > Still a problem. Chaning version to Mageia 6, Which is now no longer supported; sorry. Would you like to say whether the problem persists in Mageia 7? CC:
(none) =>
lewyssmith (In reply to Lewis Smith from comment #7) > (In reply to Dag Nygren from comment #6) > > Still a problem. Chaning version to Mageia 6, > Which is now no longer supported; sorry. > Would you like to say whether the problem persists in Mageia 7? No reply, so closing as OLD Dag, if this issue still exists in Mageia 7 or 8-cauldron, then please reopen this report and change "Version:" in the upper left of this report. Resolution:
(none) =>
OLD |