On Sat, 30 Nov 2013 10:12:35 +0100
"Dmitrij D. Czarkoff" wrote:
> Andreas Marschall wrote:
> >
> >Yes, very mature. The first statement I would agree on but in what way
> >is Arch Linux with systemd a disaster? It runs very smoothely and fast
> >over here. Or is it just the usual wannabe elitist
Andreas Marschall wrote:
>
>Yes, very mature. The first statement I would agree on but in what way
>is Arch Linux with systemd a disaster? It runs very smoothely and fast
>over here. Or is it just the usual wannabe elitist bull...?
You know, the systemd (and friends) actually does a great job of ru
On Sat, Nov 30, 2013 at 09:38:32AM +0100, Christoph Lohmann wrote:
> Greetings.
>
> On Sat, 30 Nov 2013 09:38:32 +0100 Vidya Singh wrote:
> > On Wed, Nov 27, 2013 at 09:08:43AM +0100, Silvan Jegen wrote:
> > > On Wed, Nov 27, 2013 at 6:20 AM, Ryan O’Hara wrote:
> > > > On Tue, Nov 26, 2013 at 8:
Greetings.
On Sat, 30 Nov 2013 09:38:32 +0100 Vidya Singh wrote:
> On Wed, Nov 27, 2013 at 09:08:43AM +0100, Silvan Jegen wrote:
> > On Wed, Nov 27, 2013 at 6:20 AM, Ryan O’Hara wrote:
> > > On Tue, Nov 26, 2013 at 8:00 PM, Szilágyi Szilveszter
> > > wrote:
> > >> Hello,
> > >>
> > >> I use the
On Wed, Nov 27, 2013 at 09:08:43AM +0100, Silvan Jegen wrote:
> On Wed, Nov 27, 2013 at 6:20 AM, Ryan O’Hara wrote:
> > On Tue, Nov 26, 2013 at 8:00 PM, Szilágyi Szilveszter
> > wrote:
> >> Hello,
> >>
> >> I use the same environment for 6 months
> >> and there were no problem at all.
> >>
> >> S
* Silvan Jegen [27.11.2013 09:09]:
> That might indicate that the problem lies with the MacBook Pro hardware.
Not necessarily. Like I posted before, I have this issue with my Netbook too.
It's an Asus EeePC 1215b. It has an ATI graphics card and I use the OSS driver.
I'll check out if the probl
On Wed, Nov 27, 2013 at 6:20 AM, Ryan O’Hara wrote:
> On Tue, Nov 26, 2013 at 8:00 PM, Szilágyi Szilveszter
> wrote:
>> Hello,
>>
>> I use the same environment for 6 months
>> and there were no problem at all.
>>
>> Szilveszter
>>
>
> Okay, dwm-git, st-git, Arch Linux, MacBook Pro 2012 seems to b
On Wed, Nov 27, 2013 at 6:20 AM, Ryan O’Hara wrote:
>
> Okay, dwm-git, st-git, Arch Linux, MacBook Pro 2012 seems to be what
> most people reproduce it on.
>
For a data point, I haven't had the time to compile suckless in a
while and never heard of these problems.
Hunt that bug down, while I exp
On Tue, Nov 26, 2013 at 8:00 PM, Szilágyi Szilveszter
wrote:
> Hello,
>
> I use the same environment for 6 months
> and there were no problem at all.
>
> Szilveszter
>
Okay, dwm-git, st-git, Arch Linux, MacBook Pro 2012 seems to be what
most people reproduce it on.
Hello,
I use the same environment for 6 months
and there were no problem at all.
Szilveszter
On Tue, Nov 26, 2013 at 06:12:12PM -0800, Ryan O’Hara wrote:
On Tue, Nov 26, 2013 at 07:14:27PM +0100, Andreas Marschall wrote:
I wonder why no other Arch users are reporting on this?
It has been re
On Tue, Nov 26, 2013 at 07:14:27PM +0100, Andreas Marschall wrote:
> I wonder why no other Arch users are reporting on this?
It has been reported before. It’s specifically the combination of dwm
and st, by the way.
https://bbs.archlinux.org/viewtopic.php?id=168041,
https://bbs.archlinux.org/viewt
* Alexander Huemer [26.11.2013 22:25]:
> Since nobody else reported that bug, it really seems like the problem
> lies in the nature of your particular system.
Unfortunately it's not.
I think I remember that this issue was reported here before. The problem is
quite old. I have this problem on t
On Tue, Nov 26, 2013 at 09:00:55PM +0100, Andreas Marschall wrote:
> Hello,
>
> I just cloned the latest git version and removed the commit manually
> from st.c and put the few deleted lines back in.
Why? Reverting a commit is very easy with git. In your case it's the
simple matter of doing:
Hello,
I just cloned the latest git version and removed the commit manually
from st.c and put the few deleted lines back in. Now st works just fine again.
That's
all I can say and I think that was pretty bad-ass of me given the fact
that I can only do "hello world" in C :-)
I'd say it's up to th
On Tue, Nov 26, 2013 at 08:32:36PM +0100, Andreas Marschall wrote:
> good evening,
>
> I have spottet the commit that's causing the freeze when killing X and
> trying to go back to tty. It's:
>
> http://git.suckless.org/st/commit/?id=fbc589d50603e8b0de9239e4800e227ab5d0ea69
>
> up until this com
good evening,
I have spottet the commit that's causing the freeze when killing X and
trying to go back to tty. It's:
http://git.suckless.org/st/commit/?id=fbc589d50603e8b0de9239e4800e227ab5d0ea69
up until this commit st works fine for me.
best
Andreas
On Tue, Nov 26, 2013 at 07:14:27PM +0100, Andreas Marschall wrote:
> I'd like to report a serious bug that I have for quite some time now
> with st-git. When I install the git version with "sudo make clean
> install" on my Arch Linux box it installs fine and I can use it. But as
> soon as I kill X
Hello there,
I'd like to report a serious bug that I have for quite some time now
with st-git. When I install the git version with "sudo make clean
install" on my Arch Linux box it installs fine and I can use it. But as
soon as I kill X to go back to tty the screen goes blank (or sometimes I
see t
18 matches
Mail list logo