Porteus-v5.0rc3 x86_64 bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
babam
Shogun
Shogun
Posts: 250
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 4.0 Xfce K5.11.10
Location: Rainy city

Porteus-v5.0rc3 x86_64 bug reports

Post#91 by babam » 22 Aug 2021, 15:13

@Ed_P, using parted

Code: Select all

# parted 50rc3saveX.dat p
# parted 50rc3save.dat p
Sorry, my English is bad.

User avatar
Ed_P
Contributor
Contributor
Posts: 6398
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

Porteus-v5.0rc3 x86_64 bug reports

Post#92 by Ed_P » 22 Aug 2021, 16:11

Thank you babam.

Code: Select all

guest@porteus:/mnt/sda6/porteus5.0/changes$ parted 50rc3saveX.dat p
bash: parted: command not found
guest@porteus:/mnt/sda6/porteus5.0/changes$ su
Password:                            
root@porteus:/mnt/sda6/porteus5.0/changes# parted 50rc3saveX.dat p
Error: /mnt/sda6/porteus5.0/changes/50rc3saveX.dat: unrecognised disk label
Model:  (file)                                                            
Disk /mnt/sda6/porteus5.0/changes/50rc3saveX.dat: 336MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags: 
root@porteus:/mnt/sda6/porteus5.0/changes# parted 50rc3save.dat p
Model:  (file)
Disk /mnt/sda6/porteus5.0/changes/50rc3save.dat: 537MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End    Size   File system  Flags
 1      0.00B  537MB  537MB  xfs

root@porteus:/mnt/sda6/porteus5.0/changes# 
The X file was created by expanding a full 256MB save.dat file with the Porteus Savefile Manager. The other was created as a new file by the Savefile Manager.
Ed

User avatar
babam
Shogun
Shogun
Posts: 250
Joined: 16 Nov 2016, 10:30
Distribution: Porteus 4.0 Xfce K5.11.10
Location: Rainy city

Porteus-v5.0rc3 x86_64 bug reports

Post#93 by babam » 22 Aug 2021, 16:41

Ed_P,
It looks like 50rc3saveX.dat has been corrupted.
Sorry, my English is bad.

beny
Full of knowledge
Full of knowledge
Posts: 1074
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus-v5.0rc3 x86_64 bug reports

Post#94 by beny » 22 Aug 2021, 17:59

hi Ed_P you have to make a huge dat container so don't have to worry for save changes the write of windows data is a bit weird take a long time to write the record,if you umount before..... better to make a backup of dat container.

User avatar
Ed_P
Contributor
Contributor
Posts: 6398
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

Porteus-v5.0rc3 x86_64 bug reports

Post#95 by Ed_P » 22 Aug 2021, 22:55

I do backup my save.dat file that I use with Porteus 4.0 when I make changes but not the one for Porteus 5.0 that we are still testing. But your point did remind me that I had backed up the whole hard drive not that long ago so it has a backup of the Porteus 5.0 save.dat file on it that I can restore. Thank you :worthy: beny.
Ed

Kulle
Shogun
Shogun
Posts: 332
Joined: 28 Jan 2017, 10:39
Distribution: v4.0 64bit Xfce
Location: Berlin

Porteus-v5.0rc3 x86_64 bug reports

Post#96 by Kulle » 23 Aug 2021, 12:00

I have been using Porteus-XFCE-v5.0rc3-x86_64 since today.
I created via Browser Selection and Update Tool:
chromium-ungoogled-92.0.4515.131-x86_64-de-1alien.xzm
But it doesn't work.
Error: aborted

Code: Select all

 chromium-ungoogled 
[1:1:0823/113853.097873:FATAL:chrome_main_delegate.cc(1091)] Check failed: !loaded_locale.empty(). Locale could not be found for 
#0 0x55b82ae9b0a3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bdf0a2)
#1 0x55b82aeac910 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf090f)
#2 0x55b82aead45e (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf145d)
#3 0x55b828106dd3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x1e4add2)
#4 0x55b82ae4327d (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b8727c)
#5 0x55b82ae41781 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b85780)
#6 0x55b82ae418ad (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b858ac)
#7 0x55b828106051 ChromeMain
#8 0x7fbed05981ad __libc_start_main

[2173:2173:0823/113853.097965:FATAL:chrome_main_delegate.cc(1091)] Check failed: !loaded_locale.empty(). Locale could not be found for 
#0 0x55bf0644f0a3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bdf0a2)
#1 0x55bf06460910 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf090f)
#2 0x55bf0646145e (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf145d)
#3 0x55bf036badd3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x1e4add2)
#4 0x55bf063f727d (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b8727c)
#5 0x55bf063f5781 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b85780)
#6 0x55bf063f58ad (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b858ac)
#7 0x55bf036ba051 ChromeMain
#8 0x7f74dd1541ad __libc_start_main

Received signal 6
#0 0x55b82ae9b0a3 Received signal 6
#0 0x55bf0644f0a3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bdf0a2)(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bdf0a2)

##11  0x0x55bf064e27d155b82af2e7d1  (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4c727d0)
#2 0x(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4c727d0)7fbed14e9400
 #2 0x7f74de0a5400 (/lib64/libpthread-2.33.so+0x123ff)
#(/lib64/libpthread-2.33.so+0x123ff)3
 #0x355bf06460d37  0x55b82aeacd37 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf0d36)
#4 0x(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf0d36)55bf0646145e
 #4 0x55b82aead45e (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf145d)
(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf145d)#
5# 50x 55bf036badd30x 55b828106dd3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x1e4add2)
#6(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x1e4add2) 
0x#55bf063f727d6  0x55b82ae4327d (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b8727c)
#7 0x55bf063f5781 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b8727c)
#7 0x55b82ae41781 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b85780)(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b85780)

##88  0x0x55bf063f58ad55b82ae418ad  (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b858ac)
(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b858ac)#
9# 90x 55bf036ba0510x 55b828106051 ChromeMain
ChromeMain#
10# 100x 7fbed05981ad0x 7f74dd1541ad __libc_start_main
  r8: 0000000000000000  r9: 00007fff13553570 r10: 0000000000000008 r11: 0000000000000246__libc_start_main

 r12:   r8: 000055b831cd17900000000000000000 r13:   r9: 00007fff135537c000007ffc3eeb24b0 r14:  r10: 000055b831cd17a00000000000000008 r15:  r11: aaaaaaaaaaaaaaaa0000000000000246

  di:  r12: 0000000000000002000055bf0d23d790  si:  r13: 00007fff13553570  bp: 00007fff135537b0  bx: 00007fbecf29f140
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007fbed05afadb  sp: 00007fff135535e8
  ip: 00007fbed05afadb00007ffc3eeb2700 efl: 0000000000000246 r14:  cgf: 000055bf0d23d7a0002b000000000033 r15:  erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
aaaaaaaaaaaaaaaa
  di: 0000000000000002  si: 00007ffc3eeb24b0  bp: 00007ffc3eeb26f0  bx: 00007f74dbe5b140
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007f74dd16badb  sp: 00007ffc3eeb2528
  ip: Received signal 00007f74dd16badb11 efl:  <unknown> 0000000000000246000000000000 cgf: 
002b000000000033 erf: #00000000000000000
  trp: 0x000000000000000055b82ae9b0a3 msk:  0000000000000000 cr2: 0000000000000000
[end of stack trace]
(/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bdf0a2)
#1 0x55b82af2e7d1 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4c727d0)
#2 0x7fbed14e9400 (/lib64/libpthread-2.33.so+0x123ff)
#3 0x55b82aeacd37 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf0d36)
#4 0x55b82aead45e (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf145d)
#5 0x55b828106dd3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x1e4add2)
#6 0x55b82ae4327d (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b8727c)
#7 0x55b82ae41781 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b85780)
#8 0x55b82ae418ad (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b858ac)
#9 0x55b828106051 ChromeMain
#10 0x7fbed05981ad __libc_start_main
  r8: 0000000000000000  r9: 00007fff13553570 r10: 0000000000000008 r11: 0000000000000246
 r12: 000055b831cd1790 r13: 00007fff135537c0 r14: 000055b831cd17a0 r15: aaaaaaaaaaaaaaaa
  di: 0000000000000002  si: 00007fff13553570  bp: 00007fff135537b0  bx: 00007fbecf29f140
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007fbed05afadb  sp: 00007fff13553680
  ip: 00007fbed05965e9 efl: 0000000000010246 cgf: 002b000000000033 erf: 0000000000000000
 trp: 000000000000000d msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
[2169:2169:0823/113853.138369:FATAL:zygote_host_impl_linux.cc(191)] Check failed: ReceiveFixedMessage(fds[0], kZygoteBootMessage, sizeof(kZygoteBootMessage), &boot_pid). 
#0 0x5652268370a3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bdf0a2)
#1 0x565226848910 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf090f)
#2 0x56522684945e (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf145d)
#3 0x565224fffd24 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x33a7d23)
#4 0x5652267dfecb (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b87eca)
#5 0x565224710eab (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x2ab8eaa)
#6 0x5652247114f4 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x2ab94f3)
#7 0x5652267df432 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b87431)
#8 0x5652267dd781 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b85780)
#9 0x5652267dd8ad (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b858ac)
#10 0x565223aa2051 ChromeMain
#11 0x7fba25d3c1ad __libc_start_main

Received signal 6
#0 0x5652268370a3 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bdf0a2)
#1 0x5652268ca7d1 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4c727d0)
#2 0x7fba26c8d400 (/lib64/libpthread-2.33.so+0x123ff)
#3 0x565226848d37 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf0d36)
#4 0x56522684945e (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4bf145d)
#5 0x565224fffd24 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x33a7d23)
#6 0x5652267dfecb (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b87eca)
#7 0x565224710eab (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x2ab8eaa)
#8 0x5652247114f4 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x2ab94f3)
#9 0x5652267df432 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b87431)
#10 0x5652267dd781 (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b85780)
#11 0x5652267dd8ad (/usr/lib64/chromium-ungoogled/chromium-ungoogled+0x4b858ac)
#12 0x565223aa2051 ChromeMain
#13 0x7fba25d3c1ad __libc_start_main
  r8: 0000000000000000  r9: 00007ffe5cf63bd0 r10: 0000000000000008 r11: 0000000000000246
 r12: 000056522dbbe790 r13: 00007ffe5cf63e20 r14: 000056522dbbe7a0 r15: aaaaaaaaaaaaaaaa
  di: 0000000000000002  si: 00007ffe5cf63bd0  bp: 00007ffe5cf63e10  bx: 00007fba24a43140
  dx: 0000000000000000  ax: 0000000000000000  cx: 00007fba25d53adb  sp: 00007ffe5cf63c48
  ip: 00007fba25d53adb efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
 trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Aborted
guest@porteus:~$ 

Now I created also via Browser Selection and Update Tool:
google-chrome-92.0.4515.159-x86_64-de-1.xzm
Does not work too. Only this error message appears:

Code: Select all

google-chrome-stable 
[0823/102334.026153:WARNING:minidump_writer_util.cc(50)] string Local time zone must be set--see zic manual page UTF-16 length 48 will be truncated to UTF-16 length 31
[0823/102334.026184:WARNING:minidump_writer_util.cc(50)] string Local time zone must be set--see zic manual page UTF-16 length 48 will be truncated to UTF-16 length 31
Trace/breakpoint trap

beny
Full of knowledge
Full of knowledge
Posts: 1074
Joined: 02 Jan 2011, 11:33
Location: italy

Porteus-v5.0rc3 x86_64 bug reports

Post#97 by beny » 23 Aug 2021, 15:31

hi kulle yes the alien version do not work also in my system, if you want go to the chromium site, and i have downloaded this version just for try and work /home/guest/Downloads/chromium-browser-unstable_94.0.4594.0-1_amd64.deb xzm package with deb2xzm .

User avatar
Ed_P
Contributor
Contributor
Posts: 6398
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 4.0 & 5.0rc3 ISOs
Location: Western NY, USA

Porteus-v5.0rc3 x86_64 bug reports

Post#98 by Ed_P » 23 Aug 2021, 17:43

Restored save.dat from a backup. Expanded it from 256MB to 320MB using Porteus SaveFile Manager.

Code: Select all

root@porteus:/mnt/sda6/porteus5.0/changes# parted 50rc3save.dat p
Error: /mnt/sda6/porteus5.0/changes/50rc3save.dat: unrecognised disk label
Model:  (file)                                                            
Disk /mnt/sda6/porteus5.0/changes/50rc3save.dat: 336MB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags:
root@porteus:/mnt/sda6/porteus5.0/changes# fdisk 50rc3save.dat

Welcome to fdisk (util-linux 2.37.2).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x9330b4b2.

Command (m for help): 
All unwritten changes will be lost, do you really want to quit? y
 
A backup of the restored save.dat tests ok.

Code: Select all

root@porteus:/mnt/sda6/porteus5.0/changes# parted 50rc3saveBkup.dat p
Model:  (file)
Disk /mnt/sda6/porteus5.0/changes/50rc3saveBkup.dat: 268MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End    Size   File system  Flags
 1      0.00B  268MB  268MB  xfs

root@porteus:/mnt/sda6/porteus5.0/changes# 
Added in 10 hours 17 minutes 19 seconds:
Expanded my 256MB save.dat file to 512MB using the Porteus Save File Manager in Porteus 4.0.

Code: Select all

guest@porteus:/mnt/sda6/porteus5.0/changes$ su
Password: 
root@porteus:/mnt/sda6/porteus5.0/changes# parted 50rc3save.dat p
Model:  (file)
Disk /mnt/sda6/porteus5.0/changes/50rc3save.dat: 537MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags: 

Number  Start  End    Size   File system  Flags
 1      0.00B  537MB  537MB  xfs

root@porteus:/mnt/sda6/porteus5.0/changes# ls -lh 50rc3*
-rwxrwxrwx 1 guest root 512M Aug 23 20:45 50rc3save.dat*
-rwxrwxrwx 1 guest root 256M Aug 23 19:37 50rc3saveBkup.dat*
root@porteus:/mnt/sda6/porteus5.0/changes# 
 
Rebooted with the enlarged save.dat no problem. :good:
Ed

paf
White ninja
White ninja
Posts: 12
Joined: 22 Feb 2018, 15:11
Distribution: Porteus
Location: Portugal

Porteus-v5.0rc3 x86_64 bug reports

Post#99 by paf » 08 Sep 2021, 16:48

Virtual Box Guest Additions

I am trying to build the Virtual Box Guest Additions for the latest Porteus 5.0 rc3 64 bits.

So, first step remaster Porteus with the modules from: http://ftp.nluug.nl/os/Linux/distr/port ... .0/kernel/

Replaced the kernel module and added the crippled_sources and devel modules.
Porteus boots ok, all the modules are loaded, and the Virtual Box builder does not warn of any missing files.

But, pressing ok as instructed results in a xzm module with only 4096 bytes.

The first "strange line" that appears in the "progress window" is:

Code: Select all

ver-builder/build/: No such file or directory


Which files can I use to debug the issue or compile manually the VBox Guest Additions?

And many, Many Thanks for Porteus!

jroovy
White ninja
White ninja
Posts: 14
Joined: 25 Jul 2021, 12:12
Distribution: archlinux

Porteus-v5.0rc3 x86_64 bug reports

Post#100 by jroovy » 10 Sep 2021, 18:29

fulalas wrote:
19 Aug 2021, 02:57
jroovy wrote:
27 Jul 2021, 06:16
XFCE: brightness keys are not working

1) Press the brightness keys on your laptop
2) Press Ctrl+Alt+F1
3) Observe the messages in the console saying: "No outputs have backlight property"
I don't have a laptop to test, sorry. Have you tried this? https://unix.stackexchange.com/question ... xbacklight
@fulalas yup, that solution works! Had to decompress the 002-xorg.xzm, put the conf file in /etc/X11/xorg.conf.d, recompress it, and replace the original 002-xorg.xzm file with it and it works! Thanks! :D

(btw, the acpilight package/solution you posted below didn't work)
sorry for the late reply

jroovy
White ninja
White ninja
Posts: 14
Joined: 25 Jul 2021, 12:12
Distribution: archlinux

Porteus-v5.0rc3 x86_64 bug reports

Post#101 by jroovy » 12 Sep 2021, 04:10

MATE: significant delay between pressing brightness keys

1) Repeatedly tap the brightness keys (on a laptop)
2) Notice how there's a delay before the display brightness actually goes up/down

Note: This didn't happen with the 5.0 rc2 Mate iso (brightness goes up/down immediately after key is pressed)

jroovy
White ninja
White ninja
Posts: 14
Joined: 25 Jul 2021, 12:12
Distribution: archlinux

Porteus-v5.0rc3 x86_64 bug reports

Post#102 by jroovy » 12 Sep 2021, 04:19

oh, and volume keys no longer work on the MATE iso :(

Jack
Contributor
Contributor
Posts: 1657
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 4.0rc4 My Mate 64 bit
Location: USA

Porteus-v5.0rc3 x86_64 bug reports

Post#103 by Jack » 12 Sep 2021, 04:48

jroovy wrote:
12 Sep 2021, 04:19
oh, and volume keys no longer work on the MATE iso :(
I have no problem with volume keys. I'm using Mate and rc3 of Porteus 5.0.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

User avatar
Rava
Contributor
Contributor
Posts: 3069
Joined: 11 Jan 2011, 02:46
Distribution: XFCE 5.0rc3 x86_64 + 4.0 i586
Location: Forests of Germany
Contact:

Porteus-v5.0rc3 x86_64 bug reports

Post#104 by Rava » 22 Sep 2021, 06:09

Do I get that right, did Porteus drop IRC clients in 5.0rc3, or is it just the XFCE variant that lacks an IRC client?

None is to be found in the "Browser selection and update tool" (but an IRC client is no browser)

I know that some sites are able to use IRC via a browser, but sometimes a simple IRC client is the better solution.

Or am I wrong?
Cheers!
Yours Rava

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 3210
Joined: 20 Mar 2012, 03:42
Distribution: 5.0-current-64bit
Location: australia
Contact:

Porteus-v5.0rc3 x86_64 bug reports

Post#105 by ncmprhnsbl » 22 Sep 2021, 06:47

Rava wrote:
22 Sep 2021, 06:09
Do I get that right, did Porteus drop IRC clients in 5.0rc3, or is it just the XFCE variant that lacks an IRC client?
porteus hasn't shipped with a chat client in any DE variant for quite some time ... not sure the even 3 series had one..
slackware current official repo has pidgin and hexchat .. maybe others...
Forum Rules : https://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply