Forum / NoMachine for Linux / Freezing issues on Wheezy
- This topic has 3 replies, 2 voices, and was last updated 2 years, 5 months ago by Britgirl.
-
AuthorPosts
-
June 4, 2022 at 16:26 #38792edgemirrorsParticipant
System info:
ii nomachine 7.9.2-1 amd64
Fast and secure remote access system3.2.0-4-amd64 #1 SMP Debian 3.2.82-1 x86_64 GNU/Linux (stock kernel)
lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.11 (wheezy)
Release: 7.11
Codename: wheezyThis is a headless VM, no Xorg running.
So finally I decided to upgrade to the latest 7.9 on a 64 bit wheezy server.
The problem is if I keep moving some windows around (doesn’t matter which app) it pulls 2 CPU cores to (nxnode.bin) 100% and the desktop freezes. Nothing useful in the nx logs.
If I disconnect reconnect I get white screen (everything is still frozen as it was).
I have to pkill -9 -u user to relogin.
To reproduce this bug all you really need to do is keep moving any window.
June 6, 2022 at 17:20 #38806BritgirlKeymasterWe just checked that specific Debian version just to make sure and everything works correctly. CPU usage is normal, sessions work fine.
Regarding the upgrade, we can’t be sure about what happened. Did you install the free version on top of the existing legacy free version? Please submit nxinstall.log and nxupdate.log which you can find in /usr/NX/var/log/.
After that, I recommend a complete uninstall of NoMachine and removing /usr/NX /etc/NX and /var/NX $HOME/.nx completely, then reinstalling version 7.9.2.
June 13, 2022 at 08:50 #38836edgemirrorsParticipantI have found the curlpit, the desktop I did not mention was Fluxbox 1.3.7. I have created a new user on that box and started migrating all the software (firefox, thunderbird, terminals etc) to the new user but they were not the problem it was the window manager itself.
There is something in the main config file (init) which causes this lockup/freeze issue. I have copied the keys file, menus file those are not the problem.
At this point it doesn’t even matter because I just started with a clean init config but still share this maybe someone find it useful some day.
So something in this config causes the issue.
session.screen0.slit.onhead: 0
session.screen0.slit.maxOver: false
session.screen0.slit.autoHide: false
session.screen0.slit.acceptKdeDockapps: true
session.screen0.slit.placement: RightBottom
session.screen0.slit.alpha: 255
session.screen0.slit.layer: Dock
session.screen0.toolbar.tools: prevworkspace, workspacename, nextworkspace, systemtray, iconbar, clock
session.screen0.toolbar.widthPercent: 100
session.screen0.toolbar.autoHide: false
session.screen0.toolbar.placement: TopCenter
session.screen0.toolbar.layer: Dock
session.screen0.toolbar.onhead: 1
session.screen0.toolbar.maxOver: false
session.screen0.toolbar.visible: true
session.screen0.toolbar.height: 0
session.screen0.toolbar.alpha: 255
session.screen0.clientMenu.usePixmap: true
session.screen0.window.focus.alpha: 255
session.screen0.window.unfocus.alpha: 255
session.screen0.tabs.usePixmap: true
session.screen0.tabs.maxOver: false
session.screen0.tabs.intitlebar: true
session.screen0.titlebar.left: Stick
session.screen0.titlebar.right: Minimize Maximize Close
session.screen0.menu.alpha: 255
session.screen0.iconbar.iconWidth: 128
session.screen0.iconbar.alignment: Right
session.screen0.iconbar.mode: {static groups} (workspace)
session.screen0.iconbar.usePixmap: true
session.screen0.iconbar.iconTextPadding: 10
session.screen0.tab.placement: TopLeft
session.screen0.tab.width: 64
session.screen0.windowMenu: /home/user1/.fluxbox/windowmenu
session.screen0.focusModel: ClickFocus
session.screen0.strftimeFormat: %d %b, %a %02k:%M:%S
session.screen0.workspaces: 1
session.screen0.rowPlacementDirection: LeftToRight
session.screen0.focusNewWindows: true
session.screen0.fullMaximization: false
session.screen0.tooltipDelay: 500
session.screen0.autoRaise: true
session.screen0.maxDisableResize: false
session.screen0.colPlacementDirection: TopToBottom
session.screen0.maxIgnoreIncrement: true
session.screen0.windowPlacement: RowMinOverlapPlacement
session.screen0.allowRemoteActions: false
session.screen0.workspaceNames: Workspace 1,Workspace 2,Workspace 3,Workspace 4,
session.screen0.defaultDeco: NORMAL
session.screen0.showwindowposition: false
session.screen0.workspacewarping: true
session.screen0.maxDisableMove: false
session.screen0.opaqueMove: false
session.screen0.noFocusWhileTypingDelay: 0
session.screen0.clickRaises: true
session.screen0.menuDelay: 200
session.screen0.edgeSnapThreshold: 10
session.screen0.tabFocusModel: ClickToTabFocus
session.styleFile: /usr/share/fluxbox/styles/Operation
session.colorsPerChannel: 4
session.autoRaiseDelay: 250
session.forcePseudoTransparency: false
session.ignoreBorder: false
session.appsFile: /home/user1/.fluxbox/apps
session.configVersion: 13
session.cacheLife: 5
session.slitlistFile: /home/user1/.fluxbox/slitlist
session.cacheMax: 200
session.tabsAttachArea: Window
session.tabPadding: 0
session.keyFile: ~/.fluxbox/keys
session.menuFile: ~/.fluxbox/menu
#session.styleOverlay: /home/user1/.fluxbox/overlay
session.doubleClickInterval: 250There are 2 other problems (which were not present with 3.5) with it, namely the toolbar does not extend to the end of the desktop and the windows extremely sensitive to move to other workspaces, meaning if you just move them a bit left or right it jumps all over the 4 workspaces but that does not belong to this topic as its not related to the crash.
July 15, 2022 at 17:22 #39546BritgirlKeymasterKnowing that you were using Fluxbox would have been useful 🙂
We found some issues with the Fluxbox WM which could be related to the problem you encountered. These have been queued up for investigation. I advise you to open a new topic if you have other issues.
-
AuthorPosts
This topic was marked as solved, you can't post.