Hello,
I've recently had an issue with my laptop that was overheating, which required a visit to a technician for some cleaning, replacing the thermal paste and fixing the lid that was not closing correctly.
Once everything was fixed, it now works fine most of the time, but before the repair happened, I installed KDE while already having gnome and i3 installed in my Debian 11 Bullseye that was working perfectly by then.
The problem is that now, every first time I boot the pc it freezes randomly during the process, sometimes it happens after I enter my credentials, but sometimes not even the initial login screen is displayed.
(The speakers are also presenting an issue where sometimes the sound gets distorted, but this could have been caused during an overheating episode, let's keep that for later.)
After rebooting manually once, or twice it boots normally and I'm able to use it without problems.
This is happening constantly for one week, could you help me diagnose what's happening?
Here's some info:
```
lsb_release -a
uname -rlscpulspci -k | grep -EA3 'VGA|3D'free -hlsblk```
Some error logs from journalctl as of today:X session errors as of today:
EDIT: Just confirmed with the technician that during the last visit he just repaired the lid, that was not closing properly, so this is most likely a software issue.
Thanks in advance.
I've recently had an issue with my laptop that was overheating, which required a visit to a technician for some cleaning, replacing the thermal paste and fixing the lid that was not closing correctly.
Once everything was fixed, it now works fine most of the time, but before the repair happened, I installed KDE while already having gnome and i3 installed in my Debian 11 Bullseye that was working perfectly by then.
The problem is that now, every first time I boot the pc it freezes randomly during the process, sometimes it happens after I enter my credentials, but sometimes not even the initial login screen is displayed.
(The speakers are also presenting an issue where sometimes the sound gets distorted, but this could have been caused during an overheating episode, let's keep that for later.)
After rebooting manually once, or twice it boots normally and I'm able to use it without problems.
This is happening constantly for one week, could you help me diagnose what's happening?
Here's some info:
```
lsb_release -a
Code:
Distributor ID:DebianDescription:Debian GNU/Linux 11 (bullseye)Release:11Codename:bullseyeCode:
5.10.0-33-amd64Code:
Arquitetura: x86_64Modo(s) operacional da CPU: 32-bit, 64-bitOrdem dos bytes: Little EndianTamanhos de endereço: 39 bits physical, 48 bits virtualCPU(s): 4Lista de CPU(s) on-line: 0-3Thread(s) per núcleo: 1Núcleo(s) por soquete: 4Soquete(s): 1Nó(s) de NUMA: 1ID de fornecedor: GenuineIntelFamília da CPU: 6Modelo: 158Nome do modelo: Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHzStep: 9CPU MHz: 800.087CPU MHz máx.: 3500,0000CPU MHz mín.: 800,0000BogoMIPS: 4999.90Virtualização: VT-xcache de L1d: 128 KiBcache de L1i: 128 KiBcache de L2: 1 MiBcache de L3: 6 MiBCPU(s) de nó0 NUMA: 0-3Vulnerability Gather data sampling: Mitigation; MicrocodeVulnerability Itlb multihit: KVM: Mitigation: VMX disabledVulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT disabledVulnerability Mds: Mitigation; Clear CPU buffers; SMT disabledVulnerability Meltdown: Mitigation; PTIVulnerability Mmio stale data: Mitigation; Clear CPU buffers; SMT disabledVulnerability Reg file data sampling: Not affectedVulnerability Retbleed: Mitigation; IBRSVulnerability Spec rstack overflow: Not affectedVulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccompVulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitizationVulnerability Spectre v2: Mitigation; IBRS, IBPB conditional, STIBP disabled, RSB filling, PBRSB-eIBRS Not affectedVulnerability Srbds: Mitigation; MicrocodeVulnerability Tsx async abort: Not affectedOpções: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_go od nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ss se3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave a vx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts h wp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilitiesCode:
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)Subsystem: Acer Incorporated [ALI] HD Graphics 630Kernel driver in use: i915Kernel modules: i915--01:00.0 VGA compatible controller: NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] (rev a1)Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile]Kernel driver in use: nvidiaKernel modules: nvidia--04:00.0 Non-Volatile memory controller: Realtek Semiconductor Co., Ltd. RTS5763DL NVMe SSD Controller (rev 01)Subsystem: Realtek Semiconductor Co., Ltd. RTS5763DL NVMe SSD ControllerKernel driver in use: nvmeKernel modules: nvmCode:
total used free shared buff/cache availableMem.: 23Gi 5,0Gi 14Gi 611Mi 3,5Gi 17GiSwap: 25Gi 0B 25GiCode:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTsda 8:0 0 931,5G 0 disk└─sda1 8:1 0 931,5G 0 partnvme0n1 259:0 0 476,9G 0 disk├─nvme0n1p1 259:1 0 451,2G 0 part│ └─luks-4915ea5d-eab3-4d5a-bc41-e76a75b88493 253:0 0 451,2G 0 crypt /└─nvme0n1p2 259:2 0 25,7G 0 part └─luks-5851b5f7-ef93-48de-afa6-3a287628378b 253:1 0 25,7G 0 crypt [SWAP]Some error logs from journalctl as of today:
Code:
```fev 10 07:18:51 slot-machine systemd-xdg-autostart-generator[3948]: Not generating service for XDG autostart app-Flameshot-autostart.service, error parsing Exec= line: No such file or directoryfev 10 07:18:51 slot-machine systemd-xdg-autostart-generator[3948]: Not generating service for XDG autostart app-org.gnome.DejaDup.Monitor-autostart.service, error parsing Exec= line: No such file or directoryfev 10 07:18:51 slot-machine systemd-xdg-autostart-generator[3948]: Not generating service for XDG autostart app-gsettings\x2ddata\x2dconvert-autostart.service, error parsing Exec= line: No such file or directoryfev 10 07:18:51 slot-machine systemd-xdg-autostart-generator[3948]: Not generating service for XDG autostart app-gnome\x2dsoftware\x2dservice-autostart.service, error parsing Exec= line: No such file or directoryfev 10 07:18:51 slot-machine systemd-xdg-autostart-generator[3948]: Not generating service for XDG autostart app-print\x2dapplet-autostart.service, error parsing Exec= line: No such file or directoryfev 10 07:18:51 slot-machine systemd-xdg-autostart-generator[3948]: Not generating service for XDG autostart app-orca\x2dautostart-autostart.service, error parsing Exec= line: No such file or directoryfev 10 07:18:51 slot-machine pipewire[3950]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such namefev 10 07:18:54 slot-machine org.kde.KScreen[4347]: kscreen.xcb.helper: Event Error: 147fev 10 07:19:21 slot-machine xdg-desktop-por[4113]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: ```Code:
```2025-02-10T10:18:57.279080+00:00 | proton.vpn.core.connection:461 | INFO | CONN:STATE_CHANGED | Disconnected (initial state)2025-02-10T10:18:57.622987+00:00 | proton.vpn.app.gtk.app:57 | INFO | APP:PROCESS_START | self=<app.App object at 0x7fec8fba1a00 (proton+vpn+app+gtk+app+App at 0xbcb60f0)>2025-02-10T10:18:57.729009+00:00 | proton.vpn.core.refresher.vpn_data_refresher:167 | INFO | APP.VPN_DATA_REFRESHER:ENABLE | VPN data refresher service enabled.2025-02-10T10:18:57.729263+00:00 | proton.vpn.core.refresher.vpn_data_refresher:175 | INFO | Next client config refresh scheduled in 0:00:002025-02-10T10:18:57.729407+00:00 | proton.vpn.core.refresher.vpn_data_refresher:184 | INFO | Next server list refresh scheduled in 0:00:002025-02-10T10:18:57.730028+00:00 | proton.vpn.core.refresher.vpn_data_refresher:193 | INFO | Next certificate refresh scheduled in 1 day, 6:07:52.2700162025-02-10T10:18:57.730171+00:00 | proton.vpn.core.refresher.vpn_data_refresher:202 | INFO | Next feature flags refresh scheduled in 0:00:002025-02-10T10:18:57.730536+00:00 | proton.vpn.session.utils:107 | INFO | API:REQUEST | '/vpn/v2/clientconfig'2025-02-10T10:18:57.731269+00:00 | proton.vpn.session.utils:107 | INFO | API:REQUEST | '/vpn/v1/logicals?SecureCoreFilter=all'2025-02-10T10:18:57.731437+00:00 | proton.vpn.session.utils:107 | INFO | API:REQUEST | '/feature/v2/frontend'2025-02-10T10:18:57.775144+00:00 | proton.vpn.app.gtk.services.reconnector.reconnector:94 | INFO | VPN reconnector enabled.2025-02-10T10:18:58.041143+00:00 | proton.vpn.app.gtk.controller:147 | INFO | APP.STARTUP:STARTUP_ACTIONS | Running startup actions2025-02-10T10:18:58.059832+00:00 | proton.vpn.app.gtk.widgets.vpn.vpn_widget:214 | INFO | APP.VPN:WIDGET_READY | VPN widget is ready (load time: 0.33 seconds)2025-02-10T10:18:58.060074+00:00 | proton.vpn.core.connection:354 | INFO | CONN.CONNECT:START | Server: BR#126 / Domain: node-br-07b.protonvpn.net / IP: 146.70.98.130 / OpenVPN Ports: ProtocolPorts(udp=[80, 51820, 4569, 1194, 5060], tcp=[443, 7770, 8443]) / WireGuard Ports: ProtocolPorts(udp=[443, 88, 1224, 51820, 500, 4500], tcp=[443]) / Protocol: wireguard / Backend: None2025-02-10T10:18:58.080143+00:00 | proton.vpn.app.gtk.services.reconnector.reconnector:174 | INFO | Network connectivity was detected.2025-02-10T10:18:58.408389+00:00 | proton.vpn.core.connection:373 | INFO | Using certificate based authentication for openvpn: False2025-02-10T10:18:58.409411+00:00 | proton.vpn.core.connection:461 | INFO | CONN:STATE_CHANGED | Connecting2025-02-10T10:18:58.951557+00:00 | proton.vpn.backend.linux.networkmanager.core.networkmanager:116 | INFO | VPN server REACHABLE.2025-02-10T10:18:59.119738+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.wireguard:291 | INFO | Waiting for agent status from node-br-07b.protonvpn.net...2025-02-10T10:18:59.119915+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.local_agent.listener:65 | INFO | Starting agent listener...2025-02-10T10:18:59.120022+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.local_agent.listener:74 | INFO | Establishing agent connection...2025-02-10T10:18:59.620735+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.local_agent.listener:76 | INFO | Agent connection established.2025-02-10T10:18:59.620866+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.local_agent.listener:85 | INFO | Requesting agent features...2025-02-10T10:18:59.621088+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.local_agent.listener:87 | INFO | Listening on agent connection...2025-02-10T10:18:59.830106+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.wireguard:301 | INFO | Agent status received: Status { state: CONNECTED, reason: None, features: Some(AgentFeatures { features: AgentFeatures { netshield_level: Some(0), randomized_nat: Some(true), split_tcp: Some(true), port_forwarding: Some(false), jail: Some(false), bouncing: Some("25") } }), connection_details: Some(ConnectionDetails { device_ip: "187.34.235.xxx", device_country: Some("BR"), server_ipv4: Some("146.70.98.156"), server_ipv6: Some("2a0d:5600:35:8::36") }) }2025-02-10T10:18:59.830539+00:00 | proton.vpn.core.connection:461 | INFO | CONN:STATE_CHANGED | Connected2025-02-10T10:19:00.114587+00:00 | proton.vpn.backend.linux.networkmanager.protocol.wireguard.wireguard:301 | INFO | Agent status received: Status { state: CONNECTED, reason: None, features: Some(AgentFeatures { features: AgentFeatures { netshield_level: Some(0), randomized_nat: Some(true), split_tcp: Some(true), port_forwarding: Some(false), jail: Some(false), bouncing: Some("24") } }), connection_details: Some(ConnectionDetails { device_ip: "187.34.235.xxx", device_country: Some("BR"), server_ipv4: Some("146.70.98.155"), server_ipv6: Some("2a0d:5600:35:8::35") }) }2025-02-10T10:19:00.115056+00:00 | proton.vpn.connection.states:125 | WARNING | CONN:WARNING | CONNECTED state received unexpected event: Connected2025-02-10T10:19:05.864269+00:00 | proton.vpn.session.utils:111 | INFO | API:RESPONSE | '/vpn/v2/clientconfig'2025-02-10T10:19:05.866007+00:00 | proton.vpn.core.refresher.client_config_refresher:67 | INFO | Next client config refresh scheduled in 2:38:07.1366152025-02-10T10:19:06.237859+00:00 | proton.vpn.session.utils:111 | INFO | API:RESPONSE | '/feature/v2/frontend'2025-02-10T10:19:06.239536+00:00 | proton.vpn.core.refresher.feature_flags_refresher:66 | INFO | Next feature flag refresh scheduled in 1:42:26.2606602025-02-10T10:19:07.904020+00:00 | proton.vpn.session.utils:111 | INFO | API:RESPONSE | '/vpn/v1/logicals?SecureCoreFilter=all'2025-02-10T10:19:09.086725+00:00 | proton.vpn.core.refresher.server_list_refresher:76 | INFO | Next server list refresh scheduled in 0:17:26.8886242025-02-10T10:19:09.577287+00:00 | proton.vpn.app.gtk.widgets.vpn.serverlist.serverlist:133 | INFO | Full server list widget update completed in 0.51 seconds.2025-02-10T10:36:38.822410+00:00 | proton.vpn.session.utils:107 | INFO | API:REQUEST | '/vpn/v1/loads'2025-02-10T10:36:42.386520+00:00 | proton.vpn.session.utils:111 | INFO | API:RESPONSE | '/vpn/v1/loads'2025-02-10T10:36:42.820520+00:00 | proton.vpn.core.refresher.server_list_refresher:76 | INFO | Next server list refresh scheduled in 0:14:48.7460952025-02-10T10:36:42.917501+00:00 | proton.vpn.app.gtk.widgets.vpn.serverlist.serverlist:150 | INFO | Partial server list widget update completed in 0.10 seconds.```Thanks in advance.
Statistics: Posted by marcusdavanco — 2025-02-10 10:43