Hello Debian Team,
We are using Linux Debain 9 in our moxa devices.
we are connected in a network where we connect with our moxa device via ssh and
run the commands with Gauge ip and port and get Data.
Now I'm Facing issue from 2, 3 weeks to connect the moxa using ssh and then
connect to the seri
On Mon, 17 Jul 2023, to...@tuxteam.de wrote:
On Sun, Jul 16, 2023 at 03:21:06PM -0400, Timothy M Butterworth wrote:
Do you have TCP wrappers installed and running? Please post the output
of: `less /etc/hosts.allow` `less /etc/hosts.deny`
tcpwrappers would lead to a connection refused, not a
On Sun, Jul 16, 2023 at 03:21:06PM -0400, Timothy M Butterworth wrote:
[...]
> Do you have TCP wrappers installed and running? Please post the output
> of: `less
> /etc/hosts.allow` `less /etc/hosts.deny`
tcpwrappers would lead to a connection refused, not a timeout.
Cheers
--
t
signature.as
; probable,but hey) it's sshd config.
>
> Here is netstat -antp on one of the Debian 9 machines where I am currently
> logged in locally as root via ssh.
>
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local AddressForeign Address St
destination
1ufw-before-logging-input all -- 0.0.0.0/0 0.0.0.0/0
So I would guess ufw.
That's what I thought, but there is no ufw in this Debian 9 machine. So I had
to do some archaeology.
It took me a while to discover that long ago this machine ran openSuSE 12.2 and
was dir
Roger Price writes:
> Does the style of comment give a clue to the tool used ?
Earlier you posted a list of firewall rules like this:
iptables -L -n --line-numbers reports
Chain INPUT (policy ACCEPT)
num targetprot opt source destination
1ufw-before-logging-
Roger Price wrote:
> After the restart, I tried to ssh from Debian 11 to that Debian 9 machine
>
> rprice@titan ~ ssh -v rprice@kananga
> ssh: connect to host kananga port 22: Connection timed out
>
> So it's something else? Roger
Sorry, but I didn't follow the
mick.crane (12023-07-16):
> I'd compare the public key of you at 11 to what's in the authorized_keys on
> 9.
> and what's in known_hosts.
> and what's in the sshd config file on 9 about "Listen"
> after that I dunno.
Oh, please stop. The symptoms do not point to issues with the key AT ALL
and the
On 2023-07-16 10:53, Roger Price wrote:
On Sun, 16 Jul 2023, mick.crane wrote:
did you try to ssh to the ip address?
I vaguely remember something to do with the keys where I could ssh by
number but not name.
I ssh from Debian 11 to Debian 9 :
rprice@titan ~ ssh rprice@192.168.1.13
ssh
On Sun, 16 Jul 2023, mick.crane wrote:
did you try to ssh to the ip address?
I vaguely remember something to do with the keys where I could ssh by number
but not name.
I ssh from Debian 11 to Debian 9 :
rprice@titan ~ ssh rprice@192.168.1.13
ssh: connect to host 192.168.1.13 port 22
On 2023-07-16 09:28, Roger Price wrote:
On Sun, 16 Jul 2023, mick.crane wrote:
Can you ping the problem machine by name?
rprice@titan ~ ping -c2 kananga
PING kananga (192.168.1.16) 56(84) bytes of data.
64 bytes from kananga (192.168.1.16): icmp_seq=1 ttl=64 time=1.38 ms
64 bytes from kan
On Sun, Jul 16, 2023 at 11:03:52AM +0200, Roger Price wrote:
[...]
> On a Debian 9 machine I typed the commands
>
> iptables -F
> iptables -X
> iptables -P INPUT ACCEPT
> iptables -P FORWARD ACCEPT
> iptables -P OUTPUT ACCEPT
>
> and then _immediately_ atte
On Sun, 16 Jul 2023, to...@tuxteam.de wrote:
On Sun, Jul 16, 2023 at 09:39:35AM +0200, Roger Price wrote:
I tried to clear out the existing firewall on a Debian 9 machine with the
commands
This would be a good time to try ssh :-)
But before chasing that culprit it'd be nice to kn
On Sun, 16 Jul 2023, mick.crane wrote:
Can you ping the problem machine by name?
rprice@titan ~ ping -c2 kananga
PING kananga (192.168.1.16) 56(84) bytes of data.
64 bytes from kananga (192.168.1.16): icmp_seq=1 ttl=64 time=1.38 ms
64 bytes from kananga (192.168.1.16): icmp_seq=2 ttl=64 ti
On Sun, Jul 16, 2023 at 09:07:03AM +0100, mick.crane wrote:
[...]
> Can you ping the problem machine by name?
> mick
No, it isn't a name resolution issue. The original "ssh -v" output,
which I re-quote here shows that clearly:
| rprice@kananga:~$ ssh -v rprice@maria
| OpenSSH_7.4p1 Debian-10+de
ng in.
In my Debian 9 and 11 boxes I see in /etc/ssh/sshd_config
"PermitRootLogin yes" by default, and by default local and remote root
login is possible.
Roger
Can you ping the problem machine by name?
mick
On Sun, Jul 16, 2023 at 03:46:06PM +0800, jeremy ardley wrote:
>
> On 16/7/23 15:39, Roger Price wrote:
> > So it's something else? Roger
>
>
> Have you checked /etc/ssh/sshd_config on the target to see if it is actually
> listening on port 22? You can also use netstat to see listening ports an
d out
> >
> > A timeout is an ENTIRELY different symptom, and when combined with
> > "but I can ping the remote", it means a firewall is involved. Every
> > time.
>
> I tried to clear out the existing firewall on a Debian 9 machine with the
> commands
&g
On 16/7/23 15:39, Roger Price wrote:
So it's something else? Roger
Have you checked /etc/ssh/sshd_config on the target to see if it is
actually listening on port 22? You can also use netstat to see listening
ports and processes
Second is to check the /etc/ssh/ssh_config on the originati
emote", it means a firewall is involved. Every
time.
I tried to clear out the existing firewall on a Debian 9 machine with the
commands
iptables -F
iptables -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
iptables -L -n --line-numbers reports
C
bian's ssh configuration stops root from logging in.
>
> In my Debian 9 and 11 boxes I see in /etc/ssh/sshd_config "PermitRootLogin
> yes"
> by default, and by default local and remote root login is possible.
$ cat /etc/ssh/sshd_config.d/20-no_root_login.conf
PermitRootLogin no
Also see https://wiki.debian.org/SSH .
Jeff
On Sun, 16 Jul 2023, Intense Red wrote:
Are you trying to ssh into the box as the root user?
I do not ssh into remote boxes as root; I use ssh to root only within the box.
If so, remember Debian's ssh configuration stops root from logging in.
In my Debian 9 and 11 boxes I see in
On Sun, Jul 16, 2023 at 12:47:43AM -0500, Intense Red wrote:
>Are you trying to ssh into the box as the root user? If so, remember
> Debian's ssh configuration stops root from logging in.
The ssh -v tells another story: the port isn't even open. If this
were root being rejected, it would conn
very
> > probable,but hey) it's sshd config.
>
> Here is netstat -antp on one of the Debian 9 machines where I am currently
> logged in locally as root via ssh.
>
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local AddressForeign Add
On Sat, 15 Jul 2023, to...@tuxteam.de wrote:
@Roger: what does "sudo ss -antp" (or "netstat -antp") say? Is sshd
listening on 0.0.0.0:22? Then it's firewall, otherwise (not very
probable,but hey) it's sshd config.
Here is netstat -antp on one of the Debian 9
On Sat, Jul 15, 2023 at 11:12:23AM -0400, Greg Wooledge wrote:
> On Sat, Jul 15, 2023 at 11:59:33AM +0200, Roger Price wrote:
> > rprice@kananga:~$ ssh -v rprice@maria
> > OpenSSH_7.4p1 Debian-10+deb9u2, OpenSSL 1.0.2l 25 May 2017
> > debug1: Reading configuration data /etc/ssh/ssh_config
> > debu
On Sat, Jul 15, 2023 at 07:31:51AM -0400, Timothy M Butterworth wrote:
> On Sat, Jul 15, 2023 at 7:23 AM Roger Price wrote:
>
> > On Sat, 15 Jul 2023, Timothy M Butterworth wrote:
> >
> > > On Sat, Jul 15, 2023 at 7:12 AM Roger Price
> > wrote:
> > >
Greg Wooledge (12023-07-15):
> A timeout is an ENTIRELY different symptom, and when combined with
> "but I can ping the remote", it means a firewall is involved. Every
> time.
It can on occasion be a MTU black hole. But I am nitpicking and you are
almost certainly right here.
Regards,
--
Nic
On Sat, Jul 15, 2023 at 11:59:33AM +0200, Roger Price wrote:
> rprice@kananga:~$ ssh -v rprice@maria
> OpenSSH_7.4p1 Debian-10+deb9u2, OpenSSL 1.0.2l 25 May 2017
> debug1: Reading configuration data /etc/ssh/ssh_config
> debug1: /etc/ssh/ssh_config line 19: Applying options for *
> debug1: Connect
On Sat, Jul 15, 2023 at 7:23 AM Roger Price wrote:
> On Sat, 15 Jul 2023, Timothy M Butterworth wrote:
>
> > On Sat, Jul 15, 2023 at 7:12 AM Roger Price
> wrote:
> >
> > The two debian 9 machines can ssh to themselves.
> >
> > Can you SSH from one De
On Sat, 15 Jul 2023, Timothy M Butterworth wrote:
On Sat, Jul 15, 2023 at 7:12 AM Roger Price wrote:
The two debian 9 machines can ssh to themselves.
Can you SSH from one Debian 9 to the other Debian 9?
No. I can ping, but I cannot ssh. The ssh hangs after "Connecting to
On Sat, Jul 15, 2023 at 7:12 AM Roger Price wrote:
> On Sat, 15 Jul 2023, to...@tuxteam.de wrote:
> > To sort out the possible things:
> > - log in to maria
> > - try "ssh rprice@localhost": what happens?
>
> The two debian 9 machines can ssh to themselves
On Sat, 15 Jul 2023, to...@tuxteam.de wrote:
To sort out the possible things:
- log in to maria
- try "ssh rprice@localhost": what happens?
The two debian 9 machines can ssh to themselves.
- if it works, there's an ssh daemon running on maria;
next to check would be
-
On Sat, 15 Jul 2023, Ming Kuang wrote:
Are you using any firewall rules? The phenomenon you describe is very much like
a
firewall blocking connections to these ports (you can connect out, can't
connect in).
Thanks for the suggestion. The two Debian 9 machines have customising fir
On Sat, Jul 15, 2023 at 11:59:33AM +0200, Roger Price wrote:
> I have three Debian machines on a 192.168.1/24 WiFi network. One is debian
> 11 and the two others are debian 9. The network is connected, I can ping
> from any machine to any other.
>
> The problem is that I can ssh fr
On Sat, 15 Jul 2023, Roger Price wrote:
Sorry, a formatting problem. Let's hope this is clearer
_
The debian 9 machines are listening on ports 22 and 3493:
root@maria ~ netstat -pnlt
Active Internet connec
I have three Debian machines on a 192.168.1/24 WiFi network. One is debian 11
and the two others are debian 9. The network is connected, I can ping from any
machine to any other.
The problem is that I can ssh from the debian 9's to the debian 11, but not to
any debian 9, although al
Hi,
On Mon, May 15, 2023 at 08:11:50PM +0530, amit agari wrote:
> Has ebtables package been removed from Debian 9 stretch distribution?
stretch is EOL so the entire distribution has been "removed" to
archive.debian.org. But after putting archive.debian.org in your
/etc/apt/sources.
On Mon 15 May 2023 at 20:11:50 (+0530), amit agari wrote:
> Has ebtables package been removed from Debian 9 stretch distribution?
http://archive.debian.org/debian/pool/main/e/ebtables/
appears to have ebtables_2.0.10.4-3.5+b1_amd64.deb
which is probably what you're looking for.
Cheers,
David.
Hi,
Has ebtables package been removed from Debian 9 stretch distribution?
Regards
On Thu, 21 Jul 2022, Dekks Herton wrote:
Roger Price writes:
Command cat /sys/devices/cpu/caps/pmu_name reports: westmere
I should have said also that command inxi -Fix reports MCP arch: Nehalem, which
is specified in more detail by the reference E5645 at
https://en.wikipedia.org/wiki/Wes
Roger Price writes:
> On Mon, 18 Jul 2022, Dekks Herton wrote:
>> What kernel is 11 running? are you using a Haswell or Broadwell CPU?
>
> Command inxi reports:
> System:Host: titan Kernel: 5.10.0-15-amd64 x86_64 bits: 64
> Desktop: Xfce 4.16.0 Distro: Debian GNU/Linux 11 (bullse
On Mon, 18 Jul 2022, Dekks Herton wrote:
What kernel is 11 running? are you using a Haswell or Broadwell CPU?
Command inxi reports:
System:Host: titan Kernel: 5.10.0-15-amd64 x86_64 bits: 64
Desktop: Xfce 4.16.0 Distro: Debian GNU/Linux 11 (bullseye)
Machine: Type: Desktop S
Roger Price writes:
> This ran for years with Debian 9. I upgrade to Debian 11 and hear
> nothing. The usual advice is
> (a) in /etc/crontab export XDG_RUNTIME_DIR=/run/user/1000
> (b) play the sound from a script.
>
> But that doesn't work with Debian 11. Does any rea
On Sun, 17 Jul 2022, 16 Jul 2022, Lee wrote:
Nope. Audio has always just worked; I never had to do anything
special or extra to get it working
Following https://wiki.archlinux.org/title/PulseAudio/Examples ,
I installed file ~/.config/pulse/default.pa
.include /etc/pulse/default.pa
set-
On Sun, 17 Jul 2022, Lee wrote:
On 7/17/22, The Wanderer wrote:
I don't use cron to play sounds, so I can't speak to this directly,
but...
While this may turn out in the end to be pure FUD, when I hear about
things which work properly when run by hand but not when run
automatically on a modern
Roger Price wrote:
> On Sat, 16 Jul 2022, Lee wrote:
>
> > I don't have play, so I tried aplay .. and it works, even if I'm
> > logged out, even if someone else is logged in.
> >
> > ## run the script every minute
> >
> > $ crontab -l | tail -3
> > # m h dom mon dow command
> > * * * *
On 7/17/22, The Wanderer wrote:
> On 2022-07-16 at 04:47, Roger Price wrote:
>
>> People occasionally have a cron job emit some sound each hour. On my
>> Debian 9
>> machine I hear Biff [1] barking. In /etc/crontab I have an entry to call a
>>
>> script bark.
On 2022-07-16 at 04:47, Roger Price wrote:
> People occasionally have a cron job emit some sound each hour. On my Debian
> 9
> machine I hear Biff [1] barking. In /etc/crontab I have an entry to call a
> script bark.sh which does the barking. Typically
>
> 0,1 0,12 * *
On 7/16/22, Roger Price wrote:
> On Sat, 16 Jul 2022, Lee wrote:
>
>> I don't have play, so I tried aplay .. and it works, even if I'm
>> logged out, even if someone else is logged in.
>>
>> ## run the script every minute
>>
>> $ crontab -l | tail -3
>> # m h dom mon dow command
>> * * * *
On Sat, 16 Jul 2022, Lee wrote:
I don't have play, so I tried aplay .. and it works, even if I'm
logged out, even if someone else is logged in.
## run the script every minute
$ crontab -l | tail -3
# m h dom mon dow command
* * * * */home/lee/bin/neener.sh
## which plays a .wav
On 7/16/22, Roger Price wrote:
> People occasionally have a cron job emit some sound each hour. On my Debian
> 9
> machine I hear Biff [1] barking. In /etc/crontab I have an entry to call a
> script bark.sh which does the barking. Typically
>
> 0,1 0,12 * * * rprice full-pa
People occasionally have a cron job emit some sound each hour. On my Debian 9
machine I hear Biff [1] barking. In /etc/crontab I have an entry to call a
script bark.sh which does the barking. Typically
0,1 0,12 * * * rprice full-path-to/bark.sh 12 2>>&1
where bark.sh is a Bash sc
On 7/5/22 04:36, Miroslav Skoric wrote:
On 7/3/22 7:51 PM, David Christensen wrote:
On 7/3/22 02:31, Miroslav Skoric wrote:
Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to
buster. I followed instructions in 'Chapter 4. Upgrades from Debian 9
(stretch)', so all went
El mar, 5 jul 2022 a las 8:39, Miroslav Skoric () escribió:
>
> On 7/5/22 9:37 AM, Tom Dial wrote:
> >
> > Post the output from
> >
> > # fdisk -l (or $ sudo fdisk -l)
> > # vgdisplay -v (or $ sudo vgdisplay -v)
> >
>
> Here it is:
>
> # fdisk -l
> Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 6251
On 7/5/22 9:37 AM, Tom Dial wrote:
Post the output from
# fdisk -l (or $ sudo fdisk -l)
# vgdisplay -v (or $ sudo vgdisplay -v)
Here it is:
# fdisk -l
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Disk model: Hitachi HTS54323
Units: sectors of 1 * 512 = 512 bytes
Sector si
On 7/3/22 7:51 PM, David Christensen wrote:
On 7/3/22 02:31, Miroslav Skoric wrote:
Hi all,
Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to
buster. I followed instructions in 'Chapter 4. Upgrades from Debian 9
(stretch)', so all went well with a minimal upgrad
On 7/3/22 4:28 PM, Miroslav Skoric wrote:
Haven't tried that, but something else already helped: While it was
idling with fsck in tty1, I went to tty2 and entered: apt --fix-broken
install ... and it did/resumed full upgrade. (Interestingly, this time
it did not complain about no space in /
On 7/3/22 08:28, Miroslav Skoric wrote:
...
Haven't tried that, but something else already helped: While it was idling with
fsck in tty1, I went to tty2 and entered: apt --fix-broken install ... and it
did/resumed full upgrade. (Interestingly, this time it did not complain about
no spa
On 7/3/22 02:31, Miroslav Skoric wrote:
Hi all,
Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to buster.
I followed instructions in 'Chapter 4. Upgrades from Debian 9
(stretch)', so all went well with a minimal upgrade (apt-get upgrade).
When it finished, I went t
On 7/3/22 1:17 PM, Andrew M.A. Cater wrote:
Ctrl-Alt-F2 brings tty2 from where I can log in, then sudo etc. df -h shows
that filesystem /dev/mapper/localhost-root (mounted on /) is 99% used, and
/dev/mapper/localhost-usr (mounted on /usr) is 100% used.
Apt tends to store files in /var - it's
On Sun, Jul 03, 2022 at 11:31:40AM +0200, Miroslav Skoric wrote:
> Hi all,
>
> Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to buster. I
> followed instructions in 'Chapter 4. Upgrades from Debian 9 (stretch)', so
> all went well with a minimal upgrade (
Hi all,
Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to buster.
I followed instructions in 'Chapter 4. Upgrades from Debian 9
(stretch)', so all went well with a minimal upgrade (apt-get upgrade).
When it finished, I went to the main part of the upgrade (apt
full-up
On 4/20/22 00:43, David Christensen wrote:
I have been experiencing intermittent storms of random keyboard and
mouse GUI events over the past year or more:
I found my spare mouse last week and swapped out the mouse I have been
using for the past few years. The problems went away. The bad mo
ing in mind that reporting against Debian 9 might only
result in a stifled yawn.
The same problem exists in Debian 9, 10, and 11. I can readily file bug
reports against Debian 9 and 11 (I wiped and reused my Debian 10 SSD).
I saw one GUI input event storm in ~6 hours of use following the above
> KVMs fit into this model.)
>
>
> Changing pointing device settings via Xfce Applications Menu -> Settings ->
> Mouse and Touchpad does not seem to affect the failures, but I have not made
> many changes.
>
>
> > Always bearing in mind that reporting against
ation. (I don't know how
KVMs fit into this model.)
Changing pointing device settings via Xfce Applications Menu -> Settings
-> Mouse and Touchpad does not seem to affect the failures, but I have
not made many changes.
Always bearing in mind that reporting against Debian 9 might
onnected the KVM cable to the desktop computer, and booted. The four
> (4) rear USB 2.0 ports and the two (2) rear USB 3.0 ports work
> correctly.
>
>
> Therefore, I conclude the problem is software -- whatever in Debian 9
> Xfce deals with X Windows input via USB 2.0 keyboards and
.
Therefore, I conclude the problem is software -- whatever in Debian 9
Xfce deals with X Windows input via USB 2.0 keyboards and mice.
What package do I file a bug report against?
David
On 4/20/22 14:40, Felix Miata wrote:
David Christensen composed on 2022-04-20 14:14 (UTC-0700):
Can you suggestion and commands to run that might provide clues?
Other than switching between use of DDX display drivers (intel, nouveau) and DIX
driver (modesetting, which supports: AMD, Intel, N
David Christensen composed on 2022-04-20 14:14 (UTC-0700):
> Felix Miata wrote:
>> There are two different technologies for X display drivers.
>> xserver-xorg-video-intel uses the older, DDX. It hasn't had an official
>> release in
>> nearly a decade. Unofficially it's in maintenance mode. The n
On 4/20/22 11:23, Felix Miata wrote:
David Christensen composed on 2022-04-20 10:31 (UTC-0700):
1. Dell Inspiron E1505, Intel Core 2 Duo T7400 processor, Intel GM 945
chipset (Intel® 82945GM Graphics and Memory Controller). I believe
Debian uses the xserver-xorg-video-intel driver.
3. Des
David Christensen composed on 2022-04-20 10:31 (UTC-0700):
> 1. Dell Inspiron E1505, Intel Core 2 Duo T7400 processor, Intel GM 945
> chipset (Intel® 82945GM Graphics and Memory Controller). I believe
> Debian uses the xserver-xorg-video-intel driver.
> 3. Desktop with Intel DQ67SW motherboa
On 4/20/22 4:51 AM, songbird wrote:
Dieter Rohlfing wrote:
Am Wed, 20 Apr 2022 00:43:35 -0700
schrieb David Christensen :
I have been experiencing intermittent storms of random keyboard and
mouse GUI events over the past year or more:
Same for me.
System is Debian 9.13 (kernel 4.19.0-0.bpo.
On 4/20/22 3:43 AM, Cindy Sue Causey wrote:
On 4/20/22, Dieter Rohlfing wrote:
Am Wed, 20 Apr 2022 00:43:35 -0700
schrieb David Christensen :
I have been experiencing intermittent storms of random keyboard and
mouse GUI events over the past year or more:
Same for me.
System is Debian 9.13
k the storm mainly depends on the bare host and
not on the peripheral components.
My WAG is that a bug was introduced in the X Windows and/or desktop
drivers 1~2 years ago on Debian 9, 10, and 11.
At the moment I'm tinkering with the C-states. I disabled C6 and C7 in the
BIOS and
Dieter Rohlfing wrote:
> Am Wed, 20 Apr 2022 00:43:35 -0700
> schrieb David Christensen :
>
>>I have been experiencing intermittent storms of random keyboard and
>>mouse GUI events over the past year or more:
>
> Same for me.
>
> System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) ru
On 4/20/22, Dieter Rohlfing wrote:
> Am Wed, 20 Apr 2022 00:43:35 -0700
> schrieb David Christensen :
>
>>I have been experiencing intermittent storms of random keyboard and
>>mouse GUI events over the past year or more:
>
> Same for me.
>
> System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFC
Am Wed, 20 Apr 2022 00:43:35 -0700
schrieb David Christensen :
>I have been experiencing intermittent storms of random keyboard and
>mouse GUI events over the past year or more:
Same for me.
System is Debian 9.13 (kernel 4.19.0-0.bpo.19-amd64, XFCE desktop) running
on an ASRock DeskMini H110M.
On 4/20/22 12:43 AM, David Christensen wrote:
debian-user:
I have an SSD with Debian:
2022-04-19 23:24:11 dpchrist@tinkywinky ~
$ cat /etc/debian_version ; uname -a
9.13
Linux tinkywinky 4.9.0-18-amd64 #1 SMP Debian 4.9.303-1 (2022-03-07)
x86_64 GNU/Linux
I have been experiencing intermitte
debian-user:
I have an SSD with Debian:
2022-04-19 23:24:11 dpchrist@tinkywinky ~
$ cat /etc/debian_version ; uname -a
9.13
Linux tinkywinky 4.9.0-18-amd64 #1 SMP Debian 4.9.303-1 (2022-03-07)
x86_64 GNU/Linux
I have been experiencing intermittent storms of random keyboard and
mouse GUI eve
On 2/10/22 09:54, Nagaraju Mulpuri wrote:
Dear Debian Users,
Greetings of the day!
I have been using Debian 9 version for the last 4 years. Recently, my computer
crashed. I have to install Debian OS again. I am planning to install Debian 11
version. I have many of my own programs compiled on
On Thu, Feb 10, 2022 at 05:54:08PM -, Nagaraju Mulpuri wrote:
> Dear Debian Users,
> Greetings of the day!
> I have been using Debian 9 version for the last 4 years. Recently, my
> computer crashed. I have to install Debian OS again. I am planning to install
> Debian 11 versi
On Thu, Feb 10, 2022 at 05:54:08PM -, Nagaraju Mulpuri wrote:
> I have been using Debian 9 version for the last 4 years. Recently, my
> computer crashed. I have to install Debian OS again. I am planning to install
> Debian 11 version. I have many of my own programs compiled on the
On Thu, Feb 10, 2022 at 05:54:08PM -, Nagaraju Mulpuri wrote:
> Dear Debian Users,
> Greetings of the day!
> I have been using Debian 9 version for the last 4 years. Recently, my
> computer crashed.
> I have to install Debian OS again. I am planning to install Debian 11
&g
Dear Debian Users,
Greetings of the day!
I have been using Debian 9 version for the last 4 years. Recently, my computer
crashed. I have to install Debian OS again. I am planning to install Debian 11
version. I have many of my own programs compiled on the Debian 9 version.
Compiled programs in
On Ma, 14 dec 21, 14:59:56, Thanos Katsiolis wrote:
> Kent thank you for your response.
>
>
> I also had to install the GNOME, although using dpkg I saw related
> packages, so I thought that it was installed.
> Is there a way to verify that something like DM (gdm) or GNOMe is
> installed, in orde
Kent thank you for your response.
I also had to install the GNOME, although using dpkg I saw related
packages, so I thought that it was installed.
Is there a way to verify that something like DM (gdm) or GNOMe is
installed, in order to know what to do?
Thank you all for your help.
On Mon, Dec 1
On Mon, Dec 13, 2021 at 10:14 AM Thanos Katsiolis
wrote:
> The Display Manager was missing (gdm3), I installed it and the login works
> fine.
>
> Now when I log in there is a blue screen and the cursor, nothing else is
> displayed.
> Is there a problem with GNOME?
>
Probably.
You might try rei
lowed the Release notes
> <https://www.debian.org/releases/buster/amd64/release-notes.en.pdf> for
> Debian 10, in order to update from Debian 9 to Debian 10. After running
>
> apt-get upgrade
>
> I ran
>
> apt full-upgrade
>
> to complete the update to Debian 10
On Mon, Dec 13, 2021 at 12:04:32PM +0200, Thanos Katsiolis wrote:
> Thank you Piotr for your response.
>
> As I responded to Andrei lower in the thread, neither DM nor DE must have
> been installed.
>
> I would like to get GNOME, so I will try to install it. Does this affect
> the DM somehow?
If
Thank you Piotr for your response.
As I responded to Andrei lower in the thread, neither DM nor DE must have
been installed.
I would like to get GNOME, so I will try to install it. Does this affect
the DM somehow?
On Fri, Dec 10, 2021 at 8:54 PM piorunz wrote:
> On 10/12/2021 16:24, Thanos Kat
Andrei sorry for my late response,
> More precisely, no Display Manager (DM). Even if you do have a Desktop
> Environment installed, the DM is responsible for automatically starting
> it.
>
> Please try to log in on the console and run:
>
> startx
>
>
>
startx ha the output:
/etc/X11/xinit/x
[this appears to have been meant for the list]
On Vi, 10 dec 21, 20:25:26, Thanos Katsiolis wrote:
> > Yes, it's possible, e.g. in case there was a conflict and APT decided it
> > > should remove remove your Desktop Environment to resolve the conflict.
> >
> > > This should be visible in the logs
On 10/12/2021 16:24, Thanos Katsiolis wrote:
I verified that Debian 10.10 was installed , ran cleaning commands,
reboot again but again I can only access ttys and not the Graphical
Interface.
What DE you are using?
1. Check if your DE is still installed.
dpkg -l | grep /your-de/name/
2. Instal
So I have to install a Desktop Environment.
I am thinking of using tasksel to install GNOME.
Thank you for your help.
I though about that too, that the video card somehow could have affected
the update somehow regarding DE.
The VGA compatible controller entry of lspci is NVIDIA Corporation GP107GL
[Quadro P400] (rev a1)
I don't remember anything about firmware during the installation.
On Fri, Dec 10, 2021 at 7:
On Vi, 10 dec 21, 18:24:19, Thanos Katsiolis wrote:
> Thank you both for your replies.
>
> I managed to complete the installation (run also apt full-upgrade
> successfully) and then reboot.
> After the update the system boots only with the ttys (1-6) and not with a
> graphical interface, and by th
On Fri, Dec 10, 2021 at 06:24:19PM +0200, Thanos Katsiolis wrote:
> Thank you both for your replies.
>
> I managed to complete the installation (run also apt full-upgrade
> successfully) and then reboot.
> After the update the system boots only with the ttys (1-6) and not with a
> graphical interf
Thank you both for your replies.
I managed to complete the installation (run also apt full-upgrade
successfully) and then reboot.
After the update the system boots only with the ttys (1-6) and not with a
graphical interface, and by that I mean that I tried to change to the
graphical interface with
1 - 100 of 672 matches
Mail list logo
