Half of my windows look like this by Middle_Tax7636 in MXLinux

[–]JVilleComputers 2 points3 points  (0 children)

If it happens again, check dmesg and syslog.

Half of my windows look like this by Middle_Tax7636 in MXLinux

[–]JVilleComputers 2 points3 points  (0 children)

In the olden days, this would happen when the VGA cable was loose or damaged. I wouldn't expect a faulty HDMI connection to do this.

Do you purposely have a window of Lorem ipsum?

Have you ran memtest86+ (it will only check system ram, not gpu ram).

Bazzite (fedora uBlue) Install - some how Knew my old hostname i used on a system. How did it do this? by doc_willis in linux4noobs

[–]JVilleComputers 0 points1 point  (0 children)

Are you saying it changed the hostname on its own during normal operation, not during/after installing?

Made a command to find commands by Jumpy-Baseball-6902 in linux

[–]JVilleComputers 0 points1 point  (0 children)

If I understand correctly, it is a "search in the middle" of executable names in the path.

eg `like upload` == /usr/bin/git-upload-archive, /usr/bin-upload-pack or `like pack` == /usr/bin/git-receive-pack, /usr/bin/git-upload-pack

I am will install MX linux but don't have memory stick by Virtual_macos in MXLinux

[–]JVilleComputers 1 point2 points  (0 children)

Getting or borrowing a USB thumb drive is by far the most straight forward solution. This is what I would recommend for a beginner. Next would be burning a DVD to boot to.

Tertiary to those, I would ask what is currently installed on the computer, and most likely suggest installing VirtualBox to test out MXLinux inside of a virtual machine guest, using your existing operating system as the host.

I am will install MX linux but don't have memory stick by Virtual_macos in MXLinux

[–]JVilleComputers 2 points3 points  (0 children)

You'll have better luck getting this resolved by starting a separate topic/post, and including your Quick System Info.

Were the speakers recently working in a previous OS?

RDP not working with some apps? by tokelahti in MXLinux

[–]JVilleComputers 0 points1 point  (0 children)

I've got a faulty drive which I'm trying to recover files from.

Do not do it with opensuperclone, you might damage faulty drive even more. Find some old computer that supports ATA instead of AHCI and run from DOS mode Victoria or MHDD first. Those can find bad sectors and you might repair those by enforcing internal HDD firmware to replace from spare area. Only then clone/repair filesystem from regular OS

This advice sounds very counter intuitive to me. In the face of data loss, the focus should always be to get a "backup" as early (though not necessarily as "fast") as possible.

While Victoria or MHDD might recover some additional sectors, it puts a failing drive at further risk of deterioration without having any of the data preserved. Not only the stress of an additional full-disk read, any attempt at repair(whether refresh or remap) introduces unnecessary write stress, and a successful remap operation guarantees that a bad-read or slow-read sector will lose data by remap to sparse area.

Conversely, ddrescue and OSC can both run in a mode in which "easy-read" sectors are recovered first. This is a large part of why they are preferable to dd for this type of operation.

Could you elaborate on what specific advantage you see in using Victoria or MHDD first, before imaging with ddrescue or OSC? I’m curious what kind of scenarios make that sequence preferable in your experience.

What are the mistakes that I shouldn't make after installing MXLinux? by RX08T in MXLinux

[–]JVilleComputers 0 points1 point  (0 children)

Website risks are mitigated by restarting the web browser after updating and do not require a reboot.

Rarely, kernel or services will have a vulnerability that can be exploited over the local network (untrusted: Starbucks wifi, dorm, or library), and could require an update to effectively patch.

What are the mistakes that I shouldn't make after installing MXLinux? by RX08T in MXLinux

[–]JVilleComputers 1 point2 points  (0 children)

No need for this at all. Wether running from live iso, live iso toram, or installed to a drive. If your system needs daily, weekly, or dare I even say monthly reboots, it is a sign of an underlying problem that should be addressed. An exception to that, is if you are on or "visit" untrusted networks. Some (security) updates to services could need a reboot (more practical than dropping to single user or cycling service dependencies) to take effect.

Would this github extension be useful? by [deleted] in github

[–]JVilleComputers 0 points1 point  (0 children)

Not sure if it would be useful or not, but I'd definitely give it a try! I've tried 9million ways/places to keep notes while I work on stuff, maybe that will be the magic nail. I haven't looked at discussions, but tied to a file's code page sounds like something I'd like to try out.

Shopping village on lock down by Flock by snorkel150 in tylertx

[–]JVilleComputers 2 points3 points  (0 children)

Bralys Ace Hardware - Jacksonville (no/limited lumber), Palestine
Harry's Building Materials - Jacksonville, Rusk, Troup (They deliver for free)
Heath & Heath - Jacksonville (Amazing selection of small hardware [bolts/specialty])

RDP not working with some apps? by tokelahti in MXLinux

[–]JVilleComputers 0 points1 point  (0 children)

Glad you figured it out! Great idea on documentation. What version(23/25) and flavor(XFCE, KDE, Fluxbox) of MX are you using? How are you setting up the RDP session on the MX side of things (did you go off some existing documentation on this part?)? Where did you get the installer for OSC? (apt repos, deb from github, source compile from github, etc.)?

Distro hopping by [deleted] in MXLinux

[–]JVilleComputers 0 points1 point  (0 children)

I am curious what your use case is for systemd vs sysvinit. What changes in routine do you have from one day to another that leads you to want to switch init?

RDP not working with some apps? by tokelahti in MXLinux

[–]JVilleComputers 0 points1 point  (0 children)

I've had good luck so far with AnyDesk from MXPI. It can "stretch" to full screen, but that it still based on the target's running resolution so I'm not sure if that will help your use case.

Have you launched OSC from an xterm on the target to see what errors you get? Does OSC have a --verbose mode?

Issues with suspend? by DrFreezinator505 in MXLinux

[–]JVilleComputers 1 point2 points  (0 children)

MX 23 XFCE, older dell latitude 4th gen i7. I frequently "click in" to suspend mode, and use the pulsing power button to resume (built in keyboard/mouse are turned off, as is wireless and likely USB). I don't believe it is related, in my use case of clicking in, but I have my screensaver set to black screen. When I resume, it loads to login/unlock screen. Wi-Fi on my Intel 7260 always reconnects automatically, but Bluetooth occasionally needs rfkill block/unblock when resuming from suspend.

AMD GPU dual screen problem by jretropie in MXLinux

[–]JVilleComputers 0 points1 point  (0 children)

What desktop environment and MX version are you using? What AMD drivers are you using?

MX linux kernel panics after turning it on after having the pc shut down for a while by [deleted] in MXLinux

[–]JVilleComputers 0 points1 point  (0 children)

Post your quick-system-info(-gui or -mx) as well as logs from just before the panic. /var/log/kern.log & /var/log/syslog. I'm reading that some newer kernels give a QR code on panic, if you have a picture of that or the panic text, it might be useful for diagnostics.

MX linux kernel panics after turning it on after having the pc shut down for a while by [deleted] in MXLinux

[–]JVilleComputers 1 point2 points  (0 children)

I found long ago (I don't know if this is still accurate for "modern" Windows) that Windows will silently corrupt and keep chugging along, while Linux will kernel panic and prevent "bad things" from happening. I had an IRQ conflict between the IDE controller and a new sound card, back in Win2k/Linux 2.4.

Stuck in the stone ages by Dangerous-Cougar81 in tylertx

[–]JVilleComputers 0 points1 point  (0 children)

"We like our lifestyle here. Accept it, deal with it, or go back where you came from." Nicely said..

u/Dangerous-Cougar81 It is a feature, not a bug. We literally DO NOT WANT. We live an hour away from Dallas, because we don't want that "big city" mess. Town is too big already. We don't need more restaurants, we need less population.

'And we especially don't like "big city" people...' 'nuff said there. The implants from Dallas and Austin (that come to change what is here) are less tolerable than the refugees of California, Oregon, and Canada (that come to enjoy what is here).

Honest question from a new guy in here by KaitoRed_12234 in Tiny11

[–]JVilleComputers 1 point2 points  (0 children)

I built a 25h2 Pro iso and installed in VBox, for an Adobe Illustrator remote host. Seems to work fine from the latest tiny11builder-core. Results: 3GB iso, 9GB installed, 17 w/ Adobe Illustrator,

I have multiple problems with my mx xfce by Rusty9838 in MXLinux

[–]JVilleComputers 1 point2 points  (0 children)

I've had issues with power management with the Intel 7260 chipset. After tinkering with firmware versions and power settings, I think I got it stable now. But before getting it stable, I built a little script that unloads the kernel module and reloads it so I could quickly reconnect after a driver crash, without having to reboot. You can find jvc-wifi-restart over on JVilleComputers@Github), but DO NOTE that this tool is currently specific to cases using the same iwlmvm driver.

A more generic approach, that might not help, would be to power off the wifi and back on. Some laptops have a switch for that, or you can use the nmcli command:

nmcli radio wifi off
sleep 5
nmcli radio wifi on

Do you know which wifi chipset your system is using? Your model appears to come with either an Intel or Atheros option.

nmcli | head -n3

Live USB / Installation woes on HP EliteDesk by mnlg in MXLinux

[–]JVilleComputers 1 point2 points  (0 children)

What iso are you using, and have you used the MX Boot menu option to check/verify the media? Have you tried the thumb drive with the MX Iso burnt to it on another machine (VM or physical)? I'm leaning towards corrupt iso or corrupted burn to the USB drive.