Bug 2109358

Summary: emacs fails to start: Cannot open load file: No such file or directory, comp
Product: [Fedora] Fedora Reporter: Nick Urbanik <nicku>
Component: emacs-common-ddskkAssignee: Daiki Ueno <dueno>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 36CC: dueno, edgar.hoch, i18n-bugs, jon.dufresne, kmoriwak, petersen, przemek, yamato
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: emacs-common-ddskk-17.1-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-15 08:41:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nick Urbanik 2022-07-21 03:58:33 UTC
Description of problem: emacs fails to start if emacs-ddsdk is installed


Version-Release number of selected component (if applicable):
16.2-12.fc36

How reproducible:
Always

Steps to Reproduce:
1.Install emacs, it runs
2.install emacs-ddsdk
3. Emacs refuses to start, with message, "Cannot open load file: No such file or directory, comp"

Actual results:
Emacs refuses to start, with message, "Cannot open load file: No such file or directory, comp"

Expected results:
emacs runs.

Additional info:
strace shows emacs looking iin so many places other than the right one.

Comment 1 Jon Dufresne 2022-07-21 15:16:26 UTC
I had to also remove emacs-common-ddsdk in addition to emacs-ddsdk to workaround this bug.

Comment 2 Masatake YAMATO 2023-01-06 18:21:44 UTC
I found a slightly better workaround.

  # mv /usr/share/emacs/site-lisp/ddskk/skk-setup.elc /usr/share/emacs/site-lisp/ddskk/skk-setup.elc_

Emacs can start without -Q (and -q), and ddskk from the package still works.


I inspected the issue more.

/usr/share/emacs/site-lisp/ddskk/skk-setup.elc includes 4 S expressions.


;A
(byte-code ...
;B
(defalias 'skk-isearch-setup-maybe ...
;C
(defalias 'skk-isearch-cleanup-maybe ...
;D
(byte-code ...

When I deleted all expressions, emacs -q didn't report the message.
Wenn I deleted all expressions other than A, emacs -q didn't report the message.
When I deleted all expressions other than A and B, emacs -q reported the error.

Comment 3 Jens Petersen 2023-01-07 03:25:06 UTC
*** Bug 2131129 has been marked as a duplicate of this bug. ***

Comment 4 Jens Petersen 2023-01-07 03:26:39 UTC
Thanks Yamato-san

So I think the right thing to do here is just not to compile ddskk-setup.el, ya?

Comment 5 Jens Petersen 2023-01-07 03:27:23 UTC
(We should also really update to newer https://github.com/skk-dev/ddskk/releases)

Comment 6 Jens Petersen 2023-01-07 03:28:50 UTC
(Sorry I meant skk-setup.el of course)

Comment 8 Jens Petersen 2023-01-07 03:34:49 UTC
If people can help to test this, I don't mind to build updates

Comment 9 Masatake YAMATO 2023-01-09 08:15:47 UTC
I'm not sure that removing the elc is the right thing, but it works :-).

Comment 10 Jens Petersen 2023-01-09 08:33:57 UTC
(In reply to Masatake YAMATO from comment #9)
> I'm not sure that removing the elc is the right thing, but it works :-).

Why not?  It was Fedora specific

Comment 11 Masatake YAMATO 2023-01-09 11:11:40 UTC
> Why not?  It was Fedora specific

As far as reading skk-setup.el, 'comp' is not required.
I don't understand why emacs reported 'Cannot open load file: No such file or directory, comp'. I wonder why other elc files don't cause the report.

Comment 12 Masatake YAMATO 2023-03-04 09:39:48 UTC
I installed emacs-ddskk-17.1-1.fc37.noarch. It reproduced the issue well.
After installing I removed /usr/share/emacs/site-lisp/ddskk/skk-setup.elc, the issue was gone; emacs started well.

Comment 13 Ben Cotton 2023-04-25 18:26:48 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.