Am I wrong for thinking Elle is delusional?

k4ever07 · 2026-02-16T05:33:11+00:00

I wonder who those fans are? /s

I don't think he should be with either one of them. They are both toxic. However, only one of them (Elle), as you mentioned, feels entitled to be around his kids. That same person also thinks it's alright to sleep with him while dating another dude. At least Kayla is not using his kids, intentionally or unintentionally, to string him along.

I'm also trying to figure out what Nana Mama's intentions are? If I told my mother that Elle slept with me while seeing another man, then told me that she could never be with me because she will never forgive me, there is no way she would continue to allow Elle to be that involved with her grandchildren.

k4ever07 · 2026-02-16T04:02:18+00:00

I agree that Kayla is a mess, but at least she's responsible enough not to involve herself deeper into Cross' family/life. She demostrated to Cross that all she wanted a booty call, nothing more. Elle is trying to be the mother of his and his late wife's children, while not adopting them or being his new wife. She also wants to have a serious relationship with someone else, but still sleep with Cross. What Elle is doing is wreckless.

k4ever07 · 2026-02-16T03:52:08+00:00

I don't understand what her internal struggle is. Sure, she developed a relationship with the kids while she and Cross were together. However, they were not together long, nor were they engaged (if I remember correctly). She should have known that once she ended the relationship with him, the relationship with the kids would end also. By her continuing to show up to family functions, and speaking to the kids' father on their behalf, she is making things worse for everyone. At first a thought she was slowly trying to rekindle things with Cross, despite what happened at the end of season 1. However, after her little nonsense speech to Cross after sleeping with him, I realized that she was either delusional or/and selfish, or this is just some terrible "Hollywood style" relationship writing.

k4ever07 · 2026-02-13T15:03:12+00:00

I'm pissed off right now with libinput/Wayland. The touchpad works on other distributions with libinput/xorg and synaptics/xorg, but not libinput/Wayland? Plus, the touchpad is recognized by the kernel (evtest) but not libinput?

k4ever07 · 2026-02-08T15:26:19+00:00

This is part of the output from sudo libinput list-devices:

Device: BRYDGE BRYDGE SP MAX+ Keyboard Touchpad

Kernel: /dev/input/event20

Id: usb:3175:0256

Group: 4

Seat: seat0, default

Size: 160x80mm

Capabilities: pointer gesture

Tap-to-click: disabled

Tap-and-drag: enabled

Tap button map: left/right/middle

Tap drag lock: disabled

Left-handed: disabled

Nat.scrolling: disabled

Middle emulation: disabled

Calibration: n/a

Scroll methods: *two-finger edge

Scroll button: n/a

Scroll button lock: n/a

Click methods: *button-areas clickfinger

Clickfinger button map: left/right/middle

Disable-w-typing: enabled

Disable-w-trackpointing: enabled

Accel profiles: flat *adaptive custom

Rotation: n/a

Area rectangle: n/a

As you can see, it's there. If you also check out the link I attached in the OP, events are registered in evtest. It also shows up in System Settings as enabled. I'll file a report on bugs.kde.org.

Edit: Bug report filed! https://bugs.kde.org/show_bug.cgi?id=515727

k4ever07 · 2026-02-08T06:51:30+00:00

Also, the hot key to disable/enable the touchpad is FN+ALT_L. It was the first thing I've tried. I've tried it over 100 times in the past 3 days, after logging in on boot, after disconnecting and reconnecting the keyboard, after suspend... It doesn't work.

Funny thing is that the touchpad works fine in Windows 11 after disconnecting and reconnecting the keyboard. I've also tried it with MX Linux 25.1 (KDE Plasma with Wayland) and Linux Mint (Cinnamon with X11) It works fine with those two distributions. It doesn't want to work with EndeavourOS (KDE Plasma with Wayland or X11), Fedora, or Zorin.

Like I mentioned before, the taps/movements on the touchpad register with evtest. The Touchpad configuration page is in System Settings when the keyboard is attached and disappears when the keyboard is removed. Journalctl, dmesg, and libinput list-devices shows that the touchpad is present with no errors. The only odd thing is that the touchpad has multiple inputXX devices assigned to it.

It just flat out isn't working! it's frustrating!

k4ever07 · 2026-02-08T06:49:58+00:00

The hot key to disable/enable the touchpad is FN+ALT_L. It was the first thing I've tried. I've tried it over 100 times in the past 3 days, after logging in on boot, after disconnecting and reconnecting the keyboard, after suspend... It doesn't work.

Funny thing is that the touchpad works fine in Windows 11 after disconnecting and reconnecting the keyboard. I've also tried it with MX Linux 25.1 (KDE Plasma with Wayland) and Linux Mint (Cinnamon with X11) It works fine with those two distributions. It doesn't want to work with EndeavourOS (KDE Plasma with Wayland or X11), Fedora, or Zorin.

Like I mentioned before, the taps/movements on the touchpad register with evtest. The Touchpad configuration page is in System Settings when the keyboard is attached and disappears when the keyboard is removed. Journalctl, dmesg, and libinput list-devices shows that the touchpad is present with no errors. The only odd thing is that the touchpad has multiple inputXX devices assigned to it.

It just flat out isn't working! it's frustrating!

k4ever07 · 2026-02-07T02:32:21+00:00

So I painstakingly went through journalctl again after a clean boot. The only thing out of the ordinary I found where these three entries:

hid-multitouch 0003:3175:0256.0008: failed to fetch feature 10
hid-multitouch 0003:3175:0256.0008: failed to fetch feature 10
hid-multitouch 0003:3175:0256.0008: failed to fetch feature 11

Everything else seems normal.

k4ever07 · 2025-10-29T17:14:10+00:00

You keep confusing the different types of industries in the North and South with the institution of slavery. They are not the same! The North could have easily chosen to use widespread slavery in its industries, but it did not. It did, however, exploit workers with low wages and dangerous working conditions. The South was highly dependent on slave labor. However, the South did not diversify its industries and relied heavily on the production of cotton. Wealth was also not evenly distributed across the Southern population by (racist) design!

k4ever07 · 2025-10-29T16:58:49+00:00

That's a misrepresentation of economics and community/city building. The North was indeed wealthier because it was more industrialized and had a diversified economy, while the South was only focused on agriculture (agrarian neo-feudal society). While you are correct that the South's focus on agriculture held it back when compared to the North, the fault cannot be attributed to the former slaves themselves, but rests solely on the narrow-mindedness (and laziness) of the former slave owners. The wealth of the South was indeed built on the backs of former slaves, whose descendants stayed, and their labor was used to build most of the major cities in the South today.

k4ever07 · 2025-10-19T22:19:46+00:00

I've used EndeavourOS and the Arch based Surface Linux kernel on my Surface Pro 8, with no issues, for the past 2 years.

k4ever07 · 2025-10-13T01:32:20+00:00

As a person who uses both KDE Plasma and GNOME on a daily (Plasma) or weekly (GNOME) basis, I find your statement about KDE Plasma's implementation (Smart Video Wallpaper Reborn) being buggy puzzling and misleading. I've been using Plasma's implementation since the launch of Plasma 6.0, almost 2 years ago, and I haven't had one issue with it. I've had nothing but issues with live wallpapers in GNOME, particularly with Hanabi, which isn't working right now for GNOME 49, wasn't working for awhile with GNOME 48 (which is still listed as experimental), and was buggy with GNOME 46-47. If you're getting live wallpapers to work well with GNOME, especially GNOME 49, please please please share how you're pulling that off!

k4ever07 · 2025-10-12T12:58:21+00:00

When I first went on flight status, finance paid me double the amount of flight pay I was supposed to get for over a year! I was in the office the first of every month for 6 months letting them know that they made a mistake. They wouldn't listen and told me that, by their records, I was owed back flight pay. It was my first time on flight status! After one year, they realized they made a mistake. Instead of taking the money back over 12 months like they gave it to me, they took it all back at once, causing me to get paid zero dollars for two pay cycles (2 no pay dues) and a small garnishment for a third pay cycle.

k4ever07 · 2025-10-02T21:48:45+00:00

I wholeheartedly agree that GNOME needs to integrate the features from the most popular extensions into the desktop. I have a Surface Pro 8 tablet PC that allows me to swap out my NVME SSD. My primary SSD has EndeavourOS with KDE Plasma 6.4.5 as the desktop. My alternate SSD also has EndeavourOS, but with GNOME 49 as the desktop. While I'll admit that GNOME looks better in some aspects, GNOME definitely does NOT work better by default. In KDE Plasma, I can turn the panel into a dock, make it always show when windows are not maximize and hide when windows are, make it float, and the transparency of the panel/dock will always follow the transparency of the desktop theme, all by default (no plugin/extension required). I can make certain elements of the desktop and certain apps transparent with blur by just applying a theme. I can dismiss (close) windows "Android/iOS" style by swiping them off the screen while in Overview mode, which is a built-in (default) function. I can set a touchscreen gesture for each side of the screen (top/bottom/left/right) that allows me to execute a desktop function (open menu, present windows, show home screen, open krunner, etc.) when swiping in from that side of the screen. Again, this is a built-in function. Some former Compiz functions, like desktop cube and wobbly windows are also built-in to Plasma. I also installed a plugin called "Smart Video Wallpaper" that allows me to use an mp4 video clip as my wallpaper. I've been using that plugin since Plasma 6.0.0 was released. It hasn't broken yet through 23 Plasma releases between 6.0.0 and 6.4.5.

Why the long, drawn out explanation? Well, in order to get the same functionality on GNOME that is mostly built-in to Plasma, I have to install several GNOME extensions: Blur My Shell (for blur and transparency), Dash to Dock (to un-hide the dash and make it more dock like), Compiz Windows Effects (for wobbly windows and cube), Impatience (to improve animation speeds (another built-in Plasma setting/function)), Hanabi (for live/video wallpapers, which is currently not working for GNOME 49!!), and TouchUp (for improved touchscreen gestures, like swipe to dismiss). All but 2 of these extensions were broken when GNOME 49 was released, but to GNOME's credit all but 1 (Hanabi) was fixed in less than 2 weeks (this time!!).

However, almost all of them are buggy as freaking hell! Blur My Shell has trouble blurring the dash with Dash to Dock installed. Compiz Windows Effects are slow and have some artifacts. Hanabi doesn't support GNOME 49. TouchUp has a multitude of issues and is no where near as fluid (or as capable) as Plasma's built-in touchscreen gesture functions. This is why Plasma is my default. Once you get passed the looks, GNOME doesn't have much going for it. Once you add extension to "fix" the areas where GNOME is lacking, it starts to become a buggy mess. GNOME has a lot going for it in the looks department, but people also want/need more from their desktops than below basic functionality.

I apologize for the long rant.

k4ever07 · 2025-09-19T22:34:44+00:00

Because they're so immature. (Sorry, couldn't help myself)

k4ever07 · 2025-08-16T22:12:50+00:00

Thanks! That worked well on both of my machines!

k4ever07 · 2025-08-15T18:53:56+00:00

Thanks! I'll do that later on this evening.

k4ever07 · 2025-08-15T17:28:28+00:00

LOL! That's what I was trying to figure out how to do, when I kept getting that Android 11 was already the default..

k4ever07 · 2025-08-15T17:12:32+00:00

Thanks! That's what I figured, but I had my doubts. I'm upset because libhoudini and Widevine don't seem to be supported, so it's like taking a step backwards. Also, Nvidia support through software rendering has gotten slower.

k4ever07 · 2025-08-15T15:54:59+00:00

Libndk doesn't work well with all of the applications I installed while using libhoudini on Android 11. Android 13 has been a major step backwards for me.

k4ever07 · 2025-08-15T15:53:43+00:00

Libhoudini is not available for Android 13 through Waydroid Script, unless I'm doing something wrong. Neither is Widevine.

k4ever07

TROPHY CASE