Bug 4682 - uninstalling plymouth-system-theme is producting error messages
Summary: uninstalling plymouth-system-theme is producting error messages
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2012-02-24 16:34 CET by Kamil Rytarowski
Modified: 2015-09-22 19:47 CEST (History)
7 users (show)

See Also:
Source RPM: plymouth
CVE:
Status comment:

Attachments
error message (4.21 KB, image/png)
2012-02-24 16:34 CET, Kamil Rytarowski 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kamil Rytarowski 2012-02-24 16:34:37 CET 
Created attachment 1626 [details]
error message

When uninstalling the package there is an error message. It's visible on the attachment.
Comment 1 Manuel Hiebel 2012-02-24 19:45:18 CET 
error: remove-boot-splash: plymouth no found in /boot/initrd.img

CC: (none) => anssi.hannula, boklm, dmorganec, fundawang, mageia, mageia
Source RPM: (none) => plymouth

Comment 2 Marja Van Waes 2012-05-26 13:09:09 CEST 
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 3 Marja Van Waes 2012-07-15 06:37:59 CEST 
@ Kamil

Can this bug be closed as OLD (well, or fixed, of course), or did you still run into this with current cauldron and/or Mageia 2?

CC: (none) => marja11

Comment 4 roelof Wobben 2013-01-01 11:25:15 CET 
@ Kamil

Can this bug be closed as OLD (well, or fixed, of course), or did you still run
into this with current cauldron and/or Mageia 2?

CC: (none) => r.wobben

Nicolas Vigier 2014-03-24 10:52:43 CET

CC: boklm => (none)

Comment 5 Marja Van Waes 2015-09-22 19:47:04 CEST 
No reply since over 3 years ago, closing

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.