Bug#854473: smtm: smtm not running

2017-02-07 Thread Gian-Maria Daffré
Package: smtm
Version: 1.6.10
Severity: important

Dear Maintainer,

Thanks for your work on smtm. Please find below some error messages I
have received when starting the application from the terminal in Debian stable.

* What led up to the situation?

Installed smtm. Ran it without options or stock symbols.
   
* What exactly did you do (or not do) that was effective (or
 ineffective)?

Just running the program

* What was the outcome of this action?

See error messages:

No arguments given, and no file found. Using example portfolio.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in join or string at /usr/bin/smtm line 435.
Use of uninitialized value in uc at /usr/bin/smtm line 435.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in numeric gt (>) at /usr/bin/smtm line 508.
Use of uninitialized value in split at /usr/bin/smtm line 495.
Use of uninitialized value in 

Bug#808889: src:linux: Confirm inability to read hwclock on Thinkpad x200 with libreboot

2016-01-05 Thread Gian-Maria Daffré
Package: src:linux
Followup-For: Bug #808889

Dear Maintainer,

I am facing the same problem as the original bug reporter.

Here some further information, which I hope helps further to find the problem.



hwclock -r
hwclock: ioctl(RTC_RD_TIME) to /dev/rtc to read the time failed: Invalid 
argument

hwclock -w
hwclock: ioctl(RTC_RD_TIME) to /dev/rtc to read the time failed: Invalid 
argument



kern.log:Jan  1 01:00:15 x200 kernel: [0.093160] RTC time: 23:14:56, date: 
01/01/-84
kern.log:Jan  1 01:00:15 x200 kernel: [0.795451] rtc_cmos 00:03: RTC can 
wake from S4
kern.log:Jan  1 01:00:15 x200 kernel: [0.795581] rtc_cmos 00:03: rtc core: 
registered rtc_cmos as rtc0
kern.log:Jan  1 01:00:15 x200 kernel: [0.795615] rtc_cmos 00:03: alarms up 
to one month, y3k, 242 bytes nvram, hpet irqs
kern.log:Jan  1 01:00:15 x200 kernel: [0.804337] rtc_cmos 00:03: hctosys: 
unable to read the hardware clock
kern.log:Jan  2 10:34:35 x200 kernel: [ 9769.320290] rtc_cmos 00:03: System 
wakeup disabled by ACPI
kern.log:Jan  1 01:00:15 x200 kernel: [0.093159] RTC time: 13:16:25, date: 
01/02/-84
kern.log:Jan  1 01:00:15 x200 kernel: [0.795543] rtc_cmos 00:03: RTC can 
wake from S4
kern.log:Jan  1 01:00:15 x200 kernel: [0.795672] rtc_cmos 00:03: rtc core: 
registered rtc_cmos as rtc0
kern.log:Jan  1 01:00:15 x200 kernel: [0.795706] rtc_cmos 00:03: alarms up 
to one month, y3k, 242 bytes nvram, hpet irqs
kern.log:Jan  1 01:00:15 x200 kernel: [0.804701] rtc_cmos 00:03: hctosys: 
unable to read the hardware clock


syslog.1:Jan  1 01:00:20 x200 kernel: [0.00] clocksource: 
refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 
7645519600211568 ns
syslog.1:Jan  1 01:00:20 x200 kernel: [0.00] WARNING: Persistent clock 
returned invalid value!
syslog.1:Jan  1 01:00:20 x200 kernel: [0.00] clocksource: hpet: mask: 
0x max_cycles: 0x, max_idle_ns: 133484882848 ns
syslog.1:Jan  1 01:00:20 x200 kernel: [0.00] hpet clockevent registered
syslog.1:Jan  1 01:00:20 x200 kernel: [0.093101] clocksource: jiffies: 
mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns
syslog.1:Jan  1 01:00:20 x200 kernel: [0.137385] acpi PNP0A08:00: _OSC: OS 
supports [ExtendedConfig ASPM ClockPM Segments MSI]
syslog.1:Jan  1 01:00:20 x200 kernel: [0.154089] clocksource: Switched to 
clocksource hpet
syslog.1:Jan  1 01:00:20 x200 kernel: [0.174861] clocksource: acpi_pm: 
mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns
syslog.1:Jan  1 01:00:20 x200 kernel: [0.804644] rtc_cmos 00:03: hctosys: 
unable to read the hardware clock
syslog.1:Jan  1 01:00:20 x200 kernel: [0.883982] PTP clock support 
registered
syslog.1:Jan  1 01:00:20 x200 kernel: [1.712033] clocksource: tsc: mask: 
0x max_cycles: 0x2484a22a448, max_idle_ns: 440795322058 ns
syslog.1:Jan  1 01:00:21 x200 gdm-Xorg-:0[1015]: (II) intel(0): clock: 71.1 MHz 
  Image Size:  261 x 163 mm
syslog.1:Jan  1 01:00:21 x200 gdm-Xorg-:0[1015]: (II) intel(0): clock: 59.3 MHz 
  Image Size:  261 x 163 mm
syslog.1:Jan  1 01:00:45 x200 freshclam[795]: [LibClamAV] ***  Please check the 
timezone and clock settings  ***
syslog.1:Jan  1 20:30:47 x200 ntpd[829]: clock is now synced
syslog.1:Jan  1 20:49:04 x200 ntpd[828]: adjusting clock frequency by -1.193886 
to 24.000481ppm
syslog.1:Jan  1 21:12:50 x200 ntpd[828]: adjusting clock frequency by 2.400168 
to 26.400641ppm
syslog.1:Jan  1 21:39:53 x200 ntpd[828]: adjusting clock frequency by -1.111800 
to 25.288835ppm
syslog.1:Jan  1 22:18:43 x200 gdm-Xorg-:0[21440]: (II) intel(0): clock: 71.1 
MHz   Image Size:  261 x 163 mm
syslog.1:Jan  1 22:18:43 x200 gdm-Xorg-:0[21440]: (II) intel(0): clock: 59.3 
MHz   Image Size:  261 x 163 mm
syslog.1:Jan  1 01:00:15 x200 kernel: [0.00] clocksource: 
refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 
7645519600211568 ns
syslog.1:Jan  1 01:00:15 x200 kernel: [0.00] WARNING: Persistent clock 
returned invalid value!
syslog.1:Jan  1 01:00:15 x200 kernel: [0.00] clocksource: hpet: mask: 
0x max_cycles: 0x, max_idle_ns: 133484882848 ns
syslog.1:Jan  1 01:00:15 x200 kernel: [0.00] hpet clockevent registered
syslog.1:Jan  1 01:00:15 x200 kernel: [0.093103] clocksource: jiffies: 
mask: 0x max_cycles: 0x, max_idle_ns: 764504178510 ns
syslog.1:Jan  1 01:00:15 x200 kernel: [0.137386] acpi PNP0A08:00: _OSC: OS 
supports [ExtendedConfig ASPM ClockPM Segments MSI]
syslog.1:Jan  1 01:00:15 x200 kernel: [0.154088] clocksource: Switched to 
clocksource hpet
syslog.1:Jan  1 01:00:15 x200 kernel: [0.174834] clocksource: acpi_pm: 
mask: 0xff max_cycles: 0xff, max_idle_ns: 2085701024 ns
syslog.1:Jan  1 01:00:15 x200 kernel: [0.804337] rtc_cmos 00:03: hctosys: 
unable to read the hardware clock
syslog.1:Jan  1 01:00:15 x200 kernel: [0.883374] PTP clock 

Bug#760307: specto: Does not recognize network connection when using network-manager

2014-09-02 Thread Gian-Maria Daffré
Package: specto
Version: 0.2.2-3.2
Severity: important

Dear Maintainer,


   * What led up to the situation?

Running the application and doing a refresh for monitoring the website


   * What exactly did you do (or not do) that was effective (or
 ineffective)?

just running the application

   * What was the outcome of this action?

Error message in status bar and error log.

2014-09-02 19:55:59 - watch_web_static.Web_watch - INFO - No network connection 
detected

   * What outcome did you expect instead?

Refresh and monitoring of the selected websites.


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages specto depends on:
ii  gconf23.2.5-1+build1
ii  gnome-icon-theme  3.4.0-2
ii  librsvg2-common   2.36.1-2
ii  python2.7.3-4+deb7u1
ii  python-central0.6.17
ii  python-dbus   1.1.1-1
ii  python-glade2 2.24.0-3+b1
ii  python-gnome2 2.28.1+dfsg-1
ii  python-gtk2   2.24.0-3+b1
ii  python-notify 0.1.1-3
ii  zenity3.4.0-2

specto recommends no packages.

specto suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org