Bug 29287

Hi, thanks reporting this.

GUI session frozen can be a graphic driver issue or the shell to become unresponsive.
In your exposed case, you did mention 'lxpanel' which seems to consume nearly 100% of CPU time. This is unrelated to NEdit app.

@reporter, can you precise this:

 - what desktop do you use?

 - output of: $ inxi -SGxx

Source RPM: nedit 5.7 3.mga8 x86_64 => nedit-5.7-3.mga8.src.rpm
Status: NEW => NEEDINFO
CC: (none) => ouaurelien

The desktop I use is LXDE.

It could well be videocard related, but I encounter the problem only with NEdit ; the replaced PC (a HP) which had the same problems was driven with "Intel 810 and later" configuration. The new one is an Acer.

The old one had only 1 graphic card, the new one two.



$ inxi -SGxx
System:
  Host: localhost Kernel: 5.10.52-desktop-1.mga8 x86_64 bits: 64 
  compiler: gcc v: 10.3.0 Desktop: LXDE 0.10.1 wm: Openbox dm: LXDM 
  Distro: Mageia 8 mga8 
Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
  vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
  chip ID: 8086:0116 
  Device-2: NVIDIA GF108M [GeForce GT 540M] vendor: Acer Incorporated ALI 
  driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0df4 
  Device-3: Sunplus 1.3M HD WebCam type: USB driver: uvcvideo 
  bus ID: 1-1.3:3 chip ID: 04fc:2801 
  Display: x11 server: Mageia X.org 1.20.12 driver: intel,nouveau,v4l 
  resolution: 1366x768~60Hz s-dpi: 96 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 3000 (SNB GT2) 
  v: 3.3 Mesa 21.1.5 compat-v: 3.0 direct render: Yes

I have just installed nedit to try in this context; which I can do on LXDE & other desktops. Tomorrow...
("rectangular selection" caught my eye - something I have not seen since the old DOS editor TDE, which could do rectangular/block editing; but the lack of information on how to use nedit is daunting).

CC: (none) => lewyssmith

Well, I have had a go first under LxQt, then LXDE. In each case, doing an edit to a file, Ctrl/S to save it, mostly Alt/F4 to close Nedit, sometimes Ctrl/Q. I did this 2*20 times - without hitting your problem.
Under LXDE, lxpanel does not show in 'top'. Your high CPU usage by this points to a different poblem.

> I encounter the problem only with NEdit ;
> the replaced PC (a HP) which had the same problems
is clear enough. Comment 2 lists graphics differences. This program is one of those basic X applications like Xine. Could that have a bearing?

> The desktop I use is LXDE
Do you have another desktop to try this? If not, would you be willing to install one? (Beware: it is not recommended to remove an installed desktop, so you would be better off to keep it). LxQt and Xfce are lightweight.

Status: NEEDINFO => UNCONFIRMED
Ever confirmed: 1 => 0

Many thanks to Lewis and Aurélien for the suggestions. I installed LxQt. I'm actualy using 50% on the time LXDE and for the rest LxQt with similar profils of work (astronomical data reductions) and a few NEdit sessions each time ( with use of the rectangular selection tool :) ).

Results over the last few days:
- on LXDE, the freeze at the closing of NEdit were present with the same probability as before (a dozen of freezes).
- on LxQt, _no_ freeze appened.

So, there seems to be an incompatibility between NEdit and LXDE which is not present in the NEdit LXQt duo.

How can I help to debug this ? Enabling logfiles and how can I do it ?

Thank you for your willingness to try LxQt, and for researching more evidence.
My own error-free tests with both LXDE & LxQt suggest that the problem is not just desktop related: there may be a video factor, as Aurélien proposed.

Despite you having this problem on two different machines:
> the replaced PC (a HP) which had the same problems was driven with
> "Intel 810 and later" configuration.
>_
> The new one is an Acer
> Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics 
>  vendor: Acer Incorporated ALI driver: i915 v: kernel bus ID: 00:02.0 
>  chip ID: 8086:0116 
> Device-2: NVIDIA GF108M [GeForce GT 540M] vendor: Acer Incorporated ALI 
>  driver: nouveau v: kernel bus ID: 01:00.0 chip ID: 10de:0df4
they both have Intel graphics (which mine does not).
Are you able to chose exclusively between the Intel or Nvidia graphics, and (under LXDE only) report whether the problem happens with both?

Summary: Closing nedit freezes the GUI about 1 time over 10 => Closing nedit under LXDE (not other desktops) freezes the GUI about 1 time in 10
Source RPM: nedit-5.7-3.mga8.src.rpm => nedit-5.7-3.mga8.src.rpm, lxde-common-0.99.2-3.git20190224.2.mga8.src.rpm

(In reply to Lewis Smith from comment #6)

> Are you able to chose exclusively between the Intel or Nvidia graphics, and
> (under LXDE only) report whether the problem happens with both?

@ Raoul,

The above question was directed to you, can you please answer?

Hello,

I have to say that I'm super-bad at manipulating drivers and related things.

The portable with integrated display has one svga connector, and one hdmi one. The "paramètres d'écran" lists only one display: the one from the portable. When the mouse goes somethines out of the screen at the right and it's difficult the retrive it as if there is a second screen.

I'm really sorry, but I don't know how to do the things.

On LXQt, the problem encountered on LXDE never appened.

Cheers, Raoul

The issue is not the display, but [possibly] the graphics hardware/driver it uses. In fact, if you are already using the NVIDIA GF108M, then the problem is not related to Intel graphics; but it would be interesting to know whether in this case it still happens with the Intel graphics.

Alas, myself I have no experience of two graphics devices, nor how to switch between them. My guess is:
 MCC-Hardware-Configure graphics-Install graphics driver
 Graphics card-Customise
which in my case starts by highlighting the [only] card in use.

I cannot do more than CC somebody else who should be able to advise:
- How to ascertain which card & driver are in use;
- How to change to the other one
bearing in mind the 'test' is to see whether your problem relates to the use of Intel graphics (comment 1, comment 2, comment 6): does it only happen when Intel is used, but not with Nvidia?

Await some advice. Remember that if you manage to change the graphics hardware/driver to use, to re-boot for that to take effect.

[tmb : if you can suggest somebody else, please remove your CC and add them!]

CC: (none) => tmb

Closing as old, because there was no activity in this report for over half a year and, moreover, it was incomplete.

Raoul, if this problem persists, please ask for help in the forums to get more relevant information to be added to this report and then open this report with the additional information.

Status: UNCONFIRMED => RESOLVED
Resolution: (none) => OLD