| Summary: | when trying to upgrade to the latest xfree packages I'm getting a warning (due to unsatisfied xserver-abi) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Brook Humphrey <webmedic> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | marja11 |
| Version: | Cauldron | Keywords: | NEEDINFO, Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Bug Depends on: | |||
| Bug Blocks: | 3342 | ||
| Attachments: |
skip.list
LOG.txt |
||
|
Description
Brook Humphrey
2011-11-21 20:16:04 CET
Hi, thanks for reporting this bug. Assigned to the package maintainer. Keywords:
(none) =>
Triaged Please attach your /etc/urpmi/skip.list Keywords:
(none) =>
NEEDINFO Created attachment 1096 [details]
skip.list
Here is the skip.list but it is the default.
Manuel Hiebel
2011-11-22 16:32:21 CET
Attachment 1096 mime type:
application/octet-stream =>
text/plain Can you _attach_ (not paste) the log file resulting from the following command? urpmi --auto-select 2>&1|tee LOG.txt Created attachment 1098 [details]
LOG.txt
At the last prompt I selected no because my laptop acts the exact same way but I went ahead and upgraded it and afterward the fglrx drivers no longer work and cause xfree to signal 11 all the time. It also does this with the radeonhd drivers. I plan to open another bug for that.
However on this system I also use ti for work and can't have xfree broke.
So far I simply use rpmdrake and leave out the xfree packages when I do updates.
removing NEEDINFO because, AFAICS, all requested info was given Keywords:
NEEDINFO =>
(none) What were you doing exactly? cauldron to cauldron update or mga1 to cauldron upgrade? Could you attach the bug3409.tar.xz file resulting from the following commands: urpmi --bug bug3409 --auto-select tar cfa bug3409{.tar.xz,} Keywords:
(none) =>
NEEDINFO I think this was a temporary glitch during the xserver-1.11 preparation (wasn't in core/release yet) Status:
NEW =>
RESOLVED |