Hi,
I experimented with torify of the TOR project today and failed
host:/tmp>sudo torify aria2c --async-dns false http:aria2c http://example.com
1591180702 WARNING torsocks[20364]: [syscall] Unsupported syscall number 2.
Denying the call (in tsocks_syscall() at syscall.c:604)
1591180702 WARNING
Hi,
To record my screen with audio I installed
obs and then simplescreenrecoder.
Recording the video stream more or less works (I cannot record a
firefox-window and need to record the full screen).
But recording the audio from the source which will be replayed
by firefox only give me a stutteri
Hello,
For OBS you can use the Audio Output Capture which requires PulseAudio to be
running. It will look for the monitor device of your current soundcard to
capture all audio you hear. For simplescreenrecorder, I don't know as I prefer
OBS for it's extra compositing features and convenience.
I just installed simplescreenrecorder as well. The same pulseaudio method
should also work for that by choosing the "Monitor" variants, although I have
to add that it would not allow you to capture both a mic and firefox (or other
application at the same time) unless you play back your own micro
Hi Daniel,
short question...what is catia (beside a CAD program by Dassault
Systems... ;)...
Can't find that in portage...
Cheers!
Meino
On 06/03 03:47, Daniel Sonck wrote:
> I just installed simplescreenrecorder as well. The same pulseaudio method
> should also work for that by choosing the
I'm not entirely sure if it's part of portage yet (long time since I touched
gentoo) but it's a modern jack routing program in similar style to the cadence
program. If cadence exists, it's likely bundled with catia otherwise it can be
found in the audio overlay, this issue specifically mentions
Hi Daniel,
thanks a lotcadence failed to compile...
In file included from /usr/include/qt5/QtCore/qhashfunctions.h:44,
from /usr/include/qt5/QtCore/qlist.h:47,
from /usr/include/qt5/QtCore/qstringlist.h:41,
from /usr/include/qt5/QtGui/qcolor.
It might be that your Qt5 is perhaps partially updated or out of date even,
but not sure. I do know that it can be a pain to compile due to Qt5 changing.
If it's too much of a hassle to get it to work, Catia could be replaced by
QJackCtl, however then you will need to have the tweaks Cadence doe
On Wed, Jun 03, 2020 at 12:47:34PM +0200, tu...@posteo.de wrote:
> host:/tmp>sudo torify aria2c --async-dns false http:aria2c http://example.com
> 1591180702 WARNING torsocks[20364]: [syscall] Unsupported syscall number 2.
> Denying the call (in tsocks_syscall() at syscall.c:604)
> 1591180702 WARN
Hi Daniel,
sorry for not understanding the whole setup ...
Please see my inserted questions below:
On 06/03 04:44, Daniel Sonck wrote:
> It might be that your Qt5 is perhaps partially updated or out of date even,
> but not sure. I do know that it can be a pain to compile due to Qt5 changing.
When I try to boot I'm getting an error:
"Kernel panic - not syncing: No working init found. Try passing init=
option to kernel."
I am running very low on disk space, I think.
I've tried to boot strap the system and remove some files but boot strap
is not working. When I boot from minimal-insta
I am getting a segmentation violation when running a recompiled
'cmake'. I rebuilt with debugging symbols; here are the results:
/var/tmp/portage/dev-util/cmake-3.16.5/image/usr/bin # gdb ./cmake
GNU gdb (Gentoo 9.1 vanilla) 9.1
Copyright (C) 2020 Free Software Foundation, Inc.
...
Reading symbols
the...@sys-concept.com wrote:
> When I try to boot I'm getting an error:
>
> "Kernel panic - not syncing: No working init found. Try passing init=
> option to kernel."
>
> I am running very low on disk space, I think.
> I've tried to boot strap the system and remove some files but boot strap
> is
On 06/03/2020 10:31 AM, Dale wrote:
> the...@sys-concept.com wrote:
>> When I try to boot I'm getting an error:
>>
>> "Kernel panic - not syncing: No working init found. Try passing init=
>> option to kernel."
>>
>> I am running very low on disk space, I think.
>> I've tried to boot strap the syst
Can you provide the "Command line:" information from when the kernel
first boots? It is around line 5 or so.
- Matthew
On 06/03/2020 10:57 AM, tedheadster wrote:
> Can you provide the "Command line:" information from when the kernel
> first boots? It is around line 5 or so.
>
> - Matthew
To do it I think I need to record the screen as it boots.
--
Thelma
Yes, you do need to capture the kernel output.
The usual way is to hook up a serial cable to another computer and
pipe the output to it. You interrupt the boot (usually by hitting
or in GRUB), and then edit the kernel command line thus:
console=tty1 console=ttyS0,115200n8
If you can do that yo
tedheadster wrote:
> Yes, you do need to capture the kernel output.
>
> The usual way is to hook up a serial cable to another computer and
> pipe the output to it. You interrupt the boot (usually by hitting
> or in GRUB), and then edit the kernel command line thus:
>
> console=tty1 console=ttyS0,
Hello,
On Wed, 03 Jun 2020, tu...@posteo.de wrote:
>In file included from /usr/include/qt5/QtCore/qhashfunctions.h:44,
> from /usr/include/qt5/QtCore/qlist.h:47,
> from /usr/include/qt5/QtCore/qstringlist.h:41,
> from /usr/include/qt5/QtGui/qcolor.h:
Hello,
On Wed, 03 Jun 2020, tedheadster wrote:
>I am getting a segmentation violation when running a recompiled
>'cmake'. I rebuilt with debugging symbols; here are the results:
>
>/var/tmp/portage/dev-util/cmake-3.16.5/image/usr/bin # gdb ./cmake
[..]
>Program received signal SIGSEGV, Segmentatio
On Wed, Jun 3, 2020 at 1:43 PM David Haller wrote:
>
> Hello,
>
> On Wed, 03 Jun 2020, tedheadster wrote:
> >I am getting a segmentation violation when running a recompiled
> >'cmake'. I rebuilt with debugging symbols; here are the results:
> >
> >/var/tmp/portage/dev-util/cmake-3.16.5/image/usr/b
On Wednesday, 3 June 2020 18:28:33 BST Dale wrote:
> tedheadster wrote:
> > Yes, you do need to capture the kernel output.
> >
> > The usual way is to hook up a serial cable to another computer and
> > pipe the output to it. You interrupt the boot (usually by hitting
> > or in GRUB), and then ed
On 3 June 2020 18:24:47 CEST, the...@sys-concept.com wrote:
>When I try to boot I'm getting an error:
>
>"Kernel panic - not syncing: No working init found. Try passing init=
>option to kernel."
>
>I am running very low on disk space, I think.
>I've tried to boot strap the system and remove some f
On 3 June 2020 18:52:59 CEST, the...@sys-concept.com wrote:
>On 06/03/2020 10:31 AM, Dale wrote:
>> the...@sys-concept.com wrote:
>>> When I try to boot I'm getting an error:
>>>
>>> "Kernel panic - not syncing: No working init found. Try passing
>init=
>>> option to kernel."
>>>
>>> I am running
Hello,
On Wed, 03 Jun 2020, David Haller wrote:
[..]
>1. create a file /etc/portage/env/missing-qpainterpath-flags and insert
> this line:
>
>
>CXXFLAGS="${CXXFLAGS} -include QPainterPath"
>
>
>2. add the line
>
>
>=media-sound/cadence-0.9.0-r4 missing-qpainterpath-flags
>
>
On 06/03/2020 11:28 AM, Dale wrote:
> tedheadster wrote:
>> Yes, you do need to capture the kernel output.
>>
>> The usual way is to hook up a serial cable to another computer and
>> pipe the output to it. You interrupt the boot (usually by hitting
>> or in GRUB), and then edit the kernel command
On 06/03/2020 12:06 PM, J. Roeleveld wrote:
> On 3 June 2020 18:24:47 CEST, the...@sys-concept.com wrote:
>> When I try to boot I'm getting an error:
>>
>> "Kernel panic - not syncing: No working init found. Try passing init=
>> option to kernel."
>>
>> I am running very low on disk space, I think
On 3 June 2020 20:38:49 CEST, the...@sys-concept.com wrote:
>On 06/03/2020 12:06 PM, J. Roeleveld wrote:
>> On 3 June 2020 18:24:47 CEST, the...@sys-concept.com wrote:
>>> When I try to boot I'm getting an error:
>>>
>>> "Kernel panic - not syncing: No working init found. Try passing
>init=
>>> op
Yes, I realize it might not have been clear, as I got a bit confused by my own
thought process as well.
I will also answer in pieces related to your questions
On Wednesday, June 3, 2020 5:31:43 PM CEST tu...@posteo.de wrote:
> Hi Daniel,
>
> sorry for not understanding the whole setup ...
>
>
On Thu, Jun 4, 2020 at 2:24 AM wrote:
> When I try to boot I'm getting an error:
>
> "Kernel panic - not syncing: No working init found. Try passing init=
> option to kernel."
>
> I am running very low on disk space, I think.
> I've tried to boot strap the system and remove some files but boot s
30 matches
Mail list logo