Bug#1008087: gdb caught the crash

2022-03-22 Thread Jiangsu Kumquat
See attached gdb output
gdb -p 52609
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word".
Attaching to process 52609
[New LWP 52610]
[New LWP 52611]
[New LWP 52612]
[New LWP 52613]
[New LWP 52614]
[New LWP 52615]
[New LWP 52616]
[New LWP 52617]
[New LWP 52618]
[New LWP 52619]
[New LWP 52620]
[New LWP 52621]
[New LWP 52622]
[New LWP 52623]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7feaf5a47c61 in __GI___clock_nanosleep (clock_id=clock_id@entry=0, 
flags=flags@entry=0, req=0x7ffe8c7b27e0,
rem=0x7ffe8c7b27e0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:48
48  ../sysdeps/unix/sysv/linux/clock_nanosleep.c: No such file or directory.
(gdb) c
Continuing.

Thread 6 "NTCP2" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7feaef7fe700 (LWP 52614)]
0x55669a929fd4 in i2p::data::RouterInfo::ReadFromStream(std::istream&) ()
(gdb) thread apply all bt

Thread 15 (Thread 0x7feade7fc700 (LWP 52623) "SAM"):
#0  0x7feaf5a80116 in epoll_wait (epfd=41, events=0x7feade7fb770, 
maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x55669a82b3d8 in boost::asio::detail::epoll_reactor::run(long, 
boost::asio::detail::op_queue&) ()
#2  0x55669a97b3cc in i2p::util::RunnableService::Run() ()
#3  0x7feaf5c51ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7feaf5b4fea7 in start_thread (arg=) at 
pthread_create.c:477
#5  0x7feaf5a7fdef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 14 (Thread 0x7feadeffd700 (LWP 52622) "Destination"):
#0  0x7feaf5a80116 in epoll_wait (epfd=37, events=0x7feadeffc770, 
maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x55669a82b3d8 in boost::asio::detail::epoll_reactor::run(long, 
boost::asio::detail::op_queue&) ()
#2  0x55669a97b3cc in i2p::util::RunnableService::Run() ()
#3  0x7feaf5c51ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7feaf5b4fea7 in start_thread (arg=) at 
pthread_create.c:477
#5  0x7feaf5a7fdef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 13 (Thread 0x7feadf7fe700 (LWP 52621) "Destination"):
#0  0x7feaf5a80116 in epoll_wait (epfd=32, events=0x7feadf7fd770, 
maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x55669a82b3d8 in boost::asio::detail::epoll_reactor::run(long, 
boost::asio::detail::op_queue&) ()
#2  0x55669a97b3cc in i2p::util::RunnableService::Run() ()
#3  0x7feaf5c51ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7feaf5b4fea7 in start_thread (arg=) at 
pthread_create.c:477
#5  0x7feaf5a7fdef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 12 (Thread 0x7fead700 (LWP 52620) "Destination"):
#0  0x7feaf5a80116 in epoll_wait (epfd=29, events=0x7feadfffe770, 
maxevents=128, timeout=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
#1  0x55669a82b3d8 in boost::asio::detail::epoll_reactor::run(long, 
boost::asio::detail::op_queue&) ()
#2  0x55669a97b3cc in i2p::util::RunnableService::Run() ()
#3  0x7feaf5c51ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#4  0x7feaf5b4fea7 in start_thread (arg=) at 
pthread_create.c:477
#5  0x7feaf5a7fdef in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 11 (Thread 0x7feaecff9700 (LWP 52619) "Tunnels"):
#0  futex_abstimed_wait_cancelable (private=0, abstime=0x7feaecff8ce0, 
clockid=-318796864, expected=0, futex_word=0x55669ab297a4 
) at ../sysdeps/nptl/futex-internal.h:323
#1  __pthread_cond_wait_common (abstime=0x7feaecff8ce0, clockid=-318796864, 
mutex=0x55669ab29750 , cond=0x55669ab29778 
) at pthread_cond_wait.c:520
#2  __pthread_cond_clockwait (abstime=0x7feaecff8ce0, clockid=-318796864, 
mutex=0x55669ab29750 , cond=0x55669ab29778 
) at pthread_cond_wait.c:677
--Type  for more, q to quit, c to continue without paging--c
#3  __pthread_cond_clockwait (cond=0x55669ab29778 , 
mutex=0x55669ab29750 , clockid=-318796864, 
abstime=0x7feaecff8ce0) at pthread_cond_wait.c:665
#4  0x55669a95db62 in i2p::tunnel::Tunnels::Run() ()
#5  0x7feaf5c51ed0 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6
#6  0x7feaf5b4fea7 in start_thread (arg=) at 

Bug#1008087: i2pd: I2Pd crashes after running for about 2-5 minutes. It is running on a VPS server with 2 gigs RAM.

2022-03-22 Thread Jiangsu Kumquat
Package: i2pd
Version: 2.36.0-1
Severity: important

Dear Maintainer,

The i2pd package is installed and set to run at system startup. I
noticed that it was not running and did:

systemctl restart i2pd

It ran for about 2 minutes then crashed. I started it again, and it
crashed after 5 minutes.

I have not been able to make it run without crashing.

I was expecting the service to run without crashing.

I'm trying to run i2pd on a remote VPS server that has 200 Mbps up/down

-- System Information:
Debian Release: 11.2
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-12-amd64 (SMP w/2 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages i2pd depends on:
ii  adduser 3.118
ii  init-system-helpers 1.60
ii  libboost-filesystem1.74.0   1.74.0-9
ii  libboost-program-options1.74.0  1.74.0-9
ii  libc6   2.31-13+deb11u2
ii  libgcc-s1   10.2.1-6
ii  libminiupnpc17  2.2.1-1
ii  libssl1.1   1.1.1k-1+deb11u2
ii  libstdc++6  10.2.1-6
ii  lsb-base11.1.0
ii  zlib1g  1:1.2.11.dfsg-2

i2pd recommends no packages.

i2pd suggests no packages.

-- Configuration Files:
/etc/i2pd/i2pd.conf changed:
ipv4 = true
ipv6 = true
nat = false
bandwidth = 15000
floodfill = true
[http]
address = 127.0.0.1
port = 7070
[httpproxy]
address = 127.0.0.1
port = 
[socksproxy]
address = 127.0.0.1
port = 4447
[sam]
enabled = true
[bob]
[i2cp]
[i2pcontrol]
[precomputation]
[upnp]
[reseed]
verify = true
[addressbook]
[limits]
[trust]
[exploratory]
[persist]
[cpuext]


-- no debconf information


syslog
Description: Binary data


Bug#966614: gsd-housekeeping: Failed to enumerate children of /var/tmp/systemd-private...

2020-07-31 Thread Jiangsu Kumquat
Package: gnome-settings-daemon
Version: 3.30.2-3

$ apt policy gnome-settings-daemon
gnome-settings-daemon:
  Installed: 3.30.2-3
  Candidate: 3.30.2-3
  Version table:
 *** 3.30.2-3 500
500 http://deb.debian.org/debian buster/main amd64 Packages
100 /var/lib/dpkg/status

I have a bunch of lines like this in my systemd journal logs:

I have a bunch of lines like this for several services:

Jul 31 02:35:45 debian gsd-housekeepin[1546]: Failed to enumerate
children of 
/var/tmp/systemd-private-e7659f24f12a46ba8f34fda22628c99f-upower.service-E5eC1k:
Error opening directory
'/var/tmp/systemd-private-e7659f24f12a46ba8f34fda22628c99f-upower.service-E5eC1k':
Permission denied

looking at the journal logs, they are full of almost nothing but lines
like that for various services.

uname -a
Linux debian 4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1
(2020-06-07) x86_64 GNU/Linux

libc6 Version: 2.28-10

I have not modified anything with the config for that package. I'm
using the default buster setup.



Bug#907576: ITP: dream --A Software Digital Radio Mondiale (DRM) receiver (RFP 691685)

2019-11-05 Thread Jiangsu Kumquat
I have discovered that you do not need a local receiver in order to
use this software.  Please refer to this article on how to use KiwiSDR
to route IQ audio into Dream.

KiwiSDR setup to use the DREAM Receiver
https://ka7u.us/2017/11/17/kiwisdr-setup-to-use-the-dream-receiver/