Bug#1033795: spamassassin: Spamassassin does start

2023-04-01 Thread Ed Lawson
Package: spamassassin
Version: 4.0.0-4
Severity: important
X-Debbugs-Cc: elaw...@grizzy.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

Spamassassin does not start and is not functional. I have two computers
running Debian Sid and spamassissin is not working on either.  When I
run systemctl status spamassassin it reports "Units spamassassin.service
could not be found."  If I run systemctl enable spamassassin.service it
reports "Unit file spamassassin.service does not exist."


-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
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 spamassassin depends on:
ii  adduser 3.132
ii  libhtml-parser-perl 3.81-1
ii  libhttp-date-perl   6.05-2
ii  libio-string-perl   1.08-4
ii  libmail-dkim-perl   1.20230212-1
ii  libnet-dns-perl 1.36-1
ii  libnetaddr-ip-perl  4.079+dfsg-2+b1
ii  libsocket6-perl 0.29-3
ii  libsys-hostname-long-perl   1.5-3
ii  libwww-perl 6.68-1
ii  lsb-base11.6
ii  perl [libarchive-tar-perl]  5.36.0-7
ii  sysvinit-utils [lsb-base]   3.06-3

Versions of packages spamassassin recommends:
ii  gnupg  2.2.40-1.1
ii  libbsd-resource-perl   1.2911-2+b1
ii  libmail-dmarc-perl 1.20211209-4
ii  libmail-spf-perl   2.9.0-5
ii  perl [libsys-syslog-perl]  5.36.0-7
ii  sa-compile 4.0.0-4
ii  spamc  4.0.0-4

Versions of packages spamassassin suggests:
ii  libdbi-perl   1.643-4
pn  libencode-detect-perl 
pn  libgeoip2-perl
ii  libio-socket-ssl-perl 2.081-2
pn  libnet-patricia-perl  
ii  perl [libcompress-zlib-perl]  5.36.0-7
pn  pyzor 
pn  razor 

-- no debconf information



Bug#1032325: osmo: recurring task option for repeating event nonfunctional

2023-03-03 Thread Ed lawson
Package: osmo
Version: 0.4.4-2
Severity: normal
X-Debbugs-Cc: elaw...@grizzy.com

Dear Maintainer,

When using the Advanced option page to create a recurring task you are given
the options to select the how often a recurring task is repeat in days or
months and how many times the recurring task is to repeat.  Logically you
should be able to have a task occur monthly and then set the number of
repetitions to say 36 so the task would repeat monthly for three years.
However, it does not.  If you put in any number other than 0, the task will not
repeat. Only if you select 0 will the task repeat, and apparent it will repeat
endlessly.  Logically it should not repeat if set to 0, but it does just the
opposite.


-- System Information:
Debian Release: 12.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
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 osmo depends on:
ii  libarchive13  3.6.2-1
ii  libc6 2.36-8
ii  libcairo2 1.16.0-7
ii  libgdk-pixbuf-2.0-0   2.42.10+dfsg-1+b1
ii  libglib2.0-0  2.74.6-1
ii  libgringotts2 1:1.2.1-16
ii  libgspell-1-2 1.12.0-1+b1
ii  libgtk-3-03.24.36-4
ii  libical3  3.0.16-1+b1
ii  libnotify40.8.1-1
ii  libpango-1.0-01.50.12+ds-1
ii  libpangocairo-1.0-0   1.50.12+ds-1
ii  libwebkit2gtk-4.0-37  2.38.5-1
ii  libxml2   2.9.14+dfsg-1.1+b3
ii  xdg-utils 1.1.3-4.1

osmo recommends no packages.

osmo suggests no packages.

-- no debconf information



Bug#1025626: libhamlib4: fails to set freq on TT Jupiter

2022-12-06 Thread Ed Lawson
Package: libhamlib4
Version: 4.5-2+b1
Severity: normal
X-Debbugs-Cc: elaw...@grizzy.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
When using rigctl to set a freq on the Jupiter for 20M and below, the radio is
shifted to 160M band and the reported freq is 1062MHz.  There is no problem
with setting freq/bands above 20M.  All other functions of rigctl work OK. If I
set a freq above 20M band, everything returns to normal.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Tried changing comm setting and various config option via rigctl.
   * What was the outcome of this action?
Thee was no change in the behavior.
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
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 libhamlib4 depends on:
ii  libc6 2.36-6
ii  libusb-1.0-0  2:1.0.26-1

libhamlib4 recommends no packages.

libhamlib4 suggests no packages.

-- no debconf information



Bug#1025622: lrig: Does not work with TT-538 (Jupiter)

2022-12-06 Thread Ed Lawson
Package: lrig
Version: flrig
Severity: important
X-Debbugs-Cc: elaw...@grizzy.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
I was trying to use flrig with my Jupiter, but even though the config info
looks correct and as supplied by flrig, the program always says transceiver not
responding.  I can use hamlib so I know hardware is OK. Also flrig works
properly with a different radio (FT-857D).
   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I tried all manner of config setting.
   * What was the outcome of this action?
Nothing enabled flrig to communicate with the Jupiter.
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
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



Bug#1025290: xdx fails to open due to seg fault

2022-12-01 Thread Ed Lawson
Package: xdx
Version: 2.91-1
Severity: important
X-Debbugs-Cc: elaw...@grizzy.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?  XDX would not open after recent system
upgrade
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Nothing as package will not open/run.
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
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 xdx depends on:
ii  hamradio-files   20221125
ii  libc62.36-6
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1
ii  libglib2.0-0 2.74.2-1
ii  libgtk-3-0   3.24.35-1
ii  libpango-1.0-0   1.50.10+ds-1

xdx recommends no packages.

Versions of packages xdx suggests:
ii  libhamlib-utils  4.5-2+b1

-- no debconf information



Bug#989123: xlog manual not properly displayed

2021-05-26 Thread Ed Lawson
Package: xlog
Version: 2.0.20-1
Severity: normal
X-Debbugs-Cc: elaw...@grizzy.com

Dear Maintainer,

When I attempt to open the manual pages from the help menu, the page that is
displayed shows a blank, gray panel to the left of the Xlog logo instead of a
navigation menu of various sections of the manual.  I have tried opening this
page in Firefox, Chromium, and Dillo and the result is the same.  It appears
there is at least one javascript which fails causing the navigation panel to
not be shown.


-- System Information:
Debian Release: 11.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-7-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages xlog depends on:
ii  dpkg 1.20.9
ii  libc62.31-12
ii  libcairo21.16.0-5
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk2.0-0  2.24.33-2
ii  libhamlib4   4.0-6
ii  libjs-jquery 3.5.1+dfsg+~3.5.5-7
ii  libpango-1.0-0   1.46.2-3
ii  libpangocairo-1.0-0  1.46.2-3
ii  xlog-data2.0.20-1

Versions of packages xlog recommends:
ii  shared-mime-info  2.0-1
ii  xdg-utils 1.1.3-4.1

Versions of packages xlog suggests:
pn  cwdaemon 
ii  extra-xdg-menus  1.0-5
ii  glabels  3.4.1-3



Bug#413113: Bitpim exception errors with memo and todo functions

2007-03-02 Thread Ed Lawson
Package: bitpim
Version: 0.9.12

The following occur when using the program in standalone mode and not
when attempting to
transfer anything to the phone.  I can manipulate phone number info
fine and save/pull numbers from the phone.  Calendar seems to work also.
Phone is Razr 3m and todo and memo functions are grayed out as
selections. 


When attempting to save a memo item it fails with exception and this is
in log:

BitPim version: 0.9.12-Debian
An unexpected exception has occurred.
Please see the help for details on what to do.

Traceback (most recent call last):
  File /usr/share/bitpim/code/memo.py, line 505, in _OnSave
entry=self._data[k]
KeyError

Variables by last 8 frames, innermost last

Frame _OnSave in /usr/share/bitpim/code/memo.py at line 505
  k =  None
evt =  wx._core.CommandEvent; proxy of C++ wxCommandEvent
instance at _40f0dabf_p_wxCo self =  memo.MemoWidget; proxy of C++
wxPanel instance at _003ab808_p_wxPanel sel_idx =  -1


When attempting to save a todo item, same thing with this logged
error message:

BitPim version: 0.9.12-Debian
An unexpected exception has occurred.
Please see the help for details on what to do.

Traceback (most recent call last):
  File /usr/share/bitpim/code/todo.py, line 726, in _OnSave
entry=self._data[k]
KeyError

Variables by last 8 frames, innermost last

Frame _OnSave in /usr/share/bitpim/code/todo.py at line 726
  k =  None
evt =  wx._core.CommandEvent; proxy of C++ wxCommandEvent
instance at _40f0dabf_p_wxCo self =  todo.TodoWidget; proxy of C++
wxPanel instance at _00dcc708_p_wxPanel sel_idx =  -1

I am running kernel  2.6.18-1-686 with an up to date installation of
unstable.


-- 
Ed Lawson
Ham Callsign: K1VP
PGP Key ID:   1591EAD3
PGP Key Fingerprint:  79A1 CDC3 EF3D 7F93 1D28  2D42 58E4 2287 1591 EAD3



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]