New features which should be implemented in Porteus; suggestions are welcome. All questions or problems with testing releases (alpha, beta, or rc) should go in their relevant thread here, rather than the Bug Reports section.
Traceback (most recent call last):
File "/usr/share/system-config-printer/system-config-printer.py", line 31, in <module>
File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module>
from gtk import _gtk
ImportError: No module named cairo
I just checked my tree. I think someone asked for cups to be added to all desktops as it is currently in my tree for all desktops. Please remove it from the printing module and I will turn on executable bit in 003 modules. I have removed cups from the latest printing module so no need to do anything further. Sorry for the confusion.
How do i become super user?
Wear your underpants on the outside and put on a cape.
Please remove it from the printing module and I will turn on executable bit in 003 modules. I have removed cups from the latest printing module so no need to do anything further.
What I need to do with printing module or you upload your version of printing module for us? Thanks.
What about remove cups from environments (003 modules) that don't have dependence in cups.
In environments (003 modules) who require cups, for example Cinnamon and KDE5, need to remove rc.cups from /etc/rc.d/
and stay with cups and executable rc.cups in printing modules.
If I don't have printer - executable rc.cups is not needed for me at boot up of Porteus. It takes time...
/usr/bin/system-config-printer: /usr/share/system-config-printer/system-config-printer.py: /usr/bin/python: bad interpreter: No such file or directory
/usr/bin/system-config-printer: line 3: /usr/share/system-config-printer/system-config-printer.py: Success
guest@porteus:~$ cd /var/log/packages
There is no python-2.7.11-x86_64-2.txz. Fulalas will have to add python-2.7.11-x86_64-2.txz it to its lxqt module. There is no need for tlc and tk packages.
IMO I think for all the various DEs with their unique package installs that a base functional print module with a separate support print module to satisfy one or more DEs approach would work. For example 07-printing-x86_64-02.12.2016.xzm works for Cinnamon as is but may not work for the KDE DE. For the KDE DE system it would need a 07-KDE-printing-x86_64-02.12.2016.xzm module in additon to the 07-printing-x86_64-02.12.2016.xzm to work.
I would also think that if CUPS is only needed for printing it only be a part of the 07-printing module.
I don't like the idea to put a lot of libs inside a generic module 'just in case'. In my opinion it would be smarter to put python inside printing module once is this module that's missing python, not LXQt and stuff that comes with it, right?
But maybe in this specific case it's just a matter of putting these two files inside /usr/lib64:
libpython2.7.so (symlink pointing to the lib below)
libpython2.7.so.1.0 (real lib)
brokenman wrote:I just checked my tree. I think someone asked for cups to be added to all desktops as it is currently in my tree for all desktops. Please remove it from the printing module and I will turn on executable bit in 003 modules. I have removed cups from the latest printing module so no need to do anything further. Sorry for the confusion.
It seems that brokenman has taken care of the printing module after this last statement. If the libpython2.7.so.1.0 is sufficient to do the job on your lxqt module, then this is perfect. I will have a look at it.
Cups is necessary for system-config-printer to work. Cups is needed on kde5.
Cups is necessary for system-config-printer to work.
I understand that and it is why I think it should be a part of the print module rather than the ISO. If it is going to be a part of the ISO, all ISOs, then having it in the print module is duplicate space. But I don't think it is duplicate RAM since I would think the code in one would overlay the code in the other when mounted.