Bug#989979: thunderbird: Atom feeds cannot be retrieved

2021-06-18 Thread Arjen Balfoort 
On Fri, 18 Jun 2021 09:35:18 +0200 Carsten Schoenert 
 wrote:

> Am 18.06.21 um 08:31 schrieb Arjen Balfoort:
>
> > Unfortunately, thunderbird-dbgsym is not available for amd64 in any
> > repository:
> > 
https://packages.debian.org/search?keywords=thunderbird-dbgsym&searchon=names&suite=all§ion=all

>
> I tend to disagree :)
> http://deb.debian.org/debian-debug/pool/main/t/thunderbird/
>
> More information how to enable debug-packages and how to install them
> can be found here:
> 
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols

>
> As pointed from the output of the CLI switch for debugging.
>
> > $ thunderbird -g
> > INFO -> No package 'thunderbird-dbgsym' installed! Please install 
first and restart.
> > INFO -> More information how to adjust your sources.list to being 
able installing

> > INFO -> dbgsym packages in generally can be found here:
> > INFO -> 
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols


I stand corrected! :)
I never realised the debug packages were found in a separate repository. 
You learn something new every day. Thanks!


Regards,
Arjen

Bug#989979: thunderbird: Atom feeds cannot be retrieved

2021-06-17 Thread Arjen Balfoort 
On Thu, 17 Jun 2021 19:05:51 +0200 Carsten Schoenert 
 wrote:

> Hello Arjen,
>
> Am 17.06.21 um 11:45 schrieb Arjen Balfoort:
>
> > * What led up to the situation?
> > Update from 1:78.10.0-1 to 1:78.11.0-1 breaks Atom feeds.
> >
> > * What exactly did you do (or not do) that was effective (or
> > ineffective)?
> > Checked live ISO with Thunderbird 1:78.10.0-1 which retrieved Atom 
feeds.

> > Checked that RSS feeds worked in 1:78.11.0-1 which it did.
> > Upgraded 1:78.11.0-1 to experimental 1:89.0~b2-1 which also does 
not retrieve

> > Atom feeds.
>
> I expect you are also a victim of some trouble around the libnss3
> library and changed behavior between the available version in
> testing/bullseye and unstable.
>
> Please have a look at https://bugs.debian.org/989839 for more 
information.

>
> > Debugging Thunderbird in bullseye is impossible at the moment: there
> > is no thunderbird-dbgsym package and the run-mozilla.sh script
> > mentioned in the man page does not exist.
> That's only partially true.
> Yes the man page is outdated, I haven't noticed this really before your
> email, I've adjusted the relevant part right now and this will get
> reflected within the next upload.
>
> The thunderbird binary has an option '--help' for while. This is
> available by tab completion by the way.
>
> > $ thunderbird --help
> > ...
> > thunderbird -g
> >
> > Starts Thunderbird in a GDB session if packages gdb and
> > thunderbird-dbgsym are installed.
> > ...
>
> This will you give further information in case not all requirements are
> fulfilled.


Unfortunately, thunderbird-dbgsym is not available for amd64 in any 
repository: 
https://packages.debian.org/search?keywords=thunderbird-dbgsym&searchon=names&suite=all§ion=all



> I expect you will get a full working Thunderbird again if you install
> the libnss3 package from unstable/sid.
>


I would never to expected that but indeed, upgrading libnss3 2:3.61-1 to 
2:3.67-1 fixed this issue.


Thanks for the quick response and you can close this bug report as solved.

Regards,
Arjen

Bug#989979: thunderbird: Atom feeds cannot be retrieved

2021-06-17 Thread Arjen Balfoort 
Package: thunderbird
Version: 1:78.11.0-1
Severity: normal
X-Debbugs-Cc: arjenbalfo...@hotmail.com

Dear Maintainer,



   * What led up to the situation?
Update from 1:78.10.0-1 to 1:78.11.0-1 breaks Atom feeds.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Checked live ISO with Thunderbird 1:78.10.0-1 which retrieved Atom feeds.
Checked that RSS feeds worked in 1:78.11.0-1 which it did.
Upgraded 1:78.11.0-1 to experimental 1:89.0~b2-1 which also does not retrieve
Atom feeds.

Debugging Thunderbird in bullseye is impossible at the moment: there is no
thunderbird-dbgsym package and the run-mozilla.sh script mentioned in the man
page does not exist.

Feeds used
Atom: https://forums.solydxk.com/feed
RSS: http://feeds.bbci.co.uk/news/rss.xml

   * What was the outcome of this action?
Atom feeds are no longer being retrieved.
Message: [feed_url] could not be found. Please check the name and try again.

   * What outcome did you expect instead?
Atom feeds are retrieved.




-- System Information:
Distributor ID: Solydxk
Description:SolydK 11 64-bit
Release:11
Codename:   solydxk-11
Architecture: x86_64

Kernel: Linux 5.10.0-7-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:nl
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunderbird depends on:
ii  debianutils  4.11.2
ii  fontconfig   2.13.1-4.2
ii  libatk1.0-0  2.36.0-2
ii  libbotan-2-172.17.3+dfsg-2
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-12
ii  libcairo-gobject21.16.0-5
ii  libcairo21.16.0-5
ii  libdbus-1-3  1.12.20-2
ii  libdbus-glib-1-2 0.110-6
ii  libevent-2.1-7   2.1.12-stable-1
ii  libffi7  3.3-6
ii  libfontconfig1   2.13.1-4.2
ii  libfreetype6 2.10.4+dfsg-1
ii  libgcc-s110.2.1-6
ii  libgdk-pixbuf-2.0-0  2.42.2+dfsg-1
ii  libglib2.0-0 2.66.8-1
ii  libgtk-3-0   3.24.24-4
ii  libicu67 67.1-6
ii  libjson-c5   0.15-2
ii  libnspr4 2:4.29-1
ii  libnss3  2:3.61-1
ii  libpango-1.0-0   1.46.2-3
ii  libstdc++6   10.2.1-6
ii  libvpx6  1.8.2-1
ii  libx11-6 2:1.7.1-1
ii  libx11-xcb1  2:1.7.1-1
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxext6 2:1.3.3-1.1
ii  libxrender1  1:0.9.10-1
ii  psmisc   23.4-2
ii  x11-utils7.7+5
ii  zlib1g   1:1.2.11.dfsg-2

Versions of packages thunderbird recommends:
ii  hunspell-en-us [hunspell-dictionary]  1:2019.10.06-1
ii  hunspell-nl [hunspell-dictionary] 2:2.20.19-2

Versions of packages thunderbird suggests:
ii  apparmor  2.13.6-10
ii  fonts-lyx 2.3.6-1
ii  libgssapi-krb5-2  1.18.3-5
ii  libgtk2.0-0   2.24.33-2

Bug#972633: breeze-gtk-theme: Missing border in Whisker menu logout dialog (using arrow keys)

2020-10-21 Thread Arjen Balfoort 
Package: breeze-gtk-theme
Version: 5.19.4-1
Severity: normal
X-Debbugs-Cc: arjenbalfo...@hotmail.com

Dear Maintainer,


   * What led up to the situation?
 In Xfce, open the menu logout dialog (Alt-F4) and use the arrow keys to
navigate the buttons. It is not visible which button is active.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Using another theme (Adwaita or older Xfce themes) the active button is
visible. I also tried to edit /usr/share/themes/Breeze/gtk-3.0/gtk.css but
unfortunately I could not find the code responsible for handling the button
borders for the Whisker menu.

   * What was the outcome of this action?
 I could not solve the issue.

   * What outcome did you expect instead?
 Make active buttons visible while using the arrow keys as if hovering over
the buttons with the mouse cursor.




-- System Information:
Distributor ID: Solydxk
Description:SolydX 10 64-bit
Release:10
Codename:   solydxk-10
Architecture: x86_64

Kernel: Linux 4.19.0-12-amd64 (SMP w/1 CPU thread)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
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/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages breeze-gtk-theme depends on:
ii  gtk2-engines-pixbuf  2.24.32-3

breeze-gtk-theme recommends no packages.

breeze-gtk-theme suggests no packages.

-- no debconf information

Bug#971432: debhelper: Build fails when transitional package is configured in control file

2020-09-30 Thread Arjen Balfoort 

On Wed, 30 Sep 2020 19:25:12 +0200 Niels Thykier  wrote:
> Hi,
>
> You have hit an intentional design choice from debhelper - one that I am
> admittedly have been considering to change for exactly this the problem
> you are running into.
>
> What happens is that debhelper special-cases "single-binary packages"
> (namely dh_auto_install defaults to "--destdir=debian/" rather
> than --destdir=debian/tmp" in this case). In compat 13, the dh_missing
> warning becomes an error preventing you from accidentally uploading the
> two empty packages - but it is still an unpleasant experience.
>
> If you need a second /empty/ binary, then you can override
> dh_auto_install and set dh_auto_install --destdir=debian/ 
for now.

>
> I am leaving this open until I figure out what to do about this 
corner case.

>
> Thanks,
> ~Niels
>
>

Thanks for your fast reply.
Your suggested workaround worked perfectly.

For those coming to this page, the new rules file is attached.

#!/usr/bin/make -f
export DH_VERBOSE = 1

%:
dh $@ --with python3 --buildsystem=pybuild

override_dh_auto_install:
# Set destination directory when co-building a transition package
dh_auto_install --destdir=debian/debhello

Bug#971432: debhelper: Build fails when transitional package is configured in control file

2020-09-30 Thread Arjen Balfoort 

Package: debhelper
Version: 13.2.1
Severity: normal
X-Debbugs-Cc: arjenbalfo...@hotmail.com

Dear Maintainer,

* What led up to the situation?
I needed a package name change of a pybuild package.

* What exactly did you do (or not do) that was effective (or ineffective)?
I added the configuration of the transitional package to the package control
file.

* What was the outcome of this action?
dh_missing threw the following warning on all files:
dh_missing: warning: usr/bin/hello exists in debian/tmp but is not 
installed to

anywhere

Resulting in two empty packages: the new named package and the old
(transitional) package.

* What outcome did you expect instead?
A complete package with a new name and an empty transitional package 
with the

old name.

Note: after removing the configuration of the transitional package the 
new package was built correctly.




-- System Information:
Distributor ID: Solydxk
Description: SolydK 11 64-bit
Release: 11
Codename: solydxk-11
Architecture: x86_64

Kernel: Linux 5.8.0-2-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=nl_NL.UTF-8, LC_CTYPE=nl_NL.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:nl
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debhelper depends on:
ii autotools-dev 20180224.1
ii dh-autoreconf 19
ii dh-strip-nondeterminism 1.9.0-1
ii dpkg 1.20.5
ii dpkg-dev 1.20.5
ii dwz 0.13-5
ii file 1:5.38-5
ii libdebhelper-perl 13.2.1
ii libdpkg-perl 1.20.5
ii man-db 2.9.3-2
ii perl 5.30.3-4
ii po-debconf 1.0.21

debhelper recommends no packages.

Versions of packages debhelper suggests:
pn dh-make 

Source: debhello
Section: devel
Priority: optional
Maintainer: My Name 
Build-Depends: debhelper-compat (= 12)
 , dh-python
 , python3-all
Standards-Version: 4.5.0
Homepage: 
Vcs-Git: 
X-Python3-Version: >= 3.6

Package: debhello
Architecture: all
Multi-Arch: foreign
Depends: ${misc:Depends}
 , ${python3:Depends}
 , gir1.2-gtk-3.0
 , python3-gi
Description: example package in the debmake-doc package
 This is an example package to demonstrate Debian packaging using
 the debmake command.

Package: myfirst-debhello
Architecture: all
Section: oldlibs
Depends: debhello, ${misc:Depends}
Description: transitional package
 This is a transitional package. It can safely be removed.
#!/usr/bin/make -f
export DH_VERBOSE = 1

%:
dh $@ --with python3 --buildsystem=pybuild
debuild output WITH transitional package in control file:


$ debuild
 dpkg-buildpackage -us -uc -ui
dpkg-buildpackage: info: source package debhello
dpkg-buildpackage: info: source version 1.0
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by My Name 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
pybuild --clean -i python{version} -p 3.8
I: pybuild base:217: python3.8 setup.py clean 
running clean
removing '/home/shared/Development/dev/debhello/.pybuild/cpython3_3.8/build' 
(and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.8' does not exist -- can't clean it
rm -rf .pybuild/
find . -name \*.pyc -exec rm {} \;
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f -- debian/debhello.substvars debian/myfirst-debhello.substvars 
debian/files
rm -fr -- debian/debhello/ debian/tmp/ debian/myfirst-debhello/
find .  \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path 
.\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o 
-type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a -name autom4te.cache -prune -exec rm -rf {} + \) 
\)
 dpkg-source -b .
dpkg-source: info: using source format '3.0 (native)'
dpkg-source: info: building debhello in debhello_1.0.tar.xz
dpkg-source: info: building debhello in debhello_1.0.dsc
 debian/rules build
dh build --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
pybuild --configure -i python{version} -p 3.8
I: pybuild base:217: python3.8 setup.py config 
running config
   dh_auto_build -O--buildsystem=pybuild
pybuild --build -i python{version} -p 3.8
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running

Bug#944863: plasma-discover times out when fcitx is installed

2019-11-16 Thread Arjen Balfoort 
Package: plasma-discover
Version: 5.14.5.1-1
Severity: normal

Dear Maintainer,

   * What led up to the situation?
After installation of fcitx (apt-get install fcitx fcitx-mozc kde-config-fcitx) 
Plasma Discover takes a long time to enable the fetching and update all 
buttons. When it times out, the buttons are enabled.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I started PD in update mode from the terminal: plasma-discover --mode update

   * What was the outcome of this action?
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:182:
 TypeError: Cannot assign to read-only property "parent"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:182:
 TypeError: Cannot assign to read-only property "parent"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:182:
 TypeError: Cannot assign to read-only property "parent"
file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:182:
 TypeError: Cannot assign to read-only property "parent"
adding empty sources model QStandardItemModel(0x5646e40543b0)
no packages for "org.kde.plasma.activitybar"
no packages for "org.kde.plasma.systemloadviewer"
no packages for "io.devdocs.webapp"
no packages for "org.kde.plasma.showActivityManager"
no packages for "org.kde.plasma.grouping"
no packages for "org.kde.plasma.binaryclock"
no packages for "org.kde.plasma.diskquota"
no packages for "org.kde.kscreen"
no packages for "libgphoto2"
no packages for "org.debian.debian"
no packages for "org.kde.plasma.kimpanel"
no packages for "org.kde.plasma.timer"
no packages for "im.riot.webapp"
no packages for "org.kde.plasma.appmenu"
no packages for "org.kde.plasma.quicklaunch"
invalid kns backend! "/etc/xdg/ksysguard.knsrc" because: "Config group not 
found! Check your KNS3 installation."
invalid kns backend! "/etc/xdg/servicemenu.knsrc" because: "Config group not 
found! Check your KNS3 installation."
org.kde.plasma.discover: couldn't open file 
"/home/solydxk/.cache/discover/featured-5.9.json" "No such file or directory"
org.kde.plasma.discover: couldn't open file 
"/home/solydxk/.cache/discover/featured-5.9.json" "No such file or directory"
org.kde.plasma.discover: couldn't open file 
"/home/solydxk/.cache/discover/featured-5.9.json" "No such file or directory"
org.kde.plasma.libdiscover: Failed to fetch ratings  "Timeout on 
server\nodrs.gnome.org: Socket operation timed out"
org.kde.knewstuff.core: Could not find category "Fcitx Theme"
invalid kns backend! "/etc/xdg/fcitx-skin.knsrc" because: "Backend Fcitx-skin 
took too long to initialize"
org.kde.plasma.libdiscover: Discarding invalid backend "fcitx-skin.knsrc"

PD times out on the second last line.

Content of /etc/xdg/fcitx-skin.knsrc
[KNewStuff3]
Categories=Fcitx Theme
InstallPath=.config/fcitx/skin
Uncompress=archive

   * What outcome did you expect instead?
I do not know why PD needs these knsrc files but if it does, it should not take 
so long to continue and enable the top right buttons.



-- System Information:
Distributor ID: Solydxk
Description:SolydK 10 64-bit
Release:10
Codename:   buster
Architecture: x86_64

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-discover depends on:
ii  appstream0.12.5-1
ii  apt-config-icons 0.12.5-1
ii  kio  5.54.1-1
ii  libappstreamqt2  0.12.5-1
ii  libc62.28-10
ii  libkf5attica55.54.0-1
ii  libkf5configcore55.54.0-1+deb10u1
ii  libkf5configwidgets5 5.54.0-1
ii  libkf5coreaddons55.54.0-1
ii  libkf5crash5 5.54.0-1
ii  libkf5dbusaddons55.54.0-1
ii  libkf5i18n5  5.54.0-1
ii  libkf5itemmodels55.54.0-1
ii  libkf5kiocore5   5.54.1-1
ii  libkf5kiowidgets55.54.1-1
ii  libkf5newstuffcore5  5.54.0-2
ii  libkf5notifications5 5.54.0-1
ii  libkf5service-bin5.54.0-1
ii  libkf5service5   5.54.0-1
ii  libkf5widgetsaddons5 5.54.0-1
ii  libkf5xmlgui55.54.0-1
ii  libpackagekitqt5-1   1.0.1-1
ii  libqt5core5a 5.11.3+dfsg1-1+deb10u1
ii  libqt5dbus5  5.11.3+dfsg1-1+deb10u1
ii  libqt5gui5

Bug#906053: dolphin: Dolphin crashes when overwriting files on samba share (exfat file system).

2018-08-18 Thread Arjen Balfoort 

Thanks, I missed that one.

Adding "uid=1000,gid=1000" partially solved this bug: no segfault but 
still with each move (not copy) I get this dialog for each file:

"Access denied to [destination path]"

but still, the move is successfully done.

This is the fstab mount:
//[ip address]/SHARED /media/SHARED cifs 
rw,uid=1000,gid=1000,noauto,nofail,x-systemd.automount,x-systemd.after=network-online.target,x-systemd.device-timeout=10,_netdev 
0 0


I've been experimenting with the options in fstab but no luck yet.

Bug#906053: gdb backtrace

2018-08-13 Thread Arjen Balfoort 

To clarify the dialog messages I get, these are the two:
- Acces denied to [path to destination file]
- Could not change permission for [path to destination file]

I had trouble getting a backtrace but eventually I succeeded (although I 
don't know if it helps):


$ gdb dolphin
GNU gdb (Debian 7.12-6) 7.12.0.20161007-git
Copyright (C) 2016 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"...
Reading symbols from dolphin...(no debugging symbols found)...done.
(gdb) run
Starting program: /usr/bin/dolphin
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffe1cba700 (LWP 7332)]
[New Thread 0x7fffdbfff700 (LWP 7333)]
[New Thread 0x7fffd8d49700 (LWP 7334)]
Trying to convert empty KLocalizedString to QString.
Cannot creat accessible child interface for object: 
PlacesView(0x55d89f50)  index:  17

ark.main: "video/x-matroska" is not a supported mimetype
[New Thread 0x7fffd0fc5700 (LWP 7522)]
[Thread 0x7fffd0fc5700 (LWP 7522) exited]
[New Thread 0x7fffd0fc5700 (LWP 7523)]
[New Thread 0x7fffd07c4700 (LWP 7524)]
[New Thread 0x7fffb0143700 (LWP 7528)]
[Thread 0x7fffb0143700 (LWP 7528) exited]
[Thread 0x7fffd07c4700 (LWP 7524) exited]
[Thread 0x7fffd0fc5700 (LWP 7523) exited]
[New Thread 0x7fffd07c4700 (LWP 7705)]
[New Thread 0x7fffb0143700 (LWP 7706)]
[New Thread 0x7fffd0fc5700 (LWP 7707)]
[Thread 0x7fffb0143700 (LWP 7706) exited]
[Thread 0x7fffd07c4700 (LWP 7705) exited]
ark.main: "video/x-matroska" is not a supported mimetype
ark.main: "video/x-matroska" is not a supported mimetype
[Thread 0x7fffd0fc5700 (LWP 7707) exited]
[New Thread 0x7fffd07c4700 (LWP 8425)]
[New Thread 0x7fffb0143700 (LWP 8426)]
[New Thread 0x7fffd0fc5700 (LWP 8427)]
[Thread 0x7fffb0143700 (LWP 8426) exited]
[Thread 0x7fffd07c4700 (LWP 8425) exited]

Thread 1 "dolphin" received signal SIGSEGV, Segmentation fault.
0x725517e3 in QObjectPrivate::setParent_helper(QObject*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(gdb) bt
#0  0x725517e3 in QObjectPrivate::setParent_helper(QObject*) ()
   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#1  0x73824bf2 in KCompositeJob::removeSubjob(KJob*) ()
   from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#2  0x758a4487 in ?? () from 
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#3  0x758a4a54 in ?? () from 
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5

#4  0x758a69d3 in KIO::CopyJob::slotResult(KJob*) ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#5  0x7254a5e9 in QMetaObject::activate(QObject*, int, int, 
void**) ()

   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x73825412 in KJob::result(KJob*, KJob::QPrivateSignal) ()
   from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#7  0x73826d51 in KJob::finishJob(bool) ()
   from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#8  0x758ebcc9 in KIO::FileCopyJob::slotResult(KJob*) ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#9  0x758ecbd8 in ?? () from 
/usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#10 0x7254a5e9 in QMetaObject::activate(QObject*, int, int, 
void**) ()

   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x73825412 in KJob::result(KJob*, KJob::QPrivateSignal) ()
   from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#12 0x73826d51 in KJob::finishJob(bool) ()
   from /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5
#13 0x758f686f in KIO::SimpleJob::slotFinished() ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#14 0x758f527b in KIO::SimpleJob::slotError(int, QString const&) ()
---Type  to continue, or q  to quit---
   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#15 0x7254a5e9 in QMetaObject::activate(QObject*, int, int, 
void**) ()

   from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x758cea66 in KIO::SlaveInterface::error(int, QString const&) ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#17 0x758d0af1 in KIO::SlaveInterface::dispatch(int, QByteArray 
const&) ()

   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#18 0x758cf0a7 in KIO::SlaveInterface::dispatch() ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#19 0x758d41c1 in KIO::Slave::gotInput() ()
   from /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5
#2

Bug#848101: [Pkg-raspi-maintainers] Bug#848101: marked as done (Package name + config.txt & cmdline.txt as conffiles)

2018-03-21 Thread Arjen Balfoort 

Error on postinst raspi3-firmware 1.20180316-2:

DEB_MAINT_PARAMS="configure" /etc/kernel/postinst.d/raspi3-firmware

should be:

DEB_MAINT_PARAMS="configure" /etc/kernel/postinst.d/50raspi3-firmware


After fixing that the package installed correctly and I could set up a 
hook to overwrite cmdline.txt and config.txt on kernel update.
Custom package created for SolydX RPi3: 
https://github.com/SolydXK/solydx-raspi3-adjustments

Bug#848101: [Pkg-raspi-maintainers] Bug#848101: Bug#848101: Bug#848101: cmdline.txt and config.txt overwritten with each initramfs update

2018-03-20 Thread Arjen Balfoort 


This sounds like a good option. I was also thinking of solutions and 
my idea was the following:


Put a template for cmdline.txt and config.txt (e.g cmdline.txt.in 
<http://cmdline.txt.in> and config.txt.in <http://config.txt.in>) 
somewhere in the /etc folder (e.g. /etc/raspi3-firmware). Within the 
template there are keywords that the raspi3-firmware hook (or better 
50-raspi3-firmware) will replace (sed) when it generates the files for 
/boot/firmware.

I agree that this is the most user-friendly solution.


This is still a bit cumbersome compared to the offerings of e.g. 
grub2. But I guess it is a (too) big effort to reach the level of grub2.


Yes, I've been experimenting with grub2 on the RPi but had to abandon 
the idea after quete some very frustrating experiences.


Regards,
Arjen Balfoort

Bug#848101: cmdline.txt and config.txt overwritten with each initramfs update

2018-03-13 Thread Arjen Balfoort 
I'm currently building a RPi3 version of SolydX. For the Xfce desktop to 
successfully load I need to change the boot parameters.


cmdline.txt:
console=tty0 console=ttyS1,115200 root=/dev/mmcblk0p2 rw 
elevator=deadline fsck.repair=yes net.ifnames=0 rootwait cma=256M quiet 
splash loglevel=0 vt.global_cursor_default=0 plymouth.ignore-serial-consoles


config.txt:
arm_control=0x200
kernel=vmlinuz-4.14.0-3-arm64
initramfs initrd.img-4.14.0-3-arm64 followkernel
disable_splash=1
enable_uart=1
device_tree=bcm2837-rpi-3-b.dtb
gpu_mem=16
dtoverlay=pi3-disable-bt
dtparam=audio=on

Note: I needed the "cma=256M" in cmdline.txt. Any lower Xfce would 
freeze on login.


As the OP mentioned, these files are now overwritten with each initramfs 
update. I tried to create a hook script for initramfs-tools to restore 
backup files to cmdline.txt and config.txt but so far I didn't succeed 
in that.


In a desktop environment it regularly happens that initramfs is updated 
and overwriting these files always results in a frozen desktop and that 
is not something I can trust our users with.


Is there a way to prevent this behavior or does anybody know how to run 
a script after initramfs has been updated?

Bug#892755: network-manager-gnome: aarch64/Debian Buster: nm-applet in xfce4 notification area is active but has no icon

2018-03-12 Thread Arjen Balfoort 
Package: network-manager-gnome
Version: 1.8.10-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
Setting up Network Manager on Xfce4 (aarch64) resulted in having an invisible 
Network Manger applet in the notification area.
On boot the icon flashes just before disappearing.
Left and right actions do function properly (I let the notification area show 
its borders to make it easier to find the nm-applet).

Other icons show correctly in the notification area.

   * What exactly did you do (or not do) that was effective (or ineffective)?
I found these similar reports but I decided to report this issue because this 
issue was found on aarch64 and the other reports did not describe exactly this 
issue (nm-applet is functional but just not showing in the notification area):
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549541 > 4 Oct 2009, no 
solution
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572714 > 5 March 2010, no 
solution

I tested with several styles and icon themes (Gnome, Breeze, etc.) and tried to 
change icon size for the notification area but the icon still did not show.
Although the icon flashes on boot I still checked that nm-applet* icons existed 
in the icon themes (all svg).

   * What was the outcome of this action?
There was no change.

   * What outcome did you expect instead?
Network Manager applet would show the correct icon in the notification area.

If you want I can provide an image for the RPi3.


-- System Information:
Distributor ID: SolydXK
Description:SolydX 10 ARM 32-bit
Release:10
Codename:   solydxk-10
Architecture: aarch64

Kernel: Linux 4.14.0-3-arm64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager-gnome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.6-2
ii  dbus-x11 [dbus-session-bus]   1.12.6-2
ii  dconf-gsettings-backend [gsettings-backend]   0.26.1-3
ii  libatk1.0-0   2.26.1-3
ii  libc6 2.27-1
ii  libcairo2 1.15.10-1
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.54.3-2
ii  libgtk-3-03.22.28-1
ii  libjansson4   2.11-1
ii  libmm-glib0   1.7.990-1
ii  libnm01.10.4-1+b1
ii  libnma0   1.8.10-2
ii  libnotify40.7.7-3
ii  libpango-1.0-01.40.14-1
ii  libpangocairo-1.0-0   1.40.14-1
ii  libsecret-1-0 0.18.5-6
ii  libselinux1   2.7-2+b1
ii  network-manager   1.10.4-1+b1
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-6

Versions of packages network-manager-gnome recommends:
ii  gnome-keyring3.20.1-2
ii  iso-codes3.79-1
pn  mobile-broadband-provider-info   
ii  xfce4-notifyd [notification-daemon]  0.4.1-1

Versions of packages network-manager-gnome suggests:
ii  network-manager-openconnect-gnome  1.2.4-1
ii  network-manager-openvpn-gnome  1.8.0-2
ii  network-manager-pptp-gnome 1.2.4-5+b1
ii  network-manager-vpnc-gnome 1.2.4-6

-- no debconf information

Bug#892750: Client version for current PostgreSQL version

2018-03-12 Thread Arjen Balfoort 
I've posted this issue on the xTuple forum as well and when I asked 
which client version works with PostgreSQL 9.7.6 and higher, this was 
the answer:
"4.11.0 and higher work without complaint on PostgreSQL 9.3 - 9.6. We 
have not vetted PG 10 yet."


xTuple forum topic: 
https://forums.xtuple.com/t/postgresql-version-too-new-for-xtuple-client-in-debian-stretch/

Bug#892750: postbooks: PostgreSql version too new for PostBooks client

2018-03-12 Thread Arjen Balfoort 
Package: postbooks
Version: 4.10.0-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
I installed Postbooks from the Debian Stretch repository with:
sudo apt-get install postbooks postbooks-schema-quickstart postbooks-updater 
postgresql postgresql-contrib postgresql-plv8 pgadmin3

I initiated and configured the database and the client successfully but 
whenever I start the client the following message is shown:

The database server is at version PostgreSQL 9.6.7 on x86_64-pc-linux-gnu, 
compiled by gcc (Debian 6.3.0-18) 6.3.0 20170516, 64-bit but xTuple ERP only 
supports from 9.3.0 up to but not including 9.6.0.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I installed postbooks from unstable (version 4.10.1-1) but that version had the 
same issue.

   * What was the outcome of this action?
Starting PostBooks always shows the above mentioned message.

   * What outcome did you expect instead?
The PostBook client should support the PostgreSql version provided by Debian 
Stretch.



-- System Information:
Distributor ID: SolydXK
Description:SolydK 9 64-bit
Release:9
Codename:   solydxk-9
Architecture: x86_64

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

Versions of packages postbooks depends on:
ii  libc6  2.24-11+deb9u3
ii  libdmtx0a  0.7.4-2
ii  libgcc11:6.3.0-18+deb9u1
ii  libgl1-mesa-glx [libgl1]   13.0.6-1+b2
ii  libopenrpt1v5  3.3.12-2
ii  libqt5core5a   5.7.1+dfsg-3+b1
ii  libqt5designer55.7.1-1
ii  libqt5designercomponents5  5.7.1-1
ii  libqt5gui5 5.7.1+dfsg-3+b1
ii  libqt5help55.7.1-1
ii  libqt5network5 5.7.1+dfsg-3+b1
ii  libqt5printsupport55.7.1+dfsg-3+b1
ii  libqt5qml5 5.7.1-2+b2
ii  libqt5quick5   5.7.1-2+b2
ii  libqt5script5  5.7.1~20161021+dfsg-2
ii  libqt5scripttools5 5.7.1~20161021+dfsg-2
ii  libqt5serialport5  5.7.1~20161021-2
ii  libqt5sql5 5.7.1+dfsg-3+b1
ii  libqt5sql5-psql5.7.1+dfsg-3+b1
ii  libqt5webchannel5  5.7.1-2
ii  libqt5webkit5  5.7.1+dfsg-1
ii  libqt5websockets5  5.7.1~20161021-4
ii  libqt5widgets5 5.7.1+dfsg-3+b1
ii  libqt5xml5 5.7.1+dfsg-3+b1
ii  libqt5xmlpatterns5 5.7.1~20161021-3
ii  libstdc++6 6.3.0-18+deb9u1
ii  libxtuplecommon1   4.10.0-2
ii  zlib1g 1:1.2.8.dfsg-5

postbooks recommends no packages.

Versions of packages postbooks suggests:
ii  postbooks-schema-demo1:4.10.0-2
ii  postbooks-schema-empty   1:4.10.0-2
ii  postbooks-schema-quickstart  1:4.10.0-2
ii  postbooks-updater2.4.0-3

-- no debconf information

Bug#892609: network-manager-gnome: (aarch64) nm-applet in xfce4 notification area is active but has no icon

2018-03-11 Thread Arjen Balfoort 

Package: network-manager-gnome
Version: 1.8.10-2
Severity: important
Tags: a11y

Dear Maintainer,


   * What led up to the situation?
   Setting up Network Manager on Xfce4 (aarch64) resulted in having an 
invisible Network Manger applet in the notification area.

   On boot the icon flashes just before disappearing.
   Left and right actions do function properly (I let the notification 
area show its borders to make it easier to find the nm-applet).


   Other icons show correctly in the notification area.

   * What exactly did you do (or not do) that was effective (or 
ineffective)?
   I found these similar reports but I decided to report this issue 
because this issue was found on aarch64 and the other reports did not 
describe exactly this issue (nm-applet is functional but just not 
showing in the notification area):
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549541 > 4 Oct 
2009, no solution
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572714 > 5 March 
2010, no solution


   I tested with several styles and icon themes (Gnome, Breeze, etc.) 
and tried to change icon size for the notification area but the icon 
still did not show.
   Although the icon flashes on boot I still checked that nm-applet* 
icons existed in the icon themes (all svg).


   * What was the outcome of this action?
   There was no change.

   * What outcome did you expect instead?
   Network Manager applet would show the correct icon in the 
notification area.


   If you want I can provide an image for the RPi3.


-- System Information:
Distributor ID:    SolydXK
Description:    SolydX 10 ARM 64-bit
Release:    10
Codename:    solydxk-10
Architecture: aarch64

Kernel: Linux 4.14.0-3-arm64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager-gnome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.6-2
ii  dbus-x11 [dbus-session-bus]   1.12.6-2
ii  dconf-gsettings-backend [gsettings-backend]   0.26.1-3
ii  libatk1.0-0   2.26.1-3
ii  libc6 2.27-1
ii  libcairo2 1.15.10-1
ii  libgdk-pixbuf2.0-0    2.36.11-1
ii  libglib2.0-0  2.54.3-2
ii  libgtk-3-0    3.22.28-1
ii  libjansson4   2.11-1
ii  libmm-glib0   1.6.8-2
ii  libnm0    1.10.4-1+b1
ii  libnma0   1.8.10-2
ii  libnotify4    0.7.7-3
ii  libpango-1.0-0    1.40.14-1
ii  libpangocairo-1.0-0   1.40.14-1
ii  libsecret-1-0 0.18.5-6
ii  libselinux1   2.7-2+b1
ii  network-manager   1.10.4-1+b1
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-6

Versions of packages network-manager-gnome recommends:
ii  gnome-keyring    3.20.1-2
ii  iso-codes    3.79-1
pn  mobile-broadband-provider-info   
ii  xfce4-notifyd [notification-daemon]  0.4.1-1

Versions of packages network-manager-gnome suggests:
ii  network-manager-openconnect-gnome  1.2.4-1
ii  network-manager-openvpn-gnome  1.8.0-2
ii  network-manager-pptp-gnome 1.2.4-5+b1
ii  network-manager-vpnc-gnome 1.2.4-6

-- no debconf information

Bug#892543: network-manager-gnome: nm-applet in xfce4 notification area is active but has no icon

2018-03-10 Thread Arjen Balfoort 
Package: network-manager-gnome
Version: 1.8.10-2
Severity: important
Tags: a11y

Dear Maintainer,

   * What led up to the situation?
   Setting up Network Manager on Xfce4 (aarch64) resulted in having an 
invisible Network Manger applet in the notification area.
   On boot the icon flashes just before disappearing.
   Left and right actions do function properly (I let the notification area 
show its borders to make it easier to find the nm-applet).

   Other icons show correctly in the notification area.

   * What exactly did you do (or not do) that was effective (or ineffective)?
   I found these similar reports but I decided to report this issue because 
this issue was found on aarch64 and the other reports did not describe exactly 
this issue (nm-applet is functional but just not showing in the notification 
area):
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549541 > 4 Oct 2009, no 
solution
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572714 > 5 March 2010, no 
solution

   I tested with several styles and icon themes (Gnome, Breeze, etc.) and tried 
to change icon size for the notification area but the icon still did not show.
   Although the icon flashes on boot I still checked that nm-applet* icons 
existed in the icon themes (all svg).

   * What was the outcome of this action?
   There was no change.

   * What outcome did you expect instead?
   Network Manager applet would show the correct icon in the notification area.

   If you want I can provide an image for the RPi3.


-- System Information:
Distributor ID: SolydXK
Description:SolydX 10 ARM 64-bit
Release:10
Codename:   solydxk-10
Architecture: aarch64

Kernel: Linux 4.14.0-3-arm64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager-gnome depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.6-2
ii  dbus-x11 [dbus-session-bus]   1.12.6-2
ii  dconf-gsettings-backend [gsettings-backend]   0.26.1-3
ii  libatk1.0-0   2.26.1-3
ii  libc6 2.27-1
ii  libcairo2 1.15.10-1
ii  libgdk-pixbuf2.0-02.36.11-1
ii  libglib2.0-0  2.54.3-2
ii  libgtk-3-03.22.28-1
ii  libjansson4   2.11-1
ii  libmm-glib0   1.6.8-2
ii  libnm01.10.4-1+b1
ii  libnma0   1.8.10-2
ii  libnotify40.7.7-3
ii  libpango-1.0-01.40.14-1
ii  libpangocairo-1.0-0   1.40.14-1
ii  libsecret-1-0 0.18.5-6
ii  libselinux1   2.7-2+b1
ii  network-manager   1.10.4-1+b1
ii  policykit-1-gnome [polkit-1-auth-agent]   0.105-6

Versions of packages network-manager-gnome recommends:
ii  gnome-keyring3.20.1-2
ii  iso-codes3.79-1
pn  mobile-broadband-provider-info   
ii  xfce4-notifyd [notification-daemon]  0.4.1-1

Versions of packages network-manager-gnome suggests:
ii  network-manager-openconnect-gnome  1.2.4-1
ii  network-manager-openvpn-gnome  1.8.0-2
ii  network-manager-pptp-gnome 1.2.4-5+b1
ii  network-manager-vpnc-gnome 1.2.4-6

-- no debconf information

Bug#872841: yamagi-quake2-core: Missing game.so for xatrix, rogue, ctf

2017-08-22 Thread Arjen Balfoort 

On Mon, 21 Aug 2017 20:42:46 +0100 Simon McVittie  wrote:
>
> > https://github.com/yquake2/ctf
>
> This one is (claimed to be) GPL-2+, so maybe we can include it in 
yquake2.

> Please confirm that it works correctly?

I've just been playing it. So, yes it works as expected.
Licensing can be a pain sometimes.

Thanks for the effort!

Bug#872841: yamagi-quake2-core: Missing game.so for xatrix, rogue, ctf

2017-08-21 Thread Arjen Balfoort 
Package: yamagi-quake2-core
Version: 6.00~dfsg1-1
Severity: important
Tags: upstream

Dear Maintainer,

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

   * What led up to the situation?
 Starting Quake 2 MPs with: quake2 +set game xatrix/rogue/ctf were missing 
MP specific models and even level was unplayable due to unresponsive objects.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Building game.so from source and placing those in their respective 
sub-direcotories solved the issues.
 Sources: 
 https://github.com/yquake2/xatrix
 https://github.com/yquake2/rogue
 https://github.com/yquake2/ctf
   * What was the outcome of this action?
 Mission packs and CTF were playable again.
   * What outcome did you expect instead?
 N/a


-- System Information:
Distributor ID: SolydXK
Description:SolydK 9 64-bit
Release:9
Codename:   solydxk-9
Architecture: x86_64

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

Versions of packages yamagi-quake2-core depends on:
ii  libc6   2.24-11+deb9u1
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages yamagi-quake2-core recommends:
ii  yamagi-quake2  6.00~dfsg1-1

yamagi-quake2-core suggests no packages.

-- no debconf information

Bug#823069: fixed in live-boot 1:20160511

2016-05-12 Thread Arjen Balfoort 
I can confirm that version 20160511 of live-boot and 
live-boot-initramfs-tools fixes this bug.

Thank you very much for solving this issue this quickly.

Bug#823069: RE: Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages

2016-05-09 Thread Arjen Balfoort 

That did not change a thing: output the same as in OP.

Arjen


On Mon, 9 May 2016 20:24:12 +0200 Kristian Klausen 
 wrote:

> Arjen could you try removing:
> 
PATH="/root/usr/bin:/root/usr/sbin:/root/bin:/root/sbin:/usr/bin:/usr/sbin:/bin:/sbin"

> export PATH
>
> from /lib/live/boot/9990-aaa-fixme.sh and see if it works?
>
> - Kristian
>
> 
> > Subject: Bug#823069: live-boot-initramfs-tools: Kernel panic while 
booting live with Debian stretch busybox/live packages

> > From: b...@decadent.org.uk
> > To: 823...@bugs.debian.org
> > CC: util-li...@packages.debian.org
> > Date: Mon, 9 May 2016 17:55:55 +0100
> >
> > Control: clone -1 -2
> > Control: reassign -2 util-linux
> > Control: severity -2 important
> > Control: affects -2 live-boot-initramfs-tools
> > Control: retitle -1 live-boot-initramfs-tools: wrongly adds 
directories in /root to the PATH
> > Control: retitle -2 util-linux: 'mount -o move' does not work with 
virtual filesystems

> >
> > On Sat, 30 Apr 2016 16:07:25 +0200 Arjen Balfoort 
 wrote:

> > [...]
> >> mount: /dev is write-protected, mounting read-only
> >> mount: /dev is not a block device
> >>
> >> The error is caused in 
/usr/share/initramfs-tools/scripts/init-bottom/udev

> >> Line: mount -n -o move /dev ${rootmnt}/dev
> > [...]
> >
> > This is a side-effect of my change in busybox 1.22.0-19, but I don't
> > think that change was wrong.
> >
> > live-boot-initramfs-tools adds directories under /root to $PATH, which
> > was formerly harmelss but now actually does result in some commands
> > being loaded from there. You must stop doing this; it is not
> > supportable and I will not support it.
> >
> > In particular, this mount command now invokes util-linux's mount. That
> > refuses to perform a move if the source filesystem was not mounted from
> > a block device. There is no good reason for this and obviously it
> > works with busybox and klibc's implementations of mount.
> >
> > Ben.
> >
> > --
> > Ben Hutchings
> > If you seem to know what you are doing, you'll be given more to do.
>
>

Bug#823069: Bug#823323: busybox: Side effect after disabling CONFIG_FEATURE_PREFER_APPLETS

2016-05-09 Thread Arjen Balfoort 
On Sun, 08 May 2016 22:13:13 +0100 Ben Hutchings  
wrote:

> On Sun, 2016-05-08 at 14:27 +0800, Steven Shiau wrote:
> > On 2016年05月05日 08:47, Ben Hutchings wrote:
> > >
> > > >
> > > > Since initramfs-tools only allows hook A to declare a 
dependency on >

> > (must run after) hook B, not to declare that it must run before hook B,
> > >
> > > this has to be solved in klibc. > > Ben.
> > [...]
> >
> > Thanks, and this bug report seems to be related:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823069
>
> I don't think so. Â The error messages exist in busybox mount, but not
> klibc mount. Â It looks more like ${rootmnt} is not being set.


I can confirm that upgrading libklibc (and klibc-utils) to version 
2.0.4-9 did not solve this issue.



>
> Ben.
>
> --
> Ben Hutchings
> I haven't lost my mind; it's backed up on tape somewhere.

Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages

2016-04-30 Thread Arjen Balfoort 
Package: live-boot-initramfs-tools
Version: 1:20151213
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?
 We tried to update the SolydXK EE (Enthusiast's Editions following Debian 
stretch) ISOs and found that the current update in busybox caused a kernel 
panic while booting live.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Update busybox (version 1:1.22.0-17 to  1:1.22.0-19), update live-boot and 
live-boot-initramfs-tools to the latest versions.

   * What was the outcome of this action?
 Kernel panic.
 
 This output is relevant:
 Running /scripts/init-bottom
 mount: /dev is write-protected, mounting read-only
 mount: /dev is not a block device

 The error is caused in /usr/share/initramfs-tools/scripts/init-bottom/udev
 Line: mount -n -o move /dev ${rootmnt}/dev

 This line is also present in Debian stable and does not cause a problem 
there.
 When we do not upgrade busybox we can successfully boot live.
 This problem does not occur when upgrading busybox on an installed system, 
only live.

   * What outcome did you expect instead?
 A bootable live session.

   > I can provide an ISO if you whish so.



-- System Information:
Distributor ID: SolydXK
Description:SolydK EE 9 64-bit
Release:stretch/sid
Codename:   solydxk
Architecture: x86_64

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

Versions of packages live-boot-initramfs-tools depends on:
pn  busybox | busybox-initramfs  1:1.22.0-19
ii  initramfs-tools  0.125
ii  udev 229-4

live-boot-initramfs-tools recommends no packages.

live-boot-initramfs-tools suggests no packages.

Bug#801769: os-prober does not list connected LUKS encrypted partitions

2015-10-14 Thread Arjen Balfoort 
Package: os-prober
Version: 1.65
Severity: normal
Tags: patch

Dear Maintainer,

   * What led up to the situation?
 In a multi-boot system, os-prober does not list those encrypted partitions
 with other OSs that are manually connected.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 Connecting the partition with: sudo cryptsetup luksOpen /dev/sda1 sda1
 Confirmed that the partition was mapped in /dev/mapper: ls /dev/mapper
   * What was the outcome of this action?
 os-prober returned empty
   * What outcome did you expect instead?
 Listing the OS information in /dev/mapper/sda1


-- System Information:
LSB Version:
security-4.0-amd64:security-4.0-noarch:security-4.1-amd64:security-4.1-noarch
Distributor ID: SolydXK
Description:SolydK 8 64-bit
Release:8
Codename:   solydxk
Architecture: x86_64

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

Versions of packages os-prober depends on:
ii  libc6  2.19-18+deb8u1

os-prober recommends no packages.

os-prober suggests no packages.

-- no debconf information
--- /usr/bin/os-prober	2014-09-28 23:04:17.0 +0200
+++ /home/arjen/live/solydk/root/usr/bin/os-prober	2015-10-14 11:11:56.047870558 +0200
@@ -25,6 +25,15 @@
 }
 
 partitions () {
+	# List connected LUKS devices
+	if type cryptsetup >/dev/null 2>&1; then
+		for device in $(ls /dev/mapper); do
+			if [ "$(cryptsetup status /dev/mapper/$device | grep LUKS)" != "" ]; then
+echo "/dev/mapper/$device"
+			fi
+		done
+	fi
+ 
 	# Exclude partitions that have whole_disk sysfs attribute set.
 	if [ -d /sys/block ]; then
 		# Exclude partitions on physical disks that are part of a