starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #2447] [GMOD] SRCDS Console Scroll Up #1803

New issue

Closed

opened 2026-02-27 02:59:08 +03:00 by kerem · 9 comments

kerem commented

2026-02-27 02:59:08 +03:00

Owner

Originally created by @MyDimeIsUp on GitHub (Jul 17, 2019).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2447

User Story

When attempting to scroll up using my SSH program (MobaXTerm) I can't see previous outputs by SRCDS. When scrolling up, all I see is previous outputs from my ubuntu session

Basic info

Distro: [Ubuntu 18.04]
Game: [Garry's Mod]
Command: [console]

Further Information

To Reproduce

Steps to reproduce the beha`viour:

/[servername] c
Attempt to scroll up using your SSH program

Expected behaviour

To scroll up to previous console ouputs by SRCDS

Originally created by @MyDimeIsUp on GitHub (Jul 17, 2019). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/2447 ## User Story When attempting to scroll up using my SSH program (MobaXTerm) I can't see previous outputs by SRCDS. When scrolling up, all I see is previous outputs from my ubuntu session ## Basic info * Distro: [Ubuntu 18.04] * Game: [Garry's Mod] * Command: [console] ## Further Information ![Image without scrolled up](https://i.imgur.com/eufr1ta.png) ![Image of Console scrolled up](https://i.imgur.com/Wj8IX4T.png) ## To Reproduce Steps to reproduce the beha`viour: 1. /[servername] c 2. Attempt to scroll up using your SSH program ## Expected behaviour To scroll up to previous console ouputs by SRCDS

kerem

2026-02-27 02:59:08 +03:00

closed this issue
added the
outcome: wrong forum
label

kerem commented

2026-02-27 02:59:08 +03:00

Author

Owner

@issue-label-bot[bot] commented on GitHub (Jul 17, 2019):

Issue-Label Bot is automatically applying the label type: bug to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@issue-label-bot[bot] commented on GitHub (Jul 17, 2019): Issue-Label Bot is automatically applying the label `type: bug` to this issue, with a confidence of 0.94. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback! Links: [app homepage](https://github.com/marketplace/issue-label-bot), [dashboard](https://mlbot.net/data/GameServerManagers/LinuxGSM) and [code](https://github.com/hamelsmu/MLapp) for this bot.

kerem commented

2026-02-27 02:59:08 +03:00

Author

Owner

@Bourne-ID commented on GitHub (Jul 17, 2019):

Not a LinuxGSM issue - sounds like something that MobaXTerm is causing. I suggest holding down shift when using a mouse wheel or trying the standard terminal keyboard shortcut commands to see if that helps.

Closing ticket as it's not related to LinuxGSM - feel free to come to our discord and ask for help with linux if more help is required.

@Bourne-ID commented on GitHub (Jul 17, 2019): Not a LinuxGSM issue - sounds like something that MobaXTerm is causing. I suggest [holding down shift when using a mouse wheel](https://superuser.com/a/1349250) or trying the [standard terminal keyboard shortcut commands](https://unix.stackexchange.com/a/60387) to see if that helps. Closing ticket as it's not related to LinuxGSM - feel free to come to our discord and ask for help with linux if more help is required.

kerem commented

2026-02-27 02:59:09 +03:00

Author

Owner

@MyDimeIsUp commented on GitHub (Jul 22, 2019):

I tried both putty and the MobaXTerrm and it didn't work. Same problem on putty and holding shift+scrolling up along with shift+pageup doesn't work (Not even scrolling). Can you try doing it in SRCDS with you program. If it works what program do you use?

@MyDimeIsUp commented on GitHub (Jul 22, 2019): I tried both putty and the MobaXTerrm and it didn't work. Same problem on putty and holding shift+scrolling up along with shift+pageup doesn't work (Not even scrolling). Can you try doing it in SRCDS with you program. If it works what program do you use?

kerem commented

2026-02-27 02:59:09 +03:00

Author

Owner

@MyDimeIsUp commented on GitHub (Jul 23, 2019):

@Bourne-ID

@MyDimeIsUp commented on GitHub (Jul 23, 2019): @Bourne-ID

kerem commented

2026-02-27 02:59:09 +03:00

Author

Owner

@MyDimeIsUp commented on GitHub (Jul 31, 2019):

@Bourne-ID please reopen?

@MyDimeIsUp commented on GitHub (Jul 31, 2019): @Bourne-ID please reopen?

kerem commented

2026-02-27 02:59:09 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Jul 31, 2019):

As @Bourne-ID stated this is not an issue related to LinuxGSM. It is an issue with the terminal. No requirement to re-open this. As was stated there may be someone on the LinuxGSM discord that might be able to help.

@dgibbs64 commented on GitHub (Jul 31, 2019): As @Bourne-ID stated this is not an issue related to LinuxGSM. It is an issue with the terminal. No requirement to re-open this. As was stated there may be someone on the LinuxGSM discord that _might_ be able to help.

kerem commented

2026-02-27 02:59:09 +03:00

Author

Owner

@MyDimeIsUp commented on GitHub (Feb 3, 2020):

It is tho. I literally just tried in PuTTY and it still doesn't scroll. This is in issue with LinuxGSM. Don't know how else to state it

@MyDimeIsUp commented on GitHub (Feb 3, 2020): It is tho. I literally just tried in PuTTY and it still doesn't scroll. This is in issue with LinuxGSM. Don't know how else to state it

kerem commented

2026-02-27 02:59:09 +03:00

Author

Owner

@MyDimeIsUp commented on GitHub (Feb 3, 2020):

@MyDimeIsUp commented on GitHub (Feb 3, 2020): ![image](https://user-images.githubusercontent.com/8619739/73623636-9d8bf080-460b-11ea-8f2f-fb73112775b0.png)

kerem commented

2026-02-27 02:59:09 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 3, 2021):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Feb 3, 2021): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.