Bug 26998 - Bluegriffon fails to launch: usr/lib64/bluegriffon/libxul.so No such file or directory. Also, is M7 package
Summary: Bluegriffon fails to launch: usr/lib64/bluegriffon/libxul.so No such file or ...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Stig-Ørjan Smelror
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-24 18:15 CEST by William Kenney
Modified: 2023-01-23 19:42 CET (History)
2 users (show)

See Also:
Source RPM: bluegriffon
CVE:
Status comment:


Attachments

Description William Kenney 2020-07-24 18:15:01 CEST
Description of problem:


Use:
Mageia-8-beta1-Live-Plasma-x86_64.iso
8cea7b657a1bfee91b7fb709dcebfdfc

No need to install it.
Set up the repos and using the MCC install Bluegriffon.
Open a terminal
[wilcal@localhost ~]$ bluegriffon
XPCOMGlueLoad error for file /usr/lib64/bluegriffon/libxul.so:
libstartup-notification-1.so.0: cannot open shared object file: No such file or directory
Couldn't load XPCOM.

I've run this test 2-days in a row so the fault does not appear to be a repo update issue.
Comment 1 Lewis Smith 2020-07-25 10:41:20 CEST
Thank you Bill for the report.

None-the-less (on an up-to-date M8 system):
 $ urpmf /usr/lib64/bluegriffon/libxul.so
 bluegriffon:/usr/lib64/bluegriffon/libxul.so
and
 $ urpmq -l bluegriffon | grep libxul
 /usr/lib64/bluegriffon/libxul.so
shows it is included.

I have just installed it to try: bluegriffon-3.1-5.mga7
 $ ls -l /usr/lib64/bluegriffon/libxul.so
 -rwxr-xr-x 1 root root 85659832 Mai  16  2019 /usr/lib64/bluegriffon/libxul.so*
Running under Cinnamon, it *does* work both from the Development sub-menu, and command line - no console errors at all.

Over to you, Bill. Look for the missing file. Try UNinstalling then re-installing it.

Summary: Bluegriffon fails to launch => Bluegriffon fails to launch: usr/lib64/bluegriffon/libxul.so No such file or directory
Ever confirmed: 1 => 0
Status: NEW => UNCONFIRMED
CC: (none) => lewyssmith

Comment 2 Lewis Smith 2020-07-25 10:57:44 CEST
I thought I was going mad - running M7 above? Re-booted definitely to M8:
 $ cat /etc/release
 Mageia release 8 (Cauldron) for x86_64
so I was in the right place, and the rest was true. But notice the wrong release:
 $ rpm -q bluegriffon
 bluegriffon-3.1-5.mga7
and
 $ rpm -qa | grep mga7
 filesystem-2.1.9-30.mga7
 bluegriffon-3.1-5.mga7
 lib64dmapsharing3.0_2-2.9.39-2.mga7

Assigning to Stig as registered Bluegriffon maintainer. Can you possibly correct the other two things also? Will raise a separate bug if you prefer.

Assignee: bugsquad => smelror
Summary: Bluegriffon fails to launch: usr/lib64/bluegriffon/libxul.so No such file or directory => Bluegriffon fails to launch: usr/lib64/bluegriffon/libxul.so No such file or directory. Also, is M7 package

Comment 3 William Kenney 2020-07-25 14:48:39 CEST
(In reply to Lewis Smith from comment #2)
> I thought I was going mad - running M7 above? Re-booted definitely to M8:
>  $ cat /etc/release
>  Mageia release 8 (Cauldron) for x86_64
> so I was in the right place, and the rest was true. But notice the wrong
> release:
>  $ rpm -q bluegriffon
>  bluegriffon-3.1-5.mga7
> and
>  $ rpm -qa | grep mga7
>  filesystem-2.1.9-30.mga7
>  bluegriffon-3.1-5.mga7
>  lib64dmapsharing3.0_2-2.9.39-2.mga7
> 
> Assigning to Stig as registered Bluegriffon maintainer. Can you possibly
> correct the other two things also? Will raise a separate bug if you prefer.

Do what you need to do
Comment 4 Maurice Batey 2020-08-04 16:50:36 CEST
Have just had same problem with 64-bit Plasma Mageia-8-beta1 fresh install on a Thinkpad.

Surprisingly: 

   $ rpm -q bluegriffon
   bluegriffon-3.1-5.mga7

CC: (none) => maurice

Comment 5 sturmvogel 2023-01-23 19:42:39 CET
Bluegriffon was removed from Mageia 23 month ago...

Closing OLD.

Resolution: (none) => OLD
Status: UNCONFIRMED => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.