ROSA Forum

Hi to all

System KDE 5 Rosa R6

im using Rosa R6 for some months and i love it very much so far. It seems to be the most stable Linux i ever used.


But since more or less thee weeks i have the following issue. sometimes on login after suspend mode i got black screen. Only the Pointer is visible. switch to shell with "alt + f2" works but startx not. I always have to reboot the system.

is the problem known?

Saludos from the canary islands

Used System:

cpu:
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 3013 MHz
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 3246 MHz
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 2894 MHz
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 2960 MHz
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 3312 MHz
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 2797 MHz
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 2550 MHz
Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz, 2933 MHz
keyboard:
Logitech USB Receiver
mouse:
Logitech USB Receiver
monitor:
Generic Monitor
graphics card:
nVidia VGA compatible controller
sound:
Intel Audio device
nVidia Audio device
storage:
Intel SATA controller
SATA controller
network:
eth0 Intel Ethernet controller
network interface:
eth0 Ethernet network interface
lo Loopback network interface
disk:
/dev/sda KINGSTON SH103S3
/dev/sdb KINGSTON SV300S3
/dev/sdc ST2000DM001-1CH1

cdrom:
/dev/sr0 HL-DT-ST BDDVDRW CH10LS28
usb controller:
Intel USB Controller
bridge:
Intel Host bridge
Intel PCI bridge
Intel 82801 PCI Bridge
Intel ISA bridge
hub:
Linux 3.14.53-nrj-desktop-1rosa-x86_64 ehci_hcd EHCI Host Controller
Hub
Linux 3.14.53-nrj-desktop-1rosa-x86_64 xhci_hcd xHCI Host Controller
Linux 3.14.53-nrj-desktop-1rosa-x86_64 xhci_hcd xHCI Host Controller
Linux 3.14.53-nrj-desktop-1rosa-x86_64 ehci_hcd EHCI Host Controller
Hub
Linux 3.14.53-nrj-desktop-1rosa-x86_64 xhci_hcd xHCI Host Controller

memory:
Main Memory
firewire controller:
VIA FireWire (IEEE 1394)

Logitech USB Receiver
/dev/input/event17 Logitech HD Pro Webcam C920

any idea whats happening? I think it must be some KDE + issue?

beatosch писал(а):any idea whats happening? I think it must be some KDE + issue?

Does the problem happen even after the recent updates?
I mean, we have recently issued an update for the kernel (to version 4.1.13) with lots of fixes and such.

If it does happen even after all the updates are installed, then you could try the following.

Is it possible to switch to a virtual console (e.g., with ctrl-alt-f2) after the problem happens? Or, connect to that system via SSH? If so, could you upload the diagnostics info to us with hw-probe tool? See https://linux-hardware.org/?show=check

If that is not possible, please reboot the system and then use hw-probe, the tool will also collect the logs from the previous boot that we need to analyze.

By the way, sorry for the delay.

The activity on our forums, esp. among the Russian-speaking users, is quite high, so my colleagues and I may easily miss some problem reports there.

A more reliable way to report problems is via our bug tracker, http://bugs.rosalinux.ru/enter_bug.cgi? ... top%20Bugs
If you do not know which component the problem belongs to, select "Main packages" component there.

This way, the problem reports will not go unnoticed.