Porteus-v5.0x86_64_bugs reports
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Porteus-v5.0x86_64_bugs reports
^
for now just try a different mirror (but not http://ftp.nluug.nl/os/Linux/distr/porteus since that lacks the updates ) - better a slightly slower download than a broken and useless one, yes?
for now just try a different mirror (but not http://ftp.nluug.nl/os/Linux/distr/porteus since that lacks the updates ) - better a slightly slower download than a broken and useless one, yes?
Cheers!
Yours Rava
Yours Rava
- ncmprhnsbl
- DEV Team
- Posts: 3941
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-v5.0x86_64_bugs reports
actually, this time it's not a mirror issue, but my bad, i apparently messed up with that particular md5sum. a fix is in the works...
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Porteus-v5.0x86_64_bugs reports
Does that mean the two files are downloaded - one is not okay?ncmprhnsbl wrote: ↑20 Sep 2022, 10:16i apparently messed up with that particular md5sum. a fix is in the works...
Or are both okay and only the server md5sum file is wrong?
Cheers!
Yours Rava
Yours Rava
- ncmprhnsbl
- DEV Team
- Posts: 3941
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-v5.0x86_64_bugs reports
both okay and only the server md5sum file was wrong.
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Porteus-v5.0x86_64_bugs reports
It would have been too much of an coincidence if I got a corrupted module but still both worked well for me for many weeks now.
Anyhow, any idea why the server I choose (because fastest-mirror told me its the fastest) http://ftp.nluug.nl/os/Linux/distr/porteus did have the relatively new yt-dlp module… but not the two updated 001-core.xzm and 002-xorg.xzm modules?
Is it something the server admins of ftp.nluug.nl should be told about?
Cheers!
Yours Rava
Yours Rava
Porteus-v5.0x86_64_bugs reports
Savefile Manager brings up empty config file
[UPDATE} This problem does not happen with the original 001 etc modules. It appears to be a problem with the latest updates that it is showing up.
Just noticed this with XFCE (haven't tested the others for this yet). If using the savefile manager gui, at the end of the process to edit the config file, instead of bringing up the config file, it just brings up an empty file with root access.
That might be confusing. Normally I do my editing with vi and a terminal, but the gui process used to bring up the file itself for the user to edit. Now it is just a blank empty one.
The quick solution is to bail out of the savefile manager when it asks you to edit the config file, and go to the Porteus Settings Centre to do it, which *does* bring up the proper config file to edit.
I could see this empty file being confusing for new users who don't know where the config file lives.
Anyone else see this?
[Update] does not happen with the original xzm core etc. Only seems to be with the 20220723 updates...
[UPDATE} This problem does not happen with the original 001 etc modules. It appears to be a problem with the latest updates that it is showing up.
Just noticed this with XFCE (haven't tested the others for this yet). If using the savefile manager gui, at the end of the process to edit the config file, instead of bringing up the config file, it just brings up an empty file with root access.
That might be confusing. Normally I do my editing with vi and a terminal, but the gui process used to bring up the file itself for the user to edit. Now it is just a blank empty one.
The quick solution is to bail out of the savefile manager when it asks you to edit the config file, and go to the Porteus Settings Centre to do it, which *does* bring up the proper config file to edit.
I could see this empty file being confusing for new users who don't know where the config file lives.
Anyone else see this?
[Update] does not happen with the original xzm core etc. Only seems to be with the 20220723 updates...
That's a UNIX book - cool. -Garth
- ncmprhnsbl
- DEV Team
- Posts: 3941
- Joined: 20 Mar 2012, 03:42
- Distribution: v5.0-64bit
- Location: australia
- Contact:
Porteus-v5.0x86_64_bugs reports
yes, in this update, i reverted to the old gtkdialog version(with some tweaks) and it doesn't pick up the environment variable for the boot device.. should be able to fix this and push it in the next update..
while i'm here: bug reported via irc: the magic folders gui doesn't function due to incomplete code .. also should be fixed in the next update. (probly, i'll just clean up the old gtkdialog version for now)
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Porteus-v5.0x86_64_bugs reports
System Port 5.0 XFCE
Cave! the XFCE info is misleading. XFCE is in fact 003-xfce-4.12-20220725
I presume this is not what should happen (as seen after a fresh boot due to yet another crash during suspend):I presume it was a rare occasion with my network at the time that created the situation:
I was on a open WLAN, and at times my machine is technically still connected to that WLAN, but anything HTTPS, SMTP or IMAP is not working (giving different kinds of error messages) since I need to reaffirm my approval to its terms & conditions.
The only page that works with https is the one by the provider of that WLAN for loading its terms & conditions approval page.
Code: Select all
root@porteus:~# cat /etc/porteus/*
001-core.xzm:20220723
002-xorg.xzm:20220723
002-xtra.xzm:20220630
003-xfce4.xzm:20220428
initrd.xz:20201102
I presume this is not what should happen (as seen after a fresh boot due to yet another crash during suspend):
Code: Select all
root@porteus:~# fastest-mirror
Checking fastest mirror ...
Results:
Would you like to add as your main Porteus server? [y/n]
I was on a open WLAN, and at times my machine is technically still connected to that WLAN, but anything HTTPS, SMTP or IMAP is not working (giving different kinds of error messages) since I need to reaffirm my approval to its terms & conditions.
The only page that works with https is the one by the provider of that WLAN for loading its terms & conditions approval page.
Cheers!
Yours Rava
Yours Rava
Porteus-v5.0x86_64_bugs reports
Team,
In LXDE env, USB notifications are not shown for mounting and unmounting of USB drives.
Udisks2 and gvfs volume monitor are already there.
Since notification-daemon was not there by default I have added it as well and able to see other notifications.
Any idea to fix it
In LXDE env, USB notifications are not shown for mounting and unmounting of USB drives.
Udisks2 and gvfs volume monitor are already there.
Since notification-daemon was not there by default I have added it as well and able to see other notifications.
Any idea to fix it
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Porteus-v5.0x86_64_bugs reports
^
create notification-daemon as module and place it in your porteus/base folder of your LXDE setup.
(I have not set up a LXDE - but when that fixes the issue [and I presume it would since it fixed the issue for you] notification-daemon should be added to 003-lxde .
My XFCE based Port 5.0 doesn't have notification-daemon - since XFCE does it differently:The 2>/dev/null is added to get rid of messages like this
create notification-daemon as module and place it in your porteus/base folder of your LXDE setup.
(I have not set up a LXDE - but when that fixes the issue [and I presume it would since it fixed the issue for you] notification-daemon should be added to 003-lxde .
My XFCE based Port 5.0 doesn't have notification-daemon - since XFCE does it differently:
Code: Select all
guest@porteus:/mnt/live/memory/images$ find . 2>/dev/null |grep notification-daemon
guest@porteus:/mnt/live/memory/images$
Code: Select all
find: ‘./011-slapt-get-0.11.6-x86_64-2gv.xzm/var/lib/pkgtools/setup/tmp’: Permission denied
Cheers!
Yours Rava
Yours Rava
Porteus-v5.0x86_64_bugs reports
I have notification-daemon added in my Changes folder and other notifications are working as expected. Is it mandatory to move the notification module to base folder
Just want to know if an older version of gvfs-udisk2-monitor is used in LXDE or what?
https://gitlab.gnome.org/GNOME/gvfs/-/b ... ks2utils.c
In the above page, "Device can be unplugged" is embedded in the code of gvfs.
So why showing in Cinnamon, gnome, mate and not showing in LXDE and LXQT
- Rava
- Contributor
- Posts: 5416
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
Porteus-v5.0x86_64_bugs reports
No it is not.
I not use the changes folder. But even if I did, I still would move essential things I want to be always there into /base/ - just in case of updating it all some years in the future.
Then I see some individual programs (and maybe decide one or two I do no longer want or need) and will either keep the older modules for a newer Port version when they still work and I see no need for a never version.
Like in my case, I have some programs that are from Port 4.0 times or Port 5.0rc3 times, but they still work flawlessly in Port 5.0 and at times I prefer older versions since this means much less dependencies I also need to get these versions running as compared to at times a huge increase in dependency modules sizes for most recent versions.
Sorry that I cannot answer you the rest since currently I have no clue about the workings of LXDE or LXQT.
For me, XFCE is slim enough while having a more complete Desktop Environment feel (similar to KDE or mate) than the more minimal LXDE or LXQT or Openbox.
But that's just me.
Cheers!
Yours Rava
Yours Rava
Porteus-v5.0x86_64_bugs reports
hi testuser, lxde notify you can add the dunst package,and for the lxqt you can use the lxqt-notificationd all the software are on slackware repository so you can download and make xzm,ps:all the desktop environment have the notify daemon built in,but not lxde so you can try if this work for you
Porteus-v5.0x86_64_bugs reports
Beny,
Thanks much for the info and details.
I have tried lxqt-notificationd and xfce-notifyd in my DE. Noifications are working but gvfs USB notifications cannot be seen.
Tried gcd-print-notifications in my DE as well, but it didnt worked since showing org.freedesktop.Session error.
Now I am left with no choice for USB notifications in my DE.
Thanks
Thanks much for the info and details.
I have tried lxqt-notificationd and xfce-notifyd in my DE. Noifications are working but gvfs USB notifications cannot be seen.
Tried gcd-print-notifications in my DE as well, but it didnt worked since showing org.freedesktop.Session error.
Now I am left with no choice for USB notifications in my DE.
Thanks