Artix Linux => Applications & Software => Topic started by: TopHatProductions115 on 25 May 2025, 01:51:22
Title: [SOLVED] Unable to Start Graphical Session
Post by: TopHatProductions115 on 25 May 2025, 01:51:22
I applied some updates (pacman -Syu) to my two Artix VMs on the 22nd, and have been unable to use Xfce or LightDM ever since. When powering on the VMs normally (allowing the greeter/LightDM to start), I am met with a black screen and a blinking cursor. When attempting to manually start a graphical session (startxfce4) on one of them, I received the following output:
Since one of the VMs is running Docker containers, I checked to see if those services were still available. They are still reachable, which seems to indicate that this issue only impacts my ability to start a graphical session. Has anyone else ran into this issue recently? Should I try out a different DektopEnvironment/DisplayManager, to see if the issue only impacts Xfce and LightDM?Just curious...
Title: Re: Unable to Start Graphical Session
Post by: mrbrklyn on 25 May 2025, 04:05:45
is there a suid problem?
I would uninstall X and reinstall it with pacman, just to assure you are working from a sane baseline
Title: Re: Unable to Start Graphical Session
Post by: TopHatProductions115 on 25 May 2025, 08:39:31
Title: Re: Unable to Start Graphical Session
Post by: gripped on 25 May 2025, 09:46:28
There is an error with /usr/lib/xorg/modules/drivers/vesa_drv.so
But also and (possibly more relevant?) also with /usr/lib/xorg/modules/drivers/libvgahw.so From a quick search libvgahw.so seems to be vmware specific. So I'd be investigating how vmware installs libvgahw.so in the guest and whether it could be updated or downgraded to possibly fix the issue.
But vesa_drv.so might actually be needed as well. I don't know about the inner workings of vmware so can't help much more than that.
Title: Re: Unable to Start Graphical Session
Post by: mrbrklyn on 25 May 2025, 13:59:40
I can't read these little pictures of massive amount of text. The thing about the vesa error is that it is often a fallback module that should work... and it is not. You reinstalled X and X does work. I have it running on dozens of systems. So the question is what is unique about your set up.
I also thought it might be vmware but I know nothing about it, so I was quiet about what I don't know and hoping someone else would have a decent insight.
I would remove X and by hand delete all the configuration files. and THEN try to reinstall. Missing symbols for video drivers your not using is not a big deal. Missing symbols from drivers you should be running... that is trouble. My guess is you have an incompatibility with vmware graphic drivers and the updated X.
Title: Re: Unable to Start Graphical Session
Post by: gripped on 25 May 2025, 14:50:00
Xorg drivers come from packages separate to the main xorg-sever package. And libvgahw.so may come directly from vmware ? Have a look in your pacman log to see what got updated on the 22nd.
Title: Re: Unable to Start Graphical Session
Post by: Phosphate5 on 26 May 2025, 10:30:33
I am having exactly the same issue with my Artix Linux + XFCE VM on VirtualBox. I can't start the graphical session in my VM with startx after running pacman -Syu. Here is the Xorg.0.log:
[ 130.239] X.Org X Server 1.21.1.16 X Protocol Version 11, Revision 0 [ 130.239] Current Operating System: Linux ArtixLinux 6.14.6-artix1-1 #1 SMP PREEMPT_DYNAMIC Sun, 11 May 2025 14:31:23 +0000 x86_64 [ 130.239] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=dc6bbcaa-ccd4-4747-90bf-2663c2c9f58b rw loglevel=3 quiet [ 130.239] [ 130.239] Current version of pixman: 0.46.0 [ 130.239] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 130.239] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 130.239] (==) Log file: "/home/username/.local/share/xorg/Xorg.0.log", Time: Mon May 26 11:38:21 2025 [ 130.322] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 130.368] (==) No Layout section. Using the first Screen section. [ 130.368] (==) No screen section available. Using defaults. [ 130.368] (**) |-->Screen "Default Screen Section" (0) [ 130.368] (**) | |-->Monitor "<default monitor>" [ 130.368] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 130.368] (**) Allowing byte-swapped clients [ 130.368] (==) Automatically adding devices [ 130.368] (==) Automatically enabling devices [ 130.368] (==) Automatically adding GPU devices [ 130.368] (==) Automatically binding GPU devices [ 130.368] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 130.391] (WW) The directory "/usr/share/fonts/misc" does not exist. [ 130.391] Entry deleted from font path. [ 130.391] (WW) The directory "/usr/share/fonts/TTF" does not exist. [ 130.391] Entry deleted from font path. [ 130.391] (WW) The directory "/usr/share/fonts/OTF" does not exist. [ 130.391] Entry deleted from font path. [ 130.391] (WW) The directory "/usr/share/fonts/Type1" does not exist. [ 130.391] Entry deleted from font path. [ 130.440] (==) FontPath set to: /usr/share/fonts/100dpi, /usr/share/fonts/75dpi [ 130.440] (==) ModulePath set to "/usr/lib/xorg/modules" [ 130.440] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 130.440] (II) Module ABI versions: [ 130.440] X.Org ANSI C Emulation: 0.4 [ 130.440] X.Org Video Driver: 25.2 [ 130.440] X.Org XInput driver : 24.4 [ 130.440] X.Org Server Extension : 10.0 [ 130.457] (++) using VT number 1
[ 130.461] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31 [ 130.464] (II) xfree86: Adding drm device (/dev/dri/card0) [ 130.465] (II) Platform probe for /sys/devices/pci0000:00/0000:00:02.0/drm/card0 [ 130.466] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 13 paused 0 [ 130.471] (--) PCI:*(0@0:2:0) 15ad:0405:15ad:0405 rev 0, Mem @ 0xe0000000/268435456, 0xf0000000/2097152, I/O @ 0x0000d010/16, BIOS @ 0x????????/131072 [ 130.471] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) [ 130.471] (II) LoadModule: "glx" [ 130.494] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 130.628] (II) Module glx: vendor="X.Org Foundation" [ 130.628] compiled for 1.21.1.16, module version = 1.0.0 [ 130.628] ABI class: X.Org Server Extension, version 10.0 [ 130.628] (==) Matched vmware as autoconfigured driver 0 [ 130.628] (==) Matched modesetting as autoconfigured driver 1 [ 130.628] (==) Matched fbdev as autoconfigured driver 2 [ 130.628] (==) Matched vesa as autoconfigured driver 3 [ 130.628] (==) Assigned the driver to the xf86ConfigLayout [ 130.628] (II) LoadModule: "vmware" [ 130.661] (II) Loading /usr/lib/xorg/modules/drivers/vmware_drv.so [ 130.675] (II) Module vmware: vendor="X.Org Foundation" [ 130.675] compiled for 1.21.1.16, module version = 13.4.0 [ 130.675] Module class: X.Org Video Driver [ 130.675] ABI class: X.Org Video Driver, version 25.2 [ 130.675] (II) LoadModule: "modesetting" [ 130.675] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 130.726] (II) Module modesetting: vendor="X.Org Foundation" [ 130.726] compiled for 1.21.1.16, module version = 1.21.1 [ 130.726] Module class: X.Org Video Driver [ 130.726] ABI class: X.Org Video Driver, version 25.2 [ 130.726] (II) LoadModule: "fbdev" [ 130.726] (WW) Warning, couldn't open module fbdev [ 130.726] (EE) Failed to load module "fbdev" (module does not exist, 0) [ 130.726] (II) LoadModule: "vesa" [ 130.727] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so [ 130.743] (EE) Failed to load /usr/lib/xorg/modules/drivers/vesa_drv.so: /usr/lib/xorg/modules/drivers/vesa_drv.so: undefined symbol: VBESetModeParameters [ 130.743] (EE) Failed to load module "vesa" (loader failed, 0) [ 130.743] (II) vmware: driver for VMware SVGA: vmware0405, vmware0710 [ 130.743] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 130.743] xf86EnableIO: failed to enable I/O ports 0000-03ff (Operation not permitted) [ 130.743] (WW) Falling back to old probe method for modesetting [ 130.743] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support [ 130.743] (II) vmware(0): Driver was compiled without KMS- and 3D support. [ 130.743] (WW) vmware(0): Disabling 3D support. [ 130.743] (WW) vmware(0): Disabling Render Acceleration. [ 130.743] (WW) vmware(0): Disabling RandR12+ support. [ 130.743] (--) vmware(0): VMware SVGA regs at (0xd010, 0xd011) [ 130.743] (II) Loading sub module "vgahw" [ 130.743] (II) LoadModule: "vgahw" [ 130.743] (II) Loading /usr/lib/xorg/modules/libvgahw.so [ 130.755] (II) Module vgahw: vendor="X.Org Foundation" [ 130.755] compiled for 1.21.1.16, module version = 0.1.0 [ 130.755] ABI class: X.Org Video Driver, version 25.2 [ 130.755] (EE) [ 130.755] (EE) Backtrace: [ 130.804] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 130.804] (EE) 0: /usr/lib/Xorg (?+0x0) [0x5aac138a8d4d] [ 130.805] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 130.805] (EE) 1: /usr/lib/libc.so.6 (?+0x0) [0x7fb1de77b600] [ 130.806] (EE) 2: /usr/lib/libpciaccess.so.0 (pci_io_write8+0x7) [0x7fb1dead4927] [ 130.807] (EE) 3: /usr/lib/xorg/modules/libvgahw.so (vgaHWSaveColormap+0x49) [0x7fb1ddccdbf9] [ 130.807] (EE) 4: /usr/lib/xorg/modules/libvgahw.so (vgaHWSave+0x35) [0x7fb1ddccfd75] [ 130.807] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 130.807] (EE) 5: /usr/lib/xorg/modules/drivers/vmware_drv.so (?+0x0) [0x7fb1ddfb090c] [ 130.808] (EE) 6: /usr/lib/Xorg (InitOutput+0x1702) [0x5aac138c6502] [ 130.809] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 130.809] (EE) 7: /usr/lib/Xorg (?+0x0) [0x5aac137868ce] [ 130.810] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 130.810] (EE) 8: /usr/lib/libc.so.6 (?+0x0) [0x7fb1de76552e] [ 130.811] (EE) 9: /usr/lib/libc.so.6 (__libc_start_main+0x8a) [0x7fb1de7655ea] [ 130.811] (EE) 10: /usr/lib/Xorg (_start+0x25) [0x5aac13787f15] [ 130.811] (EE) [ 130.811] (EE) Segmentation fault at address 0x8 [ 130.811] (EE) Fatal server error: [ 130.811] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 130.812] (EE) [ 130.812] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 130.812] (EE) Please also check the log file at "/home/username/.local/share/xorg/Xorg.0.log" for additional information. [ 130.812] (EE) [ 130.822] (EE) Server terminated with error (1). Closing log file.
Title: Re: Unable to Start Graphical Session
Post by: nous on 26 May 2025, 10:53:12
I think that the recent update to the mesa package may be the cause of your problems. I am not totally sure, but it could be worth investigating. https://forum.artixlinux.org/index.php/topic,8177.msg48874.html#msg48874 (https://forum.artixlinux.org/index.php/topic,8177.msg48874.html#msg48874)
Does downgrading mesa solve the issue for people running VMs?
I downgraded mesa from mesa-1:25.1.1-1 to mesa-1:25.0.5-1 but the problem is still there and I still can't start the graphical session with startx. Reinstalling the guest additions and downgrading xf86-video-vesa-2.6.0-2 to xf86-video-vesa-2.6.0-1 also didn't solve the issue.
Title: Re: Unable to Start Graphical Session
Post by: Phosphate5 on 26 May 2025, 12:18:38
I fixed my problem by downgrading mesa-1:25.1.1-1 to mesa-1:25.0.5-1 and xf86-video-vmware 13.4.0-4 to xf86-video-vmware 13.4.0-3.
Title: Re: Unable to Start Graphical Session
Post by: nous on 26 May 2025, 12:26:23
@Phosphate5 To clarify, downgrading only xf86-video-vmware wasn't enough?
Title: Re: Unable to Start Graphical Session
Post by: Phosphate5 on 26 May 2025, 12:42:10
I think that the recent update to the mesa package may be the cause of your problems. I am not totally sure, but it could be worth investigating. https://forum.artixlinux.org/index.php/topic,8177.msg48874.html#msg48874 (https://forum.artixlinux.org/index.php/topic,8177.msg48874.html#msg48874)
Does downgrading mesa solve the issue for people running VMs?
I fixed my problem by downgrading mesa-1:25.1.1-1 to mesa-1:25.0.5-1 and xf86-video-vmware 13.4.0-4 to xf86-video-vmware 13.4.0-3.
I'll have to try that out in a sec...
EDIT -- That worked :)
Title: Re: Unable to Start Graphical Session
Post by: tsedek1 on 28 May 2025, 17:45:42
Is it a game of Cat and Mouse? My Desktop disappears everyday. I reinstall, I'm not using any VM.
My graphical environment disappears everyday. Sometimes it is unbootable, not proceeding to 'local', and sometimes it boots to the Desktop devoid of everything except the desktop icons and mouse arrow, all other graphic elements missing. When my system started becoming difficult, about 5 hours being online, there haven't been any internet updates. All updates are done offline. I have not performed an -Syu, so the mesa package in my default installation is still active, iso kernel 6.13.7, 3-05-25 I believe. The iso version of Mesa: mesa 1:25.0.1-2
Mousepad wouldn't run. I just used it, why did it stop working. In a terminal I ran from the bin directory:
The error said "Cannot open file: shared libraries libxml2.so..." libxml2 is not a dependency of mousepad according to the Artix package dependency list? How would 'libxml2.so' be causing mousepad a problem?
Updates - Offline mostly I have pkg backed up to a flash drive. Odd thing, emacs-nox install, which uses libxml2 (see mousepad above), has as a dependency requirement of 'alpmtmp.randomstring' which, the 'randomstring' part changes with each attempt of installation. What is Aggressive Link Power Management and why does emacs need it? Can power management be used to gain unprivileged access?
Title: Re: Unable to Start Graphical Session
Post by: XyzzyX on 28 May 2025, 18:25:49
The error said "Cannot open file: shared libraries libxml2.so..." libxml2 is not a dependency of mousepad according to the Artix package dependency list? How would 'libxml2.so' be causing mousepad a problem?
Mousepad depends on gtksourceview4 which depends on libxml2.
Title: Re: Unable to Start Graphical Session
Post by: Phosphate5 on 28 May 2025, 23:45:25
Is it a game of Cat and Mouse? My Desktop disappears everyday. I reinstall, I'm not using any VM.
Sometimes, being on the bleeding edge is painful, but to be honest, your desktop breaking every day is a bit odd. Maybe you did a partial upgrade, and that is the root of the problems you are experiencing now. If your system breaks frequently, I think you should consider using timeshift. Additionally, most of the times, it is easy to fix problems caused by new software packages by downgrading to the last working versions. These days, updates breaking things is not specific to Linux and Windows users also frequently experience various issues due to buggy updates.
Is it a game of Cat and Mouse? My Desktop disappears everyday. I reinstall, I'm not using any VM.
Sometimes, being on the bleeding edge is painful, but to be honest, your desktop breaking every day is a bit odd.
It has nothing to do with being on the bleeding edge of anything. The desktop breaking every day is not a bit odd. It is not possible... not with Artix, or any other distro. It remains an end user problem. We should close this thread before it turns off into a black hole.
Title: Re: Unable to Start Graphical Session
Post by: tsedek1 on 29 May 2025, 12:50:32
Sometimes, being on the bleeding edge is painful, but to be honest, your desktop breaking every day is a bit odd. Maybe you did a partial upgrade, and that is the root of the problems you are experiencing now. If your system breaks frequently, I think you should consider using timeshift. Additionally, most of the times, it is easy to fix problems caused by new software packages by downgrading to the last working versions. These days, updates breaking things is not specific to Linux and Windows users also frequently experience various issues due to buggy updates. ... Have you tried the LTS Linux kernel? Maybe, the LTS kernel can solve your graphical issues.
Yes, I have tried the LTS Kernel, The Mouse disappeared. "The Mouse" is the Desktop Environment, XFCE. It's a common pattern to these activities occurring. My ability to find where the fault is, is limited. Someone was leaving messages in my audit.log file, using find, then cat, then gdm (virtual mouse, not gnome). Since I have made changes, the methods required to traverse the internal structure has changed. The common stuff: Xorg, OpenGL, Denial Of Service by filling up the RAM, drop JS persistence files in the browser, hook the *dm to start on boot. The malware being used is Indian in origin, I've had overlays on my Youtube feed of Bali Porn.
After these infiltrations, DoS and infection, people sit next to me and tell me directly "F**k You." They want me to know they're doing it. I smile and re-install. A man can't serve two masters, he will love the one and hate the other. They hate the One I love.
My current Fresh install method: iso pacman -U xyz.zst xyz=
[omniverse] Server = https://artix.sakamoto.pl/omniverse/$arch Server = https://eu-mirror.artixlinux.org/omniverse/$arch Server = https://omniverse.artixlinux.org/$arch
I haven't built a script yet. I spend so much time reinstalling, I don't have the time yet. When I can catch my breath, then I'll learn to make a bash script. I'm also trying to learn how to review the log files to get to the heart of where the problem is, but I reinstall everyday so, it makes learning difficult.
When installing Emacs-nox offline with 2 files missing, I get a reason that 'alpmtmp.randomstring' is required and wasn't downloaded.
The files I learned were dependencies: file://var/cache/pacman/pkg/libisl-0.27-1-x86_64.pkg.tar.zst file://var/cache/pacman/pkg/libmpc-1.3.1-2-x86_64.pkg.tar.zst
When I include these files, I don't see any download activity involving pacman and 'alpmtmp.randomstring'.
Title: Re: Unable to Start Graphical Session
Post by: gripped on 29 May 2025, 15:14:06
My ability to find where the fault is, is limited.
That's the most pertinent thing you wrote. It would be a struggle for someone with vast experience to keep a pacman based distro working properly using nothing but pacman -U and , possibly stale, backups of packages. What's the point ? You have to have downloaded the packages at some point and the packages are all signed so updating online is fine. I don't accept your repeated claims of getting hacked constantly within minutes or hours of reinstalling. As I've said before you sound paranoid to me. And that's not great.
If it was that easy we'd all be hacked. I don't rule out the possibility that there are backdoors / exploits in Linux that are known to nation state security services etc. I don't think it is the case (I hope not) but it can't be ruled out. But if they were known to college students, or whoever it is that shares your open wifi, then they would be common knowledge very quickly and fixed.
If you really are getting hacked so quickly then either it's something you are doing post install or I suppose it's possible, though I think unlikely, there's a rootkit in your UEFI. And rather than the constant reinstalling you'd maybe be better of building an iso image with the programs you want as part of it the image and just booting from the image. Keep your personal files on a usb drive or something. And you can md5sum your image after creating it to ensure those hackers haven't modified your iso image.
Or you could only ever browse the web in a VM and use snapshots to revert any changes the hackers have made after each session.
Title: Re: Unable to Start Graphical Session
Post by: tsedek1 on 29 May 2025, 18:27:38
My ability to find where the fault is, is limited.
That's the most pertinent thing you wrote. It would be a struggle for someone with vast experience to keep a pacman based distro working properly using nothing but pacman -U and , possibly stale, backups of packages. What's the point ? You have to have downloaded the packages at some point and the packages are all signed so updating online is fine. I don't accept your repeated claims of getting hacked constantly within minutes or hours of reinstalling. As I've said before you sound paranoid to me. And that's not great.
If it was that easy we'd all be hacked. I don't rule out the possibility that there are backdoors / exploits in Linux that are known to nation state security services etc. I don't think it is the case (I hope not) but it can't be ruled out. But if they were known to college students, or whoever it is that shares your open wifi, then they would be common knowledge very quickly and fixed.
If you really are getting hacked so quickly then either it's something you are doing post install or I suppose it's possible, though I think unlikely, there's a rootkit in your UEFI. And rather than the constant reinstalling you'd maybe be better of building an iso image with the programs you want as part of it the image and just booting from the image. Keep your personal files on a usb drive or something. And you can md5sum your image after creating it to ensure those hackers haven't modified your iso image.
Or you could only ever browse the web in a VM and use snapshots to revert any changes the hackers have made after each session.
I grew up with the CIA. A friend of the family works Asia. An apartment he was running with Military personnel, collected all of the communications in the neighborhood. 6" bundle of communications cables, including a fibre optic cable, went from the telephone pole directly through the wall into the first floor of the apartment. He was the first one I knew to use Google Voice to prevent people from getting his cell phone number and doing a sim jack. I don't like the CIA. They like to stab each other in the back for fun. "I'm testing how resilient he is." Waste of Dog Shit, they are.
I'm working on learning to read the log files. That way can differentiate between potential buggy software issues and someone living off the land inside my box. I have enough audit.log files, one shows someone fuzzing processes in my system, from a shell running echo ccccccccccccccccc... at a firefox process. That is empirical evidence, BTW. :wink: :nod:
When my skill is not as advanced as yours, how can I determine when there is a compromised repo servo providing 'extra files', or a local network replacing legitimate files like zst and zst.sig in transit? The 'cafe' where I hangout is a National Governement Institution. If any one has government level tools, it would be them.
Currently, emacs-nox seems to be the best suspect for buggy software, it and it's dependents. When the desktop disappears, there isn't much I can do except drop into a terminal, or reboot into a terminal.
Title: Re: Unable to Start Graphical Session
Post by: gripped on 29 May 2025, 19:44:12
When my skill is not as advanced as yours, how can I determine when there is a compromised repo servo providing 'extra files', or a local network replacing legitimate files like zst and zst.sig in transit?
That's what the signing keys are for. If a third party alters a package pacman won't install it. Unless the bad actor tricks you into adding their key to the keyring. Or changing the SigLevel in pacman.conf https://wiki.archlinux.org/title/Pacman/Package_signing
Title: Re: Unable to Start Graphical Session
Post by: mrbrklyn on 30 May 2025, 00:40:13
That's the most pertinent thing you wrote. It would be a struggle for someone with vast experience to keep a pacman based distro working properly using nothing but pacman -U and , possibly stale, backups of packages. What's the point ? You have to have downloaded the packages at some point and the packages are all signed so updating online is fine. I don't accept your repeated claims of getting hacked constantly within minutes or hours of reinstalling. As I've said before you sound paranoid to me. And that's not great.
If it was that easy we'd all be hacked. I don't rule out the possibility that there are backdoors / exploits in Linux that are known to nation state security services etc. I don't think it is the case (I hope not) but it can't be ruled out. But if they were known to college students, or whoever it is that shares your open wifi, then they would be common knowledge very quickly and fixed.
If you really are getting hacked so quickly then either it's something you are doing post install or I suppose it's possible, though I think unlikely, there's a rootkit in your UEFI. And rather than the constant reinstalling you'd maybe be better of building an iso image with the programs you want as part of it the image and just booting from the image. Keep your personal files on a usb drive or something. And you can md5sum your image after creating it to ensure those hackers haven't modified your iso image.
Or you could only ever browse the web in a VM and use snapshots to revert any changes the hackers have made after each session.
I grew up with the CIA. A friend of the family works Asia. An apartment he was running with Military personnel, collected all of the communications in the neighborhood. 6" bundle of communications cables, including a fibre optic cable, went from the telephone pole directly through the wall into the first floor of the apartment. He was the first one I knew to use Google Voice to prevent people from getting his cell phone number and doing a sim jack. I don't like the CIA. They like to stab each other in the back for fun. "I'm testing how resilient he is." Waste of Dog Shit, they are.
I'm working on learning to read the log files. That way can differentiate between potential buggy software issues and someone living off the land inside my box. I have enough audit.log files, one shows someone fuzzing processes in my system, from a shell running echo ccccccccccccccccc... at a firefox process. That is empirical evidence, BTW. :wink: :nod:
When my skill is not as advanced as yours, how can I determine when there is a compromised repo servo providing 'extra files', or a local network replacing legitimate files like zst and zst.sig in transit? The 'cafe' where I hangout is a National Governement Institution. If any one has government level tools, it would be them.
Currently, emacs-nox seems to be the best suspect for buggy software, it and it's dependents. When the desktop disappears, there isn't much I can do except drop into a terminal, or reboot into a terminal.
And now it is all public on the open internet in a linux forum. We should shut this down as a matter or national security. Who knows what secrets will be spilled.
Title: Re: Unable to Start Graphical Session
Post by: gripped on 30 May 2025, 02:59:33
Title: Re: Unable to Start Graphical Session
Post by: mrbrklyn on 30 May 2025, 05:34:57
I'm just sick of the board being trolled... This guy is like one of the old professional trolls on usenet. They live for this.
Title: Re: Unable to Start Graphical Session
Post by: TopHatProductions115 on 30 May 2025, 05:44:07
Could someone lock this thread? I initially hoped to leave this open until working versions of the affected packages were released, but I don't want this thread to get derailed to the point of being useless to future readers...
Title: Re: Unable to Start Graphical Session
Post by: Phosphate5 on 30 May 2025, 11:38:22
Could someone lock this thread? I initially hoped to leave this open until working versions of the affected packages were released, but I don't want this thread to get derailed to the point of being useless to future readers...
Please mark this thread as solved. We can do nothing for now except using the last working versions of mesa and xf86-video-vmware and waiting for a fix to be released. It's too bad that this thread got derailed.