View Single Post
coderus's Avatar
Posts: 6,436 | Thanked: 12,699 times | Joined on Nov 2011 @ Ängelholm, Sweden
#53
No surprise for me, Schturman scripts strikes again
remove with rpm -e sailfishos-shutdown-screen--noscripts

Originally Posted by explit View Post
Have big trouble with Shturman's shutdown screen patch:

Code:
zypper rm sailfishos-shutdown-screen
PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running.
Tell PackageKit to quit? [yes/no] (no): yes
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following package is going to be REMOVED:
  sailfishos-shutdown-screen

1 package to remove.
After the operation, 6.8 KiB will be freed.
Continue? [y/n/?] (y): y
Removing sailfishos-shutdown-screen-0.1-2 .....................................................[error]
Removal of (7830)sailfishos-shutdown-screen-0.1-2.noarch(@System) failed:
Error: Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.CZf9iX: line 2: //: is a directory
error: %preun(sailfishos-shutdown-screen-0.1-2.noarch) scriptlet failed, exit status 2
error: sailfishos-shutdown-screen-0.1-2.noarch: erase failed


Abort, retry, ignore? [a/r/i] (a): r
Removing sailfishos-shutdown-screen-0.1-2 .....................................................[error]
Removal of (7830)sailfishos-shutdown-screen-0.1-2.noarch(@System) failed:
Error: Subprocess failed. Error: RPM failed: /var/tmp/rpm-tmp.ekZS2s: line 2: //: is a directory
error: %preun(sailfishos-shutdown-screen-0.1-2.noarch) scriptlet failed, exit status 2
error: sailfishos-shutdown-screen-0.1-2.noarch: erase failed


Abort, retry, ignore? [a/r/i] (a): i
There are some running programs that use files deleted by recent upgrade. You may wish to restart some of them. Run 'zypper ps' to list these programs.
[root@Sailfish nemo]#
any ideas, how i can get rid of this package ?

THX
__________________
Telegram | Openrepos | GitHub | Revolut donations
 

The Following 4 Users Say Thank You to coderus For This Useful Post: