| Summary: | XFWM4 issues at startup. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Brian Durant <globetrotterdk> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11 |
| Version: | 1 | Keywords: | NEEDINFO, UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| See Also: | https://bugzilla.xfce.org/show_bug.cgi?id=8070 | ||
| Whiteboard: | |||
| Source RPM: | xfwm4-4.8.1-2.mga1.i586.rpm | CVE: | |
| Status comment: | |||
|
Description
Brian Durant
2011-10-24 11:36:01 CEST
Seems an upstream bug, have you report it to the xfce bug tracker ? https://bugzilla.xfce.org/ Source RPM:
(none) =>
xfwm4 (In reply to comment #1) > Seems an upstream bug, have you report it to the xfce bug tracker ? > https://bugzilla.xfce.org/ Done I think that it is this one: https://bugzilla.xfce.org/show_bug.cgi?id=8070 Keywords:
(none) =>
UPSTREAM @ Brian in the upstream bug report, in comment 3 you say: > I'll look in the path the next time I experience the problem. The issue has > also been posted to Mageia. They asked me to also pass a bug report on to you. and that was the last thing you said. Does that mean you couldn't reproduce the problem? If so, I think it is better to close this bug as "worksforme" for now, it can always be reopened later when needed (Upstream made a patch that didn't work for the only one who tested and since then nothing happened) Keywords:
(none) =>
NEEDINFO @ Brian Please reply to the question above within two weeks from now, to avoid this bug being closed as OLD. Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD. Status:
NEW =>
RESOLVED |