https://bugzilla.redhat.com/show_bug.cgi?id=2278828
Bug ID: 2278828 Summary: [abrt] ibus: bus_server_init(): ibus-daemon killed by SIGTRAP Product: Fedora Version: 40 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:e70f4ca101def3ac6f2be9e0173bd33fef6ba0ee;VAR IANT_ID=workstation; Component: ibus Assignee: tfujiwar@redhat.com Reporter: torkiz@gmx.com QA Contact: extras-qa@fedoraproject.org CC: i18n-bugs@lists.fedoraproject.org, shawn.p.huang@gmail.com, tfujiwar@redhat.com Target Milestone: --- Classification: Fedora
Version-Release number of selected component: ibus-1.5.30~rc3-1.fc40
Additional info: reporter: libreport-2.17.15 type: CCpp reason: ibus-daemon killed by SIGTRAP journald_cursor: s=926450c9204b4ee199a2df9f7b299dc4;i=56dc35;b=834d54fcea284ad599ee8afd04d17a7d;m=18f8f439;t=61761d346609b;x=e521fb9716b4d660 executable: /usr/bin/ibus-daemon cmdline: /usr/bin/ibus-daemon --panel disable cgroup: 0::/user.slice/user-1001.slice/user@1001.service/session.slice/org.freedesktop.IBus.session.GNOME.service rootdir: / uid: 1001 kernel: 6.8.7-300.fc40.x86_64 package: ibus-1.5.30~rc3-1.fc40 runlevel: N 5 backtrace_rating: 4 crash_function: bus_server_init
Truncated backtrace: Thread no. 1 (1 frames) #4 bus_server_init at /usr/src/debug/ibus-1.5.30
Potential duplicate: bug 1785276
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(torkiz@gmx.com) Doc Type|--- |If docs needed, set a value
--- Comment #13 from fujiwara tfujiwar@redhat.com --- I think your /home/zdalny/.cache/ibus has wrong permission but it was not generated by the current ibus. If you move or delete the directory, I think the problem won't happen.
(In reply to S.J. from comment #12)
Created attachment 2031017 [details] File: backtrace
#0 g_log_structured_array (log_level=<optimized out>, fields=0x7ffef11069b0, n_fields=4) at ../glib/gmessages.c:426 #1 0x00007f11f6c61377 in g_log_default_handler (log_domain=log_domain@entry=0x561abb83002c "IBUS", log_level=log_level@entry=6, message=message@entry=0x561abcec3aa0 "mkdir is failed in: /home/zdalny/.cache/ibus: Brak dost\304\231pu", unused_data=unused_data@entry=0x0) at ../glib/gmessages.c:3357 #2 0x00007f11f6c58249 in g_logv (log_domain=0x561abb83002c "IBUS", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7ffef1106b10) at ../glib/gmessages.c:1246 msg_alloc = 0x561abcec3aa0 "mkdir is failed in: /home/zdalny/.cache/ibus: Brak dost\304\231pu" msg = 0x561abcec3aa0 "mkdir is failed in: /home/zdalny/.cache/ibus: Brak dost\304\231pu" #3 0x00007f11f6c585b3 in g_log (log_domain=log_domain@entry=0x561abb83002c "IBUS", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x561abb83157c "mkdir is failed in: %s: %s") at ../glib/gmessages.c:1315 #4 0x0000561abb816d2c in bus_server_init () at /usr/src/debug/ibus-1.5.30~rc3-1.fc40.x86_64/bus/server.c:295 socket_address = 0x561abced36c0 "unix:tmpdir=/home/zdalny/.cache/ibus"
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
S.J. torkiz@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(torkiz@gmx.com) |
--- Comment #14 from S.J. torkiz@gmx.com --- "(...) mkdir is failed in: /home/zdalny/.cache/ibus: Brak dost\304\231pu", unused_data=unused_data@entry=0x0) at ../glib/gmessages.c:3357 (...)"
There is also a problem with what was supposed to point to the "/home/remote" directory when it did not exist at all and was not previously marked anywhere and in any configuration of any program - this is definitely puzzling... the mentioned path has simply never existed in system .
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |NOTABUG Status|NEW |CLOSED Last Closed| |2024-05-22 11:45:11
--- Comment #15 from fujiwara tfujiwar@redhat.com --- (In reply to S.J. from comment #14)
There is also a problem with what was supposed to point to the "/home/remote" directory when it did not exist at all and was not previously marked anywhere and in any configuration of any program - this is definitely puzzling... the mentioned path has simply never existed in system .
If "/home/remote" does not exist, probably your $HOME is not valid.
ibus-daemon tries: 1. $XDG_CACHE_HOME/ibus if XDG_CACHE_HOME environment variable is available. 2. $HOME/.cache/ibus if HOME environment variable is available. 3. <HOME>/.cache/ibus <HOME> is pulled from /etc/passwd.
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
--- Comment #16 from S.J. torkiz@gmx.com --- "/home/zdalny/" (Polish translate from backtrace) or "/home/remote" never existed with any Fedora or other Linux installation - maybe I don't understand what's going on. There is only a directory "/home/$SAMPLE_USER/.cache/ibus"
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
S.J. torkiz@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |ASSIGNED Resolution|NOTABUG |--- Keywords| |Reopened
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |CLOSED Resolution|--- |NOTABUG Last Closed|2024-05-22 11:45:11 |2024-05-22 13:58:00
--- Comment #17 from fujiwara tfujiwar@redhat.com --- You should have the home direcotry otherwise ibus continue to cause the SEGV.
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
S.J. torkiz@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTABUG |--- Status|CLOSED |POST
--- Comment #18 from S.J. torkiz@gmx.com --- I will write this clearly once again - my home directory is "/home/slawek" - I do not have and never have had a "/home/remote" directory. Neither on a physical computer nor on a virtual computer. It seemed to me that the bug reporting system works automatically since it is turned on and I can't even control what it sends to https://bugzilla.redhat.com. There is clearly a problem since my agent reports such an event to the server.
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
--- Comment #19 from fujiwara tfujiwar@redhat.com --- I already explained your configuration was bad. See https://bugzilla.redhat.com/show_bug.cgi?id=2278828#add_comment how to resolve your issue.
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
--- Comment #20 from fujiwara tfujiwar@redhat.com --- The correct suggestion: https://bugzilla.redhat.com/show_bug.cgi?id=2278828#c15
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
--- Comment #21 from S.J. torkiz@gmx.com --- Sorry, but due to your complete lack of understanding of the problem, this time I will refer you to my suggestion https://bugzilla.redhat.com/show_bug.cgi?id=2278828#c18. I doubt that my sarcasm will change anything, but other users of this system also read it - I'll call it a pure example of your incompetence and disregard for me personally and for the programming problem, which should not happen in the bug reporting system. Thx :)
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
S.J. torkiz@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|POST |CLOSED Resolution|--- |ERRATA Last Closed|2024-05-22 13:58:00 |2024-05-22 15:12:25
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
Kan-Ru Chen kanru@kanru.info changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kanru@kanru.info
--- Comment #22 from Kan-Ru Chen kanru@kanru.info --- (In reply to S.J. from comment #21)
Sorry, but due to your complete lack of understanding of the problem, this time I will refer you to my suggestion https://bugzilla.redhat.com/show_bug.cgi?id=2278828#c18. I doubt that my sarcasm will change anything, but other users of this system also read it - I'll call it a pure example of your incompetence and disregard for me personally and for the programming problem, which should not happen in the bug reporting system. Thx :)
Hi S.J.
I happen to read your message and I think it is unnecessary harsh.
We can only try to guess the problem you reported from the data we have on the file.
In the environ file attached in https://bugzilla.redhat.com/show_bug.cgi?id=2278828#c4 There is clearly a user `zdalny` whose user id is `1001`
LOGNAME=zdalny HOME=/home/zdalny USERNAME=zdalny USER=zdalny MAIL=/var/spool/mail/zdalny SSH_AUTH_SOCK=/run/user/1001/keyring/ssh XAUTHORITY=/run/user/1001/.mutter-Xwaylandauth.2RK3M2 XDG_RUNTIME_DIR=/run/user/1001 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1001/bus
From the mountinfo in https://bugzilla.redhat.com/show_bug.cgi?id=2278828#c6 There is also a user id `1000`, which I believe is your user id.
Maybe you can try to run `id 1001` to find out who is this mysterious user.
For example this is the output from my system:
$ id 1000 uid=1000(kanru) gid=1000(kanru) groups=1000(kanru),10(wheel)
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
S.J. torkiz@gmx.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|ERRATA |--- Status|CLOSED |NEW
--- Comment #23 from S.J. torkiz@gmx.com --- Unfortunately, I will not get this information anymore - in the meantime I created the user "MSI" (a long time after the error/problem was reported). At the moment, the situation is as follows:
slawek@maszyna:~$ id 1000 uid=1000(slawek) gid=1000(slawek) grupy=1000(slawek),10(wheel),971(vboxusers) slawek@maszyna:~$ id 1001 uid=1001(msi) gid=1001(msi) grupy=1001(msi)
Generally, if the "/home/zdalny" user existed, the newly created user "msi" would obtain Id 1002. The matter is even more strange.I don't think it's possible to get any more relevant information at the moment. I manually delete the contents of /var/log from time to time.
Thank you, however, for trying to help explain the problem. The conclusion is that someone may have tried to do something remotely in my system - just in case, I will reinstall Fedora 40 after resetting the disk in some known and simple way, e.g.
dd if=/dev/zero of=/dev/sdX
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
--- Comment #24 from fujiwara tfujiwar@redhat.com --- Did you reproduce the issue recently?
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
--- Comment #25 from S.J. torkiz@gmx.com --- As expected, of course, this error no longer appeared... cleaning the disk and reinstalling the entire system with add-ons did the trick.
https://bugzilla.redhat.com/show_bug.cgi?id=2278828
fujiwara tfujiwar@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |NOTABUG Last Closed|2024-05-22 15:12:25 |2024-05-28 14:10:07
--- Comment #26 from fujiwara tfujiwar@redhat.com --- Then you had a bad configuration. Please reopen when you reproduce the issue again.
i18n-bugs@lists.fedoraproject.org
-
bugzilla＠redhat.com