On Sun, Nov 3, 2024 at 4:04 PM Christian wrote:
> [...]
> Well yes, and it's pretty confusing because I disabled secure boot, and
> the problems remained. Which makes me really clueless, because there is
> not much information left on the dmesg. Maybe its something with BIOS or
> ACPI? By adding l
So far I couldn't see anything in my
cmdline which is kernel_lockdown related.
If this means that you already looked into
/proc/cmdline
then i am out of ideas why the kernel log reported
[ 47.042454] Lockdown: Xorg: raw io port access is restricted; see man
kernel_lockdown.7
Turns out,
Hi,
Christian wrote:
> So far I couldn't see anything in my
> cmdline which is kernel_lockdown related.
If this means that you already looked into
/proc/cmdline
then i am out of ideas why the kernel log reported
> > [ 47.042454] Lockdown: Xorg: raw io port access is restricted; see man
> >
On Wed, Oct 30, 2024 at 12:25 PM Christian wrote:
>
> Hello Kevin, thank you for support. I choosed Nvidia again deliberately
> because I want to play with Tesorflow, Scikit-Learn and GPT. And yes I
> had my experiences with Nvidia over the year as well. But I decided to
> take Nvidia again. Maybe
30 Oct 2024 16:25:58 Christian :
> I choosed Nvidia again deliberately because I want to play with Tesorflow,
> Scikit-Learn and GPT.
Or perhaps game. People seem to forget that 20 years ago Nvidia was the only
supporter of full featured gpu drivers on Linux.
Have you tried disabling secure bo
Hello Kevin, thank you for support. I choosed Nvidia again deliberately
because I want to play with Tesorflow, Scikit-Learn and GPT. And yes I
had my experiences with Nvidia over the year as well. But I decided to
take Nvidia again. Maybe there are more people like me, giving up the
installatio
Hello Timothy, I did so. I used Debian Testing/Trixie, which I also use
on my current old system (build 2015) with apt pinning and everything...
The ISO I used was debian-live-testing-amd64-xfce.iso.
BR Christian
On Wed, Oct 30, 2024 at 10:58 AM Christian wrote:
Hi Thomas, thank you for you
On Wed, Oct 30, 2024 at 10:58 AM Christian wrote:
> Hi Thomas, thank you for your help. So far I couldn't see anything in my
> cmdline which is kernel_lockdown related. And I grep'ed the whole /etc
> and /boot directory recursively. Nothing. And neither in the dmesg,
> there is no "lsm=" line. On
On Wed, Oct 30, 2024 at 11:27 AM Christian wrote:
> > Hello out there, I have an issue with my new Debian installation. I
> > choose stable for now, to keep it simple. So used the stable
> > installation ISO to install Debian on a MSI Z690-A with a Intel Core
> > I7-14700 and a GeForce RTX 4060Ti
Hello out there, I have an issue with my new Debian installation. I
choose stable for now, to keep it simple. So used the stable
installation ISO to install Debian on a MSI Z690-A with a Intel Core
I7-14700 and a GeForce RTX 4060Ti. The Nouveau driver did not work with
this card so I installed the
Hi Thomas, thank you for your help. So far I couldn't see anything in my
cmdline which is kernel_lockdown related. And I grep'ed the whole /etc
and /boot directory recursively. Nothing. And neither in the dmesg,
there is no "lsm=" line. Only in the kernel .config is
CONFIG_SECURITY_LOCKDOWN=y,
>> NVIDIA is a major pain in the ass with Linux. Which is why I do not
>> use them.
> Actually this is more Linux being a major pain in the ass to Nvidia.
Hmm... I haven't seen any sign that Nvidia suffers much, so I think it's
more clearly a pain inflicted on Linux.
Stefan
29 Oct 2024 17:38:39 Timothy M Butterworth :
> NVIDIA is a major pain in the ass with Linux. Which is why I do not
> use them.
Actually this is more Linux being a major pain in the ass to Nvidia.
When secure boot is enabled lockdown is automatically enabled. Really debian
should provide an Nvid
On Tue, Oct 29, 2024 at 6:56 AM Christian wrote:
> Hello out there, I have an issue with my new Debian installation. I
> choose stable for now, to keep it simple. So used the stable
> installation ISO to install Debian on a MSI Z690-A with a Intel Core
> I7-14700 and a GeForce RTX 4060Ti. The Nou
Hi,
Christian wrote:
> [ 47.042454] Lockdown: Xorg: raw io port access is restricted; see man
> kernel_lockdown.7
> I think it's still SecureBoot, but what is it this time? Can anyone help
At least the above log snippet seems to be related to SecureBoot.
In
https://manpages.debian.org/bookwo
Polyna-Maude Racicot-Summerside wrote:
> >
> > There are a bunch of loonies out there who don't like other
> > people based on gender, sex, skin color, religion, geography, or
> > merely the fact that their computer is unsecured.
> >
>
> Thanks, I didn't know the word loonies applied to yoursel
Hi,
> If I'm asking for help, I don't want to hear "try this, it's
> dangerous" unless all other possibilities have been exhausted.
>
> If you want to start a thread "dangerous things to do to risk
> your data", that's fine.
Would you be stuck in something like YOU = ALL OTHER BEING ?
Can you le
Hi,
>
>
> And there's most people on earth who don't give a minute thinking about
> this.
>
> Ask any business manager, he doesn't give much interest in his computer
> installation, as long one thing goes, what is it ? That the system
> permit core operation for the company and profit conti
Hi,
Note :
Sorry Andrei if this message may seem to be wrote directly to you
because in fact it's written to all the "you" around who may feel
concerned. You got a direct reply because I was replying to your
message. Again, this could be something not to be done.
On 2021-06-30 7:58 p.m., Andrei
On Mi, 30 iun 21, 11:44:42, Polyna-Maude Racicot-Summerside wrote:
>
> Now here's what will amaze you...
> You can do the same with a computer.
> Take risk...
> Make your computer unusable...
Sure, it's a great learning experience.
> Type "alias cd=rm -rf"
In my opinion it's generally a bad ide
On Mi, 30 iun 21, 11:02:43, Thompson, Brian wrote:
>
> Is this mailing list usually used for philosophical debates, persuasion, and
> primitive name-calling? Genuinely curious so that I can unsub if it is.
It happens more or less every time during the freeze, as there are less
problems to solve
On Mi, 30 iun 21, 05:57:19, The Wanderer wrote:
> On 2021-06-30 at 05:23, Polyna-Maude Racicot-Summerside wrote:
> >
> > On 2021-06-30 4:32 a.m., Andrei POPESCU wrote:
> >
> >> On Ma, 29 iun 21, 17:08:16, Polyna-Maude Racicot-Summerside wrote:
> >>
> >>> I can only hope that one day someone will
On Wed 30 Jun 2021 at 23:40:54 +0100, mick crane wrote:
> On 2021-06-30 18:56, Brian wrote:
>
> > > "f" word is very ancient English word which gives added emphasis
> > > especially
> > > when unexpected
> > > Doesn't bother me but as you say is inappropriate on mailing list
> > > and I'm
> > > s
On 2021-06-30 18:56, Brian wrote:
"f" word is very ancient English word which gives added emphasis
especially
when unexpected
Doesn't bother me but as you say is inappropriate on mailing list and
I'm
sure it's a one-off.
It is inappropriate anywhere in public. You are not bothered by this?
On Wed, 30 Jun 2021 09:33:37 -0400
Polyna-Maude Racicot-Summerside wrote:
>
> There's a old saying that state :
> "Give someone a fish, feed him for the day, teach him how to fish,
> feed him for life".
>
> That must be something that doesn't apply anymore.
It never did. The second clause is
On Wed 30 Jun 2021 at 14:27:16 -0400, Dan Ritter wrote:
[...]
> There are a bunch of loonies...
A very nineteenth centrury word. This bunch of people have views that
are due to some mental illness? Maybe a touch of empathy would not go
unnoticed.
[...]
--
Brian.
On Wed 30 Jun 2021 at 14:45:57 +0200, to...@tuxteam.de wrote:
> [1] I'm somewhat of a language nerd. I do love all words!
Words are words. They exist. So why do they disappear from the
language? I would suggest some consideration about using "cretin",
"moron" and "lunatic" in public. Their histo
Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> > For people that I consider part of my community, I feel a higher
> > standard of care is in order.
> >
> Haven't you ever tried to think of computing as a "no risk involved"
> possibility ?
>
> If I accept that I may risk rendering the system u
On Wed 30 Jun 2021 at 14:45:57 +0200, to...@tuxteam.de wrote:
> On Wed, Jun 30, 2021 at 01:31:37PM +0100, mick crane wrote:
> > On 2021-06-30 10:59, to...@tuxteam.de wrote:
> > >On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
> > >
> > >[...]
> > >
> > >>DO NOT USE xhost + WITH ssh
On Wed 30 Jun 2021 at 13:31:37 +0100, mick crane wrote:
> On 2021-06-30 10:59, to...@tuxteam.de wrote:
> > On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
> >
> > [...]
> >
> > > DO NOT USE xhost + WITH ssh -X OR ssh -Y
> > >
> > > That was the fucking point.
> >
> > Calm down.
Hi,
On 2021-06-30 11:59 a.m., Dan Ritter wrote:
> Polyna-Maude Racicot-Summerside wrote:
>> Now here's what will amaze you...
>> You can do the same with a computer.
>> Take risk...
>> Make your computer unusable...
>> Type "alias cd=rm -rf"
>> Open all the ports and get hacked.
>> Open all the p
On 30 Jun 2021, at 10:44, Polyna-Maude Racicot-Summerside wrote:
Hi,
To summarize, there are basically two sane approaches to remote X
clients:
"Two sane approach" ?
Okay, there's only two approach YOU believe in.
That's it.
There's at least a dozen of way to install a X11 network system
Polyna-Maude Racicot-Summerside wrote:
> Now here's what will amaze you...
> You can do the same with a computer.
> Take risk...
> Make your computer unusable...
> Type "alias cd=rm -rf"
> Open all the ports and get hacked.
> Open all the ports and not get hacked.
> Take risk and loose not much be
Hi,
>
> To summarize, there are basically two sane approaches to remote X clients:
>
"Two sane approach" ?
Okay, there's only two approach YOU believe in.
That's it.
There's at least a dozen of way to install a X11 network system.
You don't have any a power to judge other than your own self.
Y
On Wed, Jun 30, 2021 at 11:07:24AM -0400, Greg Wooledge wrote:
> On Wed, Jun 30, 2021 at 04:35:13PM +0200, to...@tuxteam.de wrote:
> > BTW: the problematic thing is called "xhost +", not "xhost +x", which
> > won't work...
> >
> > tomas@trotzki:~$ xhost + x
> > xhost: bad hostname "x"
> >
>
On Wed, Jun 30, 2021 at 04:35:13PM +0200, to...@tuxteam.de wrote:
> BTW: the problematic thing is called "xhost +", not "xhost +x", which
> won't work...
>
> tomas@trotzki:~$ xhost + x
> xhost: bad hostname "x"
>
> ...unless there's a host in your network named "x" :-)
xhost was mentioned b
On Wed, Jun 30, 2021 at 09:16:37AM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
[...]
> I didn't have in mind any type of murder or long lasting damage of any soft.
Still, it's a pretty violent metaphor, I think we can agree on that.
And perhaps somewhat off-tone for a mailing list with r
On Wed, Jun 30, 2021 at 09:33:37AM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
[...]
> I was the stupid and dumb person who started talking about "the classic
> way" of authentication using X11.
Uh, whatever. I don't think you're stupid. I don't think *you* think
you're stupid. So I'm ig
Hi,
>> [1] I'm somewhat of a language nerd. I do love all words!
>>
> I too am a language nerd. It is terribly fascinating how a particular
> word, regardless of things like history and etymology can come to be
> considered a "bad word" all on its own in any context. Other words are
> "bad" only
On 2021-06-30 at 09:16, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-06-30 5:57 a.m., The Wanderer wrote:
>
>> On 2021-06-30 at 05:23, Polyna-Maude Racicot-Summerside wrote:
>>> Yes, whatever great idea you have, even if others are wrong in
>>> what they say. Nothing justify being r
Hi,
On 2021-06-30 5:59 a.m., to...@tuxteam.de wrote:
> On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
>
> [...]
>
>> DO NOT USE xhost + WITH ssh -X OR ssh -Y
>>
>> That was the fucking point.
>
> Calm down. I understand security is close to your heart,
> but there's no need to b
Hi,
On 2021-06-30 5:57 a.m., The Wanderer wrote:
> On 2021-06-30 at 05:23, Polyna-Maude Racicot-Summerside wrote:
>
>> Hi,
>>
>> On 2021-06-30 4:32 a.m., Andrei POPESCU wrote:
>>
>>> On Ma, 29 iun 21, 17:08:16, Polyna-Maude Racicot-Summerside wrote:
>>>
I can only hope that one day someone w
On Wed, Jun 30, 2021 at 02:45:57PM +0200, to...@tuxteam.de wrote:
> On Wed, Jun 30, 2021 at 01:31:37PM +0100, mick crane wrote:
> > On 2021-06-30 10:59, to...@tuxteam.de wrote:
> > >On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
> > >
> > >[...]
> > >
> > >>DO NOT USE xhost + WITH s
On Wed, Jun 30, 2021 at 01:31:37PM +0100, mick crane wrote:
> On 2021-06-30 10:59, to...@tuxteam.de wrote:
> >On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
> >
> >[...]
> >
> >>DO NOT USE xhost + WITH ssh -X OR ssh -Y
> >>
> >>That was the fucking point.
> >
> >Calm down. I underst
On 2021-06-30 10:59, to...@tuxteam.de wrote:
On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
[...]
DO NOT USE xhost + WITH ssh -X OR ssh -Y
That was the fucking point.
Calm down. I understand security is close to your heart,
but there's no need to be so vitriolic and borderli
On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
[...]
> DO NOT USE xhost + WITH ssh -X OR ssh -Y
>
> That was the fucking point.
Calm down. I understand security is close to your heart,
but there's no need to be so vitriolic and borderline
insulting about it.
There are nicer way
On 2021-06-30 at 05:23, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-06-30 4:32 a.m., Andrei POPESCU wrote:
>
>> On Ma, 29 iun 21, 17:08:16, Polyna-Maude Racicot-Summerside wrote:
>>
>>> I can only hope that one day someone will knock you off with a
>>> shovel in the face because yo
On 2021-06-30 at 05:23, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-06-30 4:32 a.m., Andrei POPESCU wrote:
>
>> On Ma, 29 iun 21, 17:08:16, Polyna-Maude Racicot-Summerside wrote:
>>
>>> I can only hope that one day someone will knock you off with a
>>> shovel in the face because yo
On Wed, Jun 30, 2021 at 05:23:49AM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-06-30 4:32 a.m., Andrei POPESCU wrote:
> > On Ma, 29 iun 21, 17:08:16, Polyna-Maude Racicot-Summerside wrote:
> >>
> >> I can only hope that one day someone will knock you off with a shovel in
> >> t
Hi,
On 2021-06-30 4:32 a.m., Andrei POPESCU wrote:
> On Ma, 29 iun 21, 17:08:16, Polyna-Maude Racicot-Summerside wrote:
>>
>> I can only hope that one day someone will knock you off with a shovel in
>> the face because you said something wrong. This will be a great day and
>> you'll get back what
On Ma, 29 iun 21, 17:08:16, Polyna-Maude Racicot-Summerside wrote:
>
> I can only hope that one day someone will knock you off with a shovel in
> the face because you said something wrong. This will be a great day and
> you'll get back what you serve to others.
Seriously?
> This is a figure of
On Ma, 29 iun 21, 04:56:55, Polyna-Maude Racicot-Summerside wrote:
>
> On 2021-06-28 11:13 p.m., Greg Wooledge wrote:
>
> > (Avoid ANY proposed solution that talks about xhost. Seriously.)
> >
> Yes, solutions using xhost maybe a bit a pain in the ass but they are
> also some of the nice one th
Hi my friend,
On 2021-06-29 4:58 p.m., Greg Wooledge wrote:
> On Tue, Jun 29, 2021 at 04:46:48PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>> I've read back the whole series of message and no one ever said anything
>> that is somewhat possible to be interpreted as
>> using xhost +x with SSH
On Tue, Jun 29, 2021 at 04:46:48PM -0400, Polyna-Maude Racicot-Summerside wrote:
> I've read back the whole series of message and no one ever said anything
> that is somewhat possible to be interpreted as
> using xhost +x with SSH -X
https://lists.debian.org/debian-user/2021/06/msg00900.html
Hi,
>> that's how you learned things back in the early 1990s, that's your right,
>> but I hope you will at least point out how INCREDIBLY INSECURE this is,
>
> I never said in no situation something like "use xhost +".
> The same way as I never said to unblock all the ports on your router or
> to
Hi,
On 2021-06-29 2:43 p.m., Greg Wooledge wrote:
> DO NOT USE xhost + WITH ssh -X OR ssh -Y
>
> That was the fucking point.
WoW...
Take it *easy* there...
> Now, if you want to advocate that people should use xhost + because
I never talked about xhost myself.
And the only thing I said was that
Jesus h
Em 29 de junho de 2021 15:58:49 BRT, "Andrew M.A. Cater"
escreveu:
>On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
>> > On 2021-06-29 1:27 p.m., Greg Wooledge wrote:
>> > > On Tue, Jun 29, 2021 at 04:33:50PM +, Andrew M.A. Cater
>wrote:
>> > >> ssh -Y is similar to ss
On Tue, Jun 29, 2021 at 02:43:28PM -0400, Greg Wooledge wrote:
> > On 2021-06-29 1:27 p.m., Greg Wooledge wrote:
> > > On Tue, Jun 29, 2021 at 04:33:50PM +, Andrew M.A. Cater wrote:
> > >> ssh -Y is similar to ssh -X but does some authentication - yuu don't have
> > >> to use xhost+ or similar.
> On 2021-06-29 1:27 p.m., Greg Wooledge wrote:
> > On Tue, Jun 29, 2021 at 04:33:50PM +, Andrew M.A. Cater wrote:
> >> ssh -Y is similar to ssh -X but does some authentication - yuu don't have
> >> to use xhost+ or similar.
> >
> > You don't use xhost with ssh -X, either. At least, not expli
Hi,
On 2021-06-29 1:27 p.m., Greg Wooledge wrote:
> On Tue, Jun 29, 2021 at 04:33:50PM +, Andrew M.A. Cater wrote:
>> ssh -Y is similar to ssh -X but does some authentication - yuu don't have
>> to use xhost+ or similar.
>
> You don't use xhost with ssh -X, either. At least, not explicitly.
On Tue, Jun 29, 2021 at 04:33:50PM +, Andrew M.A. Cater wrote:
> ssh -Y is similar to ssh -X but does some authentication - yuu don't have
> to use xhost+ or similar.
You don't use xhost with ssh -X, either. At least, not explicitly.
ssh takes care of that for you.
In fact, on Debian, ssh -X
On Tue, Jun 29, 2021 at 12:13:53PM -0400, Polyna-Maude Racicot-Summerside wrote:
> Hi,
>
> On 2021-06-29 5:52 a.m., IL Ka wrote:
> >
> >
> > There's plenty of book you can find by searching on Google with the
> > subject "X11 architecture" or something similar.
> >
> > There is a classi
Hi,
On 2021-06-29 5:52 a.m., IL Ka wrote:
>
>
> There's plenty of book you can find by searching on Google with the
> subject "X11 architecture" or something similar.
>
> There is a classic "Definitive Guides to the X Window System" series.
> https://www.oreilly.com/library/view/x-windo
>
>
>
> There's plenty of book you can find by searching on Google with the
> subject "X11 architecture" or something similar.
>
> There is a classic "Definitive Guides to the X Window System" series.
https://www.oreilly.com/library/view/x-windows-system/9780937175835/
Also
https://www.oreilly.com/
Hi,
On 2021-06-28 11:13 p.m., Greg Wooledge wrote:
> On Mon, Jun 28, 2021 at 10:46:01PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>> On 2021-06-28 10:12 p.m., Rick Thomas wrote:
>>> I'd love to be able to do that! E.g. a headless machine with plenty of RAM
>>> and CPU power to run Mate, b
On Mon, Jun 28, 2021 at 10:46:01PM -0400, Polyna-Maude Racicot-Summerside wrote:
> On 2021-06-28 10:12 p.m., Rick Thomas wrote:
> > I'd love to be able to do that! E.g. a headless machine with plenty of RAM
> > and CPU power to run Mate, but located in a locked building on the other
> > side of
Hi,
On 2021-06-28 10:12 p.m., Rick Thomas wrote:
> On Sun, Jun 27, 2021, at 8:33 AM, Peter Ehlert wrote:
>>> X clients like MATE don't directly depend on an X server, because in
>>> theory, the X server could be on a different machine.
>
> I'd love to be able to do that! E.g. a headless machine
Felix Miata composed on 2019-07-08 23:21 (UTC-0400):
> ISTR your experience is known to upstream, but I get lost trying to
> find anything I want in their tracking systems. :-P
https://gitlab.freedesktop.org/xorg/xserver/issues/542 might be what I was
thinking of.
--
Evolution as taught in publi
Teemu Likonen composed on 2019-07-07 15:13 (UTC+0300):
> Solved. The X server chooses automatically some wrong graphics module
> ("modeset" I guess). If I force it to use "intel" module the X server
> works again.
The Intel DDX hasn't had an official release since five years ago:
https://cgit.fre
Teemu Likonen [2019-07-07T14:29:03+03] wrote:
> The problem: X server doesn't start anymore with Debian 10's default
> kernel version 4.19. The X server starts and works nicely with kernel
> 4.9 which I have still installed from Debian 9.
>
> What happens: Even a simple X session like "startx /usr
On 2019-07-07 14:29 +0300, Teemu Likonen wrote:
> Upgrade to Debian 10 didn't end up well although all packages upgraded
> smoothly.
>
> The problem: X server doesn't start anymore with Debian 10's default
> kernel version 4.19. The X server starts and works nicely with kernel
> 4.9 which I have s
On Sun, 2015-08-02 at 15:46 -0700, ydld1p...@sneakemail.com wrote:
> Last Friday I used aptitude to update the software on my old Dell
> Precision Workstation 340, which is running Debian's testing
> distribution. After the update completed, I rebooted and X Server
> failed to start. At the en
Am Donnerstag, den 23.10.2014, 14:06 -0700 schrieb Don Armstrong:
> On Thu, 23 Oct 2014, Jürgen Kleber wrote:
> > I did not mention yet that I tried lightdm/xfce4 - and it failed, too.
> > You should assign the bug additionally to lightdm.
>
> What was output to syslog when you did this?
>
> Wh
On Thu, 23 Oct 2014, Jürgen Kleber wrote:
> I did not mention yet that I tried lightdm/xfce4 - and it failed, too.
> You should assign the bug additionally to lightdm.
What was output to syslog when you did this?
What versions of these packages did you have installed?
What is output to ~/.xsess
Am Donnerstag, den 23.10.2014, 11:59 -0700 schrieb Don Armstrong:
> Control: retitle -1 gdm3 fails to load login screen (with less-than-useful
> error message)
> Control: severity -1 important
> Control: tag -1 moreinfo
> Control: reassign -1 gdm3
> Control: found -1 3.14.1-1
>
> On Thu, 23 Oct
Control: retitle -1 gdm3 fails to load login screen (with less-than-useful
error message)
Control: severity -1 important
Control: tag -1 moreinfo
Control: reassign -1 gdm3
Control: found -1 3.14.1-1
On Thu, 23 Oct 2014, Jürgen Kleber wrote:
> after updating the system on 21 Oct. the X server was
On Tue, May 1, 2012 at 7:13 PM, Charles Kroeger
wrote:
>
> After a dist-upgrade to an AMD64 wheezy/sid installation I get the following:
>
> $startx
> /etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found
>
> xinit: giving up
> xinit: unable to connect to X server: connection refused
> xinit: s
Indulekha wrote:
> Charles Kroeger wrote:
> > $startx
> > /etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found
>
> Appears you no longer have the xserver installed.
> Upgrade get interrupted, or finish with errors perhaps?
I noticed today that an 'apt-get dist-upgrade' in Sid wanted to remove
On Tue, May 01, 2012 at 09:53:55PM -0500, Charles Kroeger wrote:
> On Wed, 02 May 2012 02:00:02 +0200
> Indulekha wrote:
>
>
> > Appears you no longer have the xserver installed.
> > Upgrade get interrupted, or finish with errors perhaps?
>
>
> Thanks for your response however I'm not sure it
On Wed, 02 May 2012 02:00:02 +0200
Indulekha wrote:
> Appears you no longer have the xserver installed.
> Upgrade get interrupted, or finish with errors perhaps?
Thanks for your response however I'm not sure it isn't something else as all
the nividia-glx 295.40-1 sources and drivers inclusive
On Tue, May 01, 2012 at 06:13:51PM -0500, Charles Kroeger wrote:
> After a dist-upgrade to an AMD64 wheezy/sid installation I get the following:
>
> $startx
> /etc/X11/xinit/sderverrc: 3: exec: /usr/bin/X: not found
>
> xinit: giving up
> xinit: unable to connect to X server: connection refused
>
On Sb, 17 mar 12, 21:02:10, Andriy Samsonyuk wrote:
>
> i simply changed LABEL=lv_* with /dev/sda? for correct partitions.
> As a result the partitions seemed to be mounted read only for the user.
> And X crashed with different errors :-/
> I still was able to write in /home and /tmp. But after ch
On Sat, Mar 17, 2012 at 09:02:10PM +0100, Andriy Samsonyuk wrote:
> LABEL=lv_var /var ext3 defaults,noatime,nosuid,nodev 0 2
> LABEL=lv_tmp /tmp ext3 defaults,noatime,nosuid,nodev 0 2
> LABEL=lv_home /home ext2 defaults,noatime,nosuid,nodev 0 2
> ***
>
> i simply changed LABEL=lv_* with /dev
> Would you care to expand a bit? Might help others in your situation.
i will try ;-)
Since i debootstrapt my system and have different partitions for
/, swap, /usr, /var, /tmp and /home directories i had to set the mount
options in /etc/fstab manually.
The easiest way was to take an existing, wo
On Vi, 16 mar 12, 13:48:20, Andriy Samsonyuk wrote:
> Eureka!
> the problem was in wrongly mounted /var and /usr partitions.
> was not so easy to find :-(
Would you care to expand a bit? Might help others in your situation.
Kind regards,
Andrei
--
Offtopic discussions among Debian users and deve
Eureka!
the problem was in wrongly mounted /var and /usr partitions.
was not so easy to find :-(
Thanx for your help!
--
You're not my type. For that matter, you're not even my species!!!
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
On Fri, Mar 16, 2012 at 01:17:51AM +0200, Andrei POPESCU wrote:
> On Jo, 15 mar 12, 23:35:22, Andriy Samsonyuk wrote:
> > > I usually run startx as a user to get it up & running; I'm puzzled
> > > by your insistence on 'xinit'. :)
> > i tryed startx. I get more output:
> >
> > hostname: Name or
On Jo, 15 mar 12, 23:35:22, Andriy Samsonyuk wrote:
> > I usually run startx as a user to get it up & running; I'm puzzled
> > by your insistence on 'xinit'. :)
> i tryed startx. I get more output:
>
> hostname: Name or service not known
> xauth: (stdin):1: bad display name "$HOSTNAME:0" in "add
> I usually run startx as a user to get it up & running; I'm puzzled
> by your insistence on 'xinit'. :)
i tryed startx. I get more output:
hostname: Name or service not known
xauth: (stdin):1: bad display name "$HOSTNAME:0" in "add" command
X: user not authorized...
Can someone tell me what i
On 15/03/12 16:03, Andriy Samsonyuk wrote:
after user login ->
"X: user not authorized to run the X server"
no ~/.xsession-errors
no /var/log/Xorg.0.log
root# xinit
-> everything works fine
what am i missing?
I usually run startx as a user to get it up & running; I'm puzzled by
your insi
> > i am starting from scratch - reinstalled X + default configuration
>
> Mmmm, unfortunately that won't overide any config files you may have
> changed.
since the config files changed by me were in /etc/X11/ i simply removed
the directory before installing xorg for the second time ;-)
> What v
Andriy Samsonyuk wrote:
> /etc/inittab is the same as on my working debian squeeze machine:
>
> ***
This looks OK for me. You should find out why the X-Server starts on tty0
and not on tty7. Maybe that is the problem, but it's only a guess. Does
anybody here in this Forum know where this can be
No need to CC me, I am subscribed.
Note: I am running Wheezy, but I am fairly sure this applies to Squeeze.
On Wed, Mar 14, 2012 at 10:51:23AM +0100, Andriy Samsonyuk wrote:
> > On Tue, Mar 13, 2012 at 12:26:53PM +0100, Andriy Samsonyuk wrote:
> > > Hello,
> > >
> > > i am currenttly running d
On Tue, Mar 13, 2012 at 09:08:07PM +0100, Juergen F. Pennings wrote:
> Andriy Samsonyuk wrote:
> > Every time i start X i get:
> >
> > Fatal server error:
> > xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
> >
> Hello Andriy,
> for me it looks strange that you want to start th
Hi,
first of all thanks for help!
On Wed, Mar 14, 2012 at 06:47:38PM +1300, Chris Bannister wrote:
> [CCing Andriy, (I'm guessing he is not subscribed)]
>
> Andriy, if you are subscribed please let us know.
i am indeed subscribed to the list
>
> On Tue, Mar 13, 2012 at 12:26:53PM +0100, Andriy
[CCing Andriy, (I'm guessing he is not subscribed)]
Andriy, if you are subscribed please let us know.
On Tue, Mar 13, 2012 at 12:26:53PM +0100, Andriy Samsonyuk wrote:
> Hello,
>
> i am currenttly running debian 6.0 with 2.6.32-5-486 on CF-27 (toughbook)
> 300MHz Pentium II with 128MB RAM.
>
>
Andriy Samsonyuk wrote:
> Every time i start X i get:
>
> Fatal server error:
> xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
>
Hello Andriy,
for me it looks strange that you want to start the X-Server on tty0. The
normal behaviour under debian is to start it on tty7 or highe
On Tue, Mar 13, 2012 at 11:03, Andrei POPESCU wrote:
> On Ma, 13 mar 12, 12:26:53, Andriy Samsonyuk wrote:
>>
>> Every time i start X i get:
>>
>> Fatal server error:
>> xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
>>
>> changing of the permissions of /dev/tty0 does not help.
On Ma, 13 mar 12, 12:26:53, Andriy Samsonyuk wrote:
>
> Every time i start X i get:
>
> Fatal server error:
> xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
>
> changing of the permissions of /dev/tty0 does not help.
Something interesting in /var/log/Xorg.0.log ?
Kind regar
On Tue 13 Mar 2012 at 11:05:27 +0100, Andriy Samsonyuk wrote:
> i am currenttly running debian 6.0 with 2.6.32-5-486 on CF-27 (toughbook)
> 300MHz Pentium II with 128MB RAM.
>
> I dont need a desktop (gnome, kde, etc) but would like to have X-server
> running.
>
> X starts for root, but not for
1 - 100 of 370 matches
Mail list logo
