Bug 414760 - Can't remove KTorrent on openSUSE Tumbleweed
Summary: Can't remove KTorrent on openSUSE Tumbleweed
Status: RESOLVED WORKSFORME
Alias: None
Product: Discover
Classification: Applications
Component: discover (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Dan Leinir Turthra Jensen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-02 18:05 UTC by Nate Graham
Modified: 2019-12-02 19:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nate Graham 2019-12-02 18:05:10 UTC
Discover and all other KDE software from git master on openSUSE Tumbleweed.


STEPS TO REPRODUCE
1. Be on openSUSE Tumbleweed
2. Open Discover and install all updates (if any) and restart (to work around https://bugzilla.opensuse.org/show_bug.cgi?id=1154973)
3. Open Discover again
4. Install Ktorrent
5. Remove KTorrent

OBSERVED RESULT
Discover prompts for your password and appears to be removing KTorrent, but it doesn't actually do it. A PassiveNotification saying "Package not found" briefly appears.


EXPECTED RESULT
KTorrent is removed


ADDITIONAL INFORMATION
Other apps like Kolourpaint can be removed.

`pkcon remove ktorrent` works just fine:

$ pkcon remove ktorrent
Resolving                     [=========================]         
Testing changes               [=========================]         
Finished                      [=========================]         
Removing                      [=========================]         
Waiting for authentication    [=========================]         
Removing packages             [=========================]         
Resolving dependencies        [=========================]         
Removing packages             [=========================]         
Finished                      [=========================]
$ echo $?
0

PKMon shows the following during the KTorrent removal transaction from Discover:

pkmon 
Transactions:
 [none]
daemon connected=1
network status=online
Transactions:
 1      /8_adaaceac
/8_adaaceac     allow_cancel 1
/8_adaaceac     role         remove-packages
/8_adaaceac     status       setup
/8_adaaceac     percentage   10
/8_adaaceac     percentage   40
/8_adaaceac     status       dep-resolve
/8_adaaceac     percentage   100
/8_adaaceac     percentage   0
/8_adaaceac     percentage   100
/8_adaaceac     status       finished
Transactions:
 [none]
/8_adaaceac     exit code: success
Transactions:
 1      /9_abddacee
/9_abddacee     allow_cancel 1
/9_abddacee     percentage   -1
/9_abddacee     role         remove-packages
/9_abddacee     status       setup
/9_abddacee     status       remove
/9_abddacee     percentage   0
/9_abddacee     percentage   10
/9_abddacee     percentage   40
/9_abddacee     status       dep-resolve
/9_abddacee     percentage   100
/9_abddacee     status       remove
/9_abddacee     percentage   0
/9_abddacee     percentage   100
/9_abddacee     status       finished
/9_abddacee     exit code: success
Transactions:
 [none]
updates-changed
Transactions:
 1      /10_ebaadeab
/10_ebaadeab    allow_cancel 1
/10_ebaadeab    role         get-updates
/10_ebaadeab    status       query
/10_ebaadeab    status       refresh-cache
/10_ebaadeab    percentage   12
/10_ebaadeab    percentage   25
/10_ebaadeab    percentage   37
/10_ebaadeab    percentage   50
/10_ebaadeab    percentage   62
/10_ebaadeab    percentage   75
/10_ebaadeab    percentage   100
/10_ebaadeab    percentage   40
/10_ebaadeab    percentage   80
/10_ebaadeab    percentage   100
/10_ebaadeab    status       finished
Transactions:
 [none]
/10_ebaadeab    exit code: success
Comment 1 Aleix Pol 2019-12-02 18:19:34 UTC

*** This bug has been marked as a duplicate of bug 413872 ***
Comment 2 Aleix Pol 2019-12-02 18:20:07 UTC
my bad
Comment 3 Aleix Pol 2019-12-02 19:05:44 UTC
I am unable to reproduce this bug. It seems weird, can you try it with zypper, see if there's some kind of package that needs removing too or something?
Comment 4 Nate Graham 2019-12-02 19:55:19 UTC
Weird, not I can no longer reproduce the issue no matter how hard I try. :/

Sigh. Will re-open if it happens again.