How do I configure konqueror in buster so that I can run more than one instance?
Doc
--
Web: http://enginehousebooks.com/drevans
signature.asc
Description: OpenPGP digital signature
Thanks to those who replied to my original post,
<45c61e48-0393-a413-4f7a-d88be911a...@gmail.com>; the responses gave me enough
clues to find the source of the problem.
The solution turned out to be obvious in retrospect (like so many things).
For some reason, the buster installation had not
1. I have a server that does all I need it to do under stretch.
2. On that machine, I have installed a clean version of buster on a separate
bootable drive.
3. Under buster on that machine, I have installed (by copy from stretch) an
iptables configuration that seems to be behaving as I expect.
pe...@easthope.ca wrote on 7/17/19 3:32 PM:
> Jul 16 11:25:16 joule stunnel: LOG5[4]: Service [https] accepted connection
> from 127.0.0.1:36140
>
> * From: Reco recovery...@enotuniq.net
> * Date: Wed, 17 Jul 2019 11:01:32 +0300
>> No, you're incorrect. A client application has
Sven Joachim wrote on 6/28/19 11:06 PM:
>
> If you cannot get systemd-tmpfiles-clean.service to do its job,
> something like this should do the trick:
>
> find /tmp -mindepth 1 -mtime +35 -atime +35 -delete
>
I was hoping to avoid having to write a script (because obviously one needs to
add
My reading of the man page for tmpfiles.d suggests that if I edit the file
/etc/tmpfiles.d/tmp.conf so that it contains the line:
d /tmp 1777 root root 35d
then files in /tmp will be deleted after 35 days.
However, that isn't happening; I see for example:
drwxr-xr-x 18 n7dr n7dr4096
finn wrote on 11/07/2018 08:45 AM:
> Solution 1:
> sudo apt purge python3-ipykernel
> sudo apt install python3-ipykernel
>
> Solution 2:
> OR, purge python-notebook package and install it again, it will automatically
> install ipykernel package while resolving its dependency.
> sudo apt purge
D. R. Evans wrote on 11/06/2018 07:56 AM:
> D. R. Evans wrote on 11/05/2018 06:14 PM:
>> vipul kumar wrote on 11/05/2018 05:35 PM:
>>> Run Jupyter-notebook from terminal. Send log report which you'll get on
>>> terminal while running jupyter-notebook.
>>>
>&
D. R. Evans wrote on 11/05/2018 06:14 PM:
> vipul kumar wrote on 11/05/2018 05:35 PM:
>> Run Jupyter-notebook from terminal. Send log report which you'll get on
>> terminal while running jupyter-notebook.
>>
>
>
> [HN:~] jupyter-notebook
> [I 18:11:04.210 No
vipul kumar wrote on 11/05/2018 05:35 PM:
> Run Jupyter-notebook from terminal. Send log report which you'll get on
> terminal while running jupyter-notebook.
>
>
[W 18:07:15.047 NotebookApp] Widgets are unavailable. On Debian, notebook
support for widgets is provided by the package
Running current debian stable (64-bit).
I installed the jupyter-notebook package (which caused several other packages
associated with python3 to be installed).
There was no indication of any problems with the installation, and I didn't
see any messages suggesting that anything else needs to be
Greg Wooledge wrote on 01/18/2018 02:43 PM:
>
> The pacakge for ISC's BIND is called bind9.
>
> This would certainly do the job, but it's massively overkill for a simple
> home LAN DNS server. Nevertheless, if it's what you already know, there
> is benefit in using the known but overengineered
Pascal Hambourg wrote on 01/18/2018 02:41 PM:
>
> named is not a package name. The package name is and has always been
> bind9. Note that there are other recursive DNS server packages such as
> unbound.
Ah! It's been so long since I've built a system that didn't install bind
automatically
I am trying to configure a debian stretch box to provide certain services to
my home network. (In the past this was a wheezy box, and I had everything
working fine. I have not changed the configuration of any other machine; so,
for example, DNS requests from machines on the LAN are still sent to
D. R. Evans wrote on 09/22/2017 11:42 PM:
> I just upgraded my main desktop system (64-bit) from jessie to stretch, and
> there seems to be several problems, but all probably related and caused by a
> single issue somehow related to the kernel; but I don't have any idea how to
>
I just upgraded my main desktop system (64-bit) from jessie to stretch, and
there seems to be several problems, but all probably related and caused by a
single issue somehow related to the kernel; but I don't have any idea how to
move forward.
Following the upgrade:
1. the expected kernel
D. R. Evans wrote on 08/07/2017 10:45 AM:
> Daniel Bareiro wrote on 08/07/2017 09:36 AM:
>
>>>
>>> BUT enigmail won't run because it seems that the current update requires a
>>> version of gnupg that is more recent than the official version that is part
>&g
Daniel Bareiro wrote on 08/07/2017 09:36 AM:
>>
>> BUT enigmail won't run because it seems that the current update requires a
>> version of gnupg that is more recent than the official version that is part
>> of
>> the repositories :-(
>
> I don't remember having this issue. I think I just did
I have been away for a week, and this morning saw that enigmail had been
updated in my absence, so I updated all the jessie updates offered me by the
official repositories.
This updated thunderbird and enigmail, as expected.
BUT enigmail won't run because it seems that the current update
Daniel Bareiro wrote on 07/25/2017 03:18 PM:
> Hi all!
>
> I just updated Thunderbird on Jessie. Support for the 45.x series has
> ended, so starting with this update Debian is now following the 52.x
> releases.
>
> But after the update, Enigmail stopped working. In fact, when I go to
> (my
Felix Miata wrote on 07/23/2017 08:26 PM:
>
>> I tried this solution (for Arch; I saw some posts about Debian, but nothing
>> that seemed to be a definitive solution):
>
>> https://wiki.archlinux.org/index.php/GRUB/Tips_and_tricks#Setting_the_framebuffer_resolution
>
[material elided]
> The
D. R. Evans wrote on 07/22/2017 11:48 AM:
> I am 99+% sure that the proprietary driver is being used, because the screen
> looks quite different during the boot sequence, and slightly different once I
I have discovered that if I open a console after switching to the NVIDIA
driver, th
Hans wrote on 07/22/2017 11:55 AM:
> Maybe try to add a file /etc/X11/xorg.conf (ask google, how it has to look),
> and in it set the driver "nvidia".
>
nvidia-xconfig created such a file, and the driver in it is set to "nvidia",
so I think that is indeed the confirmation I was looking for.
Reco wrote on 07/22/2017 12:37 PM:
> grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
[HN:~] grep -i glx ~/.local/share/xorg/Xorg.[0-9]*.log
grep: /home/n7dr/.local/share/xorg/Xorg.[0-9]*.log: No such file or directory
[HN:~]
Doc
--
Web: http://enginehousebooks.com/drevans
signature.asc
As my old thread has been hijacked, I thought that I'd better start a new one.
Teemu Likonen wrote on 07/17/2017 03:09 PM:
> D. R. Evans [2017-07-17 14:19:32-06] wrote:
>
>> Beginning a couple of weeks ago, I started to experience occasional freezes
>> or
>> sudden bl
Beginning a couple of weeks ago, I started to experience occasional freezes or
sudden blank screens on my 64-bit jessie system.
It just happened again, and this time the following appeared in the syslog:
Jul 17 13:55:05 homebrew kernel: [24064.296254] nouveau E[
PFIFO][:01:00.0] write fault
David Wright wrote on 06/24/2017 06:42 PM:
>
>>> The error message above indicates, that you have network-manager
>>> installed and since stretch NetworkManager-wait-online.service is
>>> enabled by default (it wasn't in jessie).
>
> this would suggest a cause. Do you need the network before
David Wright wrote on 06/23/2017 08:42 AM:
>> Can anyone provide suggestions as to how to remove this delay?
>
> Did you miss https://lists.debian.org/debian-user/2017/06/msg00858.html
> which gave one possibility? It also asked for two things, neither of
> which were forthcoming. I can't find
Fungi4All wrote on 06/22/2017 09:48 PM:
>> From: doc.ev...@gmail.com
>> To: debian-user@lists.debian.org
>>
>> D. R. Evans wrote on 06/21/2017 09:53 AM:
>> It adds about 30 useless seconds to the boot time while the system waits for
>> it
>> to time
D. R. Evans wrote on 06/21/2017 09:53 AM:
> But when I tried the reboot following the upgrade, I lost all network
> connectivity. The boot screen said:
> Failed to Start Network Manager Wait Online
>
> It also suggested issuing the command:
> systemctl status N
Felix Miata wrote on 06/21/2017 01:33 PM:
> Gian Carlo composed on 2017-06-21 21:05 (UTC+0200):
> .
>> What is the output of "/sbin/ifconfig"?
>> Do you see "eth0" or something like "enXX"?
> .
> ip is not included in a default Stretch install. Try 'ip a'
>
That command seems to give more or
Gian Carlo wrote on 06/21/2017 01:05 PM:
> What is the output of "/sbin/ifconfig"?
It's too long to type it all. If you want some part of it, please let me know
and I'll try to type it without too many mistakes.
> Do you see "eth0" or something like "enXX"?
eth0, eth1 and lo are the three
I just completed an upgrade to stretch on an i386 machine.
There were no obvious showstopping errors during the install. I saw a few
"unable to delete directory; directory not empty" errors fly by, but nothing
that seemed dangerous, and the installation didn't complain about anything.
But when I
Paul van der Vlis wrote on 02/15/2017 01:24 PM:
> On 15-02-17 16:32, D. R. Evans wrote:
>
>> That said, I had an icedove crash a few days ago, but it was the first time
>> for perhaps a month, whereas at one point it was happening several times per
>> day.
>
> D
Daniel Bareiro wrote on 02/15/2017 08:07 AM:
>
> That does not sound good. I have been experiencing this for a while in
> Jessie and I was hoping it would be fixed on Stretch :(
>
Getting a bit off-topic, but I have been assuming that icedove must still be
broken in stretch, because surely a
David Wright wrote on 01/21/2017 08:23 AM:
> On Fri 20 Jan 2017 at 10:56:50 (-0700), D. R. Evans wrote:
>> D. R. Evans wrote on 01/02/2017 11:28 AM:
>>> Michael Luecke wrote on 01/01/2017 10:29 AM:
>>>
>>>> Maybe you could try this to find out if there i
D. R. Evans wrote on 01/02/2017 11:28 AM:
> Michael Luecke wrote on 01/01/2017 10:29 AM:
>
>> Maybe you could try this to find out if there is some process blocking
>> the sound device:
>>
>> $ fuser -v /dev/snd/* /dev/dsp*
>
> Thank you very much for that
Michael Luecke wrote on 01/01/2017 10:29 AM:
> Maybe you could try this to find out if there is some process blocking
> the sound device:
>
> $ fuser -v /dev/snd/* /dev/dsp*
Thank you very much for that suggestion. I'll try it when I next reboot that
machine (probably sometime in the next
D. R. Evans wrote on 12/28/2016 04:18 PM:
> I have a 32-bit system running jessie that gives the following error the
> first time that I try to use ALSA following a reboot: ERROR: Cannot open
> audio device: hw:0,0 error number -16 Device or resource busy
>
> It doesn't seem to ma
I have a 32-bit system running jessie that gives the following error the first
time that I try to use ALSA following a reboot:
ERROR: Cannot open audio device: hw:0,0
error number -16
Device or resource busy
It doesn't seem to matter how long I wait following a reboot, the above error
deloptes wrote on 10/27/2016 12:14 PM:
>>
>
> It looks reasonable. What you can do, since you have pulse installed, you
> could run pavucontrol and setup the input devices properly. Perhaps your
> problem is visible there - muted/default etc. I usually start recording and
> run pavucontrol,
deloptes wrote on 10/27/2016 12:32 AM:
>
> It is very simple
I am glad to hear it.
>
> 1) find out the input
>
> shell> cat /proc/asound/devices
n7dr@shack:~$ cat /proc/asound/devices
2: [ 0] : control
3: [ 0- 0]: digital audio playback
4: [ 0- 0]: digital audio capture
5: [
I am trying to set up the ability to record line-in, but have been unable to
make it work and would appreciate advice. (I have looked at quite a few web
pages of various kinds of help for ALSA, but all of them seem to be rather
vague on the details of recording.)
The hardware is very simple:
Jonathan Dowland wrote on 09/01/2016 03:07 AM:
>
> I'd report it against gscan2pdf in the first instance. The maintainers of the
> package which has broken will be best equipped to figure out whether or not
> the
> problem needs changes in the gscan2pdf package or elsewhere; the bug can
>
As of a few days ago the gscan2pdf program is no longer functioning properly
in up-to-date jessie.
The culprit seems to be one of the packages updated as part of the recent
imagemagick security update. But I don't which of the updated files, or even
which package, causes the problem (indeed, I am
Emile Antonios wrote on 08/04/2016 01:18 AM:
> I've noticed that over the last few weeks Icedove is crashing. I've
> never had a problem with that before. It typically happens when clicking
> on or deleting an email. I don't get any error, it just closes.
>
> I'm running Jessie KDE
>
> same
Michael Biebl wrote on 07/16/2016 07:25 AM:
>
> tmpreaper is no longer needed or recommended under systemd.
> systemd-tmpfiles already does time-based cleanup as builtin feature.
>
Thank you for that information (which was news to me), but in any case I would
far rather rely on a separate
MI wrote on 07/16/2016 06:53 AM:
>
> That is, it works as an equivalent to TMPTIME=-1. But I do want to cleanup
> /tmp, just
> with some value of TMPTIME > 0.
That's what tmpreaper is for.
Doc
--
Web: http://www.sff.net/people/N7DR
signature.asc
Description: OpenPGP digital signature
MI wrote on 07/11/2016 09:44 AM:
>
> Sounds promising!
>
> Would you share what you have in /etc/tmpfiles.d/ ? From what I had read,
> that is
> where systemd would read it's tmp settings, and where it would have migrated
> settings
> from rcS on upgades.
>
[HN:tmpfiles.d] ls -al
total 20
MI wrote on 07/10/2016 03:04 PM:
> That was how it has "always" worked before. But now systemd ignores TMPTIME,
> and also
> seems to ignore it's own "age" option, unless I'm not using it right.
>
I am running Jessie, and have
TMPTIME=-1
in /etc/default/rcS
and it still works fine for me.
In wheezy, the following command worked correctly:
qdbus org.kde.yakuake /yakuake/sessions runCommandInTerminal $SESSION_ID "tmux"
Following my upgrade to jessie, the same command produces:
qdbus: could not exec '/usr/lib/i386-linux-gnu/qt4/bin/qdbus': No such file or
D. R. Evans wrote on 08/31/2015 01:09 PM:
>> The solution of this problem should be as simple as:
>>
>> chgrp adm /var/log/polipo/pol*
>> rm -f /var/log/polipo/polipo.log.1.gz
>
> OK; I have done that, and will let you know tomorrow whether the problem has
> go
Reco wrote on 08/29/2015 12:17 PM:
>
> Your /etc/logrotate.d/polipo should contain this line:
>
> su proxy adm
>
Yep.
[stuff elided]
>
> The solution of this problem should be as simple as:
>
> chgrp adm /var/log/polipo/pol*
> rm -f /var/log/polipo/polipo.log.1.gz
OK; I have done that,
Martin T wrote on 08/27/2015 08:08 AM:
Now for some reason db5.1-util package is kept back despite the fact
that I execute apt-get dist-upgrade:
I did an upgrade yesterday, and saw the same thing.
Experience suggests to me that it's a packaging dependency inconsistency
somewhere and will
niya levi wrote on 08/22/2015 11:40 AM:
i have tried but unsuccessful.
I suggest providing details and asking for help on the zfs-discuss reflector.
I am now running zfs on jessie, but it was a (rather painful) upgrade rather
than a clean installation.
Doc
--
Web:
D. R. Evans wrote on 08/25/2015 02:04 PM:
D. R. Evans wrote on 08/25/2015 01:56 PM:
I am trying to upgrade my main desktop machine, but the process is halting
with an error, after all the packages are downloaded and half an hour or so
of
actual installation:
Error
I am trying to upgrade my main desktop machine, but the process is halting
with an error, after all the packages are downloaded and half an hour or so of
actual installation:
Setting up libxkbcommon0:amd64 (0.4.3-2) ...
dpkg: dependency problems prevent configuration of libgtk-3-bin:
D. R. Evans wrote on 08/25/2015 01:56 PM:
I am trying to upgrade my main desktop machine, but the process is halting
with an error, after all the packages are downloaded and half an hour or so of
actual installation:
Error: GDBus.Error:org.freedesktop.DBus.Error.Spawn.PermissionsInvalid
Siard wrote on 07/15/2015 11:12 AM:
If these links are not broken, i.e. either cm-super or cm-super-minimal
(TeX font package) is installed, so the fonts in /usr/share/texmf/fonts
exist, then these fonts should be available, e.g. in LibreOffice.
The links are not broken. I can happily look
David Wright wrote on 07/15/2015 09:43 PM:
They appear just fine here (jessie) so it's tricky to think of what's wrong.
Do you have any other type1 fonts that work ok? If there's a mistake
Yep.
$ fc-list :spacing=mono
includes, for example,
/usr/share/fonts/X11/Type1/c0582bt_.pfb: Courier
Gene Heskett wrote on 07/16/2015 02:31 PM:
On Thursday 16 July 2015 16:25:29 Mike Castle wrote:
For xfce, you might try this:
Settings Manager Session and Startup Application Autostart
Scroll down and uncheck Screensaver.
Hadn't thought of that, thanks. I did set it by unchecking all the
Siard wrote on 07/15/2015 08:00 AM:
D. R. Evans wrote:
The description of the package cm-super-x11 says:
This package makes the cm-super fonts available to X11. This
package does not contain any fonts itself but allows one to reuse the
cm-super fonts as X11 screen fonts.
Nice, but how
The description of the package cm-super-x11 says:
This package makes the cm-super fonts available to X11. This package
does not contain any fonts itself but allows one to reuse the cm-super
fonts as X11 screen fonts.
Nice, but how does one actually use these fonts once the package has been
Fekete Tamás wrote on 06/01/2015 11:02 AM:
The only thing I can add to this topic that the problem came not because of
a
bad apt-get dist-upgrade, because boot was slowly even if I installed a
completely new jessie.
Based on your answers, it seems my problem is an exception and not the
bri...@aracnet.com wrote on 05/28/2015 09:47 PM:
what is the physical port, is it an actual rs-232 ?
Yes. ( Amazingly, such things do still exist :-) )
But I figured it out this morning. I was being completely misled by the error
message that came from the application, which made it seem that
Prior to installing debian, I have used several releases of *buntu on a
machine on which /dev/ttyS4 is used; *buntu always detected and allowed me to
use the port automagically.
Wheezy, however, sees only ttyS0, S1, S2 and S3. As far as I have been able to
determine, none of these is associated
Re-send, with the correct subject line. I keep getting wheezy and jessie mixed
up. Sorry.
Prior to installing debian, I have used several releases of *buntu on a
machine on which /dev/ttyS4 is used; *buntu always detected and allowed me to
use the port automagically.
Jessie, however, sees
David Wright wrote on 05/26/2015 05:35 PM:
If I understand you correctly, I think that you are saying that:
n7dr@shack:~$ AUTHORITY=/home/n7dr/.Xauthority HOME=/root sudo -E xterm
I probably misunderstood you.
No, but you left out the X in XAUTHORITY.
I'm glad that one of us is awake
I have just installed stable (jessie) on a machine that used to run Kubuntu.
This machine is mostly accessed remotely, using ssh.
If I log in as a normal user over ssh, I can run X programs fine. (For
example, typing xterm brings up the expected terminal.)
However, if I execute sudo xterm, then
Reco wrote on 05/26/2015 01:53 PM:
Yet there's a way to solve your problem - get a habit of running
X clients like this:
HOME=/root sudo -E xterm
Re-defining $HOME is crucial as otherwise you risk users' rewriting
configuration files by root.
Are you saying that if I type:
Lisi Reisz wrote on 05/26/2015 03:06 PM:
When you installed, did you install with root?
I'm sorry, I don't understand the question.
But:
n7dr@shack:~$ pwd
/home/n7dr
n7dr@shack:~$ su
Password:
root@shack:/home/n7dr# pwd
/home/n7dr
root@shack:/home/n7dr# cd
root@shack:~# pwd
/root
D. R. Evans wrote on 05/26/2015 04:52 PM:
If I understand you correctly, I think that you are saying that:
n7dr@shack:~$ AUTHORITY=/home/n7dr/.Xauthority HOME=/root sudo -E xterm
I probably misunderstood you.
Anyway, after some more experimenting, I discovered that this works:
sudo
David Wright wrote on 05/26/2015 04:16 PM:
When I ssh to a remote machine as myself, DISPLAY is set to localhost:10.0
(11, 12, etc) and AIUI X clients find my local X server through the
encrypted ssh connection. Because the authority file on the remote
host is in its standard location, namely
Lisi Reisz wrote on 05/26/2015 02:30 PM:
On Tuesday 26 May 2015 20:43:57 D. R. Evans wrote:
What is wrong and how do I fix it so that I can run graphical programs
across the network using sudo?
I'm sure it's just a simple configuration issue, but my google-fu seems to
be lacking today
David Christensen wrote on 01/01/2015 05:53 PM:
restore). More recently, I learned enough zfs-fuse for single and
mirrored data drives. I later migrated to ZOL for performance.
Administration of ZFS file systems requires a lot more knowledge and
planning.
This must be one of those
Mark Neyhart wrote on 11/20/2014 05:49 PM:
The update (auto-update.sh) executed without error with the message:
ASPEED Graphics Family Linux XORG 7.7 driver update finished
This should result in the file ast_drv.so in
/usr/lib/xorg/modules/drivers
Is it there?
Yes; as I mentioned in
Andrei POPESCU wrote on 11/20/2014 10:51 PM:
On Jo, 20 nov 14, 16:00:23, D. R. Evans wrote:
The update (auto-update.sh) executed without error with the message:
ASPEED Graphics Family Linux XORG 7.7 driver update finished
I'll stop with a stab in the dark: I see from your Xorg.0.log
lee wrote on 11/20/2014 04:36 PM:
D. R. Evans doc.ev...@gmail.com writes:
I just installed wheezy on a new system, and no matter what I have tried, I
am
unable to get the attached monitor to display at 1920x1200. All my other
systems display at that resolution when attached to the same
I just installed wheezy on a new system, and no matter what I have tried, I am
unable to get the attached monitor to display at 1920x1200. All my other
systems display at that resolution when attached to the same monitor.
I won't bore you with all the things I've tried without success. (At least,
Andrei POPESCU wrote on 11/20/2014 12:19 PM:
On Jo, 20 nov 14, 12:05:11, D. R. Evans wrote:
I just installed wheezy on a new system, and no matter what I have tried, I
am
unable to get the attached monitor to display at 1920x1200. All my other
systems display at that resolution when attached
Andrei POPESCU wrote on 11/20/2014 02:03 PM:
your adapter. It might be prudent to give more details about where you
obtained it from (e.g. the download page).
I downloaded it from:
http://www.asus.com/us/Commercial_Servers_Workstations/P9DE4L/HelpDesk_Download/
Select Linux, then VGA.
101 - 181 of 181 matches
Mail list logo
