Bug#905549: fwupdate-amd64-signed: missing script/binary in /usr/lib/fwupdate/

[Eric Côté]

Package: fwupdate-amd64-signed
Version: 12+2
Severity: normal

=== >8 ===

Setting up fwupdate (12-2) ...
Installing fwupx64.efi to EFI system partition.
/var/lib/dpkg/info/fwupdate.postinst: 46: /var/lib/dpkg/info/fwupdate.postinst: 
/usr/lib/fwupdate/cleanup: not found
Setting up gir1.2-nm-1.0:amd64 (1.12.2-2) ...
Setting up fwupdate-amd64-signed (12+2) ...
/var/lib/dpkg/info/fwupdate-amd64-signed.postinst: 46: 
/var/lib/dpkg/info/fwupdate-amd64-signed.postinst: /usr/lib/fwupdate/cleanup: 
not found

=== 8< ===

I checked that dir, I only see the efi binaries, and that `install' script, no 
`cleanup' .

TY
Eric

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (1001, 'unstable'), (1000, 'experimental'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.17.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fwupdate-amd64-signed depends on:
ii  fwupdate  12-2

fwupdate-amd64-signed recommends no packages.

fwupdate-amd64-signed suggests no packages.

-- no debconf information

Bug#891703: [Pkg-mailman-hackers] Bug#891703: Bug#891703: mailman3-suite: DB user isn't read from setting_local (mailman3-suite.py in /etc)

[Eric Côté]

Yeah, sorry man, I got distracted by other stuff and forgot. Many profuse
apologies. Just for the sake of completeness (taking into account you've
closed it), here's my output (modified by the new package names/dirs/files):

(my "l" command is : "ls -lAFh")

l /etc/mailman3/
total 88K
-rw-r--r-- 1 root root  399 Mar 14 15:57 apache.conf
-rw-r- 1 root list  701 Feb 12 20:03 hyperkitty.cfg
-rw-r- 1 root www-data 5.9K Mar  5 04:00 mailman3-suite.py
-rw-r--r-- 1 root root 5.7K Feb 28 03:40 mailman3-suite.py.ucf-dist
-rw-r- 1 root list  11K Feb 14 17:46 mailman.cfg
-rw-r--r-- 1 root root  11K Mar 26 07:07 mailman.cfg.ucf-dist
-rw-r- 1 root list  692 Aug 19  2015 mailman-hyperkitty.cfg
-rw-r--r-- 1 root root  701 Mar 14 12:35 mailman-hyperkitty.cfg.ucf-dist
-rw-r- 1 root www-data 5.9K Mar 18 02:15 mailman-web.py
-rw-r--r-- 1 root root 5.7K Mar 18 02:17 mailman-web.py.ucf-dist
-rw-r--r-- 1 root root 2.9K Mar 14 15:57 nginx.conf
-rw-r--r-- 1 root root 5.3K Mar 18 02:14 suite2web.py.patch
-rw-r--r-- 1 root root 1.5K Mar 14 15:57 uwsgi.ini

l /usr/share/mailman3-web
total 48K
-rwxr-xr-x 1 root root  242 May 23  2017 manage.py*
lrwxrwxrwx 1 root root   28 Mar 24 16:39 settings_local.py ->
/etc/mailman3/mailman-web.py
-rw-r- 1 root root 3.5K Mar 25 06:44 settings_local.pyc
-rw-r--r-- 1 root root 5.7K Mar 24 16:39 settings_local.py.sample
-rw-r--r-- 1 root root  15K Mar 24 16:39 settings.py
-rw-r--r-- 1 root root 8.0K Mar 25 06:44 settings.pyc
-rw-r--r-- 1 root root 1.3K May 23  2017 urls.py
-rw-r--r-- 1 root root 1.2K May 23  2017 wsgi.py

On 29 March 2018 at 12:00, Jonas Meurer  wrote:

> Hi Eric,
>
> I'm closing this bugreport as it's missing further information from you.
>
> I'm pretty sure that the bug you discovered is solved in the current
> mailman3/mailman3-web packages in Debian unstable/testing/stretch-
> backports.
>
> Cheers,
>  jonas
>
> Am 15.03.2018 um 22:47 schrieb Jonas Meurer:
> > Hi Eric,
> >
> > Am 04.03.2018 um 04:59 schrieb Eric Côté:
> >> Bug is still present.
> >
> > I did quite some testing of the mailman3 packages in the last days,
> > using all possible database backends. So far, I failed to reproduce the
> > bug you discovered.
> >
> > We renamed the 'mailman3-suite' package to 'mailman3-web' recently, to
> > avoid further confusion about the purpose of the package. Similarly, we
> > renamed 'mailman3-core' to 'mailman3'. You should find all these
> > packages in Debian Unstable by now.
> >
> > Would you mind to purge all your mailman3 packages, do a fresh
> > installation and see, whether you're still able to reproduce the bug
> > with the latest packages from Debian Unstable?
> >
> >> Like I mentioned in my original report, "mailman3suite" is the user in
> >> /usr/share/mailman3-suite/settings.py . I've had to hand edit it so my
> install
> >> reads my DB settings in /etc/mailman3/mailman3-suite.py .
> >
> > After testing different settings, I'm pretty confident that indeed the
> > database settings from '/etc/mailman3/mailman3-suite.py' (or now
> > '/etc/mailman/mailman-web.py') are used in a clean
> > mailman3-suite/mailman3-web installation.
> >
> > Please send the output of the following commands:
> >
> > $ ls -al /etc/mailman3/mailman-suite.py
> > $ ls -al /usr/share/mailman3-suite/settings*
> >
> >> Seems this might be in either python-django-hyperkitty (which is I
> think is the
> >> case), since the log is referencing django and hyperkitty, or in
> >> python3-mailman-hyperkitty (which doesn't seem to be picking up my list
> content
> >> anyway; I should be seeing archives, but I don't, in the web UI).
> >>
> >> I dunno how to refile a bug to another source package or tag another
> (if that's doable).
> >
> > You can reassign existing bugreports by using 'Control:' pseudo-headers
> > at the beginning of mails or by sending control commands to the
> > bugtracker[1].
> >
> > [1] https://www.debian.org/Bugs/server-control
> >
> > Cheers,
> >  jonas
> >
> >
> >
> > ___
> > Pkg-mailman-hackers mailing list
> > pkg-mailman-hack...@lists.alioth.debian.org
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/
> pkg-mailman-hackers
> >
>
>
>


-- 


Eric Côté
[image: https://]about.me/eric.cote.lnu
<https://about.me/eric.cote.lnu?promo=email_sig&utm_source=email_sig&utm_medium=email_sig&utm_campaign=external_links>

Bug#891703: [Pkg-mailman-hackers] Bug#891703: mailman3-suite: DB user isn't read from setting_local (mailman3-suite.py in /etc)

[Eric Côté]

Thank you so much. I'm tracking sid on that box, so I'll be seeing that 
shortly. Thanks for your help and time. Have an awesome day :)

I'll reply with your requested info once I have computer (PC not smartphone) 
access (going to work soon, so don't have time right now).

Take care Jonas, mailman hackers crew

On March 15, 2018 5:47:30 PM EDT, Jonas Meurer  wrote:
>Hi Eric,
>
>Am 04.03.2018 um 04:59 schrieb Eric Côté:
>> Bug is still present.
>
>I did quite some testing of the mailman3 packages in the last days,
>using all possible database backends. So far, I failed to reproduce the
>bug you discovered.
>
>We renamed the 'mailman3-suite' package to 'mailman3-web' recently, to
>avoid further confusion about the purpose of the package. Similarly, we
>renamed 'mailman3-core' to 'mailman3'. You should find all these
>packages in Debian Unstable by now.
>
>Would you mind to purge all your mailman3 packages, do a fresh
>installation and see, whether you're still able to reproduce the bug
>with the latest packages from Debian Unstable?
>
>> Like I mentioned in my original report, "mailman3suite" is the user
>in
>> /usr/share/mailman3-suite/settings.py . I've had to hand edit it so
>my install
>> reads my DB settings in /etc/mailman3/mailman3-suite.py . 
>
>After testing different settings, I'm pretty confident that indeed the
>database settings from '/etc/mailman3/mailman3-suite.py' (or now
>'/etc/mailman/mailman-web.py') are used in a clean
>mailman3-suite/mailman3-web installation.
>
>Please send the output of the following commands:
>
>$ ls -al /etc/mailman3/mailman-suite.py
>$ ls -al /usr/share/mailman3-suite/settings*
>
>> Seems this might be in either python-django-hyperkitty (which is I
>think is the
>> case), since the log is referencing django and hyperkitty, or in
>> python3-mailman-hyperkitty (which doesn't seem to be picking up my
>list content
>> anyway; I should be seeing archives, but I don't, in the web UI).
>> 
>> I dunno how to refile a bug to another source package or tag another
>(if that's doable).
>
>You can reassign existing bugreports by using 'Control:' pseudo-headers
>at the beginning of mails or by sending control commands to the
>bugtracker[1].
>
>[1] https://www.debian.org/Bugs/server-control
>
>Cheers,
> jonas

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#891703: mailman3-suite: DB user isn't read from setting_local (mailman3-suite.py in /etc)

[Eric Côté]

Package: mailman3-suite
Version: 0+20170523-11
Followup-For: Bug #891703

Hi,

Bug is still present.


Like I mentioned in my original report, "mailman3suite" is the user in
/usr/share/mailman3-suite/settings.py . I've had to hand edit it so my install
reads my DB settings in /etc/mailman3/mailman3-suite.py . 


Here's a log excerpt:

=== >8 ===

ERROR 2018-03-04 03:38:09,552 11510 hyperkitty.lib.utils Failed to update the 
fulltext index: FATAL:  Peer authentication failed for user "mailmansuite"
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/hyperkitty/lib/utils.py", line 186, in 
run_with_lock
fn(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/hyperkitty/search_indexes.py", line 
87, in update_index
update_cmd.update_backend("hyperkitty", "default")
  File 
"/usr/lib/python2.7/dist-packages/haystack/management/commands/update_index.py",
 line 256, in update_backend
total = qs.count()
  File "/usr/lib/python2.7/dist-packages/django/db/models/query.py", line 364, 
in count
return self.query.get_count(using=self.db)
  File "/usr/lib/python2.7/dist-packages/django/db/models/sql/query.py", line 
499, in get_count
number = obj.get_aggregation(using, ['__count'])['__count']
  File "/usr/lib/python2.7/dist-packages/django/db/models/sql/query.py", line 
480, in get_aggregation
result = compiler.execute_sql(SINGLE)
  File "/usr/lib/python2.7/dist-packages/django/db/models/sql/compiler.py", 
line 887, in execute_sql
cursor = self.connection.cursor()
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
254, in cursor
return self._cursor()
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
229, in _cursor
self.ensure_connection()
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
213, in ensure_connection
self.connect()
  File "/usr/lib/python2.7/dist-packages/django/db/utils.py", line 94, in 
__exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
213, in ensure_connection
self.connect()
  File "/usr/lib/python2.7/dist-packages/django/db/backends/base/base.py", line 
189, in connect
self.connection = self.get_new_connection(conn_params)
  File 
"/usr/lib/python2.7/dist-packages/django/db/backends/postgresql/base.py", line 
176, in get_new_connection
connection = Database.connect(**conn_params)
  File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 130, in 
connect
conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
OperationalError: FATAL:  Peer authentication failed for user "mailmansuite"

=== 8< ===

Seems this might be in either python-django-hyperkitty (which is I think is the
case), since the log is referencing django and hyperkitty, or in
python3-mailman-hyperkitty (which doesn't seem to be picking up my list content
anyway; I should be seeing archives, but I don't, in the web UI).

I dunno how to refile a bug to another source package or tag another (if that's 
doable).

Sorry if it's not on this package and the bother this may have caused - it's
nice something else got fixed though :).


Thank you for your work,
Eric


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

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mailman3-suite depends on:
ii  dbconfig-mysql2.0.9
ii  dbconfig-pgsql2.0.9
ii  dbconfig-sqlite3  2.0.9
ii  debconf [debconf-2.0] 1.5.66
ii  lsb-base  9.20170808
ii  node-less 1.6.3~dfsg-2
ii  python2.7.14-4
ii  python-django-hyperkitty  1.1.4-3
ii  python-django-postorius   1.1.2-2
ii  python-psycopg2   2.7.4-1
ii  python-pymysql0.8.0-1
ii  python-whoosh 2.7.4+git6-g9134ad92-1
ii  ruby-sass 3.5.3-1
ii  ucf   3.0038
ii  uwsgi 2.0.15-10.2
ii  uwsgi-plugin-python   2.0.15-10.2

Versions of packages mailman3-suite recommends:
ii  nginx-extras [nginx]  1.13.9-1

Versions of packages mailman3-suite suggests:
ii  mariadb-server-10.1 [virtual-mysql-server]  1:10.1.29-6
ii  postgresql  10+190

-- Configuration Files:
/etc/logrotate.d/mailman3-suite changed:
/var/log/mailman3/mailman-suite.log {
copytruncate
daily
rotate 5
compress
delaycompress
missingok
notifempty
su www-data list
create 660 www-data list
}
/var/log/mailman3/mailman-suite-uwsgi.log {
copytruncate
weekly
rotate 3
compress
delaycompre

Bug#891703: [Pkg-mailman-hackers] Bug#891703: DB user isn't read from setting_local (mailman3-suite.py in /etc)

[Eric Côté]

Hi (sorry for top posting)

I’m using Postgres, not SQLite. It uses the defaults set in settings.py . How I 
can tell is that the user trying to log in to postgres is what is set in 
settings.py, and *not* settings_local.py/mailman3-suite.py . I set different 
things (user, db, pswd) there. If it’s fixed, yay, and TY !

From: Jonas Meurer
Sent: March 3, 2018 05:51
To: mar...@runout.at; 
891...@bugs.debian.org; 
ericcotelnu+debian...@gmail.com
Subject: Re: [Pkg-mailman-hackers] Bug#891703: DB user isn't read from 
setting_local (mailman3-suite.py in /etc)

Hi Markus, hi Eric,

I'm pretty sure that the bug you discovered is not that the DB settings
are read from wrong file (settings.py instead of settings_local.py).

Instead it's that the permssions for the SQLite database file were
wrong. The initial django-admin commands in the postinst maintainer
script were run by root, which is wrong.

I fixed this now in the mailman3-suite packaging Git repo and the fix
will be part of the next mailman3-suite upload.

Am 02.03.2018 um 01:07 schrieb Markus Gschwendt:
> as a sidenote:
> there are 2 .db files in that directory:

That's now fixed as well :)

Cheers,
jonas

[SNIP]

Bug#891703: mailman3-suite: DB user isn't read from setting_local (mailman3-suite.py in /etc)

[Eric Côté]

Package: mailman3-suite
Version: 0+20170523-10
Severity: important

Hi,

The default user is being read from the packaged settings.py instead of the 
settings_local.py file symlinked to /etc/mailman3 .
I see error logs saying "mailmansuite" has no access, which is true since 
that's not what I configured. I had to hand edit
the /usr/share/mailman3-suite/settings.py by hand to have to work like I wanted 
(which isn't recommended, nor what I would like to do).

Is there some solution to this?

Thank you
Eric

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

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mailman3-suite depends on:
ii  dbconfig-mysql2.0.9
ii  dbconfig-pgsql2.0.9
ii  dbconfig-sqlite3  2.0.9
ii  debconf [debconf-2.0] 1.5.65
ii  lsb-base  9.20170808
ii  node-less 1.6.3~dfsg-2
ii  python2.7.14-4
ii  python-django-hyperkitty  1.1.4-3
ii  python-django-postorius   1.1.2-1
ii  python-psycopg2   2.7.4-1
ii  python-whoosh 2.7.4+git6-g9134ad92-1
ii  python3-pymysql   0.8.0-1
ii  ruby-sass 3.5.3-1
ii  ucf   3.0038
ii  uwsgi 2.0.15-10.2
ii  uwsgi-plugin-python   2.0.15-10.2

Versions of packages mailman3-suite recommends:
ii  nginx-extras [nginx]  1.13.9-1

Versions of packages mailman3-suite suggests:
ii  mariadb-server-10.1 [virtual-mysql-server]  1:10.1.29-6
ii  postgresql  10+190

-- Configuration Files:
/etc/cron.d/mailman3-suite changed:
* * * * *   listcommand -v django-admin >/dev/null && django-admin 
runjobs minutely --pythonpath /usr/share/mailman3-suite --settings settings
2,17,32,47 * * * * root command -v django-admin >/dev/null && django-admin 
runjobs quarter_hourly --pythonpath /usr/share/mailman3-suite --settings 
settings
@hourly listcommand -v django-admin >/dev/null && django-admin 
runjobs hourly   --pythonpath /usr/share/mailman3-suite --settings settings
@daily  listcommand -v django-admin >/dev/null && django-admin 
runjobs daily--pythonpath /usr/share/mailman3-suite --settings settings
@weekly listcommand -v django-admin >/dev/null && django-admin 
runjobs weekly   --pythonpath /usr/share/mailman3-suite --settings settings
@monthlylistcommand -v django-admin >/dev/null && django-admin 
runjobs monthly  --pythonpath /usr/share/mailman3-suite --settings settings
@yearly listcommand -v django-admin >/dev/null && django-admin 
runjobs yearly   --pythonpath /usr/share/mailman3-suite --settings settings

/etc/logrotate.d/mailman3-suite changed:
/var/log/mailman3/mailman-suite.log {
copytruncate
daily
rotate 5
compress
delaycompress
missingok
notifempty
su www-data list
create 660 www-data list
}
/var/log/mailman3/mailman-suite-uwsgi.log {
copytruncate
weekly
rotate 3
compress
delaycompress
missingok
notifempty
su www-data list
create 660 www-data list
}


-- debconf information excluded

Bug#880543: lvm2-dbusd fails to Depend on python3-udev hence fails to start

[Eric Côté]

Package: lvm2-dbusd
Version: 2.02.175-1
Severity: normal

Please add python3-udev to dependencies :).

Thanks

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (1001, 'unstable'), (1000, 'experimental'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en_GB (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lvm2-dbusd depends on:
ii  dbus 1.12.0-1
ii  lvm2 2.02.175-1
ii  python3  3.6.3-2

lvm2-dbusd recommends no packages.

lvm2-dbusd suggests no packages.

-- no debconf information

Bug#878092: linux-image-4.13.0-1-amd64: hung thread(s) : Workqueue: phy0 ieee80211_ba_session_work [mac80211]

[Eric Côté]

Package: src:linux
Version: 4.13.4-1
Severity: normal

Not running the kernel affected:
a) too many tolerable issues, constant journal spam with wpa_supplicant
and hung threads (will paste the kernel msg dump I had before)
b) issues with email now resolved (hopefully)

Sorry about this, but can't be helped.

Patch found in this LKML thread:

https://lkml.org/lkml/2017/9/6/489

WLAN module: ath10k_pci :03:00.0

I started getting this as sson as I connected the WLAN.

= >8 =
Oct  9 13:27:34 asuslap kernel: [  967.645932] INFO: task kworker/u8:1:119 
blocked for more than 120 seconds.
Oct  9 13:27:34 asuslap kernel: [  967.645936]   Not tainted 4.13.0-1-amd64 
#1 Debian 4.13.4-1
Oct  9 13:27:34 asuslap kernel: [  967.645937] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct  9 13:27:34 asuslap kernel: [  967.645938] kworker/u8:1D0   119 
 2 0x
Oct  9 13:27:34 asuslap kernel: [  967.645963] Workqueue: phy0 
ieee80211_ba_session_work [mac80211]
Oct  9 13:27:34 asuslap kernel: [  967.645965] Call Trace:
Oct  9 13:27:34 asuslap kernel: [  967.645970]  ? __schedule+0x3c8/0x860
Oct  9 13:27:34 asuslap kernel: [  967.645971]  ? schedule+0x32/0x80
Oct  9 13:27:34 asuslap kernel: [  967.645972]  ? 
schedule_preempt_disabled+0xa/0x10
Oct  9 13:27:34 asuslap kernel: [  967.645973]  ? 
__mutex_lock.isra.1+0x2c3/0x4f0
Oct  9 13:27:34 asuslap kernel: [  967.645984]  ? 
__ieee80211_start_rx_ba_session+0x167/0x500 [mac80211]
Oct  9 13:27:34 asuslap kernel: [  967.645993]  ? 
__ieee80211_start_rx_ba_session+0x167/0x500 [mac80211]
Oct  9 13:27:34 asuslap kernel: [  967.645995]  ? sched_clock+0x5/0x10
Oct  9 13:27:34 asuslap kernel: [  967.645997]  ? sched_clock_cpu+0xc/0xb0
Oct  9 13:27:34 asuslap kernel: [  967.646007]  ? 
ieee80211_ba_session_work+0x154/0x240 [mac80211]
Oct  9 13:27:34 asuslap kernel: [  967.646009]  ? __schedule+0x3d0/0x860
Oct  9 13:27:34 asuslap kernel: [  967.646011]  ? process_one_work+0x181/0x370
Oct  9 13:27:34 asuslap kernel: [  967.646012]  ? worker_thread+0x4d/0x3a0
Oct  9 13:27:34 asuslap kernel: [  967.646014]  ? kthread+0xfc/0x130
Oct  9 13:27:34 asuslap kernel: [  967.646015]  ? process_one_work+0x370/0x370
Oct  9 13:27:34 asuslap kernel: [  967.646017]  ? 
kthread_create_on_node+0x70/0x70
Oct  9 13:27:34 asuslap kernel: [  967.646019]  ? ret_from_fork+0x25/0x30
= >8 =


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: X756UAK
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: X756UAK.307
board_vendor: ASUSTeK COMPUTER INC.
board_name: X756UAK
board_version: 1.0   

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core 
Processor Host Bridge/DRAM Registers [8086:5904] (rev 02)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers [1043:14d0]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 
[8086:5916] (rev 02) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:14d0]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 02)
Subsystem: ASUSTeK Computer Inc. Skylake Processor Thermal Subsystem 
[1043:14d0]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 21) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP USB 3.0 xHCI 
Controller [1043:201f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 21)
Subsystem: ASUSTeK Computer Inc. Sunrise Point-LP Thermal subsystem 
[1043:14d0]

Bug#813533: inosync: [PATCH] So someone can -c configfile a dot file

[Eric Côté]

Cool, that's fine, thank you :).

On January 19, 2017 6:37:05 AM EST, Carsten Leonhardt  wrote:
>Control: tags -1 - moreinfo
>Control: severity -1 wishlist
>Control: retitle -1 Please allow a dotfile to be used as configfile
>
>Hi Eric,
>
>thanks for your feedback. I'm setting the bug to severity "wishlist",
>maybe someone will come up with a solution.
>
> - Carsten

-- 
Drum carrier for Travelling Spirit Drum

Bug#813533: inosync: [PATCH] So someone can -c configfile a dot file

[Eric Côté]

Worked briefly, then I got busy with other things and moved on. I was hoping 
that I could easily fix it, but alas no. However, except for that one issue 
with config, it works quite well, Does The Right Thing, as expected.

I was hoping to contribute something more, but that I for another time for now. 
Thank you Carsten for your time and efforts.

Bug#836143: linux-image-4.7.0-1-686-pae-unsigned: WiFi with b43 (BCM4312) fails to authenticate

[Eric Côté]

Package: src:linux
Version: 4.7.2-1
Severity: grave
Justification: renders package unusable

Hello,

I spent 3 hours trying to make this work, and I couldn't. Network Manager sends 
out an error -4,
and wpa_supplicant says "timed out", and using NM, it keeps trying, even though 
other
devices are using the same WiFi with no issues, and the 4.6 kernel I am using 
now has none either.

It's very disconcerting, since I know it's an iffy device, but still works well 
enough to be usable,
and it's our only computer right now.

Thanks
Eric

-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information

** Network interface configuration:

auto lo
iface lo inet loopback
address 127.0.0.1
network 127.0.0.0
netmask 255.255.0.0
post-up ip addr add 127.0.0.2 dev lo
post-up ip addr add 127.0.1.1 dev lo
post-up ip addr add 127.0.1.2 dev lo
post-ip ip addr add 127.0.1.3 dev lo
post-up ip addr add 127.0.1.4 dev lo
post-up ip addr add 127.0.1.5 dev lo
post-up ip addr add 127.0.1.6 dev lo





** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GSE Express Memory 
Controller Hub [8086:27ac] (rev 03)
Subsystem: Hewlett-Packard Company Mobile 945GSE Express Memory 
Controller Hub [103c:1468]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GSE 
Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA 
controller])
Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated 
Graphics Controller [103c:1468]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 
943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML 
Express Integrated Graphics Controller [103c:1468]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 02)
Subsystem: Hewlett-Packard Company NM10/ICH7 Family High Definition 
Audio Controller [103c:1468]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1d.0 USB controller [0c03]: Intel Corporation NM10/ICH7 Family USB UHCI 
Controller #1 [8086:27c8] (rev 02) (prog-if 00 [UHCI])
Subsystem: Hewlett-Packard Company NM10/ICH7 Family USB UHCI Controller 
[103c:1468]
Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- TAbort- 
SERR- 
Kernel driver in use: ehci-pci
Kernel modules: ehci_pci

00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge 
[8086:2448] (rev e2) (prog-if 01 [Subtractive decode])
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- 
Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 

00:1f.0 ISA bridge [0601]: Intel 

Bug#813533: inosync: [PATCH] So someone can -c configfile a dot file

[Eric Côté]

Package: inosync
Version: 0.2.1-1
Severity: normal
Tags: patch

line 134:
add:

  if configfile.startswith("."):
 configfile = configfile.strip(".")

right after the

  if configfile.endswith(".py"):


Thanks,
Eric


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (900, 'unstable'), (899, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages inosync depends on:
ii  python2.7.11-1
ii  python-pyinotify  0.9.5-1
ii  rsync 3.1.1-3

inosync recommends no packages.

inosync suggests no packages.

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/inosync (from inosync package)

Bug#778603: [debian-mysql] Bug#778603: mariadb-server: Missing Aria DB engine "Aria engine is not enabled ..."

[Eric Côté]

Hi,

My hosting provider had a major power outage in their area, and so when the 
host came back up, the aria log had issues, so when I tried to start it, it 
would write that in the error log. I removed the aria_log* and that other 
aria_log_ file and it started successfully. I also ran an aria_chk -oc $(find 
/var/lib/mysql -name '*. MAI') before I removed the files.

In my fatigue I interpreted the log message literally, and thought somehow 
missed a NEWS, or some other issue. 

I'm documenting this here for others who get the same/similar issue. You can 
close this happily, and thank you for your patience and time. I apologise for 
my lack of patience in my fatigue to you and your team. 


-- 
Sent from my Android device.


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

Bug#778603: Please close this 'bug'

[Eric Côté]

As I resolved it.

Sent from Blue Mail

Bug#778603: mariadb-server: Missing Aria DB engine "Aria engine is not enabled ..."

[Eric Côté]

Package: mariadb-server
Version: 10.0.16-1
Severity: important

"[ERROR] Aria engine is not enabled or did not start. The Aria engine must be 
enabled to continue as mysqld was configured with --with-aria-tmp-tables"

Would have been nice to let people know in a NEWS file about the change. Now my 
mysqld doesn't start. Pardon me for being a little impatient, but I've been 
trying to fix this for the last 3 hours, and I'd rather get some sleep.

I know I take my chances, but notification somehow would have been wise, IMO.

-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (1000, 'testing'), (998, 'stable'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages mariadb-server depends on:
ii  mariadb-server-10.0  10.0.16-1

mariadb-server recommends no packages.

mariadb-server 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

Bug#750518: phamm: Update to new ustream version

[Eric Côté]

Source: phamm
Severity: normal

Hi,

New upstream version is 0.6.2, one in Debian is 0.5.18.

Thank you.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (1000, 'testing'), (500, 'unstable'), (400, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.14-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


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