Comment # 1 on bug 1091353 from Dominique Leuenberger

Looking at the logs, the main difference seems to be:

GOOD
*****
>2018-04-22 11:29:51 <1> susetest(2815) [packagekit] pk-backend-zypp.cpp(backend_resolve_thread):2853 found (586)inkscape-0.92.2-6.2.x86_64(@System)
>2018-04-22 11:29:51 <1> susetest(2815) [packagekit] pk-backend-zypp.cpp(backend_resolve_thread):2853 found (18816)inkscape-0.92.2-6.2.x86_64(repo1)
>2018-04-22 11:29:51 <1> susetest(2815) [packagekit] pk-backend-zypp.cpp(backend_resolve_thread):2864 emit (18816)inkscape-0.92.2-6.2.x86_64(repo1)
>2018-04-22 11:29:51 <1> susetest(2815) [packagekit] pk-backend-zypp.cpp(backend_resolve_thread):2853 found (18815)inkscape-0.92.2-6.2.i586(repo1)
>2018-04-22 11:29:51 <1> susetest(2815) [packagekit] pk-backend-zypp.cpp(backend_resolve_thread):2873 emit just newest (18816)inkscape-0.92.2-6.2.x86_64(repo1)

BAD
*****
>2018-04-24 18:18:44 <1> susetest(2205) [packagekit] pk-backend-zypp.cpp(backend_resolve_thread):2825 inkscape ~installed;newest;arch;~source
>2018-04-24 18:18:44 <1> susetest(2205) [packagekit] pk-backend-zypp.cpp(backend_resolve_thread):2853 found (581)inkscape-0.92.2-6.2.x86_64(@System)

In the BAD case, no repo* info was found