[Closed]Login screen freezes the computer when I log in

This forum is dedicated to testing early releases and cauldron : Howtos, tips, tricks and user global feedback and thoughts...

Helpful tip :
For bugs tracking we use : https://bugs.mageia.org = The Mageia Bug Tracker
In this bug tracker you'll find already reported bugs and you'll be able to report those you have found....

Re: Login screen freezes the computer when I log in

Postby banjo » Jun 3rd, '21, 15:54

I set up this WiFi connection using the Network Center. I could not find anywhere in the Network Center a configuration item that allows me to tell it not to accept a hostname from the router. I assumed that the Network Center is the NetworkManager. Different tool?

I cannot find any NetworkManager.conf in /etc/NetworkManager. I cannot find the man page for networkmanager.conf on this system, although I found it online. There is no networkmanager binary in my search path. The "networkmanager" package in the MCC says that it is a daemon. Does it have a GUI?

What I did do was log into the router and change the Device Name of the IP lease to be identical with the name of the computer. So if the router sets a "new" hostname, it should be the same as the computer name.

Now I need to log in and out and reboot for a few weeks to see if the problem goes away.

Any other suggestions and/or info would be welcome.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby sturmvogel » Jun 3rd, '21, 16:57

Yes, networkmanager has a GUI. Here is the Wiki for it:
https://wiki.mageia.org/en/Switching_to_networkmanager
sturmvogel
 
Posts: 674
Joined: Jul 30th, '12, 00:39

Re: Login screen freezes the computer when I log in

Postby doktor5000 » Jun 3rd, '21, 17:04

banjo wrote:I assumed that the Network Center is the NetworkManager. Different tool?


Yes. You mentioned networkmanager. Network Center from MCC uses the normal Mageia tools, where our net_applet is responsible for the connection.
But that also offers the option to obtain a hostname via DHCP, see the bottom half of the second screenshot here: https://doc.mageia.org/mcc/8/en/content ... ml#d4e1620
Image
Should be the same for network center, it should be under the advanced button.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17603
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » Jun 3rd, '21, 17:47

Sorry for the confusion in the terminology. I didn't realize there were two systems. I will look into NetworkManager, although this computer does not roam, so having an automatic network manager would not be much benefit.

The Network Center screens are different from the images posted in the installation instructions, so I am not sure what to change.

The IP configuration screen does not have the Host Name field.

NetworkCenter1.png
NetworkCenter1.png (56.97 KiB) Viewed 3125 times


When I click on the Advanced button I get the following screen.

NetworkCenter2.png
NetworkCenter2.png (74.64 KiB) Viewed 3125 times


The outlined field, "DHCP host name" is ambiguous. It could be the name of the router hosting the DHCP, or it could be the hostname of this computer stored by DHCP. I presume that it refers to the host name of this computer as stored at DHCP. There does not appear to be an option, "Assign host name from DHCP server". I presume that is automatic if the field is left blank?
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby doktor5000 » Jun 3rd, '21, 19:00

banjo wrote:The outlined field, "DHCP host name" is ambiguous. It could be the name of the router hosting the DHCP, or it could be the hostname of this computer stored by DHCP.

No, it's not - as the DHCP server provides your configuration - you only need to provide the IP for the DHCP server, name resolution for the DHCP server itself is not necessary.
Cauldron is not for the faint of heart!
Caution: Hot, bubbling magic inside. May explode or cook your kittens!
----
Disclaimer: Beware of allergic reactions in answer to unconstructive complaint-type posts
User avatar
doktor5000
 
Posts: 17603
Joined: Jun 4th, '11, 10:10
Location: Leipzig, Germany

Re: Login screen freezes the computer when I log in

Postby banjo » Jun 3rd, '21, 20:43

OK. I put the computer name into the "DHCP host name" field and rebooted. The network connected fine. SDDM worked fine.

Since I cannot reproduce the problem on demand, all I can do now is continue using the system to see if the problem arises again.

Stay tuned.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » Jun 17th, '21, 16:58

I was just about to call this issue resolved when it happened again. The symptoms were the same; the mouse buttons and keyboard have no effect at all, and I have to shut down with the power button. The proper naming of the computer both locally and at the DHCP server has not fixed it.

The boot log shows the same end state with a loop of "plasma-polkit-agent.service: Failed with result 'timeout'." and "plasma-powerdevil.service: Failed with result 'timeout'." I think that is a symptom, not a cause.

My next attempt will be to log in as a new user for a while and see if the problem persists. It will take a couple of weeks at least.
Attachments
LoginFailureBootlog-20210616.txt
Boot log for failed login
(166.82 KiB) Downloaded 156 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » Jul 3rd, '21, 14:54

Yesterday, the login screen froze again while logging in as the new user. The symptoms are the same. The GUI freezes, and no keyboard or mouse buttons work. The clock also freezes. The computer itself is not frozen. It continues to try to start Plasma and eventually shuts down after it senses that I have held in the power button.

The log shows the system in a loop with errors "plasma-polkit-agent.service: Failed with result 'timeout'." and "plasma-powerdevil.service: Failed with result 'timeout'."

I still am not seeing any "Me too" replies, so it is probably something about this system that is causing it.

I'm not sure what to try next. A workaround would be to use LightDM instead of SDDM, but doing that will not help me trouble shoot this problem.

LoginFailureBootLog-20210702.txt
Login Freeze Boot log for July 2
(173.96 KiB) Downloaded 159 times
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: Login screen freezes the computer when I log in

Postby banjo » Oct 11th, '21, 16:57

I have not posted on this thread for a while, but I am not ignoring the problem. It is still happening on occasion. I have grabbed logs from each event. To get a feel for the frequency of the lockups, here are the dates of the events since my last post on July 3.

July 9
Aug 4
Aug 11
Sep 2
Sep 15
Sep 25
Oct 11

In the most recent lockup, today, there is a suspicious section of the log where SDDM throws errors and stops. The most suspicious error is

"sddm-greeter[3707]: QObject::installEventFilter(): Cannot filter events for objects in a different thread."

One effect that I am seeing is that no keyboard or mouse button events are getting through to SDDM. Coincidence?

Here is the log snippet, which shows the log from the SDDM errors to when I pushed the power button to reboot.

Code: Select all
Oct 11 10:17:54 BSKMageia systemd[1]: Started Session c1 of User sddm.
Oct 11 10:17:54 BSKMageia systemd[3694]: Started GnuPG cryptographic agent and passphrase cache.
Oct 11 10:17:54 BSKMageia systemd[3694]: Reached target Main User Target.
Oct 11 10:17:54 BSKMageia systemd[3694]: Startup finished in 718ms.
Oct 11 10:17:54 BSKMageia gpg-agent[3705]: gpg-agent (GnuPG) 2.3.2 starting in supervised mode.
Oct 11 10:17:54 BSKMageia gpg-agent[3705]: using fd 3 for std socket (/run/user/981/gnupg/S.gpg-agent)
Oct 11 10:17:54 BSKMageia gpg-agent[3705]: listening on: std=3 extra=-1 browser=-1 ssh=-1
Oct 11 10:17:54 BSKMageia systemd[3694]: Starting D-Bus User Message Bus...
Oct 11 10:17:55 BSKMageia systemd[3694]: Started D-Bus User Message Bus.
Oct 11 10:17:55 BSKMageia sddm-greeter[3707]: QFont::fromString: Invalid description '(empty)'
Oct 11 10:17:55 BSKMageia sddm-greeter[3707]: Loading file:///usr/share/sddm/themes/breeze/Main.qml...
Oct 11 10:17:56 BSKMageia sddm-greeter[3707]: QObject: Cannot create children for a parent that is in a different thread.
                                              (Parent is QGuiApplication(0x7ffd1489b540), parent's thread is QThread(0xb18d60), current thread is QThread(0xbad160)
Oct 11 10:17:56 BSKMageia sddm-greeter[3707]: QObject: Cannot create children for a parent that is in a different thread.
                                              (Parent is QGuiApplication(0x7ffd1489b540), parent's thread is QThread(0xb18d60), current thread is QThread(0xbad160)
Oct 11 10:17:56 BSKMageia sddm-greeter[3707]: QObject: Cannot create children for a parent that is in a different thread.
                                              (Parent is QGuiApplication(0x7ffd1489b540), parent's thread is QThread(0xb18d60), current thread is QThread(0xbad160)
Oct 11 10:17:56 BSKMageia sddm-greeter[3707]: QObject::installEventFilter(): Cannot filter events for objects in a different thread.
Oct 11 10:18:00 BSKMageia sddm-greeter[3707]: file:///usr/share/sddm/themes/breeze/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed
Oct 11 10:18:04 BSKMageia chronyd[971]: Selected source 73.239.136.185 (pool.ntp.org)
Oct 11 10:18:16 BSKMageia sddm-helper[5236]: PAM unable to dlopen(/usr/lib64/security/pam_cracklib.so): /usr/lib64/security/pam_cracklib.so: cannot open shared object file: No such file or directory
Oct 11 10:18:16 BSKMageia sddm-helper[5236]: PAM adding faulty module: /usr/lib64/security/pam_cracklib.so
Oct 11 10:18:17 BSKMageia sddm-helper[5236]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
Oct 11 10:18:17 BSKMageia sddm-helper[5236]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
Oct 11 10:18:17 BSKMageia systemd[1]: Created slice User Slice of UID 1001.
Oct 11 10:18:17 BSKMageia systemd[1]: Starting User Runtime Directory /run/user/1001...
Oct 11 10:18:17 BSKMageia systemd-logind[814]: New session c2 of user brian.
Oct 11 10:18:17 BSKMageia systemd[1]: Finished User Runtime Directory /run/user/1001.
Oct 11 10:18:17 BSKMageia systemd[1]: Starting User Manager for UID 1001...
Oct 11 10:18:17 BSKMageia sddm-helper[3689]: pam_unix(sddm-greeter:session): session closed for user sddm
Oct 11 10:18:17 BSKMageia systemd[1]: session-c1.scope: Deactivated successfully.
Oct 11 10:18:17 BSKMageia systemd-logind[814]: Session c1 logged out. Waiting for processes to exit.
Oct 11 10:18:17 BSKMageia systemd-logind[814]: Removed session c1.
Oct 11 10:18:17 BSKMageia systemd[5241]: Queued start job for default target Main User Target.
Oct 11 10:18:17 BSKMageia sddm-helper[5236]: pam_unix(sddm:session): session opened for user brian(uid=1001) by (uid=0)
Oct 11 10:18:17 BSKMageia systemd[5241]: Created slice User Application Slice.
Oct 11 10:18:17 BSKMageia sddm-helper[5236]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
Oct 11 10:18:17 BSKMageia systemd[5241]: Reached target Paths.
Oct 11 10:18:18 BSKMageia gpg-agent[5255]: gpg-agent (GnuPG) 2.3.2 starting in supervised mode.
Oct 11 10:18:18 BSKMageia gpg-agent[5255]: using fd 3 for std socket (/run/user/1001/gnupg/S.gpg-agent)
Oct 11 10:18:18 BSKMageia gpg-agent[5255]: listening on: std=3 extra=-1 browser=-1 ssh=-1
Oct 11 10:18:17 BSKMageia sddm-helper[5258]: pam_kwallet5: final socket path: /run/user/1001/kwallet5.socket
Oct 11 10:18:17 BSKMageia systemd[5241]: Reached target Timers.
Oct 11 10:18:17 BSKMageia systemd[5241]: Starting D-Bus User Message Bus Socket...
Oct 11 10:18:18 BSKMageia dbus-daemon[780]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.58' (uid=1001 pid=5266 comm="/usr/bin/hostnamectl --transient")
Oct 11 10:18:17 BSKMageia systemd[5241]: Listening on GnuPG cryptographic agent and passphrase cache.
Oct 11 10:18:17 BSKMageia systemd[5241]: Listening on Sound System.
Oct 11 10:18:17 BSKMageia systemd[5241]: Listening on D-Bus User Message Bus Socket.
Oct 11 10:18:17 BSKMageia systemd[5241]: Reached target Sockets.
Oct 11 10:18:17 BSKMageia systemd[5241]: Reached target Basic System.
Oct 11 10:18:17 BSKMageia systemd[1]: Started User Manager for UID 1001.
Oct 11 10:18:17 BSKMageia systemd[5241]: Started GnuPG cryptographic agent and passphrase cache.
Oct 11 10:18:17 BSKMageia systemd[5241]: Reached target Main User Target.
Oct 11 10:18:17 BSKMageia systemd[5241]: Startup finished in 497ms.
Oct 11 10:18:17 BSKMageia systemd[1]: Started Session c2 of User brian.
Oct 11 10:18:17 BSKMageia sddm-helper[5236]: Starting: "/usr/share/sddm/scripts/Xsession \"/usr/bin/startplasma-x11\""
Oct 11 10:18:18 BSKMageia systemd[1]: Starting Hostname Service...
Oct 11 10:18:18 BSKMageia dbus-daemon[780]: [system] Successfully activated service 'org.freedesktop.hostname1'
Oct 11 10:18:18 BSKMageia systemd[1]: Started Hostname Service.
Oct 11 10:18:19 BSKMageia systemd[5241]: Starting D-Bus User Message Bus...
Oct 11 10:18:19 BSKMageia systemd[5241]: Started D-Bus User Message Bus.
Oct 11 10:18:19 BSKMageia dbus-daemon[5331]: [session uid=1001 pid=5331] Successfully activated service 'org.freedesktop.systemd1'
Oct 11 10:18:19 BSKMageia systemd[5241]: /run/user/1001/systemd/generator.late/app-mac@autostart.service:17: WorkingDirectory= path is not absolute, ignoring:
Oct 11 10:18:19 BSKMageia systemd[5241]: /run/user/1001/systemd/generator.late/app-Wx@autostart.service:17: WorkingDirectory= path is not absolute, ignoring:
Oct 11 10:18:19 BSKMageia systemd[5241]: /run/user/1001/systemd/generator.late/app-NixieClock3@autostart.service:17: WorkingDirectory= path is not absolute, ignoring:
Oct 11 10:18:19 BSKMageia systemd[5241]: /run/user/1001/systemd/generator.late/app-NixieClock2@autostart.service:17: WorkingDirectory= path is not absolute, ignoring:
Oct 11 10:18:19 BSKMageia systemd[5241]: /run/user/1001/systemd/generator.late/app-MOBO@autostart.service:17: WorkingDirectory= path is not absolute, ignoring:
Oct 11 10:18:19 BSKMageia systemd[5241]: /run/user/1001/systemd/generator.late/app-DGEyes@autostart.service:17: WorkingDirectory= path is not absolute, ignoring:
Oct 11 10:18:20 BSKMageia systemd[5241]: Created slice User Background Tasks Slice.
Oct 11 10:18:20 BSKMageia systemd[5241]: Created slice User Core Session Slice.
Oct 11 10:18:20 BSKMageia systemd[5241]: Reached target Session services which should run early before the graphical session is brought up.
Oct 11 10:18:20 BSKMageia systemd[5241]: Starting KDE Config Module Initialization...
Oct 11 10:18:20 BSKMageia systemd[5241]: Starting KDE Daemon...
Oct 11 10:18:20 BSKMageia systemd[5241]: Starting KDE Session Management Server...
Oct 11 10:18:20 BSKMageia systemd[5241]: Starting KDE Window Manager...
Oct 11 10:18:20 BSKMageia ksmserver[5353]: Qt: Session management error: networkIdsList argument is NULL
Oct 11 10:18:20 BSKMageia systemd[5241]: Started KDE Daemon.
Oct 11 10:18:20 BSKMageia dbus-daemon[5331]: [session uid=1001 pid=5331] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by ':1.5' (uid=1001 pid=5353 comm="/usr/bin/ksmserver")
Oct 11 10:18:20 BSKMageia systemd[5241]: Starting KDE Global Shortcuts Server...
Oct 11 10:18:20 BSKMageia dbus-daemon[5331]: [session uid=1001 pid=5331] Successfully activated service 'org.kde.kglobalaccel'
Oct 11 10:18:20 BSKMageia systemd[5241]: Started KDE Global Shortcuts Server.
Oct 11 10:18:20 BSKMageia ksplashqml[5336]: file:///usr/share/plasma/look-and-feel/org.mageia.breeze.desktop/contents/splash/Splash.qml:89: ReferenceError: bottomRect is not defined
Oct 11 10:18:20 BSKMageia ksplashqml[5336]: file:///usr/share/plasma/look-and-feel/org.mageia.breeze.desktop/contents/splash/Splash.qml:88: ReferenceError: bottomRect is not defined
Oct 11 10:18:20 BSKMageia ksplashqml[5336]: file:///usr/share/plasma/look-and-feel/org.mageia.breeze.desktop/contents/splash/Splash.qml:89: ReferenceError: bottomRect is not defined
Oct 11 10:18:21 BSKMageia dbus-daemon[5331]: [session uid=1001 pid=5331] Activating via systemd: service name='ca.desrt.dconf' unit='dconf.service' requested by ':1.7' (uid=1001 pid=5352 comm="/usr/bin/kded5")
Oct 11 10:18:21 BSKMageia systemd[5241]: Starting User preferences database...
Oct 11 10:18:21 BSKMageia dbus-daemon[5331]: [session uid=1001 pid=5331] Successfully activated service 'ca.desrt.dconf'
Oct 11 10:18:21 BSKMageia systemd[5241]: Started User preferences database.
Oct 11 10:18:27 BSKMageia systemd[1]: Stopping User Manager for UID 981...
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopped target Main User Target.
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopping D-Bus User Message Bus...
Oct 11 10:18:27 BSKMageia gpg-agent[3705]: SIGTERM received - shutting down ...
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopping GnuPG cryptographic agent and passphrase cache...
Oct 11 10:18:27 BSKMageia gpg-agent[3705]: gpg-agent (GnuPG) 2.3.2 stopped
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopped D-Bus User Message Bus.
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopped GnuPG cryptographic agent and passphrase cache.
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopped target Basic System.
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopped target Paths.
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopped target Sockets.
Oct 11 10:18:27 BSKMageia systemd[3694]: Stopped target Timers.
Oct 11 10:18:27 BSKMageia systemd[3694]: Closed D-Bus User Message Bus Socket.
Oct 11 10:18:27 BSKMageia systemd[3694]: Closed GnuPG cryptographic agent and passphrase cache.
Oct 11 10:18:27 BSKMageia systemd[3694]: Closed Sound System.
Oct 11 10:18:27 BSKMageia systemd[3694]: Removed slice User Application Slice.
Oct 11 10:18:27 BSKMageia systemd[3694]: Reached target Shutdown.
Oct 11 10:18:27 BSKMageia systemd[3694]: Finished Exit the Session.
Oct 11 10:18:27 BSKMageia systemd[3694]: Reached target Exit the Session.
Oct 11 10:18:27 BSKMageia systemd[1]: user@981.service: Deactivated successfully.
Oct 11 10:18:27 BSKMageia systemd[1]: Stopped User Manager for UID 981.
Oct 11 10:18:27 BSKMageia systemd[1]: Stopping User Runtime Directory /run/user/981...
Oct 11 10:18:27 BSKMageia systemd[1]: run-user-981.mount: Deactivated successfully.
Oct 11 10:18:27 BSKMageia systemd[1]: user-runtime-dir@981.service: Deactivated successfully.
Oct 11 10:18:27 BSKMageia systemd[1]: Stopped User Runtime Directory /run/user/981.
Oct 11 10:18:27 BSKMageia systemd[1]: Removed slice User Slice of UID 981.
Oct 11 10:18:27 BSKMageia systemd[1]: user-981.slice: Consumed 1.152s CPU time.
Oct 11 10:18:48 BSKMageia systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Oct 11 10:19:10 BSKMageia chronyd[971]: Selected source 38.229.58.9 (pool.ntp.org)
Oct 11 10:19:36 BSKMageia systemd-logind[814]: Power key pressed.
Oct 11 10:19:36 BSKMageia systemd-logind[814]: Powering Off...
Oct 11 10:19:36 BSKMageia systemd-logind[814]: System is powering down.
Oct 11 10:19:36 BSKMageia sddm[3418]: Authentication error: "Process crashed"
Oct 11 10:19:36 BSKMageia sddm[3418]: Auth: sddm-helper crashed (exit code 15)
Oct 11 10:19:36 BSKMageia sddm[3418]: Authentication error: "Process crashed"
Oct 11 10:19:36 BSKMageia sddm[3418]: Auth: sddm-helper exited with 15
Oct 11 10:19:36 BSKMageia systemd[1]: Stopping Session c2 of User brian...


This is a fully updated Cauldron system.

Code: Select all
[brian@BSKMageia LoginFailure]$ inxi -b
System:    Host: BSKMageia Kernel: 5.14.11-desktop-2.mga9 x86_64 bits: 64 Desktop: KDE Plasma 5.22.3 Distro: Mageia 9 mga9
Machine:   Type: Desktop Mobo: ASUSTeK model: P5G41T-M LX PLUS v: Rev X.0x serial: <superuser required>
           BIOS: American Megatrends v: 0502 date: 10/21/2011
CPU:       Info: Dual Core Intel Core2 Duo E7300 [MCP] speed: 2427 MHz
Graphics:  Device-1: NVIDIA G94 [GeForce 9600 GT] driver: nouveau v: kernel
           Display: x11 server: Mageia X.org 1.21.0.99 driver: loaded: nouveau,v4l resolution: 1920x1080~60Hz
           OpenGL: renderer: NV94 v: 3.3 Mesa 21.2.3
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169
           Device-2: Realtek RTL-8100/8101L/8139 PCI Fast Ethernet Adapter driver: 8139too
           Device-3: Qualcomm Atheros AR9271 802.11n type: USB driver: ath9k_htc
Drives:    Local Storage: total: 465.76 GiB used: 34.08 GiB (7.3%)
Info:      Processes: 201 Uptime: 34m Memory: 3.84 GiB used: 1.57 GiB (40.9%) Shell: Bash inxi: 3.3.06
[brian@BSKMageia LoginFailure]$
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: [Closed]Login screen freezes the computer when I log in

Postby banjo » Nov 28th, '22, 16:21

I am marking this "Closed".

I have not seen the problem since June, and I have just mothballed the computer that was having the problem. I am now running Cauldron on a newer computer, and I have not seen this problem. So I think that it is OBE at this point.
If only the best bird sang, the forest would be a very quiet place.
User avatar
banjo
 
Posts: 445
Joined: May 4th, '11, 03:50
Location: Reading, Massachusetts

Re: [Closed]Login screen freezes the computer when I log in

Postby varrin » Dec 12th, '22, 17:49

I just stumbled on this thread sort of randomly. I may have had this problem for some time during a similar timeframe. I would have chimed in earlier had I found this but it was so intermittent that I didn't think it was worth trying to chase down. For me, too, it seems resolved as of some months ago. Just thought I'd mention it...

V-
varrin
 
Posts: 54
Joined: Nov 20th, '11, 03:12

Previous

Return to Testing : Alpha, Beta, RC and Cauldron

Who is online

Users browsing this forum: No registered users and 1 guest

cron