> I'm slightly worried by this comment though:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885140#77
I have now tried to temporarily upgrade to the wicd-curses,
wicd-cli, wicd-daemon and python3-wicd versions present in
Debian/experimental. Unfortunately I can only see a fraction
of the Wi
> If nobody steps up to finish the porting, there is (not so nice) plan B:
> disable
> wicd-gtk and leave wicd-curses (more buggy than it should be, but
> usable) and wicd-cli.
Sadly it appears no one has stepped up to do the porting in the four years
since 2017. As a user of wicd-curses, can I h
Hi!
I have been attempting to install emscripten today, and ended up the
libstdc++6 breakage.
Next I found this bug and I'm simply wondering what I can do to help
you guys make progress on this bug?
Unfortunately, I'm just a new user of emscripten so I barely know how
to use it once it is installe
>> Could you please try to upgrade to slim/1.3.6-5.1 to see if that
>> fixes your issue?
> Of course, no problem, but it will have to wait a day or so.
I can now confirm that upgrading to 1.3.6-5.1 does indeed fix
the issue I was experiencing. From my perspective that means
that you may mark this
Of course, no problem, but it will have to wait a day or so. I didn't
notice that there was a new version in /unstable or /experimental when I
checked the other day so it is likely fairly recent.
/Sebastian
Package: slim
Version: 1.3.6-5
Severity: serious
When upgrading from 1.3.6-4+b2 to 1.3.6-5 of slim I noticed that my
window manager appeared to suddenly "crash" and logged me out. However
I had
not changed anything related to that but I had recently upgraded slim so I
investigated it a bit.
I com
6 matches
Mail list logo
