Page 5 of 15
ld.so.conf fix
Posted: 30 Jan 2017, 19:20
by lolololo
This not a "bug" but can create one
Both in porteus 3.2.1 and 3.2.2 the file "ld.so.conf" has a line pointing to...
/usr/i486-slackware-linux/lib
should be
/usr/i586-slackware-linux/lib
slackware 14.2 use i586 not i486
bye
Re: Porteus-v3.2.2 bug reports here
Posted: 31 Jan 2017, 05:09
by Ed_P
update-pepperflash is not showing the update version USM is.
viewtopic.php?f=48&t=6614&p=52659#p52656
Re: Porteus-v3.2.2 bug reports here
Posted: 31 Jan 2017, 10:07
by donald
XFCE-4.9.0-porteus i686
Bug?
The /home/guest/.cache/ folder collects "keyring-*" folders
shouldn't they been overwritten / replaced?
Re: Porteus-v3.2.2 bug reports here
Posted: 01 Feb 2017, 17:39
by Blaze
Trouble with PPTP connection (connection via cable - is not through a router) in Porteus 3.2.2
Code: Select all
/usr/sbin/pppd: pppd is unable to open the /dev/ppp device.
You need to create the /dev/ppp device node by
executing the following command as root:
mknod /dev/ppp c 108 0
and PPTP with Static IP has the same story.
This command
has fixed this issue.
Probably, Porteus does not load the ppp kernel module?
More info
http://www.ru.j-npcs.org/usoft/WWW/HOWT ... WTO-6.html
BTW, not confirmed, but probably we have the same problem with PPPoE connection (connection via cable - is not through a router) in Porteus 3.2.2.
Bug report from
this post (Russian topic)
All credits to
Roader
Re: Porteus-v3.2.2 bug reports here
Posted: 03 Feb 2017, 22:44
by francois
I did not read all about this 3.2.2 thread. Sorry if this a known bug.
I boot into kde5 there is no wallpaper (black screen) and no panel menu. The right click menu appears. I can run command and from there start some application.
From this same contextual menu, I try to add another panel menu. It does not work.
No panel at all.
Thanks.
Re: Porteus-v3.2.2 bug reports here
Posted: 04 Feb 2017, 01:35
by Bogomips
Been running kde5 (32 bit) solid since new year, not come across this. Got all sorts of things also somewhat like this, before tuning kde5. Normally landing in such situation by killing X, and then doing init 4.
Re: Porteus-v3.2.2 bug reports here
Posted: 04 Feb 2017, 16:11
by francois
@bogomips:
Thanks for your proposition. However:
would not provide any changes. There is still is no panel.
Everything was fine for me under 3.2.1 under every desktop environment.
Since 3.2.2, I have to use the
acpi=no cheatcode to run porteus, otherwise the os will not even boot. With that syntax xfce DE will work perfectly. At least as I can see yet. But this not the case of kde5 plasma as stated in the above post of mine.
Here is my lspci output, if it could be of any help. I have a toshiba satellite z930:
Code: Select all
root@porteus:/home/guest# lspci
00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller
00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller
00:19.0 Ethernet controller: Intel Corporation 82579V Gigabit Network Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Control
00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Contr
00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev
00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 3 (rev
00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Control
00:1f.0 ISA bridge: Intel Corporation HM76 Express Chipset LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (
01:00.0 System peripheral: Ricoh Co Ltd PCIe SDXC/MMC Host Controller (rev 07)
02:00.0 Network controller: Intel Corporation Centrino Wireless-N 2230 (rev c4)
root@porteus:/home/guest#
There is no similar issue on the net about that type of problem.
http://superuser.com/questions/946206/k ... k-desktopI
not a solution.
https://bbs.archlinux.org/viewtopic.php?id=210439
Would someone with the 3.2.2 kde environment try the acpi=no cheatcode, just to see if this is the issue?
Thanks.
Re: Porteus-v3.2.2 bug reports here
Posted: 05 Feb 2017, 11:07
by movobojo
Hello, not bug, but text mistake: In "XFCE" go to "Menu > System > Create Porteus live USB" and now you can see twice "Pertition" instead of "Partition".
Re: Porteus-v3.2.2 bug reports here
Posted: 05 Feb 2017, 17:33
by neko
@movobojo
Thank you for your point out.
It is my mistake.
My poor English skill produced the spell miss.
======================================
source files: /usr/share/live-usb/bin/live-usb, /usr/share/live-usb/src/live-usb.po
package: live-usb-3.1-noarch-7
module: 002-xorg
---------------------------------------------------------------
live-usb: line 73
FP_SIZE=`gettext live-usb "1st Pertition size(MB)"`
---->
FP_SIZE=`gettext live-usb "1st Partition size(MB)"`
live-usb: line 74
SP_FS=`gettext live-usb "2nd Pertition File System"`
---->
SP_FS=`gettext live-usb "2nd Partition File System"`
live-usb.po: line 30
msgid "1st Pertition size(MB)"
---->
msgid "1st Partition size(MB)"
live-usb.po: line 33
msgid "2nd Pertition File System"
---->
msgid "2nd Partition File System"
======================================
If you edited your own language "live-usb.po", it must be corrected coresponding lines.
And "live-usb.mo" must be converted from the corrected "live-usb.po" with "msgfmt" command too.
I am sorry.
Re: Porteus-v3.2.2 bug reports here
Posted: 07 Feb 2017, 15:55
by Seq_Res
hi,
The current v3.2.2 XFCE seems not stable in my laptop.Sometimes work well, but give a lot of error messages which can only be seen when shutting down; then at next boot
the display resolution will not be correct (default 1024*768, instead of the NORMAL 1366*768), and cannot be adjusted; also, mouse response become very slow. Can someone tell me the reason and how to get around this problem? thanks!
I use several modules since v2.1, ie, audacity, gimp2.8.6, code::blocks12.11, etc; do these modules conflict with the current version of porteus ?
Re: Porteus-v3.2.2 bug reports here
Posted: 07 Feb 2017, 16:48
by Bogomips
Code: Select all
oot@porteus:/home/guest# usm -s gimp
gimp-2.8.16-i586-1.txz was found in slackware [not installed]
gimp-2.8.18-i586-1_slack14.2.txz was found in slackwarepatches [not installed]
gimp now 2.8.16. If using here same modules as for 2.1 could have old dependencies, which are no longer being satisfied. Need a gimp with 14.2 dependencies IMHO.
Re: Porteus-v3.2.2 bug reports here
Posted: 08 Feb 2017, 19:17
by Blaze
Hi
brokenman.
XFCE x86_64
1) I have done a new module with right click actions for XFCE -
Download uca-xfce-actions-by-blaze.xzm
Please, replace uca.xml in the 003-xfce4.xzm (for /home/guest and /root - you can get it from my module)
My $HOME/.config/Thunar/uca.xml
Code: Select all
<?xml encoding="UTF-8" version="1.0"?>
<actions>
<action>
<icon>folder</icon>
<name>Open Folder as root</name>
<name xml:lang="ru">Открыть каталог с правами root</name>
<unique-id>1406920422374556-1</unique-id>
<command>gksu Thunar %F</command>
<description>Open Folder as root</description>
<description xml:lang="ru">Открыть текущий каталог в Thunar с правами root</description>
<patterns>*</patterns>
<startup-notify/>
<directories/>
</action>
<action>
<icon>utilities-terminal</icon>
<name>Open Terminal Here</name>
<name xml:lang="ru">Открыть терминал в текущем каталоге</name>
<unique-id>1406920422374566-2</unique-id>
<command>exo-open --working-directory %f --launch TerminalEmulator</command>
<description>Open Terminal Here</description>
<description xml:lang="ru">Открыть терминал в текущем каталоге</description>
<patterns>*</patterns>
<startup-notify/>
<directories/>
</action>
<action>
<icon>cdr</icon>
<name>Extract module</name>
<name xml:lang="ru">Распаковать модуль</name>
<unique-id>1406927163866770-3</unique-id>
<command>/opt/porteus-scripts/context-menu/extract-module %F</command>
<description>Extract porteus module</description>
<description xml:lang="ru">Распаковать модуль Porteus</description>
<patterns>*.xzm</patterns>
<other-files/>
</action>
<action>
<icon>cdr</icon>
<name>Create module</name>
<name xml:lang="ru">Создать модуль</name>
<unique-id>1406927334521790-4</unique-id>
<command>/opt/porteus-scripts/context-menu/create-module %f</command>
<description>Create a porteus module from a folder</description>
<description xml:lang="ru">Создать из папки модуль для Porteus</description>
<patterns>*</patterns>
<directories/>
</action>
<action>
<icon>deb</icon>
<name>deb2xzm</name>
<name xml:lang="ru">Конвертировать deb в xzm модуль</name>
<unique-id>1406927432353616-5</unique-id>
<command>/opt/porteus-scripts/context-menu/convert_deb %f</command>
<description>Convert a debian archive to a porteus module</description>
<description xml:lang="ru">Конвертировать deb архив в модуль Porteus</description>
<patterns>*.deb</patterns>
<other-files/>
</action>
<action>
<icon>rpm</icon>
<name>rpm2xzm</name>
<name xml:lang="ru">Конвертировать rpm в xzm модуль</name>
<unique-id>1406927432353716-6</unique-id>
<command>/opt/porteus-scripts/context-menu/convert_rpm %f</command>
<description>Convert a rpm archive to a porteus module</description>
<description xml:lang="ru">Конвертировать rpm архив в модуль Porteus</description>
<patterns>*.rpm</patterns>
<other-files/>
</action>
<action>
<icon>usmslackware</icon>
<name>txz2xzm</name>
<name xml:lang="ru">Конвертировать txz/tgz в xzm модуль</name>
<unique-id>1406927847266624-7</unique-id>
<command>/opt/porteus-scripts/context-menu/convert_txz %F</command>
<description>Convert slackware package to porteus module</description>
<description xml:lang="ru">Конвертировать пакет Slackware в модуль Porteus</description>
<patterns>*.txz;*.tgz</patterns>
<other-files/>
</action>
<action>
<icon>usmslackware</icon>
<name>Install Slackware package</name>
<name xml:lang="ru">Установить пакет Slackware</name>
<unique-id>1406927831728030-8</unique-id>
<command>/opt/porteus-scripts/context-menu/install-slack %F</command>
<description>Install slackware package</description>
<description xml:lang="ru">Установить пакет Slackware</description>
<patterns>*.txz;*.tgz</patterns>
<other-files/>
</action>
<action>
<icon>media-cdr</icon>
<name>Mount ISO</name>
<name xml:lang="ru">Смонтировать образ ISO</name>
<unique-id>1406927813307622-9</unique-id>
<command>/usr/libexec/gvfsd-archive file=%f</command>
<description>Mount an ISO file</description>
<description xml:lang="ru">Смонтировать образ ISO</description>
<patterns>*.iso;*.ISO</patterns>
<other-files/>
</action>
<action>
<icon>cdr</icon>
<name>Mount module</name>
<name xml:lang="ru">Смонтировать модуль в /mnt/loop</name>
<unique-id>1406927895129246-10</unique-id>
<command>/opt/porteus-scripts/context-menu/mount-module %f</command>
<description>Mount module read only</description>
<description xml:lang="ru">Смонтировать модуль в /mnt/loop в режиме только для чтения</description>
<patterns>*.xzm</patterns>
<other-files/>
</action>
<action>
<icon>cdr</icon>
<name>Umount module</name>
<name xml:lang="ru">Размонтировтаь модуль из /mnt/loop</name>
<unique-id>1406927895128346-11</unique-id>
<command>/opt/porteus-scripts/context-menu/unmount-module %f</command>
<description>Umount module mounted at /mnt/loop</description>
<description xml:lang="ru">Размонтировать модуль, смонтированный в /mnt/loop</description>
<patterns>*.xzm</patterns>
<other-files/>
</action>
<action>
<icon>usmslackware</icon>
<name>Unistall Slackware package</name>
<name xml:lang="ru">Деинсталлировать пакет Slackware</name>
<unique-id>1406927953138467-12</unique-id>
<command>/opt/porteus-scripts/context-menu/remove-slack %f</command>
<description>Uninstall slackware package</description>
<description xml:lang="ru">Деинсталлировать пакет Slackware</description>
<patterns>*.txz;*.tgz</patterns>
<other-files/>
</action>
<action>
<icon>package-x-generic</icon>
<name>Extract here</name>
<name xml:lang="ru">Распаковать здесь</name>
<unique-id>1406927955138667-13</unique-id>
<command>engrampa --extract-here %F</command>
<description>Extract here</description>
<description xml:lang="ru">Распаковать здесь</description>
<patterns>*.7z;*.zip;*.ZIP;*.rar;*.RAR;*.iso;*.ISO;*.r0*;*.R0*;*.*01;*.tar;*.TAR;*.gz;*.GZ;*.tar.bz2;*.TAR.BZ2;*.gzip;*.GZIP;*tar.gz;*TAR.GZ;*tar.xz;*TAR.XZ;*tar.lz;*TAR.LZ;*.tgz</patterns>
<directories/>
<audio-files/>
<image-files/>
<other-files/>
<text-files/>
<video-files/>
</action>
<action>
<icon>package-x-generic</icon>
<name>Compress...</name>
<name xml:lang="ru">Сжать...</name>
<unique-id>1406927957138869-14</unique-id>
<command>engrampa --add %F</command>
<description>Add to archive</description>
<description xml:lang="ru">Добавить в архив</description>
<patterns>*</patterns>
<directories/>
<audio-files/>
<image-files/>
<other-files/>
<text-files/>
<video-files/>
</action>
</actions>
2) In Menu>Settings Manager>Keyboard>Application Shortcuts - we are have some missing keyboard shortcuts (hotkeys).
For example Ctrl+Alt+T for opening a terminal (xfce4-terminal) window.
The configured keyboard shortcuts are stored in : ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml
And the system default : /etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml
For 003-xfce4.xzm. Open
/003-xfce4/home/guest/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml
/003-xfce4/root/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml
/003-xfce4/etc/xdg/xfce4/xfconf/xfce-perchannel-xml/xfce4-keyboard-shortcuts.xml
find
Code: Select all
<property name="Print" type="string" value="xfce4-screenshooter"/>
add after
Code: Select all
<property name="<Primary><Alt>t" type="string" value="xfce4-terminal"/>
BTW, I not able to set a hotkeys Ctrl+Alt+Print Screen with the command xfce4-screenshooter -w for get active windows screenshot (for XFCE it's not critical, because all ok with Print Screen - you have a good choice in this window).
3) I think that 7zip-GUI (/usr/bin/7zFM and probably others 7zip GUI apps too) must been removed (action for a right click for 7zip of context menu too)
"no need for the 7z-GUI", but the CLI version of 7-Zip is need as air and water.
More info look at this topic
4) If press Start and click on a green icon with profile, I recive this message about absent
mugshot
Regards,
Blaze
Re: Porteus-v3.2.2 bug reports here
Posted: 09 Feb 2017, 19:08
by Blaze
XFCE x86_64
1) In XFCE -
gksu.mo and
libgksu.mo for Russian localization is absent at /usr/share/locale/ru/LC_MESSAGES
Code: Select all
guest@porteus:~$ find /var/log/packages -name *gksu*
/var/log/packages/gksu-2.0.2-x86_64-1jay
/var/log/packages/libgksu-2.0.12-x86_64-2jay
guest@porteus:~$ find /usr/share/locale/ru/LC_MESSAGES -name *gksu*
guest@porteus:~$
In the source
https://slackbuilds.org/repository/14.2/system/gksu/
Code: Select all
guest@porteus:~$ ls /home/guest/Загрузки/gksu-2.0.2/po/
ChangeLog ar.po de.po hu.po lt.po pt.po sk.po zh_CN.po
Makefile.in.in ca.po es.po it.po nb.po pt_BR.po sv.po
Makevars cs.po fr.po ja.po nl.po ro.po th.po
POTFILES.in da.po gl.po ko.po pl.po ru.po xh.po
guest@porteus:~$ ls /home/guest/Загрузки/libgksu-2.0.12/po/
ChangeLog ca.po es.po it.po nl.po ru.po zh_CN.po
Makefile.in.in cs.po eu.po ko.po pl.po sk.po
Makevars da.po fr.po lt.po pt_BR.po sv.po*
POTFILES.in de.po hu.po nb.po ro.po th.po
guest@porteus:~$
localization for
gksu.mo and
libgksu.mo are present.
Code: Select all
Fix:: Recompiled libgksu and gksu to include locales
2) About a new localization for
pfilesearch
Code: Select all
su
toor
wget http://smokey01.com/zigbert/pfilesearch_NLS.pet
mv pfilesearch_NLS.pet pfilesearch_NLS.tar.gz
gunzip pfilesearch_NLS.tar.gz
tar xf pfilesearch_NLS.tar
cd pfilesearch_NLS
rm pet.specs
# here is your steps, for example:
# cp /home/guest/Загрузки/pfilesearch_NLS/usr/share/locale/de/LC_MESSAGES/pfilesearch.mo /de-localization-module/usr/share/locale/de/LC_MESSAGES/
# cp /home/guest/Загрузки/pfilesearch_NLS/usr/share/locale/fr/LC_MESSAGES/pfilesearch.mo /fr-localization-module/usr/share/locale/fr/LC_MESSAGES/
# cp /home/guest/Загрузки/pfilesearch_NLS/usr/share/locale/it/LC_MESSAGES/pfilesearch.mo /it-localization-module/usr/share/locale/it/LC_MESSAGES/
# cp /home/guest/Загрузки/pfilesearch_NLS/usr/share/locale/pl/LC_MESSAGES/pfilesearch.mo /pl-localization-module/usr/share/locale/pl/LC_MESSAGES/
# cp /home/guest/Загрузки/pfilesearch_NLS/usr/share/locale/ru/LC_MESSAGES/pfilesearch.mo /ru-localization-module/usr/share/locale/ru/LC_MESSAGES/
Code: Select all
tree /home/guest/Загрузки/pfilesearch_NLS/
/home/guest/Загрузки/pfilesearch_NLS/
└── usr
└── share
└── locale
├── de
│ └── LC_MESSAGES
│ └── pfilesearch.mo
├── fr
│ └── LC_MESSAGES
│ └── pfilesearch.mo
├── it
│ └── LC_MESSAGES
│ └── pfilesearch.mo
├── pl
│ └── LC_MESSAGES
│ └── pfilesearch.mo
└── ru
└── LC_MESSAGES
└── pfilesearch.mo
13 directories, 5 files
3) About mugshot error look at my post above - item
4)
https://launchpad.net/mugshot/+download
https://github.com/Papitux/SlackStuff/t ... er/mugshot
I think you can build this package for Slackware.
Code: Select all
usm -g python3 -nodep
usm -g python-distutils-extra
I stuck on the
Code: Select all
mugshot-0.3.2/po/pt_BR.po
mugshot-0.3.2/po/sk.po
mugshot-0.3.2/po/is.po
mugshot-0.3.2/COPYING
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- a/mugshot/MugshotWindow.py
|+++ b/mugshot/MugshotWindow.py
--------------------------
patching file mugshot/MugshotWindow.py
Using Plan A...
Hunk #1 succeeded at 612 (offset -20 lines).
done
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--------------------------
|--- a/mugshot/MugshotWindow.py
|+++ b/mugshot/MugshotWindow.py
--------------------------
patching file mugshot/MugshotWindow.py
Using Plan A...
Hunk #1 succeeded at 678 (offset 3 lines).
Hunk #2 succeeded at 692 (offset 3 lines).
done
To build mugshot you need https://launchpad.net/python-distutils-extra
root@porteus:/home/guest/Загрузки#
Re: Porteus-v3.2.2 bug reports here
Posted: 15 Feb 2017, 05:36
by Falcony
Porteus-v3.2.2 bug - on all images
initrd fall to FATAL PANIC
Code: Select all
Kernel panic - not syncing: Attempted to kill the idle task!
This happens on old PCs and some notebook produced 2005-2008.
This happens on first init stage before DEBUG option enable.
On new PC/notebook it is not happened
On v. 3.2.1 v it is not happened.
As it happens on first satge of booting - not possible to show logs
Some kernel 4.9 bug?
Re: Porteus-v3.2.2 bug reports here
Posted: 15 Feb 2017, 15:52
by Blaze
Hi
Falcony.
Use this cheat code
More info
look at this topic