Bugzilla – Bug 1214643
Freshly installed Nyxt fails to launch
Last modified: 2023-09-04 16:20:43 UTC
Hello, I just installed Nyxt for the first time. Though it fails to launch :-( $ nyxt Unhandled SIMPLE-ERROR in thread #<SB-THREAD:THREAD tid=25973 "main thread" RUNNING {10057E0003}>: Error opening shared object "libfixposix.so.4": libfixposix.so.4: cannot open shared object file: No such file or directory. Backtrace for: #<SB-THREAD:THREAD tid=25973 "main thread" RUNNING {10057E0003}> 0: (SB-DEBUG::DEBUGGER-DISABLED-HOOK #<SIMPLE-ERROR "Error opening ~:[runtime~;shared object ~:*~S~]: ~A." {10057A8253}> #<unused argument> :QUIT T) 1: (SB-DEBUG::RUN-HOOK *INVOKE-DEBUGGER-HOOK* #<SIMPLE-ERROR "Error opening ~:[runtime~;shared object ~:*~S~]: ~A." {10057A8253}>) 2: (INVOKE-DEBUGGER #<SIMPLE-ERROR "Error opening ~:[runtime~;shared object ~:*~S~]: ~A." {10057A8253}>) 3: (ERROR "Error opening ~:[runtime~;shared object ~:*~S~]: ~A." "libfixposix.so.4" "libfixposix.so.4: cannot open shared object file: No such file or directory") 4: (SB-SYS:DLOPEN-OR-LOSE #S(SB-ALIEN::SHARED-OBJECT :PATHNAME #P"libfixposix.so.4" :NAMESTRING "libfixposix.so.4" :HANDLE NIL :DONT-SAVE NIL)) 5: (SB-ALIEN::TRY-REOPEN-SHARED-OBJECT #S(SB-ALIEN::SHARED-OBJECT :PATHNAME #P"libfixposix.so.4" :NAMESTRING "libfixposix.so.4" :HANDLE NIL :DONT-SAVE NIL)) 6: (SB-SYS:REOPEN-SHARED-OBJECTS) 7: (SB-IMPL::FOREIGN-REINIT) 8: (SB-IMPL::REINIT T) 9: ((FLET SB-UNIX::BODY :IN SB-IMPL::START-LISP)) 10: ((FLET "WITHOUT-INTERRUPTS-BODY-3" :IN SB-IMPL::START-LISP)) 11: (SB-IMPL::%START-LISP) unhandled condition in --disable-debugger mode, quitting -------------------------------------------------------------------------------- Some information about my machine: $ uname -a Linux rostam 6.4.11-1-default #1 SMP PREEMPT_DYNAMIC Thu Aug 17 04:57:43 UTC 2023 (2a5b3f6) x86_64 x86_64 x86_64 GNU/Linu $ cat /usr/lib/os-release | grep -E '^(NAME|VERSION_ID)' NAME="openSUSE Tumbleweed" VERSION_ID="20230823" $ rpm -q nyxt nyxt-3.6.0-1.1.x86_64 $ ldd $(which nyxt) linux-vdso.so.1 (0x00007ffe6373a000) libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f98e42e2000) libm.so.6 => /lib64/libm.so.6 (0x00007f98e41fb000) libc.so.6 => /lib64/libc.so.6 (0x00007f98e3e00000) /lib64/ld-linux-x86-64.so.2 (0x00007f98e43b6000) -------------------------------------------------------------------------------- Let me know if I missed any bit of detail. Thanks,
Thanks, the package is buggy and missing dependencies. I have submitted an updated fixed package which will be available in a few days, but in the meantime you can manually fix it with: zypper in libfixposix4 You might also need: zypper in libwebkit2gtk-4_1-0
(In reply to Michael Pujos from comment #1) > Thanks, the package is buggy and missing dependencies. > > I have submitted an updated fixed package which will be available in a few > days, but in the meantime you can manually fix it with: > > zypper in libfixposix4 It works \o/ That was all I needed. Thanks! PS: Say I'm not new to RPM packaging and wanted to submit a patch to update the spec in a similar scenario. What would be a good place/doc to start w/?
You'd need to familiarize with OBS (Open Build Service, hosted on https://build.opensuse.org/) where the distros and packages are maintained and built, the web site, its terminology and its command-line tool osc (in package osc). There are various documentations about it. The workflow for making a modification to an existing package: - branch the package to your home OBS repo from its devel OBS project - checkout the package files on your machine - make modifications - build package locally to test that they work - submit modifications to your home repo - submit your modifications upstream to the devel project
(In reply to Michael Pujos from comment #3) > You'd need to familiarize with OBS (Open Build Service, hosted on > https://build.opensuse.org/) where the distros and packages are maintained > and built, the web site, its terminology and its command-line tool osc (in > package osc). There are various documentations about it. > > The workflow for making a modification to an existing package: > > - branch the package to your home OBS repo from its devel OBS project > - checkout the package files on your machine > - make modifications > - build package locally to test that they work > - submit modifications to your home repo > - submit your modifications upstream to the devel project Thanks. I'll definitely give it a shot. I could try to help you & submit patches for this particular package if you don't mind.
Fixed in v3.6.1