[Bug 1202064] New: Unable to install fcitx5
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 Bug ID: 1202064 Summary: Unable to install fcitx5 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Installation Assignee: yast2-maintainers@suse.de Reporter: php4fan@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- I was trying to troubleshoot issues with fcitx and came across some note on some of their official websites (I'm to lazy to find it again now) that said something like: fcitx4 is in low-maintenance mode. fcitx5 is mature enough, you should use that instead Those were not the exact words but it was the gist of it. So first I uninstalled fcitx completely because I wanted to try to install iBus again, you'll find other bug reports of mine about that. Then I uninstalled iBus again too, and I tried: suzo zypper install fcitx5 and this is the output: `````` Resolving package dependencies... Problem: the to be installed fcitx5-5.0.18-1.1.x86_64 requires 'libFcitx5Config.so.6()(64bit)', but this requirement cannot be provided not installable providers: libFcitx5Config6-5.0.18-1.1.x86_64[repo-oss] Solution 1: Following actions will be done: architecture change of fcitx-qt5-1.2.7-1.10.x86_64 to fcitx-qt5-1.2.7-1.10.i586 architecture change of libfcitx-gclient1-4.2.9.8-5.3.x86_64 to libfcitx-gclient1-4.2.9.8-5.3.i586 Solution 2: do not install fcitx5-5.0.18-1.1.x86_64 Solution 3: break fcitx5-5.0.18-1.1.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/c/d/?] (c): c `````` Obviously solutions 2 and 3 are non-solutions, but 1 doesn't seem right. I'm not sure exactly what the "architecture change" means, but my CPU is an x86_64, so changing the "architecture of something" to i586 definitely doesn't sound right. If I can't just install fcitx5 right away without having to do scary stuff, something is wrong. And if Fitx's authors say version 5 is mature enough (to the point that they don't put effort into fixing issues and supporting the previous version) and you don't allow me to use it, either they are lying or you're not up to date. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c1 Andreas Stieger <Andreas.Stieger@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |Andreas.Stieger@gmx.de, | |i@xuzhao.net Component|Installation |Other Resolution|--- |WORKSFORME Assignee|yast2-maintainers@suse.de |i@xuzhao.net QA Contact|jsrain@suse.com |qa-bugs@suse.de --- Comment #1 from Andreas Stieger <Andreas.Stieger@gmx.de> --- Not a YaST bug, moving to maintainer. Also confirmed to NOT affect stock Factory. Looks like you are using incompatible repositories or locks. Closing as WORKSFORME. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c2 --- Comment #2 from Andreas Stieger <Andreas.Stieger@gmx.de> --- for completeness: zypper sl # | Alias | Name | Enabled | GPG Check | Refresh | Type --+--------------+-----------------------------+---------+-----------+---------+------- 1 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | NONE 2 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | rpm-md 3 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | rpm-md 4 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | NONE 5 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | rpm-md zypper in --dry-run fcitx5 Loading repository data... Reading installed packages... Resolving package dependencies... The following 64 NEW packages are going to be installed: Mesa Mesa-dri Mesa-gallium Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 enchant-1-backends fcitx5 gdk-pixbuf-query-loaders gio-branding-openSUSE glib2-tools libFcitx5Config6 libFcitx5Core7 libFcitx5Utils2 libLLVM14 libX11-xcb1 libXfixes3 libXxf86vm1 libcairo2 libdatrie1 libdrm2 libdrm_amdgpu1 libdrm_intel1 libdrm_nouveau2 libdrm_radeon1 libenchant1 libfribidi0 libgbm1 libgdk_pixbuf-2_0-0 libgio-2_0-0 libglvnd libgobject-2_0-0 libgraphite2-3 libharfbuzz0 libhunspell-1_7-0 libpango-1_0-0 libpciaccess0 libpixman-1-0 libthai-data libthai0 libwayland-client0 libwayland-server0 libxcb-dri2-0 libxcb-dri3-0 libxcb-ewmh2 libxcb-glx0 libxcb-icccm4 libxcb-imdkit1 libxcb-keysyms1 libxcb-present0 libxcb-randr0 libxcb-render0 libxcb-shm0 libxcb-sync1 libxcb-util1 libxcb-xfixes0 libxcb-xinerama0 libxcb-xkb1 libxkbcommon-x11-0 libxkbcommon0 libxkbfile1 libxshmfence1 shared-mime-info xkeyboard-config 64 new packages to install. Overall download size: 47.2 MiB. Already cached: 0 B. After the operation, additional 202.9 MiB will be used. Continue? [y/n/v/...? shows all options] (y): -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c3 --- Comment #3 from teo teo <php4fan@gmail.com> ---
Looks like you are using incompatible repositories or locks.
If I ended up with any of that it's probably because of some bug in the first place. I definitely didn't choose to install incompatible repositories and I don't know what a lock is in this context. I don't even know who conceived "works for me" as a reason for closing a bug. If it works for you you need to figure out why it doesn't work for everybody. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c4 --- Comment #4 from Andreas Stieger <Andreas.Stieger@gmx.de> --- Actually, no. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c5 --- Comment #5 from Andreas Stieger <Andreas.Stieger@gmx.de> --- The resolution ���WORKSFORME��� means that we have made attempts to reproduce the issue. I have taken time out of my day to do your homework: see if this happens on stock Tumbleweed. I added evidence to that fact. So that means that your claim that the package does not install is invalidated. If it does not install with a random selection of repositories, then this may or may not be supported. You raised similar issues before with similar hints. I am not doing this for you, but for everyone else: the package installs fine. If you would like help with your special case please choose a less escalating, sensationalist approach. On your case I would audit your current repositories and confirm whether you want to continue using packages from there -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c6 --- Comment #6 from teo teo <php4fan@gmail.com> ---
I have taken time out of my day to do your homework
LOL oh LOL no. Nothing is my homework. I don't know what is or is not your job here, but I definitely have no homework here. This is not a support forum, I am not asking for help. I am reporting a bug. I found something in a piece of software that was not working as expected (or so it strongly seemed to me, and still seems in this case) and *I* took time out of my day to report it, instead of just googling for a workaround for my use case. I don't expect to be thanked, I know it's a tiny to negligible contribution, but I certainly wouldn't expect to be reprehended for not doing more. The report may be incomplete, it may be flawed, it may be useless or even completely bogus (obviously that wouldn't be my intention), I do my best (well not exactly, to be more precise I try to give what little information I have that doesn't require too much work of me) which may be very little, but it's more than is required from me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c7 --- Comment #7 from teo teo <php4fan@gmail.com> ---
I am not doing this for you, but for everyone else
EXACTLY. In every reply of yours, you seem to keep forgetting that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c8 --- Comment #8 from Andreas Stieger <Andreas.Stieger@gmx.de> --- Your report is invalidated by the logs noted above. Check your repositories. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c9 --- Comment #9 from teo teo <php4fan@gmail.com> --- So I have been able to fix it, and everything still seems to indicate that it is a bug. Let's leave aside how the original error message doesn't give even remotely enough of a clue of what's wrong. Here's the output of (because I think you asked, or at least you posted yours):
zypper sl # | Alias | Name | Enabled | GPG Check | Refresh | Type ---+----------------------------------+-----------------------------+---------+-----------+---------+------- 1 | Google-Chrome | Google-Chrome | Yes | (r ) Yes | No | rpm-md 2 | gh-cli | packages for the GitHub CLI | Yes | (r ) Yes | No | rpm-md 3 | google-chrome | google-chrome | Yes | (r ) Yes | Yes | rpm-md 4 | http-ftp.gwdg.de-39a00487 | Packman Repository | Yes | (r ) Yes | Yes | rpm-md 5 | http-opensuse-guide.org-96f6d2e6 | libdvdcss repository | Yes | (r ) Yes | Yes | rpm-md 6 | openSUSE-20201014-0 | openSUSE-20201014-0 | No | ---- | ---- | rpm-md 7 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | NONE 8 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss | Yes | (r ) Yes | Yes | rpm-md 9 | repo-oss | openSUSE-Tumbleweed-Oss | Yes | (r ) Yes | Yes | rpm-md 10 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | NONE 11 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | rpm-md
but I don't think any of that is relevant. What fixed the issue for me was to manually uninstall "fcitx-qt5" and "libfcitx-gclient1". The following commands and their output where after uninstalling fcitx (4) and before I managed to install fcitx5. `````
zypper info fcitx-qt5 [...]
Information for package fcitx-qt5: ---------------------------------- Repository : openSUSE-Tumbleweed-Oss Name : fcitx-qt5 Version : 1.2.7-1.10 Arch : x86_64 Vendor : openSUSE Installed Size : 576,3 KiB Installed : Yes (automatically) <<<<<<<<<<<<<<<<<<<<<<<< THIS Status : up-to-date [...] `````` So first of all that comes from an official repository, right? Then, it says it was installed automatically, hence I understand it was installed as a dependency of something else. So let's try to uninstall this. If that something else is still installed, it will ask me whether I want to uninstall that too. ``````
sudo zypper remove fcitx-qt5 (...) The following package is going to be REMOVED: fcitx-qt5
1 package to remove. <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< THIS After the operation, 576,3 KiB will be freed. Continue? [y/n/v/...? shows all options] (y): y (1/1) Removing fcitx-qt5-1.2.7-1.10.x86_64 `````` So, this had been installed as a dependency of something, but that something is no longer there (or no longer depends on this). So that means this is safe to remove, and could even be removed automatically. I would expect one of three things: a. it would have already been removed automatically. b. at some point it should have given me a prompt that says something like: "The following packages were installed automatically and are no longer needed. Do you want to remove them?" (I distinctly remember that message in Ubuntu's package manager apt, I'm not sure if I had seen it also in zypper) c. When trying to install fcitx5, since this package causes trouble, and it's a package that was installed automatically as a dependency and is no longer needed, either uninstall it or offer me the possibility to uninstall it as one of the proposed solutions to the conflict. The exact same thing went for libfcitx-gclient1. Once I removed both, I ran "sudo zypper install fcitx5" and it installed succesfully. Whether or not any of this is the result of having some non-standard repository doesn't seem relevant to me in any way. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c10 --- Comment #10 from Andreas Stieger <Andreas.Stieger@gmx.de> --- You should not assume that information is not relevant. As we have established you are confused about some things that are happening.
a. it would have already been removed automatically.
See man zypper, about rm --clean-deps
b.
No, and that is by design choice.
Whether or not any of this is the result of having some non-standard repository doesn't seem relevant to me in any way.
Don't assume that. Your report shows that it was not installable. Turns out it is. You wiped the original vendor of the packages, but it would seem that you either had a lock on them or installed it from another repository (and vendor). In any case, unsurprisingly if you use the distribution packages is works. Like I said. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1202064 http://bugzilla.opensuse.org/show_bug.cgi?id=1202064#c11 --- Comment #11 from teo teo <php4fan@gmail.com> ---
You should not assume that information is not relevant.
I didn't, that's why I posted it anyway. I said I *thought* it wasn't relevant, that's not the same as assuming.
b. No, and that is by design choice.
What about c (specifically the second part of the either-or)??
Whether or not any of this is the result of having some non-standard repository doesn't seem relevant to me in any way.
Don't assume that.
Again, I didn't _assume_ that, I explained why I think that.
You wiped the original vendor of the packages,
Are you assuming that?
but it would seem that you either had a lock on them or installed it from another repository (and vendor)
And the error message didn't give any hint about any of that. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com