0.3.61-1 doesn't run on Fedora 23 (0.2.59-1 does)

[David Novak]

I love Sunflower, and have been using 0.2.59-1 for a long time, so decided to upgrade to the latest 0.3.61-1 (Fedora 23, kernel 4.3.5-300). Unfortunately, it fails to start.  No messages, just nothing.  Went back to 0.2.59-1, and all is well.

Are the rpm's for 0.3.61-1 now OK to use?  Wasn't sure after reading your "RPM Love" post.

Thanks for any help or suggestions!

[Mladen Mijatov]

RPM should be ready to build. I did make a mistake and uploaded empty RPM. Can you download again and check just to make sure am not chasing ghosts. 

Other than that, yeah they should be ready and working.

Thanks for kind words though. And there's always a possibility I messed something up. Never made RPMs before :) so I might use you as guinea pig and test.

-- 
Mladen Mijatov

Key ID: 4096R/83EFD5A0 2013-08-18

--
You received this message because you are subscribed to the Google Groups "Sunflower" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sunflower-fm...@googlegroups.com.
To post to this group, send email to sunflo...@googlegroups.com.
Visit this group at https://groups.google.com/group/sunflower-fm.
For more options, visit https://groups.google.com/d/optout.

[David Novak]

I re-downloaded the rpm but it was same size as original, so no surprise that I got the same results.

I did think this time to look at the system log (journalctl) after it failed and found the following:

Feb 11 01:24:35 pcc9395.localdomain org.gnome.Software[1930]: /usr/bin/sunflower: line 3: /usr/share/sunflower/Sunflower.py: Permission denied
Feb 11 01:24:35 pcc9395.localdomain org.gnome.Software[1930]: /usr/bin/sunflower: line 3: exec: /usr/share/sunflower/Sunflower.py: cannot execute: Permission denied

/usr/share/sunflower/Sunflower.py had permissions of 644, so I changed it to 755 and tried again.

Still a no-go, but this showed up in the system log:

Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: Traceback (most recent call last):
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: File "/usr/share/sunflower/application/main.py", line 31, in <module>
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: from gui.main_window import MainWindow
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: File "/usr/share/sunflower/application/gui/main_window.py", line 31, in <module>
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: from plugin_base.item_list import ItemList
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: File "/usr/share/sunflower/application/plugin_base/item_list.py", line 11, in <module>
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: from tools.viewer import Viewer
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: File "/usr/share/sunflower/application/tools/viewer.py", line 2, in <module>
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: import chardet
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: ImportError: No module named chardet
Feb 11 01:29:09 pcc9395.localdomain sunflower.desktop[8473]: Failed running with python2.7

So it looks like module "chardet" is missing.

Hope this helps.

[Mladen Mijatov]

Great debugging I might add. So permissions need to be changed for RPM build process. After that Sunflower is starting but having issues with missing module. Could you search Fedora repositories and see if "chardet" module is anywhere to be found. On Debian I have it installed from "python-chardet" but I think I might drop the whole module as it's used only on file viewer. Another dependency is not good although it should have been listed in RPM. :/ So that's another issue.

Also, can I ask you to create issue on GitHub?

https://github.com/MeanEYE/Sunflower/issues

Thanks!

-- 
Mladen Mijatov

Key ID: 4096R/83EFD5A0 2013-08-18

[David Novak]

python-chardet is in the "fedora" repo.  After I dnf installed it (and made Sunflower.py executable), everything is running OK.

I opened issue #193 on GitHub.  Let me know if you get the RPM fixed, and I'll try it again.

[Christian Mallwitz]

I believe I requested chardet to be added to viewer to be able to view
files with unhandled character encodings - should I take a look to
make the import optional? Or is there a better option? I don't think
just removing it is a good solution...

Cheers
Christian

[Mladen Mijatov]

Well, ideally we'd need a standardized way of detecting character encoding without requiring extra module. If that is possible then it's an ideal solution. Otherwise we just require a module. In general it was my mistake not to include requirements in RPM files.

We can always make it optional, but I don't like that idea too much.

-- 
Mladen Mijatov

Key ID: 4096R/83EFD5A0 2013-08-18