yes i wanted to replace these 2 libraries that are mentioned in the xorg log and in the xorg core dumps, from the live usb into the installation… and it seems that those are the same libraries on the live usb as on your installation, so replace the /usr/lib/libLLVM-13.so from the installation with the one in the live usb… then let me know
I’m going to second this. 
That’s not something to dismiss or ignore or hold off until later.
Do nvme (and smartctl if applicable) hint to any drive errors?
Just so you know, the live USB is Xfce Desktop (because lighter so quicker to download). System is KDE Plasma. I guess it doesn’t make difference though?
Before confirmation, I did diff /mnt/manjaro/usr/lib/libLLVM-13.so /usr/lib/libLLVM-13.so and it appears binary files are different.
Thanks for your help @winnie! I think this have been fixed earlier. But I’ll do. From chroot, right?
Sorry, I meant from live USB with partition unmounted, right?
i thought that youre in the same live usb as is your installation… so no dont replace them if youre on different desktop…
try reinstalling this:
pacman -S glibc
exit
systemctl reboot
and test if that helped…
You want to check the physical drive(s), as well.
Yes, from a live USB environment, with nothing mounted.
First, get the names of your physical drives.
lsblk
I think your original post for inxi was cut off. Do you only have an NVMe drive? Or a SATA SSD as well?
Some NVMe can support smartctl commands, so for example:
sudo smartctl -a /dev/nvme0
You can also use the nvme commands (found in the package nvme-cli) which are geared specifically for NVMe devices. However, some drives/firmware will spam “errors” that are harmless (such as “transport type not indicated”.)
Sorry, no result. Same black screen, same coredump… It looks that something wrong is still happening with /usr/lib/libLLVM-13.so. Here is its MD5 sum:
md5sum /mnt/manjaro/usr/lib/libLLVM-13.so
2710d576f068247fbe9f7758c3a0a766 /mnt/manjaro/usr/lib/libLLVM-13.so
I looked online but I cannot find another one to compare. Maybe you can with you own system if similar?
From Manjaro live USB:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 71,3M 1 loop /run/miso/sfs/livefs
loop1 7:1 0 844,9M 1 loop /run/miso/sfs/mhwdfs
loop2 7:2 0 1,7G 1 loop /run/miso/sfs/desktopfs
loop3 7:3 0 643,2M 1 loop /run/miso/sfs/rootfs
sda 8:0 1 29,3G 0 disk /run/miso/bootmnt
├─sda1 8:1 1 3,3G 0 part
└─sda2 8:2 1 4M 0 part
nvme0n1 259:0 0 476,9G 0 disk
├─nvme0n1p1 259:1 0 300M 0 part
├─nvme0n1p2 259:2 0 467,8G 0 part
│ └─manjaro-uncrypted 254:0 0 467,8G 0 crypt
└─nvme0n1p3 259:3 0 8,8G 0 part
Please note manjaro-uncrypted is obtained with: sudo cryptsetup open /dev/nvme0n1p2 manjaro-uncrypted
No SSD, only NVMe.
inxi -Fza
System:
Kernel: 5.15.32-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 11.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-x86_64 lang=fr_FR keytable=fr tz=UTC
misobasedir=manjaro misolabel=MANJARO_XFCE_2126 quiet
systemd.show_status=1 apparmor=1 security=apparmor driver=free
nouveau.modeset=1 i915.modeset=1 radeon.modeset=1
Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel wm: xfwm
v: 4.16.1 vt: 7 dm: LightDM v: 1.30.0 Distro: Manjaro Linux
base: Arch Linux
Machine:
Type: Laptop System: HUAWEI product: NBLK-WAX9X v: M1150
serial: <superuser required>
Mobo: HUAWEI model: NBLK-WAX9X-PCB v: M1150 serial: <superuser required>
UEFI: HUAWEI v: 1.05 date: 12/04/2019
Battery:
ID-1: BAT1 charge: 48.7 Wh (99.0%) condition: 49.2/55.3 Wh (89.0%)
volts: 17.2 min: 15.3 model: Sunwoda-H HB4692Z9ECW-41 type: Li-ion
serial: <filter> status: not charging cycles: 279
CPU:
Info: model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx bits: 64
type: MT MCP arch: Zen/Zen+ note: check family: 0x17 (23)
model-id: 0x18 (24) stepping: 1 microcode: 0x8108109
Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
L1: 384 KiB desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB
L3: 4 MiB desc: 1x4 MiB
Speed (MHz): avg: 1239 high: 1266 min/max: 1400/2300 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 1234 2: 1264
3: 1221 4: 1212 5: 1234 6: 1223 7: 1266 8: 1259 bogomips: 36748
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Retpolines, IBPB: conditional, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series]
vendor: Huawei driver: amdgpu v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 03:00.0
chip-ID: 1002:15d8 class-ID: 0300
Device-2: IMC Networks ov9734_azurewave_camera type: USB driver: uvcvideo
bus-ID: 1-4:3 chip-ID: 13d3:56f8 class-ID: 0e02 serial: <filter>
Display: x11 server: X.Org v: 1.21.1.3 compositor: xfwm v: 4.16.1 driver:
X: loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa gpu: amdgpu
display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: eDP-1 mapped: eDP model: ChiMei InnoLux 0x1404 built: 2016
res: 1920x1080 hz: 60 dpi: 158 gamma: 1.2 size: 309x173mm (12.17x6.81")
diag: 354mm (13.9") ratio: 16:9 modes: max: 1920x1080 min: 640x480
Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
Device-1: AMD Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Huawei
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 03:00.1 chip-ID: 1002:15de class-ID: 0403
Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Huawei
driver: snd_pci_acp3x v: kernel alternate: snd_rn_pci_acp3x,snd_pci_acp5x
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 03:00.5 chip-ID: 1022:15e2
class-ID: 0480
Device-3: AMD Family 17h/19h HD Audio vendor: Huawei
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 03:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k5.15.32-1-MANJARO running: yes
Sound Server-2: JACK v: 1.9.20 running: no
Sound Server-3: PulseAudio v: 15.0 running: yes
Sound Server-4: PipeWire v: 0.3.49 running: yes
Network:
Device-1: Realtek RTL8822CE 802.11ac PCIe Wireless Network Adapter
vendor: & Tele RSH driver: rtw_8822ce v: N/A modules: rtw88_8822ce pcie:
gen: 1 speed: 2.5 GT/s lanes: 1 port: 2000 bus-ID: 02:00.0
chip-ID: 10ec:c822 class-ID: 0280
IF: wlp2s0 state: up mac: <filter>
Bluetooth:
Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
bus-ID: 3-2:3 chip-ID: 1358:c123 class-ID: e001 serial: <filter>
Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: enabled,running
rfk-block: hardware: no software: yes address: see --recommends
Drives:
Local Storage: total: 506.24 GiB used: 0 KiB (0.0%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: PC SN730 SDBPNTY-512G-1027 size: 476.94 GiB block-size:
physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 11110000 temp: 40.9 C scheme: GPT
ID-2: /dev/sda maj-min: 8:0 type: USB model: N/A size: 29.3 GiB
block-size: physical: 512 B logical: 512 B type: N/A serial: <filter>
rev: 2.00 scheme: MBR
SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure?
Partition:
Message: No partition data found.
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: N/A mobo: N/A gpu: amdgpu temp: 63.0 C
Fan Speeds (RPM): N/A
Info:
Processes: 251 Uptime: 12m wakeups: 1 Memory: 6.78 GiB
used: 2.05 GiB (30.2%) Init: systemd v: 250 tool: systemctl Compilers:
gcc: 11.2.0 clang: 13.0.1 Packages: pacman: 1140 lib: 319 flatpak: 0
Shell: Bash v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.15
This one is complete, I double checked.
nvme: command not found (still from live USB) so I installed it on live USB with sudo pacman -Sy nvme-cli, then:
sudo nvme list
Node SN Model Namespace Usage Format FW Rev
---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
/dev/nvme0n1 19522A804661 WDC PC SN730 SDBPNTY-512G-1027 1 512,11 GB / 512,11 GB 512 B + 0 B 11110000
sudo nvme verify /dev/nvme0n1
NVMe status: INVALID_OPCODE: The associated command opcode field is not valid(0x4001)
I’m sorry, I don’t know how to use nvme properly to check the disk…
About smartctl:
sudo smartctl -a /dev/nvme0n1p2
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-5.15.32-1-MANJARO] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WDC PC SN730 SDBPNTY-512G-1027
Serial Number: 19522A804661
Firmware Version: 11110000
PCI Vendor/Subsystem ID: 0x15b7
IEEE OUI Identifier: 0x001b44
Total NVM Capacity: 512 110 190 592 [512 GB]
Unallocated NVM Capacity: 0
Controller ID: 8215
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512 110 190 592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 001b44 8b468fe58f
Local Time is: Tue May 31 15:06:51 2022 UTC
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 88 Celsius
Namespace 1 Features (0x02): NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 5.50W - - 0 0 0 0 0 0
1 + 3.50W - - 1 1 1 1 0 0
2 + 3.00W - - 2 2 2 2 0 0
3 - 0.0700W - - 3 3 3 3 4000 10000
4 - 0.0025W - - 4 4 4 4 4000 40000
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 2
1 - 4096 0 1
=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
SMART/Health Information (NVMe Log 0x02)
Critical Warning: 0x00
Temperature: 42 Celsius
Available Spare: 100%
Available Spare Threshold: 10%
Percentage Used: 12%
Data Units Read: 148 815 266 [76,1 TB]
Data Units Written: 63 153 325 [32,3 TB]
Host Read Commands: 5 520 997 332
Host Write Commands: 3 427 700 196
Controller Busy Time: 7 896
Power Cycles: 1 948
Power On Hours: 5 317
Unsafe Shutdowns: 306
Media and Data Integrity Errors: 0
Error Information Log Entries: 1
Warning Comp. Temperature Time: 0
Critical Comp. Temperature Time: 0
Error Information (NVMe Log 0x01, 16 of 256 entries)
No Errors Logged
Thanks again guys, I deeply appreciate your help!
i wanted to try to replace the libLLVM from the installation with the one in the kde live usb… whats important is that they have the same version and the same symlinks… and they did, at least the from the xfce live usb had the same as mine on kde… so what you could try is to replace it from xfce, if you dont have access to kde iso - but i dont know if that would help since those are 2 different desktops… or you can overwrite your files … or just reinstall your system, while keep your home directory with settings…
edit: can you check the size of your libLLVM-13.so on your kde?
mine is: 104,4 MiB (109 489 408)
also check more logs, maybe there will be something:
journalctl --boot=-1 --priority=5 --no-pager
Same here (109 489 408):
ls -al /usr/lib/libLLVM-13.so
-rwxr-xr-x 1 root root 109489408 May 19 19:51 /usr/lib/libLLVM-13.so
I think the file can be corrupted, but its size preserved though. However, checksum should confirm mine is fine if yours is also 2710d576f068247fbe9f7758c3a0a766 (MD5). Anyway, probabilities are low so I guess the library is fine.
I don’t see anything but the coredump and:
May 31 16:48:31 matebook kernel: amdgpu 0000:03:00.0: amdgpu: PSP runtime database doesn't exist
May 31 16:48:31 matebook kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
If required, I can download an iso of Manjaro KDE Plasma and use it as live USB. I though it won’t make any differences but if so, I can.
About reinstalling, that’s sound like a nightmare… 
It will take so much time (that I don’t have unfortunately)… And preserving the /home from an encrypted disk sounds too complicated for me.
Once again, thank you for your help!
i have a diiferent checksum… but if the size is correct, it probably wont help to replace it…
well i dont know what to try except this overwrite command:
pacman -Qqn | pacman --overwrite=* -S -
this basically reinstalls everything on top of your already installed files
when its done:
exit
systemctl reboot
and finger crossed that it works…
To run a “short” test:
nvme device-self-test --self-test-code 1h /dev/nvme0
Replace 1h with 2h if you want to run a long test, or eh to run a “vendor specific” test.
You can also install badblocks and run a simple read-only test, which will report any I/O errors for read operations.
For example,
badblocks -b 512 -c 65535 -s -v -o badblocks_log.txt /dev/nvme0n1
Due to the nature of storage devices, even if the read-only test passes, it doesn’t rule out that corruption (of data) exists on the drive, and writes can still save corrupted data.
If it means anything, same exact file size, same modification timestamp, different MD5 hashes.
$ ls -l /usr/lib/libLLVM-13.so
root root 109489408 May 19 13:51 /usr/lib/libLLVM-13.so
$ md5sum /usr/lib/libLLVM-13.so
89d0da2617cce83c0bcd7b1e5cc83ae1 /usr/lib/libLLVM-13.so
I also downloaded the package llvm-libs-13.0.1-4-x86_64.pkg.tar.zst (from an up-to-date Manjaro repository), and it has the same MD5 hash for libLLVM-13.so as the one installed on my system.
If you’re on the stable repository and fully updated, your MD5 hash should match.
Since it doesn’t, this can mean:
- Failing storage device (improper writes)
- Failing RAM (since an archive needs to be extracted before written)
- Failing CPU (not as likely)
Or…
- During the update, there was some sort of power outage in which your system was left in a partially upgraded state. (Yet the file should not have been written in a corrupt form if everything listed above is in working order.)
Are you on the Stable Updates train?
No - it means
sudo grub-mkconfig -o /boot/grub/grub.cfg
Or the Manjaro convenience script
sudo update-grub
But as discovered - filesystem errors can produce the most unexpected hard to troubleshoot issues.
It appears a bit strange if the update would have caused filesystem errors - unless of course the sync was interupted by a power failure - that can cause some very weird issues as well.
Hooray, it finally works! 
I focused on /usr/lib/libLLVM-13.so different MD5 checksums. So I just did pacman --overwrite=libLLVM-13.so -S llvm-libs (from chroot). Then, I checked again the checksum with md5sum /usr/lib/libLLVM-13.so and it changed to 89d0da2617cce83c0bcd7b1e5cc83ae1, matching the one shared by @winnie.
exit, then systemctl reboot and it works like a charm!
I can’t thank you enough for your help, time, ideas, hints, tries, etc. I’m using Linux based distros since more than a decade, but I learnt a LOT from your expertise since yesterday. I’m really glad we find a solution thanks to this amazing team work. I’m so grateful!
I’m marking this message as a solution, but the whole thread should be read.
Here is my full post-mortem, I hope it can help others: in my very own case, libLLVM-13.so was faulty but much probably only because a disk writing issue or because something happened during an update. It could have been any other file actually.
libLLVM-13.so have been identified because it was mentioned in journalctl --boot=-1 --priority=3 --no-pager.
Another way to identified it was by switching to tty2 (Ctrl+Alt+F2), then trying to launch startx with no success. A mentioned log file were /home/username/.local/share/xorg/Xorg.0.log, where we can find:
[ 5584.703] (EE) Backtrace:
[ 5584.703] (EE) 0: /usr/lib/Xorg (xorg_backtrace+0x89) [0x5621290c70d9]
[ 5584.703] (EE) 1: /usr/lib/Xorg (0x562128f77000+0x15aef9) [0x5621290d1ef9]
[ 5584.704] (EE) 2: /usr/lib/libc.so.6 (0x7f1d84311000+0x3e8e0) [0x7f1d8434f8e0]
[ 5584.704] (EE) 3: /usr/lib/libLLVM-13.so (0x7f1d7b22f000+0x411a56c) [0x7f1d7f34956c]
[ 5584.704] (EE)
[ 5584.704] (EE) Segmentation fault at address 0x7f1d7f34956c
[ 5584.704] (EE)
Fatal server error:
[ 5584.704] (EE) Caught signal 11 (Segmentation fault). Server aborting
As a result, it appeared libLLVM-13.so was corrupted. MD5 checksum confirmed it. Replacing the file fixed the issue.
I’ve to say other things have been fixed during investigations such as removing an EOL kernel, cleaning some remaining packages, fixing bad looking disk issues, upgrading to 5.17 kernel, cleaning odd files, etc. Nothing was enough to fix the black screen issue by its own, but a combination with the identified solution cannot be excluded (especially disk errors fix).
Also, acpi_backlight=vendor is still removed from /etc/default/grub. Since I didn’t applied changes with sudo update-grub I’m not sure if it’s live or not. Since it works, I won’t touch anything for now, but I might if needed later.
I didn’t move forward about checking NVMe disk. It might be a good idea but since everything works I’m reluctant to tempt fate…
For the record, this is current booting logs:
journalctl --boot=0 --priority=3 --no-pager
mai 31 20:12:38 matebook kernel: sd 0:0:0:0: [sda] No Caching mode page found
mai 31 20:12:38 matebook kernel: sd 0:0:0:0: [sda] Assuming drive cache: write through
mai 31 20:12:56 matebook kded5[1222]: org.kde.plasma.dataengine.geolocation: error: "Unknown host location.services.mozilla.com: Host not found"
mai 31 20:12:56 matebook kded5[1222]: org.kde.plasma.dataengine.geolocation: error: "Unknown host location.services.mozilla.com: Host not found"
mai 31 20:12:56 matebook akonadiserver[1508]: org.kde.pim.akonadiserver: "\nSql error: Table 'akonadi.schemaversiontable' doesn't exist in engine QMYSQL: Unable to execute query\nQuery: ALTER TABLE SchemaVersionTable ADD COLUMN version INTEGER NOT NULL DEFAULT 0"
mai 31 20:12:56 matebook akonadiserver[1508]: org.kde.pim.akonadiserver: Unable to initialize database.
Much shorter! There are still a few errors I should probably work on, but I’ll do later and in another thread.
One final question: Is it normal to have a lib32 llvm-libs installed?
pacman -Qqn | grep llvm-libs
lib32-llvm-libs
llvm-libs
Alright, that’s it! Once again, thank you so so much everyone!
I wouldn’t just check the NVMe drive. I would also run a memtest and mprime test.
If that was my system, I would not feel comfortable using it, knowing it already wrote data in a corrupted state.
Imagine if that happens to a photo, or video, or email, or document?
You really want to rule out a faulty drive, RAM, or CPU when you already know of data corruption.
Remember, bad RAM can write to disk corrupted images, videos, and documents, but you wouldn’t get any sort of “warning” since your system will run fine and not crash. It’s actually a good thing when a crucial system file is corrupted, because you’ll know there’s an issue with your system when it crashes and/or cannot boot up properly.
For all you know, the specific file libLLVM-13.so might only be a canary in a coalmine. We just so happened to discover it was corrupted.
Here is a plausible scenario. (There are many possibilities, but here’s just one of them):
Your RAM and/or CPU is recently faulty. You don’t notice this, because it hasn’t written a corrupt system file yet.
Then you update Manjaro, which essentially downloads and unpacks the packages.
Because the RAM and/or CPU is faulty, some packages extract their files into a corrupted state, which are written to the drive.
Now you try to reboot and are met with errors, because a system file is corrupt.
Now you know something is wrong…
And it wasn’t until you ran a system update were you alerted by this “canary in a coalmine” that your RAM or CPU could be faulting. (Even infrequent faults are unacceptable.)
(Another canary in the coalmine were the checksum errors in your Ext4 filesystem…)
@winnie Got it, I will. You’re perfectly right.
I’m pretty confident it came because I closed the lid while the update was performing. The release was huge (more than 2gb). Last time I checked, download was still under 1gb. I had to go 10 min later, closed the lid (not thinking the download was possibly done -very poor connection here). When back, I wasn’t able to wake it up like it appears on a regular basis with matebook unfortunately (the issue have been identified but not solved as far as I know). I forced to shut down and then the black screen issue appeared from this very instant.
I checked pacman logs from tty2 (my first post) and it appeared to me the update was entirely done, but I think I was wrong. Closing the lid much probably corrupt the update.
That being said, you’re totally right and I’ll check the NVMe drive. It silly to not check. I will also run a memtest and mprime test.Thanks for your suggestions!
nice job of fixing it with that command of yours…
i also have the lib32 llvm-libs installed
and also just to be sure, you can check the checksum of that other library that was mentioned in the logs: md5sum /usr/lib/libc.so.6
mine is: e0e02bde032a3488ba098df28eec312a
Thanks, @brahma!
md5sum /usr/lib/libc.so.6
e0e02bde032a3488ba098df28eec312a /usr/lib/libc.so.6
It matches! 
Hah! BOTH of your computers must be corrupted, because my libc.so.6 MD5 is d8f3f334e72c0e30032f2a1a1229aef1
Oh, wait… 
…
…
…Oh! OH NOOOOOOOOO!!! 
* winnie has been disconnected *
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.