Bug#1037086: dropbear-initramfs: /etc/dropbear/initramfs/dropbear_dss_host_key file not generated

2023-08-08 Thread Michael Meier

Sorry for the late reply, I've been in vacations.

ok as it seems, everything I've mentioned was just wrong.

The problem was/is, that if the root filesystem is not encrypted, 
dropbear-initramfs does nothing, besides showing cryptic error messages.


To my defense, as it seems I haven't been the only person with that 
problem, I've found it in several forums, without answers ;-).


Possible solutions are:

- Encrypt rootfs (Haven't got permission to do so)

- in /etc/crypttab add "initramfs" as parameter to the corresponding 
partition


Maybe mentioning that in

/usr/share/doc/dropbear-initramfs/initrfamfs.README

would help future users.

Even more helpful would probably be, that

update-initramfs

would spit out a message, that no encrypted fs have been found.

'

hope you didn't loose too much time trying reproducing the error. sorry.


On 30.06.23 16:30, Guilhem Moulin wrote:

On Fri, 30 Jun 2023 at 11:14:35 -0500, Michael Meier wrote:

I had to edit the file /usr/share/initramfs-tools-hooks so it also copies the 
dss key:

src:dropbear doesn't ship that file, do you mean 
/usr/share/initramfs-tools/hooks/dropbear?


The option DROPBEAR_OPTIONS="-E" should be default, so the user gets some
kind of error message if something is not working. Would have saved me an
hour or so...

-E is the default in debug mode…  Need a debug trace anyway to track
this down, because it works just fine here (and in ci).





Bug#1037086: dropbear-initramfs: /etc/dropbear/initramfs/dropbear_dss_host_key file not generated

2023-06-30 Thread Michael Meier
I've had the same problem. Took me quite some time to realize why 
nothing is working.

I'm using debian bookworm.

dropbear-initramfs:
  Installed: 2022.83-1

dropbear-bin:
  Installed: 2022.83-1

I had to edit the file /usr/share/initramfs-tools-hooks so it also 
copies the dss key:

< for keytype in dss rsa ecdsa ed25519; do
---
> for keytype in rsa ecdsa ed25519; do

then

dropbearkey -t dss -f /etc/dropbear/initramfs/dropbear_dss_host_key

update-initramfs -u

And finally. Dropbear could be started!

The option DROPBEAR_OPTIONS="-E" should be default, so the user gets 
some kind of error message if something is not working. Would have saved 
me an hour or so...




Bug#998736: In other package

2023-02-02 Thread Michael Meier

I've also been looking for a newer adb version.
In testing and unstable in the non-free repo you find
google-android-platform-tools-installer which seems to superseed the adb 
package. Right now it's in version 33.




Bug#1019854: firmware-nonfree: Please consider to update this package and its binaries

2022-10-05 Thread Michael Meier
Package: firmware-linux-nonfree
Version: 20210818-1
Followup-For: Bug #1019854
X-Debbugs-Cc: schissdra...@rmm.li

I support this request. It's way too much work to get debian testing/unstable
working on new Hardware, since way too many firmwares are missing.
Took me forever to get the installer find at least the wifi firmware.


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

Kernel: Linux 5.19.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages firmware-linux-nonfree depends on:
ii  firmware-amd-graphics  20210818-1
ii  firmware-misc-nonfree  20210818-1

Versions of packages firmware-linux-nonfree recommends:
pn  amd64-microcode  
ii  intel-microcode  3.20220809.1

firmware-linux-nonfree suggests no packages.

-- no debconf information



Bug#1016708: thunderbird: Thunderbird 102 doesn't recognize installed hunspell and myspell dictionaries

2022-08-07 Thread Michael Meier

hi Carsten

On 05.08.22 14:51, Carsten Schoenert wrote:

Hello Michael,

Am 05.08.22 um 21:14 schrieb Michael Meier:


I've just installed Thunderbird 102.
Now it doesn't recognize anymore the installed hunspell and myspell
dictionaries for spellchecking. If they aren't supported anymore by
thunderbird, then they should be removed from the recommended list.


an Add-ons installed? What happens if you disable all Add-ons?
Is that happen too if you start with a new profile?
Does this behavior also happen if you use pre-build upstream binary?

Please note also the hints within the Debian wiki.

https://wiki.debian.org/Thunderbird#Bug_Reporting_.2F_Issues

Thanks for your reply. Actually I've took a look at the wiki, but when I 
saw the first thing beeing mentioned is icedove I've assumed it's 
completely outdated, and didn't continue reading, sorry.


As it seems the problems are no add ons or anything. But maybe it has to 
do with KDE.


I'm using kde plasma. When I pin thunderbird to the task bar, and start 
it up from there, then the only dictionary available is the english one. 
When I start it from the console, application launcher or krunner 
(alt+f2) all the installed dictionaries are available.


No idea what is different when it's pinned to the task bar. Maybe some 
environment variables? no idea how to find out. In previous versions of 
thunderbird that wasn't an issue.


To get it there right click on the application in the task bar, choose 
"pin to task manager".




Bug#1016708: thunderbird: Thunderbird 102 doesn't recognize installed hunspell and myspell dictionaries

2022-08-05 Thread Michael Meier
Package: thunderbird
Version: 1:102.1.0-1
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

I've just installed Thunderbird 102.
Now it doesn't recognize anymore the installed hunspell and myspell
dictionaries for spellchecking. If they aren't supported anymore by
thunderbird, then they should be removed from the recommended list.


-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (600, 'testing'), (300, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages thunderbird depends on:
ii  debianutils  5.7-0.2
ii  fontconfig   2.13.1-4.4
ii  kdialog  4:21.12.3-1
ii  libasound2   1.2.7.2-1
ii  libatk1.0-0  2.38.0-1
ii  libc62.33-8
ii  libcairo-gobject21.16.0-6
ii  libcairo21.16.0-6
ii  libdbus-1-3  1.14.0-2
ii  libdbus-glib-1-2 0.112-2
ii  libevent-2.1-7   2.1.12-stable-5+b1
ii  libffi8  3.4.2-4
ii  libfontconfig1   2.13.1-4.4
ii  libfreetype6 2.12.1+dfsg-3
ii  libgcc-s112.1.0-7
ii  libgdk-pixbuf-2.0-0  2.42.8+dfsg-2
ii  libglib2.0-0 2.72.3-1
ii  libgtk-3-0   3.24.34-1
ii  libicu71 71.1-3
ii  libnspr4 2:4.34-1
ii  libnss3  2:3.81-1
ii  libpango-1.0-0   1.50.7+ds-1
ii  librnp0  0.16.0-1
ii  libstdc++6   12.1.0-7
ii  libvpx7  1.12.0-1
ii  libx11-6 2:1.8.1-2
ii  libx11-xcb1  2:1.8.1-2
ii  libxcb-shm0  1.14-3
ii  libxcb1  1.14-3
ii  libxext6 2:1.3.4-1
ii  libxrandr2   2:1.5.2-2+b1
ii  psmisc   23.5-3
ii  x11-utils7.7+5
ii  zlib1g   1:1.2.11.dfsg-4

Versions of packages thunderbird recommends:
ii  hunspell-de-ch-frami [hunspell-dictionary]  1:7.2.0-2
ii  hunspell-en-gb [hunspell-dictionary]1:7.2.0-2
ii  hunspell-en-us [hunspell-dictionary]1:2020.12.07-2
ii  hunspell-es [hunspell-dictionary]   1:7.2.0-2
ii  myspell-fr-gut [myspell-dictionary] 1:1.0-32.2

Versions of packages thunderbird suggests:
ii  apparmor  3.0.6-1
ii  fonts-lyx 2.3.6.1-1
ii  libgssapi-krb5-2  1.20-1

-- no debconf information



Bug#1002693: plasma-desktop: kde plasma doesn't show logout prompt using wayland

2021-12-27 Thread Michael Meier
After I've noticed, that also the lock screen isn't working, and I 
couldn't get back into my sessions, i've searched through the packages 
list. I've installed layer-shell-qt

and now logout screen and lock screen are working.
Seems like that package is absolutely necessary

On 27.12.21 10:38, Michael Meier wrote:

Package: plasma-desktop
Version: 4:5.23.4-2
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

I'm using kde plasma together with wayland.
When I choose in the system menu, logout/reboot/shutdown nothing happens (The
usualy logout screen is not shown). But after about 30 seconds the chosen
actions gets executed.
Reboot won't work properly anyway, it will shutdown everything, and then hang
with
showing ^@^@^@ . But I guess that doesn't depend on the bug described here?
With xserver everything works properly.

journalctl shows me following errors (propably some missing dependencies?) and
crashes

Dez 27 10:20:59 dbus-daemon[1889]: [session uid=1000 pid=1889] Activating
service name='org.kde.LogoutPrompt' requested by ':1.71' (uid=1000 pid=2460
comm="/usr/bin/plasmashell ")
Dez 27 10:20:59 dbus-daemon[1889]: [session uid=1000 pid=1889] Successfully
activated service 'org.kde.LogoutPrompt'
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: No shell
integration named "layer-shell" found
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Loading shell
integration failed.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Attempted to load
the following shells ("layer-shell")
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Wayland does not
support QWindow::requestActivate()
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Wayland does not
support QWindow::requestActivate()
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:258: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:463: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:659: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:913: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1049: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1251: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1453: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1631: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1739: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1980: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:2223: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:05 su[3712]: pam_unix(su:session): session closed for user root
Dez 27 10:21:30 dbus-daemon[1889]: [session uid=1000 pid=1889] Activating
service name='org.kde.Shutdown' requested by ':1.112' (uid=1000 pid=5148
comm="/usr/lib/x86_64-linux-gnu/libexec/ksmserver-logout")
Dez 27 10:21:30 dbus-daemon[1889]: [session uid=1000 pid=1889] Successfully
activated service 'org.kde.Shutdown'
Dez 27 10:21:30 systemd[1845]: app-
thunderbird-7bcb5e9c845d4f2fa1469ec1bd491c3a.scope: Consumed 31.958s CPU time.
Dez 27 10:21:31 systemd[1845]: app-
firefox-81ae0ea346c04ac59b4f9a04dba50dc8.scope: Consumed 2min 53.922s CPU time.
Dez 27 10:21:31 systemd-logind[919]: System is rebooting.
Dez 27 10:21:31 kactivitymanagerd[2010]: The Wayland connection broke. Did the
Wayland compositor die?
Dez 27 10:21:31 kactivitymanagerd[2010]: KCrash: crashing...
crashRecursionCounter = 2
Dez 27 10:21:31 kactivitymanagerd[2010]: KCrash: Application Name =
kactivitymanagerd path = /usr/lib/x86_64-linux-gnu/libexec pid = 2010
Dez 27 10:21:31 kactivitymanagerd[2010]: KCrash: Arguments:
/usr/lib/x86_64-linux-gnu/libexec/kactivitymanagerd
Dez 27 10:21:31 sddm[1075]: Authentication error: "Process crashed"
Dez 27 10:21:31 sddm[1075]: Auth: sddm-helper crashed (exit code 15)
Dez 27 10:21:31 sddm[1075]: Authentication error: "Process crashed"
Dez 27 10:21:31 sddm[1075]: Auth: sddm-helper exited with 15


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TA

Bug#1002696: kwin-wayland should depend (or at least mention) more explicitely on kwin-wayland-backend-drm

2021-12-27 Thread Michael Meier
Package: kwin-wayland
Version: 4:5.23.4-1
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

I've installed plasma-workspace-wayland which install kwin-wayland which
installed kwin-wayland-backend-wayland.
When I tried to start up kde plasma in a wayland session, the screen got black
for a few seconds, and then I was back at the login screen (sddm I guess).
No error messages or easily findable logs or anything.
After quite some research I've found ~/.local/share/sddm/wayland-session.log
which explained me that it couldn't find any viable backend. Seems like the
installed kwin-wayland-backend-wayland doesn't work. So I've just tried to
install kwin-wayland-backend-drm and then the sessions was able to properly
start up.
Don't ask my why kwin-wayland-backend-wayland was installed instead of kwin-
wayland-backend-drm. But I remember that I've tried wayland out, maybe 1-1.5
years ago, maybe there were some rest overs?
But I guess for most installations the drm should be preferred. Or at least
mentioned in the description of plasma-workspace-wayland?
Then sddm should show a proper message, which would help a lot, and instead of
only logging to ~/.local/share/sddm/wayland-session.log which is basically
impossible to find, it should also log to journalctl.


Here ~/.local/share/sddm/wayland-session.log:

No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
No backend specified through command line argument, trying auto resolution
FATAL ERROR: could not find a backend
startplasmacompositor: Shutting down...
startplasmacompositor: Done.


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages kwin-wayland depends on:
ii  kwayland-integration  5.23.4-1
ii  kwin-common   4:5.23.4-1
ii  kwin-wayland-backend-drm  4:5.23.4-1
ii  kwin-wayland-backend-wayland  4:5.23.4-1
ii  libc6 2.33-1
ii  libcap2   1:2.44-1
ii  libcap2-bin   1:2.44-1
ii  libepoxy0 1.5.9-2
ii  libfontconfig12.13.1-4.2
ii  libfreetype6  2.11.0+dfsg-1
ii  libkf5configcore5 5.88.0-1
ii  libkf5coreaddons5 5.88.0-1
ii  libkf5crash5  5.88.0-1
ii  libkf5globalaccelprivate5 5.88.0-1
ii  libkf5i18n5   5.88.0-2
ii  libkf5idletime5   5.88.0-1
ii  libkf5notifications5  5.88.0-2
ii  libkf5quickaddons55.88.0-1
ii  libkf5waylandclient5  4:5.88.0-1
ii  libkf5windowsystem5   5.88.0-1
ii  libkwaylandserver5 [libkwaylandserver5-5.23]  5.23.4-1
ii  libkwin4-effect-builtins1 4:5.23.4-1
ii  libkwineffects13  4:5.23.4-1
ii  libkwinglutils13  4:5.23.4-1
ii  libpipewire-0.3-0 0.3.42-1
ii  libqt5core5a [qtbase-abi-5-15-2]  5.15.2+dfsg-14
ii  libqt5dbus5   5.15.2+dfsg-14
ii  libqt5gui55.15.2+dfsg-14
ii  libqt5network55.15.2+dfsg-14
ii  libqt5widgets55.15.2+dfsg-14
ii  libstdc++6

Bug#1002693: plasma-desktop: kde plasma doesn't show logout prompt using wayland

2021-12-27 Thread Michael Meier
Package: plasma-desktop
Version: 4:5.23.4-2
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

I'm using kde plasma together with wayland.
When I choose in the system menu, logout/reboot/shutdown nothing happens (The
usualy logout screen is not shown). But after about 30 seconds the chosen
actions gets executed.
Reboot won't work properly anyway, it will shutdown everything, and then hang
with
showing ^@^@^@ . But I guess that doesn't depend on the bug described here?
With xserver everything works properly.

journalctl shows me following errors (propably some missing dependencies?) and
crashes

Dez 27 10:20:59 dbus-daemon[1889]: [session uid=1000 pid=1889] Activating
service name='org.kde.LogoutPrompt' requested by ':1.71' (uid=1000 pid=2460
comm="/usr/bin/plasmashell ")
Dez 27 10:20:59 dbus-daemon[1889]: [session uid=1000 pid=1889] Successfully
activated service 'org.kde.LogoutPrompt'
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: No shell
integration named "layer-shell" found
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Loading shell
integration failed.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Attempted to load
the following shells ("layer-shell")
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Wayland does not
support QWindow::requestActivate()
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.qpa.wayland: Wayland does not
support QWindow::requestActivate()
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:258: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:463: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:659: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:913: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1049: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1251: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1453: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1631: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1739: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:1980: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:00 org.kde.LogoutPrompt[5148]: qt.svg: :303:2223: Could not
add child element to parent element because the types are incorrect.
Dez 27 10:21:05 su[3712]: pam_unix(su:session): session closed for user root
Dez 27 10:21:30 dbus-daemon[1889]: [session uid=1000 pid=1889] Activating
service name='org.kde.Shutdown' requested by ':1.112' (uid=1000 pid=5148
comm="/usr/lib/x86_64-linux-gnu/libexec/ksmserver-logout")
Dez 27 10:21:30 dbus-daemon[1889]: [session uid=1000 pid=1889] Successfully
activated service 'org.kde.Shutdown'
Dez 27 10:21:30 systemd[1845]: app-
thunderbird-7bcb5e9c845d4f2fa1469ec1bd491c3a.scope: Consumed 31.958s CPU time.
Dez 27 10:21:31 systemd[1845]: app-
firefox-81ae0ea346c04ac59b4f9a04dba50dc8.scope: Consumed 2min 53.922s CPU time.
Dez 27 10:21:31 systemd-logind[919]: System is rebooting.
Dez 27 10:21:31 kactivitymanagerd[2010]: The Wayland connection broke. Did the
Wayland compositor die?
Dez 27 10:21:31 kactivitymanagerd[2010]: KCrash: crashing...
crashRecursionCounter = 2
Dez 27 10:21:31 kactivitymanagerd[2010]: KCrash: Application Name =
kactivitymanagerd path = /usr/lib/x86_64-linux-gnu/libexec pid = 2010
Dez 27 10:21:31 kactivitymanagerd[2010]: KCrash: Arguments:
/usr/lib/x86_64-linux-gnu/libexec/kactivitymanagerd
Dez 27 10:21:31 sddm[1075]: Authentication error: "Process crashed"
Dez 27 10:21:31 sddm[1075]: Auth: sddm-helper crashed (exit code 15)
Dez 27 10:21:31 sddm[1075]: Authentication error: "Process crashed"
Dez 27 10:21:31 sddm[1075]: Auth: sddm-helper exited with 15


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-desktop depends on:
ii  accountsservice  0.6.55-3
ii  breeze   4:5.23.4-1
ii 

Bug#1002691: openssh-client: ssh-agent doesn't get autostarted under wayland

2021-12-27 Thread Michael Meier
Package: openssh-client
Version: 1:8.7p1-2
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

I'm using wayland with kde plasma on debian testing. Under wayland the ssh
agent doesn't get auto started as it does under x-server. According to google
that seems to be a known issue, but I couldn't find any bug report for debian.
So here it is :-).
I've solved it by applying this solution:
https://blog.debiania.in.ua/posts/2020-05-18-howto-auto-start-ssh-agent-with-
systemd-on-debian-bullseye.html


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

Kernel: Linux 5.15.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openssh-client depends on:
ii  adduser   3.118
ii  dpkg  1.21.1
ii  libc6 2.33-1
ii  libedit2  3.1-20210910-1
ii  libfido2-11.9.0-1
ii  libgssapi-krb5-2  1.18.3-7
ii  libselinux1   3.3-1+b1
ii  libssl1.1 1.1.1m-1
ii  passwd1:4.8.1-2
ii  zlib1g1:1.2.11.dfsg-2

Versions of packages openssh-client recommends:
ii  xauth  1:1.1-1

Versions of packages openssh-client suggests:
pn  keychain   
ii  ksshaskpass [ssh-askpass]  4:5.23.4-1
pn  libpam-ssh 
pn  monkeysphere   

-- Configuration Files:
/etc/ssh/ssh_config changed [not included]

-- no debconf information



Bug#999423: powerdevil does not detect if on ac or battery

2021-11-10 Thread Michael Meier
Package: powerdevil
Version: 4:5.23.3-1
Severity: important
X-Debbugs-Cc: schissdra...@rmm.li

Powerdevil doesn't detect If i'm on AC or not. It always shows that the
powercord is plugged in. Doesn't matter if I unplug it or not.
It used to work (don't ask me when, maybe months ago?). So it doesn't do any of
the events it should do when on battery like reducing the screen brightness.
tlp does detect it correctly and at least sets everything else correctly.


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

Kernel: Linux 5.14.0-4-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages powerdevil depends on:
ii  kio  5.86.0-1
ii  libc62.32-4
ii  libcap2-bin  1:2.44-1
ii  libkf5activities55.86.0-1
ii  libkf5authcore5  5.86.0-1
ii  libkf5completion55.86.0-1
ii  libkf5configcore55.86.0-1
ii  libkf5configgui5 5.86.0-1
ii  libkf5configwidgets5 5.86.0-1
ii  libkf5coreaddons55.86.0-1
ii  libkf5crash5 5.86.0-1
ii  libkf5dbusaddons55.86.0-1
ii  libkf5i18n5  5.86.0-1
ii  libkf5kiowidgets55.86.0-1
ii  libkf5networkmanagerqt6  5.86.0-1
ii  libkf5notifyconfig5  5.86.0-1
ii  libkf5service-bin5.86.0-1
ii  libkf5service5   5.86.0-1
ii  libkf5solid5 5.86.0-1
ii  libkf5widgetsaddons5 5.86.0-1
ii  libkworkspace5-5 4:5.23.3-1
ii  libpowerdevilcore2   4:5.23.3-1
ii  libpowerdevilui5 4:5.23.3-1
ii  libqt5core5a 5.15.2+dfsg-12
ii  libqt5dbus5  5.15.2+dfsg-12
ii  libqt5gui5   5.15.2+dfsg-12
ii  libqt5widgets5   5.15.2+dfsg-12
ii  libstdc++6   11.2.0-10
ii  libudev1 249.5-2
ii  powerdevil-data  4:5.23.3-1

powerdevil recommends no packages.

powerdevil suggests no packages.

-- no debconf information



Bug#998250: Acknowledgement (plasma-nm: "Missing Plugin" when trying to connect to openvpn vpn)

2021-11-01 Thread Michael Meier
I've forgot to mention. I'm using a password protected key file. So 
network-manager needs to ask me for the password.


On 01.11.21 11:24, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 998250: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998250.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   schissdra...@rmm.li
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian Qt/KDE Maintainers 

If you wish to submit further information on this problem, please
send it to 998...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.





Bug#998250: plasma-nm: "Missing Plugin" when trying to connect to openvpn vpn

2021-11-01 Thread Michael Meier
Package: plasma-nm
Version: 4:5.23.0-1
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

When in the system tray I click on the network manager, choose an openvpn
connection, and tell it to connect it shows me: "Missing VPN plugin".

network-manager-openvpn is installed and it's been working since years but I
didn't use it in the last two months. So I guess an update of either plasma-nm
or network-manager itself led to that error.

After I've installed network-manager-openvpn-gnome I could start the vpn
connection using nmcli but still not usting plasma-nm


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

Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages plasma-nm depends on:
ii  kio 5.86.0-1
ii  libc6   2.32-4
ii  libkf5completion5   5.86.0-1
ii  libkf5configcore5   5.86.0-1
ii  libkf5configwidgets55.86.0-1
ii  libkf5coreaddons5   5.86.0-1
ii  libkf5dbusaddons5   5.86.0-1
ii  libkf5declarative5  5.86.0-1
ii  libkf5i18n5 5.86.0-1
ii  libkf5kiowidgets5   5.86.0-1
ii  libkf5modemmanagerqt6   5.86.0-1
ii  libkf5networkmanagerqt6 5.86.0-1
ii  libkf5notifications55.86.0-1
ii  libkf5solid55.86.0-1
ii  libkf5wallet-bin5.86.0-1
ii  libkf5wallet5   5.86.0-1
ii  libkf5widgetsaddons55.86.0-1
ii  libkf5windowsystem5 5.86.0-1
ii  libnm0  1.32.12-1
ii  libopenconnect5 8.10-2+b1
ii  libqca-qt5-22.3.4-1
ii  libqt5core5a5.15.2+dfsg-12
ii  libqt5dbus5 5.15.2+dfsg-12
ii  libqt5gui5  5.15.2+dfsg-12
ii  libqt5network5  5.15.2+dfsg-12
ii  libqt5qml5  5.15.2+dfsg-8
ii  libqt5quickwidgets5 5.15.2+dfsg-8
ii  libqt5widgets5  5.15.2+dfsg-12
ii  libqt5xml5  5.15.2+dfsg-12
ii  libstdc++6  11.2.0-10
ii  mobile-broadband-provider-info  20210805-1
ii  network-manager 1.32.12-1
ii  plasma-framework5.86.0-1
ii  qml-module-org-kde-kcoreaddons  5.86.0-1
ii  qml-module-org-kde-kirigami25.86.0-1
ii  qml-module-org-kde-prison   5.86.0-1

plasma-nm recommends no packages.

Versions of packages plasma-nm suggests:
ii  network-manager-fortisslvpn  1.2.8-2+b2
ii  network-manager-iodine   1.2.0-3
pn  network-manager-l2tp 
pn  network-manager-openconnect  
ii  network-manager-openvpn  1.8.16-1
ii  network-manager-pptp 1.2.8-4
ii  network-manager-ssh  1.2.11-1
pn  network-manager-strongswan   
pn  network-manager-vpnc 

-- no debconf information



Bug#982961: tomcat9: cron.daily/tomcat9 compress /var/log/tomcat9 *subfolders* breaking some deployed apps

2021-05-28 Thread Michael Meier
Package: tomcat9
Version: 9.0.35-1
Followup-For: Bug #982961
X-Debbugs-Cc: schissdra...@rmm.li

I've got the same problems with the subfolders in /var/log/tomcat9
It would be great if you could add the maxdepth=1 argument to the package.



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

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

Versions of packages tomcat9 depends on:
ii  lsb-base11.1.0
ii  systemd 247.3-5
hi  tomcat9-common  9.0.35-1
ii  ucf 3.0043

Versions of packages tomcat9 recommends:
pn  libtcnative-1  

Versions of packages tomcat9 suggests:
pn  tomcat9-admin 
pn  tomcat9-docs  
pn  tomcat9-examples  
pn  tomcat9-user  



Bug#839662: [firmware-atheros] ath10k_pci firmware crashes when ap changes bandwith

2021-03-24 Thread Michael Meier
sorry. I've solved the problem by getting an other network adapter => 
can't help anymore



On 24.03.21 11:18, maximilian attems wrote:

tags 839662 moreinfo
stop


The same problem here with firmware-atheros version 20170823-1~bpo9+1
and kernel 4.14.0-2-amd64.
It's a dell xps 13 8th gen, with a:

Is this reproducible with an up to date Debian Testing?


Sorry for the late reply and thank you for the reports.






Bug#984725: openjdk-11-jre-dcevm: incompatible with newest openjdk-11-jre 11.0.11+4-1

2021-03-07 Thread Michael Meier
Package: openjdk-11-jre-dcevm
Version: 11.0.10+1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: schissdra...@rmm.li

After the last update of openjdk-11-jre from 11.0.10+9-1 to 11.0.11+4-1 dcevm
can't be used anymore. The error is:
java -dcevm
:(
[0.040s][error][class] Name nativeParkEventPointer should be in the SymbolTable
since its class is loaded
Error occurred during initialization of VM
Invalid layout of well-known class: java.lang.Thread





-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (600, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openjdk-11-jre-dcevm depends on:
ii  libc62.31-9
ii  openjdk-11-jre-headless  11.0.11+4-1

openjdk-11-jre-dcevm recommends no packages.

openjdk-11-jre-dcevm suggests no packages.



Bug#983530: fastboot: please update fastboot. Current version hangs with my smartphone

2021-02-25 Thread Michael Meier
Package: fastboot
Version: 1:10.0.0+r36-7
Followup-For: Bug #983530
X-Debbugs-Cc: schissdra...@rmm.li

I've just realized. It doesn't have anything to do with the fastboot version.
It only accidentally worked with the new one.
As it seems the only way to make it work is (independently the version):
- Disconnect the device
- execute the fastboot command, so it says: "< waiting for any device >"
- connection the device
- now the fastboot command will be executed correctly.

so I guess that's just a normal bug report then, now idea how to change the
subject though



Bug#983530: fastboot: please update fastboot. Current version hangs with my smartphone

2021-02-25 Thread Michael Meier
Package: fastboot
Version: 1:10.0.0+r36-7
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

When trying to flash a recovery to my smartphone (poco x3). It hangs forever at
Sending 'recovery' (131072 KB)

After a while an error appears in dmesg:
[227526.825738] INFO: task fastboot:960640 blocked for more than 120 seconds.
[227526.825742]   Tainted: G   OE 5.10.0-3-amd64 #1 Debian
5.10.13-1
[227526.825743] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables
this message.
[227526.825745] task:fastbootstate:D stack:0 pid:960640 ppid:959360
flags:0x
[227526.825747] Call Trace:
[227526.825753]  __schedule+0x282/0x870
[227526.825755]  ? usleep_range+0x80/0x80
[227526.825757]  schedule+0x46/0xb0
[227526.825758]  schedule_timeout+0xff/0x140
[227526.825761]  ? __prepare_to_swait+0x4b/0x70
[227526.825762]  __wait_for_common+0xae/0x160
[227526.825774]  usb_start_wait_urb+0x83/0x160 [usbcore]
[227526.825783]  do_proc_bulk+0x12e/0x2c0 [usbcore]
[227526.825792]  usbdev_ioctl+0x299/0x1060 [usbcore]
[227526.825796]  __x64_sys_ioctl+0x83/0xb0
[227526.825797]  do_syscall_64+0x33/0x80
[227526.825799]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[227526.825801] RIP: 0033:0x7f1e24e8acc7
[227526.825803] RSP: 002b:7ffd36ed8fa8 EFLAGS: 0246 ORIG_RAX:
0010
[227526.825804] RAX: ffda RBX:  RCX:
7f1e24e8acc7
[227526.825805] RDX: 7ffd36ed8fb8 RSI: c0185502 RDI:
0004
[227526.825806] RBP: 7ffd36ed8fd0 R08: 021d42a0 R09:

[227526.825807] R10: 7ffd36f0d080 R11: 0246 R12:
0040
[227526.825807] R13: 021d30d0 R14: 0040 R15:
7ffd36ed9140


With the newest fastboot version from following url:
https://dl.google.com/android/repository/platform-tools_r31.0.0-linux.zip

it works.






-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (600, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages fastboot depends on:
ii  android-libadb 1:10.0.0+r36-7
ii  android-libbase1:10.0.0+r36-7
ii  android-libboringssl   10.0.0+r36-1
ii  android-libcutils  1:10.0.0+r36-7
ii  android-libext4-utils  10.0.0+r36+ds-2
ii  android-libsparse  1:10.0.0+r36-7
ii  android-libunwind  10.0.0+r36-4
ii  android-libziparchive  1:10.0.0+r36-7
ii  android-sdk-platform-tools-common  28.0.2+3
ii  libc6  2.31-9
ii  libgcc-s1  10.2.1-6
ii  libstdc++6 10.2.1-6

fastboot recommends no packages.

Versions of packages fastboot suggests:
pn  android-sdk-platform-tools  



Bug#982909: pigz: Unable to update pigz after applying dpkg-divert from readme.debian

2021-02-16 Thread Michael Meier
Package: pigz
Version: 2.6-1
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

Years ago when I've installed pigz, I've applied the process descriped in
README.debian to replace gzip with pigz.:

dpkg-divert --local --add --rename --divert /bin/gzip.gzip /bin/gzip
ln -s /usr/bin/pigz /bin/gzip

I've never had any problems so, until about a week or two ago, the first time
in years pigz was going to be updated. And the upgrade failed (I obviously had
no idea anymore what I did years ago). Today it was updated again, fortunately
the last update was only a few weeks ago, so I remembered what I've done then.
It fails with following message:

Preparing to unpack .../0-pigz_2.6-1_amd64.deb ...
ERROR: /bin/gzip executable becomes unusable after removal of pigz!
See /usr/share/doc/pigz/README.Debian for details.
dpkg: warning: old pigz package pre-removal script subprocess returned error
exit status 1
dpkg: trying script from the new package instead ...
ERROR: /bin/gzip executable becomes unusable after removal of pigz!
See /usr/share/doc/pigz/README.Debian for details.
dpkg: error processing archive /tmp/apt-dpkg-install-
dBBAy4/0-pigz_2.6-1_amd64.deb (--unpack):
 new pigz package pre-removal script subprocess returned error exit status 1

So I first had to undo the changes described above before I could update. It
would be great if the update process automatically detects those changes,
undoes them, updates, and reapplies them. So the update process doesn't fail.
Since those changes are in the README.debian, there like halfway official, so
it would be great if they'd also work with updates :-). Maybe one could even
make those changes a dpkg-reconfigure question?



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (600, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-3-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pigz depends on:
ii  dpkg1.20.7.1
ii  libc6   2.31-9
ii  zlib1g  1:1.2.11.dfsg-2

pigz recommends no packages.

pigz suggests no packages.

-- no debconf information



Bug#972788: openjdk-11-jre-dcevm: incompatible with openjdk-11-jre 11.0.9

2020-10-23 Thread Michael Meier
Package: openjdk-11-jre-dcevm
Version: 11.0.7+1-1
Severity: normal
X-Debbugs-Cc: schissdra...@rmm.li

my system just upgraded to openjdk-11-jre 11.0.9.
when starting up java with dcevm support you get following error:
java --version -dcevm
Error occurred during initialization of VM
Unable to load native library: /usr/lib/jvm/java-11-openjdk-
amd64/lib/libjava.so: undefined symbol: JVM_IsUseContainerSupport, version
SUNWprivate_1.1

Downgrading openjdk-11-jre to 11.0.8 makes it work again.

So the dcevm package is broken (again) for newer java versions.



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (600, 'testing'), (300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openjdk-11-jre-dcevm depends on:
ii  libc62.31-4
ii  openjdk-11-jre-headless  11.0.9+11-1

openjdk-11-jre-dcevm recommends no packages.

openjdk-11-jre-dcevm suggests no packages.

-- no debconf information



Bug#962668: same error

2020-08-14 Thread Michael Meier
I've got exactly the same error (the one with the surrogates not 
allowed) with way too many PDFs. Already since months, always using the 
newest calibre version in testing.

Now I've just installed the official version as described in
https://calibre-ebook.com/download_linux
and that version does the conversion without any problems. So the 
problem must be in the debian package.




Bug#964147: freerdp2-x11: xfreerdp fails with symbol lookup error

2020-07-02 Thread Michael Meier

so after some trying out I've foudn out that I've also had to update:
libfreerdp-client2-2:amd64 2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u1 
-> 2.1.2+dfsg1-2


then it works.
The version dependency seems to be wrong somewhere...

On 02.07.20 10:06, Michael Meier wrote:

Package: freerdp2-x11
Version: 2.1.2+dfsg1-1
Severity: grave
Justification: renders package unusable

I've just updated xfreerdp. The new versions can't be executed.it fails with:

xfreerdp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libfreerdp-
client2.so.2: undefined symbol: msusb_msconfig_write

The previous version i used: 2.0.0~git20190204.1.2693389a+dfsg1-2~bpo10+1
worked well.

Propably some library version dependency which isn't correctly stated in the
.deb package?



-- System Information:
Debian Release: 10.4
   APT prefers stable
   APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), 
(300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages freerdp2-x11 depends on:
ii  libc6 2.30-4
ii  libfreerdp-client2-2  2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u1
ii  libfreerdp2-2 2.1.2+dfsg1-1
ii  libwinpr2-2   2.1.2+dfsg1-1
ii  libx11-6  2:1.6.7-1
ii  libxcursor1   1:1.1.15-2
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.4-2
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1

freerdp2-x11 recommends no packages.

freerdp2-x11 suggests no packages.

-- no debconf information





Bug#964147: freerdp2-x11: xfreerdp fails with symbol lookup error

2020-07-02 Thread Michael Meier
Package: freerdp2-x11
Version: 2.1.2+dfsg1-1
Severity: grave
Justification: renders package unusable

I've just updated xfreerdp. The new versions can't be executed.it fails with:

xfreerdp: symbol lookup error: /usr/lib/x86_64-linux-gnu/libfreerdp-
client2.so.2: undefined symbol: msusb_msconfig_write

The previous version i used: 2.0.0~git20190204.1.2693389a+dfsg1-2~bpo10+1
worked well.

Propably some library version dependency which isn't correctly stated in the
.deb package?



-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages freerdp2-x11 depends on:
ii  libc6 2.30-4
ii  libfreerdp-client2-2  2.0.0~git20190204.1.2693389a+dfsg1-1+deb10u1
ii  libfreerdp2-2 2.1.2+dfsg1-1
ii  libwinpr2-2   2.1.2+dfsg1-1
ii  libx11-6  2:1.6.7-1
ii  libxcursor1   1:1.1.15-2
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.4-2
ii  libxrandr22:1.5.1-1
ii  libxrender1   1:0.9.10-1

freerdp2-x11 recommends no packages.

freerdp2-x11 suggests no packages.

-- no debconf information



Bug#892325: New versions of Linphone (4.X) available

2020-06-01 Thread Michael Meier

Is there any chance that a newer version will be ever packed for debian?



Bug#961630: redmine: please update to redmine 4.1

2020-05-26 Thread Michael Meier
Package: redmine
Severity: wishlist

Redmine 4.1 is available. It would be great if we could update to it.



-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.6.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages redmine depends on:
pn  dbconfig-common 
ii  debconf [debconf-2.0]   1.5.71
pn  libjs-chart.js  
ii  libjs-jquery3.3.1~dfsg-3
ii  libjs-jquery-ui 1.12.1+dfsg-5
pn  libjs-raphael   
pn  redmine-sqlite | redmine-mysql | redmine-pgsql  
ii  ruby1:2.5.1
pn  ruby-actionpack-action-caching  
pn  ruby-actionpack-xml-parser  
pn  ruby-bundler
pn  ruby-coderay
pn  ruby-csv
pn  ruby-i18n   
pn  ruby-jquery-rails   
pn  ruby-mail   
pn  ruby-mime-types 
pn  ruby-mimemagic  
pn  ruby-mini-mime  
pn  ruby-net-ldap   
pn  ruby-nokogiri   
pn  ruby-rack   
pn  ruby-rack-test  
pn  ruby-rails  
pn  ruby-rails-dom-testing  
pn  ruby-rails-observers
pn  ruby-rbpdf  
pn  ruby-redcarpet  
pn  ruby-request-store  
pn  ruby-rmagick
pn  ruby-roadie 
pn  ruby-roadie-rails   
pn  ruby-rouge  

Versions of packages redmine recommends:
pn  passenger  

Versions of packages redmine suggests:
pn  bzr 
pn  cvs 
pn  darcs   
ii  git 1:2.26.2-1~bpo10+1
pn  mercurial   
pn  ruby-fcgi   
pn  subversion  



Bug#959937: tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application

2020-05-07 Thread Michael Meier



On 07.05.20 06:31, Markus Koschany wrote:


Am 07.05.20 um 10:04 schrieb Michael Meier:

Package: tomcat9
Version: 9.0.16-4
Severity: grave
Justification: renders package unusable

I've just been called out of bed.
As it seems unattended-upgrades upgraded on a debian buster server
from:9.0.16-4 to 9.0.31-1~deb10u1
One of the installed webapps throws following error when trying to use it:

[https-openssl-nio-8443-exec-13] ERROR org.zkoss.zk.ui.metainfo.Property -
Failed to assign [value=${i18n:rt('Benutzername')}] to 
Unable to find ExpressionFactory of type: # Licensed to the Apache Software
Foundation (ASF) under one or more

Downgrading to 9.0.16-4 solves the issue.

Have you read the changelog or the Debian security announcement before
upgrading Tomcat 9 ? Does your application require the AJP protocol to
work? Then you probably need to slightly change your Tomcat
configuration. For more information please also refer to the official
documentation at

   https://tomcat.apache.org/tomcat-9.0-doc/config/ajp.html


The application doesn't use ajp.

The sense of using unattended-upgrades and debian stable (no breaking 
changes on updates) is not to read each security announcement in before.


I'm not working in an area, where anybody would (be able to) pay for that.



If that does not solve your problem, then we need more information about
your setup and configuration to debug the problem but note that we ship
the latest upstream version basically unmodified, so this would be most
likely an upstream bug.


I could trace it back to the zk library used:

https://bz.apache.org/bugzilla/show_bug.cgi?id=64097

https://tracker.zkoss.org/browse/ZK-4510

That seems to be a really really weird bug. If I understand it 
correctly, it's the fault of zk, but I'm not 100% sure.


Anyway, as it seems if I manage to update the project to the new zk 
major version, it's supposed to work again.




Bug#959937: tomcat9: update to tomcat9:amd64 9.0.31-1~deb10u1 breaks application

2020-05-07 Thread Michael Meier
Package: tomcat9
Version: 9.0.16-4
Severity: grave
Justification: renders package unusable

I've just been called out of bed.
As it seems unattended-upgrades upgraded on a debian buster server
from:9.0.16-4 to 9.0.31-1~deb10u1
One of the installed webapps throws following error when trying to use it:

[https-openssl-nio-8443-exec-13] ERROR org.zkoss.zk.ui.metainfo.Property -
Failed to assign [value=${i18n:rt('Benutzername')}] to 
Unable to find ExpressionFactory of type: # Licensed to the Apache Software
Foundation (ASF) under one or more

Downgrading to 9.0.16-4 solves the issue.



-- System Information:
Debian Release: 10.3
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages tomcat9 depends on:
ii  lsb-base10.2019051400
ii  systemd 245.5-2~bpo10+1
ii  tomcat9-common  9.0.16-4
ii  ucf 3.0038+nmu1

Versions of packages tomcat9 recommends:
pn  libtcnative-1  

Versions of packages tomcat9 suggests:
pn  tomcat9-admin 
pn  tomcat9-docs  
pn  tomcat9-examples  
pn  tomcat9-user  

-- no debconf information



Bug#954822: openjdk-11-jre: Java application (Eclipse) regularly crashes with SIGSEGV

2020-03-25 Thread Michael Meier

ok.
So after downgrading libc and openjdk-11 didn't help. I've downgraded my 
eclipse installation from 2020-3 to 2019-12.

And since then it was running stable, for several hours.
Is it possible, that that is a strange bug in eclipse, or would it just 
be, that the new version of eclipse triggers an until yet undiscovered 
bug in openjdk-11?

Maybe somebody who knows more about this stuff could answer me?



Bug#954822: openjdk-11-jre: Java application (Eclipse) regularly crashes with SIGSEGV

2020-03-24 Thread Michael Meier

I've downgraded libc6 to 2.29-10 again.
Still the same behaviour.
So i've downgraded all the openjdk packages to 11.0.4+11-1~deb10u1 .
Still the same result.

Could it be possible that it is an eclipse problem? I've recently 
updated to the new 2020-03 version.

I thought a programm shouldn't be able to sigsegv the virtual machine.


On 23.03.20 21:26, Michael Meier wrote:

Package: openjdk-11-jre
Version: 11.0.6+10-2
Severity: important

Recently Eclipse regularly crashes with a sigsevg.
I'm pretty sure that started happening since libc6 was updated on my system
about 1 week ago. Before I've never had that problem.
Unfortunately I can't downgrade it easily to test it out, since to many
packages depend on it.

Here is the message:

1 error
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x7fa351edd245, pid=23923, tid=24047
#
# JRE version: OpenJDK Runtime Environment (11.0.6+10) (build 11.0.6+10-post-
Debian-2)
# Java VM: OpenJDK 64-Bit Server VM (11.0.6+10-post-Debian-2, mixed mode,
sharing, tiered, compressed oops, g1 gc, linux-amd64)
# Problematic frame:
# C  [libpthread.so.0+0x11245]  pthread_getcpuclockid+0x5
#
# No core dump will be written. Core dumps have been disabled. To enable core
dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /home/rmm/hs_err_pid23923.log
Compiled method (nm)  372019 35610 n 0
sun.management.ThreadImpl::getThreadTotalCpuTime0 (native)
  total in heap  [0x7fa33d6cd310,0x7fa33d6cd6b0] = 928
  relocation [0x7fa33d6cd488,0x7fa33d6cd4b8] = 48
  main code  [0x7fa33d6cd4c0,0x7fa33d6cd6b0] = 496
#
# If you would like to submit a bug report, please visit:
#   https://bugs.debian.org/openjdk-11
#

let's see if report bug let me attach the mentioned file ;-)



-- System Information:
Debian Release: 10.3
   APT prefers stable
   APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), 
(300, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openjdk-11-jre depends on:
ii  libc62.30-2
ii  libgif7  5.1.4-3
ii  libgl1   1.1.0-1
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  libpng16-16  1.6.36-6
ii  libx11-6 2:1.6.7-1
ii  libxext6 2:1.3.3-1+b2
ii  openjdk-11-jre-headless  11.0.6+10-2

Versions of packages openjdk-11-jre recommends:
ii  fonts-dejavu-extra   2.37-1
ii  libatk-wrapper-java-jni  0.38.0-1~bpo10+1

openjdk-11-jre suggests no packages.

-- no debconf information





Bug#945801: wish: file picker: enable lookahead search again

2019-11-28 Thread Michael Meier
Package: libgtk-3-0
Version: 3.24.5-1
Severity: wishlist

Since years the recursive search of the gtk file picker is driving me nuts each
time I have to use it (fortunately only a very few programs use it). As it
seems there is no option which lets the user choose what he prefers...
At least archlinux does have a package (patch?) which enables the old typeahead
search (only in the same folder) again.

https://aur.archlinux.org/packages/gtk3-typeahead/

Would there be any chance that could be incorporated into debian?



-- System Information:
Debian Release: 10.2
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-0.bpo.2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme   3.30.1-1
ii  hicolor-icon-theme   0.17-2
ii  libatk-bridge2.0-0   2.34.0-3~bpo10+1
ii  libatk1.0-0  2.34.0-1~bpo10+1
ii  libc62.29-3
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcolord2   1.4.3-4
ii  libcups2 2.2.10-6+deb10u1
ii  libepoxy01.5.3-0.1
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.10.1-2
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2+deb10u2
ii  libgtk-3-common  3.24.5-1
ii  libharfbuzz0b2.3.1-1
ii  libjson-glib-1.0-0   1.4.4-2
ii  libpango-1.0-0   1.42.4-7~deb10u1
ii  libpangocairo-1.0-0  1.42.4-7~deb10u1
ii  libpangoft2-1.0-01.42.4-7~deb10u1
ii  librest-0.7-00.8.1-1
ii  libsoup2.4-1 2.64.2-2
ii  libwayland-client0   1.16.0-1
ii  libwayland-cursor0   1.16.0-1
ii  libwayland-egl1  1.16.0-1
ii  libx11-6 2:1.6.7-1
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-2
ii  libxdamage1  1:1.1.4-3+b3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxinerama1 2:1.1.4-2
ii  libxkbcommon00.8.2-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libxrandr2   2:1.5.1-1
ii  shared-mime-info 1.10-1

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.24.5-1

Versions of packages libgtk-3-0 suggests:
pn  gvfs 
ii  librsvg2-common  2.44.10-2.1

Versions of packages libgtk-3-0 is related to:
pn  appmenu-gtk3-module   
pn  fcitx-frontend-gtk3   
pn  gcin-gtk3-immodule
pn  gtk-vector-screenshot 
pn  gtk3-engines-xfce 
pn  gtk3-im-libthai   
pn  hime-gtk3-immodule
pn  ibus-gtk3 
pn  imhangul-gtk3 
ii  libcanberra-gtk3-module   0.30-7
pn  libcaribou-gtk3-module
pn  libgtk3-nocsd0
pn  maliit-inputcontext-gtk3  
pn  packagekit-gtk3-module
pn  scim-gtk-immodule 
pn  topmenu-gtk3  
pn  uim-gtk3  
pn  uim-gtk3-immodule 

-- no debconf information



Bug#942876: openjdk-11-jre-dcevm: Doesn't start up anymore after updating openjdk-11-jre

2019-10-22 Thread Michael Meier
Package: openjdk-11-jre-dcevm
Version: 11.0.3+1-1
Severity: grave
Justification: renders package unusable

java -dvecm can't be executed anymore:

java -dcevm
java: relocation error: /usr/lib/jvm/java-11-openjdk-amd64/lib/libjava.so:
symbol JVM_InitializeFromArchive version SUNWprivate_1.1 not defined in file
libjvm.so with link time reference

This seems to be the case since yesterday my system updated openjdk-11-jre to
version 11.0.5 from the security repository



-- System Information:
Debian Release: 10.1
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (400, 'testing'), (300, 
'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.2.0-2-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages openjdk-11-jre-dcevm depends on:
ii  libc62.29-2
ii  openjdk-11-jre-headless  11.0.5+10-1~deb10u1

openjdk-11-jre-dcevm recommends no packages.

openjdk-11-jre-dcevm suggests no packages.

-- no debconf information



Bug#936061: reportbug: querybts doesn't find a certain existing bug report for package linux-image-5.2.0-2-amd64

2019-09-08 Thread Michael Meier



On 31.08.19 07:07, Nis Martensen wrote:

On 29 Aug 2019 Michael Meier wrote:


I wanted to report a bug for linux-image-5.2.0-2-amd64. I've used 
reportbug-ng
to find out if the bug was already reported.  Yes, I know it's not 
maintained

anymore, but it still just works better to find existing bug reports.
The bug was already reported. The Bug number is 935852. Then I wanted 
to add

some information to the bug so I've tried to find it again with
querybts linux-image-5.2.0-2-amd64
But it doesn't find it at all, it also can't find it for
linux-image-amd64 or any other similar package I've tried out.


Thank you for the report. I've tried to reproduce and can confirm the 
problem. However, I don't think this is a bug in reportbug:


 - The binary package names you list (linux-image-5.2.0-2-amd64, 
linux-image-amd64) belong to the source package linux-signed-amd64.


 - The bug you've been looking for was reported against a different 
source package (linux). Reportbug doesn't query bug reports across 
multiple source packages, so the bug was evidently not listed.


To search bugs across different packages, you are better off using a 
web search, see https://www.debian.org/Bugs/ or 
https://udd.debian.org/bugs/
Such complex bug searches are beyond what is reasonable for a simple 
tool like reportbug.


I've just tried that out, I didn't manage to find the bug with 
https://www.debian.org/Bugs/ and I've got not a single idea how to 
properly search on https://udd.debian.org/bugs/ .


Probably it would be possible to somehow find them over those pages. But 
when I want to report a bug, I usually just want to make sure nobody 
reported it yet, on which i don't want to spend more than a minute. And 
since reportbug shows me already reported bugs, I expect that if no 
report similar to mine shows up, that it hasn't been reported yet. It 
basically was just an accident that I've noticed that the bug was 
already reported against an other source package. Anyway, I guess that 
problem only appears with the linux kernel? So it would be the only one 
which would get double bug reports because of that.


I've noticed there are quite a few bug reports for the kernel 5.2.0 
which seemingly were reported against the other source package, so you 
can't find them when reporting against linux-image-5.2.0 .


Maybe it would be possible to somehow make sure, those bug reports are 
bundled at the same place, but I guess that's not the responsibility of 
reportbug.



I'm not familiar with reportbug-ng so I cannot tell how you managed to 
find the bug there. In any case, if you already have the bug number 
and want to submit followup information, you can 
In reportbug-ng I've just entered as package linux-image-5.2.0-2-amd64 
and it found all relevant bug reports for it.

use "reportbug -N $BUG".

Thanks. that actually helps :-).



Bug#936061: reportbug: querybts doesn't find a certain existing bug report for package linux-image-5.2.0-2-amd64

2019-08-29 Thread Michael Meier
Package: reportbug
Version: 7.5.3
Severity: normal

I wanted to report a bug for linux-image-5.2.0-2-amd64. I've used reportbug-ng
to find out if the bug was already reported.  Yes, I know it's not maintained
anymore, but it still just works better to find existing bug reports.
The bug was already reported. The Bug number is 935852. Then I wanted to add
some information to the bug so I've tried to find it again with
querybts linux-image-5.2.0-2-amd64
But it doesn't find it at all, it also can't find it for
linux-image-amd64 or any other similar package I've tried out.



-- Package-specific info:
** Environment settings:
EDITOR="/bin/nano"
PAGER="less"
VISUAL="/bin/nano"
INTERFACE="gtk"

** /home/rmm/.reportbugrc:
reportbug_version "7.5.2"
mode advanced
ui gtk
realname "Michael Meier"
email "schissdra...@rmm.li"
no-cc
list-cc-me
smtphost reportbug.debian.org

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable'), (500, 
'stable-updates')
Architecture: amd64 (x86_64)

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

Versions of packages reportbug depends on:
ii  apt1.8.2
ii  python33.7.3-1
ii  python3-reportbug  7.5.3
ii  sensible-utils 0.0.12

reportbug recommends no packages.

Versions of packages reportbug suggests:
pn  claws-mail  
pn  debconf-utils   
pn  debsums 
pn  dlocate 
pn  emacs-bin-common
ii  file1:5.35-4
ii  gnupg   2.2.12-1
pn  postfix | exim4 | mail-transport-agent  
pn  python3-urwid   
ii  reportbug-gtk   7.5.3
ii  xdg-utils   1.1.3-1

Versions of packages python3-reportbug depends on:
ii  apt1.8.2
ii  file   1:5.35-4
ii  python33.7.3-1
ii  python3-apt1.8.4
ii  python3-debian 0.1.35
ii  python3-debianbts  2.8.2
ii  python3-requests   2.21.0-1
ii  sensible-utils 0.0.12

python3-reportbug suggests no packages.

-- no debconf information



Bug#935852: linux-image-5.2.0-2-amd64: Heavy static noise on headphone jack snd_hda_intel

2019-08-29 Thread Michael Meier
I've got the exactly same problem. Using an Dell XPS 13 8th gen, soudn 
device is:


00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 
21) (prog-if 80)

Subsystem: Dell Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 32, IRQ 149
Memory at dc328000 (64-bit, non-prefetchable) [size=16K]
Memory at dc30 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl



Bug#931669: ephoto doesn't even start up

2019-08-11 Thread Michael Meier

Hi Ross

Ok, I've just given it another try.

I've installed libevas1-engine-x (with -drm it didn't work).

Now it starts up, but then it segfaults. Here first the startup messages:

ephoto
ERR<5972>:eina_safety lib/evas/canvas/evas_object_rectangle.c:95 
evas_object_rectangle_add() safety check failed: efl_isa(e, 
EVAS_CANVAS_CLASS) is false

## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589390c0c 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589391901 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589392cd3 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f15893a9380 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libevas.so.1   0x7f158914c3ef 0x7f15890b6000
/usr/bin/ephoto  0x55f174e0abad 0x55f174de8000
/usr/bin/ephoto  0x55f174e0414a 0x55f174de8000
/usr/bin/ephoto  0x55f174e04f6c 0x55f174de8000
/usr/bin/ephoto  0x55f174df1b7f 0x55f174de8000
/usr/bin/ephoto  0x55f174df18dc 0x55f174de8000
/lib/x86_64-linux-gnu/libc.so.6  0x7f15885d209b 0x7f15885ae000
/usr/bin/ephoto  0x55f174df191a 0x55f174de8000
EOF

ERR<5972>:eina_safety lib/evas/canvas/evas_callbacks.c:479 
evas_object_event_callback_priority_add() safety check failed: eo_obj == 
NULL

## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589390c0c 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589391901 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589392cd3 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f15893a9380 0x7f1589367000
/usr/bin/ephoto  0x55f174e0ac00 0x55f174de8000
/usr/bin/ephoto  0x55f174e0414a 0x55f174de8000
/usr/bin/ephoto  0x55f174e04f6c 0x55f174de8000
/usr/bin/ephoto  0x55f174df1b7f 0x55f174de8000
/usr/bin/ephoto  0x55f174df18dc 0x55f174de8000
/lib/x86_64-linux-gnu/libc.so.6  0x7f15885d209b 0x7f15885ae000
/usr/bin/ephoto  0x55f174df191a 0x55f174de8000
EOF

ERR<5972>:eina_safety lib/evas/canvas/evas_object_rectangle.c:95 
evas_object_rectangle_add() safety check failed: efl_isa(e, 
EVAS_CANVAS_CLASS) is false

## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589390c0c 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589391901 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589392cd3 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f15893a9380 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libevas.so.1   0x7f158914c3ef 0x7f15890b6000
/usr/bin/ephoto  0x55f174e0abad 0x55f174de8000
/usr/bin/ephoto  0x55f174e0378a 0x55f174de8000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f1588ecabd7 0x7f1588eb5000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f1588ec5a77 0x7f1588eb5000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f1588ec5a77 0x7f1588eb5000
/usr/bin/ephoto  0x55f174e11782 0x55f174de8000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906bdc9 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f1589072d1f 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906ede9 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906da27 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f1589068bbb 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906928d 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906ed19 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906dcd7 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f1589069327 0x7f158904a000
/usr/bin/ephoto  0x55f174df1aff 0x55f174de8000
/usr/bin/ephoto  0x55f174df18dc 0x55f174de8000
/lib/x86_64-linux-gnu/libc.so.6  0x7f15885d209b 0x7f15885ae000
/usr/bin/ephoto  0x55f174df191a 0x55f174de8000
EOF

ERR<5972>:eina_safety lib/evas/canvas/evas_callbacks.c:479 
evas_object_event_callback_priority_add() safety check failed: eo_obj == 
NULL

## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589390c0c 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589391901 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1589392cd3 0x7f1589367000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f15893a9380 0x7f1589367000
/usr/bin/ephoto  0x55f174e0ac00 0x55f174de8000
/usr/bin/ephoto  0x55f174e0378a 0x55f174de8000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f1588ecabd7 0x7f1588eb5000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f1588ec5a77 0x7f1588eb5000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f1588ec5a77 0x7f1588eb5000
/usr/bin/ephoto  0x55f174e11782 0x55f174de8000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906bdc9 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f1589072d1f 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906ede9 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  0x7f158906da27 0x7f158904a000
/usr/lib/x86_64-linux-gnu/libecore.so.1  

Bug#933676: openjdk-11-jre-dcevm: openjdk-11-jre-dvecm doesn't include the hotswap agent

2019-08-09 Thread Michael Meier
No idea how to change this report into a RFP, so I just created a new 
one (which took me long enough to find out how to): Bug#934318


So I guess you can close that one here :-).

thanks
Michael

On 01.08.19 14:53, Emmanuel Bourg wrote:

Le 01/08/2019 à 20:21, Michael Meier a écrit :


according to http://hotswapagent.org and https://github.com/TravaOpenJDK/trava-
jdk-11-dcevm/ the java 11 dvecm version is supposed to include the
hotswapagent.
This package here doesn't do so. Would be great if it also could include it. So
the tutorials/manuals on the web work directly.

Hi Michael,

Thank you for the suggestion. Technically the hotswap agent is a
separate project [1] so it can't really fit in the openjdk-11-jre-dcevm
package (it could depend on it though). I suggest turning this bug
report into a RFP.

Emmanuel Bourg

[1] https://github.com/HotswapProjects/HotswapAgent




Bug#934318: RFP: hotswap-agent -- Java unlimited redefinition of classes at runtime

2019-08-09 Thread Michael Meier
Package: wnpp
Severity: wishlist

* Package name: hotswap-agent
  Version : 1.3.1
* URL : https://github.com/HotswapProjects/HotswapAgent
* License : GPL 2
  Programming Lang: Java
  Description : Java unlimited redefinition of classes at runtime

HotswapAgent is needed when you want to use openjdk-11-jre-dcevm vor developing
so you can hotswap code in a debug session.
According to http://hotswapagent.org and https://github.com/TravaOpenJDK/trava-
jdk-11-dcevm/ the java 11 dvecm version is supposed to include the
hotswapagent. But as it seems it should be packed as a separate package, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933676



Bug#934317: reportbug-gtk: After pressing back button, fields can't be edited anymore

2019-08-09 Thread Michael Meier
Package: reportbug-gtk
Version: 7.5.2
Severity: important

When in the gui, at one point you press back, or even worse, you're forced to
do it because of an error message, then you can't edit the previous fields
anymore. You even can't copy the previous text, so you need to start all over
again! (Just had to do that 3 times for a bug report)



-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages reportbug-gtk depends on:
ii  gir1.2-gtk-3.0 3.24.5-1
ii  gir1.2-vte-2.910.54.2-2
ii  python3-gi 3.30.4-1
ii  python3-gi-cairo   3.30.4-1
ii  python3-gtkspellcheck  4.0.5-1
ii  reportbug  7.5.2

reportbug-gtk recommends no packages.

reportbug-gtk suggests no packages.

-- no debconf information



Bug#933676: openjdk-11-jre-dcevm: openjdk-11-jre-dvecm doesn't include the hotswap agent

2019-08-01 Thread Michael Meier
Package: openjdk-11-jre-dcevm
Version: 11.0.3+1-1
Severity: normal

according to http://hotswapagent.org and https://github.com/TravaOpenJDK/trava-
jdk-11-dcevm/ the java 11 dvecm version is supposed to include the
hotswapagent.
This package here doesn't do so. Would be great if it also could include it. So
the tutorials/manuals on the web work directly.



-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (900, 'stable'), (700, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages openjdk-11-jre-dcevm depends on:
ii  libc62.28-10
ii  openjdk-11-jre-headless  11.0.4+11-1~deb10u1

openjdk-11-jre-dcevm recommends no packages.

openjdk-11-jre-dcevm suggests no packages.

-- no debconf information



Bug#928680: [openfortivpn] Since switching to buster openfortivpn can't connect to vpn anymore

2019-07-25 Thread Michael Meier

Ok, i've updated my whole system again. And now it seems to work.

You can close the bug.

Thanks a lot for your efforts.

On 08.05.19 23:05, Daniel Echeverry wrote:

tags 928680 + moreinfo unreproducible
severity 928680 normal
thanks

Hi!

El mié., 8 de may. de 2019 a la(s) 14:15, Michael Meier (c...@rmm.li 
<mailto:c...@rmm.li>) escribió:


Package: openfortivpn
Version: 1.8.1-1
Severity: normal

I've installed the fortivpn package in debian stable (stretch), and
managed to get it working with a vpn connection.
Somewhen I updated my System to buster and now realized that
openfortivpn can't connect to the vpn anymore. While another computer
which is still running on stretch connects to the same vpn without
any
problems with exactly the same config parameters. Also
openfortivpn and
ppp are the same version on both systems.
As it seems it doesn't manage to configure the ppp interface
correctly.
Maybe in buster something changed the way interfaces are
configured? No
idea.

Thanks for your report!! Unfortunately, I can't reproduce this bug, I 
tried openfortivpn package in 2 differents machines with buster and 
works fine, Could you upgrade your system? I think that you dont have 
the last versions of dependencies.


Regards

--
Daniel Echeverry
Debian Developer
https://wiki.debian.org/DanielEcheverry
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB


Bug#931669: ephoto doesn't even start up

2019-07-08 Thread Michael Meier
Package: ephoto
Version: 1.5-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I've just installed ephoto to try it out. I didn't get very far. It doesn't
even start up. If I try to start it up on the console, that's what it tells me:

ERR<26189>:ecore_evas lib/elementary/efl_ui_win.c:5300
_elm_win_finalize_internal() Cannot create window.
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71dcc0c 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71dd901 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71decd3 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b84c6a 0x7f5ce690
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b870c1 0x7f5ce690
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d127a7 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8750c 0x7f5ce690
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d127a7 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d0f8e4 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8742b 0x7f5ce690
/usr/bin/ephoto  0x563c68457604 0x563c6843b000
/usr/bin/ephoto  0x563c68444b7f 0x563c6843b000
/usr/bin/ephoto  0x563c684448dc 0x563c6843b000
/lib/x86_64-linux-gnu/libc.so.6  0x7f5ce641e09b 0x7f5ce63fa000
/usr/bin/ephoto  0x563c6844491a 0x563c6843b000
EOF

ERR<26189>:eo lib/eo/eo.c:993 _efl_add_internal_end() Object of class
'Efl.Ui.Win_Legacy' - Not all of the object constructors have been executed.
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71dcc0c 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71dd901 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71decd3 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d0f9bc 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8742b 0x7f5ce690
/usr/bin/ephoto  0x563c68457604 0x563c6843b000
/usr/bin/ephoto  0x563c68444b7f 0x563c6843b000
/usr/bin/ephoto  0x563c684448dc 0x563c6843b000
/lib/x86_64-linux-gnu/libc.so.6  0x7f5ce641e09b 0x7f5ce63fa000
/usr/bin/ephoto  0x563c6844491a 0x563c6843b000
EOF

ERR<26189>:evas_main lib/evas/canvas/evas_object_smart.c:718
_efl_canvas_group_efl_object_destructor() efl_canvas_group_del() was not called
on this object: 0x40007457 (Efl.Ui.Win_Legacy)
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71dcc0c 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71dd901 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f5ce71decd3 0x7f5ce71b3000
/usr/lib/x86_64-linux-gnu/libevas.so.1   0x7f5ce6f9c2c8 0x7f5ce6f02000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b7025c 0x7f5ce690
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6be29a4 0x7f5ce690
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b82d9b 0x7f5ce690
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d126c7 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libeo.so.1 0x7f5ce6d0fcec 0x7f5ce6d01000
/usr/lib/x86_64-linux-gnu/libelementary.so.1 0x7f5ce6b8742b 0x7f5ce690
/usr/bin/ephoto  0x563c68457604 0x563c6843b000
/usr/bin/ephoto  0x563c68444b7f 0x563c6843b000
/usr/bin/ephoto  0x563c684448dc 0x563c6843b000
/lib/x86_64-linux-gnu/libc.so.6  0x7f5ce641e09b 0x7f5ce63fa000
/usr/bin/ephoto  0x563c6844491a 0x563c6843b000
EOF

1 rmm@RMMbook ~ % ERR<26198>:efreet_desktop lib/efreet/efreet_desktop.c:986
efreet_desktop_generic_fields_parse() no Name or _Name fields in file
'/home/rmm/.local/share/applications/_home_rmm_local_eclipse_jee-2018-12_eclipse_.desktop'
## Copy & Paste the below (until EOF) into a terminal, then hit Enter

eina_btlog << EOF
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1dabe73c0c 0x7f1dabe4a000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1dabe74901 0x7f1dabe4a000
/usr/lib/x86_64-linux-gnu/libeina.so.1   0x7f1dabe75cd3 0x7f1dabe4a000
/usr/lib/x86_64-linux-gnu/libefreet.so.1 0x7f1dabe0f1ab 0x7f1dabe01000
/usr/lib/x86_64-linux-gnu/efreet/v-1.21/efreet_desktop_cache_create
0x55c6a298ee5f 0x55c6a298b000
/usr/lib/x86_64-linux-gnu/efreet/v-1.21/efreet_desktop_cache_create
0x55c6a298dba0 0x55c6a298b000
/lib/x86_64-linux-gnu/libc.so.6  0x7f1dabc6209b 0x7f1dabc3e000
/usr/lib/x86_64-linux-gnu/efreet/v-1.21/efreet_desktop_cache_create
0x55c6a298e95a 0x55c6a298b000
EOF




-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (900, 'stable'), (600, 'unstable')
Architecture: amd64 

Bug#928680: [openfortivpn] Since switching to buster openfortivpn can't connect to vpn anymore

2019-05-09 Thread Michael Meier
ok. I will upgrade my system, but it could take a bit. I'm on an island 
right now with internet connections of about 10kB/s...


meanwhile I managed to convince openfortivpn that the tunnel is working.

While it was waiting for ppp0 to become up, I configured ppp0 manually 
by executing:


ip addr add 192.168.0.231/24 peer 192.0.2.1/32 dev ppp0
ip link set up ppp0

openfortivpn afterwards set the routes correctly. And as least as far as 
I can see, then ppp0 and the routes are
configured exactly the same, as on the machine where it is working. But 
unfortunately no data goes through the tunnel.


But I'll try with an update (my last system update was about one week ago).

Log would look like that:

INFO:   Connected to gateway.
INFO:   Authenticated.
INFO:   Remote gateway has allocated a VPN.
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
< at that moment I configured ppp0 manually >
INFO:   Interface ppp0 is UP.
INFO:   Setting new routes...
INFO:   Tunnel is up and running.


On 08.05.19 22:05, Daniel Echeverry wrote:

tags 928680 + moreinfo unreproducible
severity 928680 normal
thanks

Hi!

El mié., 8 de may. de 2019 a la(s) 14:15, Michael Meier (c...@rmm.li 
<mailto:c...@rmm.li>) escribió:


Package: openfortivpn
Version: 1.8.1-1
Severity: normal

I've installed the fortivpn package in debian stable (stretch), and
managed to get it working with a vpn connection.
Somewhen I updated my System to buster and now realized that
openfortivpn can't connect to the vpn anymore. While another computer
which is still running on stretch connects to the same vpn without
any
problems with exactly the same config parameters. Also
openfortivpn and
ppp are the same version on both systems.
As it seems it doesn't manage to configure the ppp interface
correctly.
Maybe in buster something changed the way interfaces are
configured? No
idea.

Thanks for your report!! Unfortunately, I can't reproduce this bug, I 
tried openfortivpn package in 2 differents machines with buster and 
works fine, Could you upgrade your system? I think that you dont have 
the last versions of dependencies.


Regards

--
Daniel Echeverry
Debian Developer
https://wiki.debian.org/DanielEcheverry
Linux user: #477840
GPG Fingerprint:
D0D0 85B1 69C3 BFD9 4048 58FA 21FC 2950 4B52 30DB


Bug#928680: [openfortivpn] Since switching to buster openfortivpn can't connect to vpn anymore

2019-05-08 Thread Michael Meier

Package: openfortivpn
Version: 1.8.1-1
Severity: normal

I've installed the fortivpn package in debian stable (stretch), and 
managed to get it working with a vpn connection.
Somewhen I updated my System to buster and now realized that 
openfortivpn can't connect to the vpn anymore. While another computer 
which is still running on stretch connects to the same vpn without any 
problems with exactly the same config parameters. Also openfortivpn and 
ppp are the same version on both systems.

As it seems it doesn't manage to configure the ppp interface correctly.
Maybe in buster something changed the way interfaces are configured? No 
idea.


Here is the openfortivpn logfile (i've deleted the repetition of certain 
messages and removed privacy related information) further down is the 
ppp log:


DEBUG:  openfortivpn 1.8.1
DEBUG:  Loaded config file "/etc/openfortivpn/config". 



DEBUG:  Resolving gateway host ip 



DEBUG:  Establishing ssl connection 



DEBUG:  server_addr: 



DEBUG:  server_port: 10443 



DEBUG:  gateway_addr:
DEBUG:  gateway_port: 10443 



DEBUG:  Gateway certificate validation failed. 



DEBUG:  Gateway certificate digest found in white list. 



INFO:   Connected to gateway.
DEBUG:  Cookie: SVPNCOOKIE=...== 




INFO:   Authenticated.
DEBUG:  Cookie: SVPNCOOKIE=...== 




INFO:   Remote gateway has allocated a VPN.
DEBUG:  server_addr: ...
DEBUG:  server_port: 10443 



DEBUG:  gateway_addr: ...
DEBUG:  gateway_port: 10443 



DEBUG:  Gateway certificate validation failed. 



DEBUG:  Gateway certificate digest found in white list. 



DEBUG:  Retrieving configuration 



DEBUG:  Establishing the tunnel 



DEBUG:  ppp_path: /usr/sbin/pppd 



DEBUG:  Switch to tunneling mode 



DEBUG:  Starting IO through the tunnel 



DEBUG:  pppd_read thread 



DEBUG:  ssl_read thread 



DEBUG:  ssl_write thread 



DEBUG:  if_config thread 



DEBUG:  pppd_write thread 



DEBUG:  pppd ---> gateway (16 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (16 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  pppd ---> gateway (10 bytes) 



DEBUG:  pppd ---> gateway (17 bytes) 



DEBUG:  pppd ---> gateway (18 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (10 bytes) 



DEBUG:  gateway ---> pppd (25 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
DEBUG:  Got Address: 192.168.0.231
DEBUG:  if_config: not ready yet... 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  gateway ---> pppd (12 bytes) 



DEBUG:  gateway ---> pppd (12 bytes) 



INFO:   Got addresses: [192.168.0.231], ns [0.0.0.0, 0.0.0.0]
INFO:   negotiation complete
DEBUG:  pppd ---> gateway (12 bytes)
DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: not ready yet... 



DEBUG:  pppd ---> gateway (12 bytes) 



DEBUG:  Got Address: 192.168.0.231 



DEBUG:  if_config: 

Bug#925311: [pulseaudio] pulseaudio does not switch automatically to headset microphone when plugged in

2019-03-22 Thread Michael Meier

Package: pulseaudio
Version: 12.2-4
Severity: normal

I've got a laptop  (Dell XPS 13) according to lspci the audio chip is:
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
using following module: snd_hda_intel

My problem since quite some time is that if I plug in a headset into the 
audio jack, pulseaudio correctly changes the output device to "Headphone 
(plugged in)", but the input device stays "Internal Microphone", I have 
to set it manually to "Headset Microphone", what I usually forget until 
somebody complains about the speech quality of my "phone".
I've just switched to buster in the hope the problem would be solved 
here. but it isn't.

When I use a usb headset, pulseaudio changes correctly.


--- System information. ---
Architecture: Kernel:   Linux 4.19.0-2-amd64

Debian Release: buster/sid
  500 zesty   ppa.launchpad.net   500 testing 
ftp.us.debian.org   500 stretch-pgdgapt.postgresql.org   500 stretch 
packagecloud.io   500 stable  repo.skype.com   500 
stable  linux.teamviewer.com

--- Package information. ---
Depends  (Version) | Installed
==-+-===
libasound2  (>= 1.1.0) | 1.1.8-1
libc6(>= 2.27) | 2.28-8
libcap2(>= 1:2.10) | 1:2.25-2
libdbus-1-3(>= 1.9.14) | 1.12.12-1
libgcc1 (>= 1:3.0) | 1:8.3.0-2
libice6   (>= 1:1.0.0) | 2:1.0.9-2
libltdl7(>= 2.4.6) | 2.4.6-9
liborc-0.4-0 (>= 1:0.4.25) | 1:0.4.28-3.1
libpulse0   (= 12.2-4) | 12.2-4
libsm6 | 2:1.2.3-1
libsndfile1(>= 1.0.20) | 1.0.28-6
libsoxr0(>= 0.1.0) | 0.1.2-3
libspeexdsp1(>= 1.2~beta3.2-1) | 1.2~rc1.2-1+b2
libstdc++6  (>= 4.1.1) | 8.3.0-2
libsystemd0| 241-1
libtdb1 (>= 1.2.7+git20101214) | 1.3.16-2+b1
libudev1  (>= 183) | 241-1
libwebrtc-audio-processing1| 0.3-1
libx11-6   | 2:1.6.7-1
libx11-xcb1| 2:1.6.7-1
libxcb1| 1.13.1-2
libxtst6   | 2:1.2.3-1
adduser| 3.118
lsb-base   (>= 3.2-13) | 10.2019031300
libasound2-plugins | 1.1.8-1
pulseaudio-utils   | 12.2-4


Recommends (Version) | Installed
-+-===
rtkit| 0.11-6
libpam-systemd   | 241-1
dbus-user-session|

Suggests (Version) | Installed
==-+-===
udev   | 241-1
pavumeter  | pavucontrol| paman 
| paprefs|



--- Output from package bug script ---
File '/etc/default/pulseaudio' does not exist

-- BEGIN ATTACHMENTS --
/etc/pulse/client.conf
-- END ATTACHMENTS --
-- BEGIN ATTACHMENTS --
/etc/pulse/daemon.conf
-- END ATTACHMENTS --
-- BEGIN ATTACHMENTS --
/etc/pulse/default.pa
-- END ATTACHMENTS --
-- BEGIN ATTACHMENTS --
/etc/pulse/system.pa
-- END ATTACHMENTS --
-- BEGIN ATTACHMENTS --
/tmp/bug-pulseaudio-aplay_-L.CPPzAo
-- END ATTACHMENTS --
-- BEGIN ATTACHMENTS --
/tmp/bug-pulseaudio-pactl_list.RV7NDi
-- END ATTACHMENTS --
-- BEGIN ATTACHMENTS --
/tmp/bug-pulseaudio-pactl_info.8recdJ
-- END ATTACHMENTS --



Bug#923326: Acknowledgement (RFP: trava-jdk-11-dcevm -- Alternative VM for OpenJDK 11 with enhanced class redefinition)

2019-02-26 Thread Michael Meier
Wow that was fast. I've just updated my apt sources and the package just 
came in. Brand new.


You can close that here.



Bug#923326: RFP: trava-jdk-11-dcevm -- Alternative VM for OpenJDK 11 with enhanced class redefinition

2019-02-26 Thread Michael Meier

Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-de...@lists.debian.org

Would be the replacement for the outdated openjdk-8-jre-dcevm package 
which is in debian stretch.
For Java Developpers having the updated package would make live a lot 
easier :-).


--- Please fill out the fields below. ---

   Package name: trava-jdk-11-dcevm

Version: 11
URL: https://github.com/TravaOpenJDK/trava-jdk-11-dcevm
License: apache



Bug#909313: [xul-ext-sogo-connector] Not compatible with thunderbird 60 (New version exists)

2018-09-27 Thread Michael Meier

On 27.09.18 13:56, Carsten Schoenert wrote:

Am 21.09.18 um 17:36 schrieb Michael Meier:

Before doing all this we need to be sure that the new version of
sogo-connector is really working with TB >= 60.x.


I've just tested out the nightly build, and it seems to be working. I've
created some events, tried to sync them in both ways, delete them.

So at least basic functionality seems to be working. The rest time will
show...

The new version is not compatibly to thunderbird version <60.

I did some testing for the released version 31.0.6 and I don't get this
version installed into my local profile nor if I've build this version
as a deb package.

What did you mean by 'nightly build'? I don't see any new commit after
the tagged version 31.0.6 on GitHub.

https://github.com/inverse-inc/sogo-connector.tb31


The commits are here:

https://github.com/inverse-inc/sogo-connector

Nightly Build:

http://packages.inverse.ca/SOGo/thunderbird/nightly/



Bug#909313: [xul-ext-sogo-connector] Not compatible with thunderbird 60 (New version exists)

2018-09-21 Thread Michael Meier

ups, I didn't reply to the list...

On 9/21/18 9:21 AM, Carsten Schoenert


Hello Michael,

Am 21.09.18 um 15:29 schrieb Michael Meier:

The version 31.0.5-2 is not compatible with thunderbird 60.
But it seems there exists already a new sogo-connector version which is
compatible. Please update.

have you tested this?

Updating to 31.0.6 is not that easy as simply importing the updated 
version.

First we need to be able to build every thing from source due the DFSG
and secondly the packaging need to be moved over to the packaging format
of webextension packages.

Before doing all this we need to be sure that the new version of
sogo-connector is really working with TB >= 60.x.

I've just tested out the nightly build, and it seems to be working. I've 
created some events, tried to sync them in both ways, delete them.


So at least basic functionality seems to be working. The rest time will 
show...


The new version is not compatibly to thunderbird version <60.



Bug#909313: [xul-ext-sogo-connector] Not compatible with thunderbird 60 (New version exists)

2018-09-21 Thread Michael Meier

Package: xul-ext-sogo-connector
Version: 31.0.5-2
Severity: important

--- Please enter the report below this line. ---

The version 31.0.5-2 is not compatible with thunderbird 60.
But it seems there exists already a new sogo-connector version which is 
compatible. Please update.



--- System information. ---
Architecture: Kernel:   Linux 4.18.0-1-amd64

Debian Release: 9.5
  900 stretch packagecloud.io   900 stable 
security.debian.org   900 stable  ftp.ch.debian.org   800 
stretch-backports ftp.ch.debian.org   700 testing 
ftp.ch.debian.org   600 unstableftp.ch.debian.org   500 zesty 
   ppa.launchpad.net   500 stretch-pgdgapt.postgresql.org   500 
stable-updates  ftp.ch.debian.org   500 stable  repo.skype.com 
500 stable  linux.teamviewer.com   500 stable 
download.jitsi.org   500 preview linux.teamviewer.com

--- Package information. ---
Depends  (Version) | Installed
==-+-===
lightning  | 1:52.9.1-1
thunderbird (>= 31.0)  | 1:52.9.1-1
 OR icedove  (>= 31.0) |

Package's Recommends field is empty.

Package's Suggests field is empty.



Bug#888577: [tlp] tlp makes bluetooth disfunctional

2018-01-27 Thread Michael Meier

Package: tlp
Version: 1.0-1~bpo9+1
Severity: important

After install TLP i can not use bluetooth anymore (when trying to 
activate it from the kde system tray).
The interesting thing is, if I install TLP, when bluetooth is activated 
and shutdown the computer, it seems to save the state of bluetooth on 
startup and activates it, and it works perfectly, even 
disabling/enabling the adapter.
The problem only seems to appear, if the adapter isn't activated by TLP 
on boot.


syslog tells me:

Jan 27 12:30:56 RMMbook kernel: [   41.988563] Bluetooth: hci0 urb 
971614031600 failed to resubmit (113)

Jan 27 12:31:04 RMMbook bluetoothd[709]: Failed to set mode: Failed (0x03)
Jan 27 12:31:06 RMMbook kernel: [   51.792216] Bluetooth: hci0 urb 
9716797e53c0 failed to resubmit (113)

Jan 27 12:31:14 RMMbook bluetoothd[709]: Failed to set mode: Failed (0x03)
Jan 27 12:31:16 RMMbook kernel: [   62.028298] Bluetooth: hci0 urb 
97163e790900 failed to resubmit (113)

Jan 27 12:31:24 RMMbook bluetoothd[709]: Failed to set mode: Failed (0x03)

The same error exists indepentendly of if t he package tlp-rdw is 
installed or not.


kernel version is:
4.14.0-2-amd64

laptop model is:
dell xps 13 9360, intel 8th gen

hwinfo about bluetooth tells:

  [Created at usb.122]
  Unique ID: 2UT6.UCUpDou4XhB
  Parent ID: k4bc.2DFUsyrieMD
  SysFS ID: /devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0
  SysFS BusID: 1-3:1.0
  Hardware Class: bluetooth
  Model: "Qualcomm Atheros Bluetooth Device"
  Hotplug: USB
  Vendor: usb 0x0cf3 "Qualcomm Atheros Communications"
  Device: usb 0xe300
  Revision: "0.01"
  Driver: "btusb"
  Driver Modules: "btusb"
  Speed: 12 Mbps
  Module Alias: "usb:v0CF3pE300d0001dcE0dsc01dp01icE0isc01ip01in00"
  Driver Info #0:
Driver Status: btusb is active
Driver Activation Cmd: "modprobe btusb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #43 (Hub)

I can't find any setting in /etc/default/tlp to deactivate bluetooth 
support...



--- System information. ---
Architecture: Kernel:   Linux 4.14.0-2-amd64

Debian Release: 9.3
  900 stretch packagecloud.io   900 stable 
security.debian.org   900 stable  ftp.ch.debian.org   800 
stretch-backports ftp.ch.debian.org   700 testing 
ftp.ch.debian.org   600 unstableftp.ch.debian.org   500 zesty 
   ppa.launchpad.net   500 stable-updates  ftp.ch.debian.org   500 
stable  repo.skype.com

--- Package information. ---
Depends  (Version) | Installed
==-+-===
init-system-helpers (>= 1.18~) | 1.48
lsb-base   | 9.20161125
hdparm | 9.51+ds-1
iw | 4.9-0.1
 OR wireless-tools | 30~pre9-12+b1
pciutils   | 1:3.5.2-1
rfkill | 0.5-1+b1
usbutils   | 1:007-4+b1


Recommends  (Version) | Installed
=-+-===
tlp-rdw   | ethtool   | 1:4.8-1+b1
smartmontools | 6.5+svn4324-1
linux-cpupower|

Suggests(Version) | Installed
=-+-===
tp-smapi-dkms | acpi-call-dkms|



Bug#839662: [firmware-atheros] ath10k_pci firmware crashes when ap changes bandwith

2018-01-05 Thread Michael Meier

Package: firmware-atheros
Version: 20170823-1~bpo9+1

--- Please enter the report below this line. ---

The same problem here with firmware-atheros version 20170823-1~bpo9+1 
and kernel 4.14.0-2-amd64.

It's a dell xps 13 8th gen, with a:
3a:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)


When that happens I need to deactivate and reactive the wlan, and it 
works again...


[  326.283775] wlan0: AP c0:25:06:b7:87:d9 changed bandwidth, new config 
is 2412 MHz, width 2 (2422/0 MHz)

[  326.338516] ath10k_pci :3a:00.0: firmware crashed! (guid n/a)
[  326.338539] ath10k_pci :3a:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:1535
[  326.338545] ath10k_pci :3a:00.0: kconfig debug 0 debugfs 0 
tracing 0 dfs 0 testmode 0
[  326.339963] ath10k_pci :3a:00.0: firmware ver 
WLAN.RM.4.4-00022-QCARMSWPZ-2 api 6 features wowlan,ignore-otp crc32 
4d458559
[  326.340970] ath10k_pci :3a:00.0: board_file api 2 bmi_id N/A 
crc32 07ee144e
[  326.340980] ath10k_pci :3a:00.0: htt-ver 3.32 wmi-op 4 htt-op 3 
cal otp max-sta 32 raw 0 hwcrypto 1

[  326.342993] ath10k_pci :3a:00.0: firmware register dump:
[  326.343003] ath10k_pci :3a:00.0: [00]: 0x0503 0x15B3 
0x009873D4 0x00955B31


[  326.343010] ath10k_pci :3a:00.0: [04]: 0x009873D4 0x00060730 
0x0004 0x0041FF88


[  326.343016] ath10k_pci :3a:00.0: [08]: 0x004089E0 0x00955A00 
0x000A0B00 0x0040
[  326.343021] ath10k_pci :3a:00.0: [12]: 0x0009 0x 
0x00952CD0 0x00952CE6
[  326.343027] ath10k_pci :3a:00.0: [16]: 0x00952CC4 0x00998131 
0x 0x0091080D
[  326.343032] ath10k_pci :3a:00.0: [20]: 0x409873D4 0x0040E7A8 
0x 0x0041EA7C
[  326.343037] ath10k_pci :3a:00.0: [24]: 0x809AB233 0x0040E808 
0x0040E8C0 0xC09873D4
[  326.343042] ath10k_pci :3a:00.0: [28]: 0x809A5AF4 0x0040E948 
0x0041FA80 0x0043418C
[  326.343047] ath10k_pci :3a:00.0: [32]: 0x809A526B 0x0040E988 
0x0040E9AC 0x0042CD84
[  326.343056] ath10k_pci :3a:00.0: [36]: 0x8091D252 0x0040E9A8 
0x0002 0x0001
[  326.343061] ath10k_pci :3a:00.0: [40]: 0x809FA4D1 0x0040EA58 
0x0043D11C 0x0042D130
[  326.343066] ath10k_pci :3a:00.0: [44]: 0x809F5BAB 0x0040EA78 
0x0043D11C 0x0001
[  326.343072] ath10k_pci :3a:00.0: [48]: 0x80911210 0x0040EAC8 
0x0010 0x004041D0
[  326.343077] ath10k_pci :3a:00.0: [52]: 0x80911154 0x0040EB28 
0x0040 0x
[  326.343082] ath10k_pci :3a:00.0: [56]: 0x8091122D 0x0040EB48 
0x 0x00400600

[  326.343087] ath10k_pci :3a:00.0: Copy Engine register dump:
[  326.343100] ath10k_pci :3a:00.0: [00]: 0x00034400   0   0   3   3
[  326.343113] ath10k_pci :3a:00.0: [01]: 0x00034800   8   8 117 118
[  326.343126] ath10k_pci :3a:00.0: [02]: 0x00034c00  25  25  24  25
[  326.343139] ath10k_pci :3a:00.0: [03]: 0x00035000   1   1   2   1
[  326.343151] ath10k_pci :3a:00.0: [04]: 0x00035400 6573 6573  24 216
[  326.343164] ath10k_pci :3a:00.0: [05]: 0x00035800   0   0  64   0
[  326.343178] ath10k_pci :3a:00.0: [06]: 0x00035c00  11  11  20  20
[  326.343192] ath10k_pci :3a:00.0: [07]: 0x00036000   1   1   1   1
[  326.442208] ieee80211 phy0: Hardware restart was requested
[  327.153570] ath10k_pci :3a:00.0: Unknown eventid: 90118
[  327.258250] ath10k_pci :3a:00.0: device successfully recovered
[  393.690488] wlan0: deauthenticating from c0:25:06:b7:87:d9 by local 
choice (Reason: 3=DEAUTH_LEAVING)

[  396.666205] ath10k_pci :3a:00.0: Unknown eventid: 90118




--- System information. ---
Architecture: Kernel:   Linux 4.14.0-2-amd64

Debian Release: 9.3
  900 stretch packagecloud.io   900 stable security.debian.org 
 900 stable  ftp.ch.debian.org   800 stretch-backports 
ftp.ch.debian.org   700 testing ftp.ch.debian.org   600 unstable 
ftp.ch.debian.org   500 stable-updates  ftp.ch.debian.org

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Suggests (Version) | Installed
==-+-===
initramfs-tools| 0.130



Bug#869911: kdeconnect mounts /home/rmm/.config/[..]/kdeconnect_sftp/4a96caf88189a37d as root

2017-07-27 Thread Michael Meier
Package: kdeconnect
Version: 1.0.3-1
Severity: normal

When I try to access the filesystem on my mobile phone over kdeconnect, it 
seems like only the file manager dolphin is able to access it.
I wanted to use doublecommander but it fails, so I checked out at the console 
what is happening, I've found the mount:
kdeconnect@192.168.10.184:/ on 
/home/rmm/.config/kdeconnect/4a96caf88189a37d/kdeconnect_sftp/4a96caf88189a37d 
type fuse.sshfs (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)

When I try to ls the conntent of 
/home/rmm/.config/kdeconnect/4a96caf88189a37d/kdeconnect_sftp/4a96caf88189a37d 
I get a "no permission", so I checked the owner of that directory, and it is 
root.

d--x-- 1 root root 0 Jan  9  1970 4a96caf88189a37d

But I can't su to try to change the owner or permissions, when I do an ls as 
root I get:
d? ? ? ? ?? 4a96caf88189a37d

Is there any way to change that, so also other file manager could access that 
mount?


-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (900, 'stable'), (850, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 kdeconnect depends on:
ii  kde-cli-tools  4:5.8.4-2
ii  kio5.28.0-2
ii  libc6  2.24-11+deb9u1
ii  libfakekey00.1-9
ii  libkf5configcore5  5.28.0-2
ii  libkf5configwidgets5   5.28.0-2
ii  libkf5coreaddons5  5.28.0-2
ii  libkf5dbusaddons5  5.28.0-1
ii  libkf5i18n55.28.0-2
ii  libkf5iconthemes5  5.28.0-2
ii  libkf5kcmutils55.28.0-2
ii  libkf5kiocore5 5.28.0-2
ii  libkf5kiofilewidgets5  5.28.0-2
ii  libkf5kiowidgets5  5.28.0-2
ii  libkf5notifications5   5.28.0-1
ii  libkf5service-bin  5.28.0-1
ii  libkf5service5 5.28.0-1
ii  libkf5waylandclient5   4:5.28.0-1
ii  libkf5widgetsaddons5   5.28.0-3
ii  libqca-qt5-2   2.1.1-4+b2
ii  libqca-qt5-2-plugins   2.1.1-4+b2
ii  libqt5core5a   5.7.1+dfsg-3+b1
ii  libqt5dbus55.7.1+dfsg-3+b1
ii  libqt5gui5 5.7.1+dfsg-3+b1
ii  libqt5network5 5.7.1+dfsg-3+b1
ii  libqt5qml5 5.7.1-2+b2
ii  libqt5widgets5 5.7.1+dfsg-3+b1
ii  libqt5x11extras5   5.7.1~20161021-2
ii  libstdc++6 6.3.0-18
ii  libx11-6   2:1.6.4-3
ii  libxtst6   2:1.2.3-1
ii  plasma-workspace   4:5.8.6-2.1
ii  sshfs  2.8-1

kdeconnect recommends no packages.

kdeconnect suggests no packages.

-- no debconf information



Bug#857268: plasma-workspace: xembedsniproxy does not work properly with all applications which use the task tray

2017-03-09 Thread Michael Meier
Package: plasma-workspace
Version: 4:5.8.4-1
Severity: normal


I marked this report as serious because of:
- makes unrelated software on the system (or the whole system) break

xembedsniproxy which is used, to make software work with the new task tray of 
the kde plasma desktop, does not really work properly with quite most software 
which I use (and propably a lot more).
A minor issues is, that the background of every icon is black.
A Major issue is that the context menus of several softwares are not working 
anymore. In my case for "taskcoach" and "workrave".
Workrave is practically rendered unusable like that, since I can not enter the 
software anymore, neither left nor right click works.
The package "gajim" shows 2 tray icons, of which one has no icon at all, and is 
only grey (I'm not sure if it should be only one icon).
In gmusicbrowser the popup on mouse over doesn't work anymore.
Anyway those are just the application which I've got open right now, I know I 
found other ones, and I'm sure there are a lot more around.
Eventhough those issues should sooner or later be fixed in those application 
(or the libarries they use) themselves (at least I guess that's what the kde 
team hopes for), for the moment beeing it makes it
a pain using a lot of applications. Besides that xembedsniproxy also likes to 
segfault (I filled an other bug report for that one).
I guess it's not possible, but it would be great if that issue would be fixed 
before the next stable release.
Since I'll get a new computer next month, my personal solution will be, just to 
install an other desktop environment, but I guess that's not a solution for 
everybody.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 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 plasma-workspace depends on:
ii  dbus-x11 1.10.16-1
ii  frameworkintegration 5.28.0-1
ii  gdb-minimal [gdb]7.12-6
ii  iso-codes3.74-1
ii  kactivitymanagerd5.8.4-1
ii  kde-cli-tools4:5.8.4-1
ii  kded55.28.0-1
ii  kinit5.28.0-1
ii  kio  5.28.0-1
ii  kpackagetool55.28.1-1
ii  libc62.24-9
ii  libcln6  1.3.4-2+b1
ii  libdbusmenu-qt5-20.9.3+16.04.20160218-1
ii  libgcc1  1:6.3.0-6
ii  libgps22 3.16-4
ii  libice6  2:1.0.9-2
ii  libkf5activities55.28.0-1
ii  libkf5auth5  5.28.0-1
ii  libkf5baloo5 5.28.0-2
ii  libkf5bookmarks5 5.28.0-1
ii  libkf5calendarevents55.28.0-1
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-1
ii  libkf5configgui5 5.28.0-1
ii  libkf5configwidgets5 5.28.0-1
ii  libkf5coreaddons55.28.0-1
ii  libkf5crash5 5.28.0-1
ii  libkf5dbusaddons55.28.0-1
ii  libkf5declarative5   5.28.0-1
ii  libkf5globalaccel-bin5.28.0-1
ii  libkf5globalaccel5   5.28.0-1
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.28.0-1
ii  libkf5iconthemes55.28.0-1
ii  libkf5idletime5  5.28.0-1
ii  libkf5itemviews5 5.28.0-1
ii  libkf5jobwidgets55.28.0-1
ii  libkf5js55.28.0-1
ii  libkf5jsembed5   5.28.0-1
ii  libkf5kdelibs4support5   5.28.0-1
ii  libkf5kiocore5   5.28.0-1
ii  libkf5kiofilewidgets55.28.0-1
ii  libkf5kiowidgets55.28.0-1
ii  libkf5networkmanagerqt6  5.28.0-1
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5package5   5.28.1-1
ii  libkf5plasma55.28.0-1
ii  libkf5plasmaquick5   5.28.0-1
ii  libkf5quickaddons5   5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin

Bug#857264: plasma-workspace: xembedsniproxy often segfaults

2017-03-09 Thread Michael Meier
Package: plasma-workspace
Version: 4:5.8.4-1
Severity: important

When starting up the computer, often (not always) xembedsniproxy segfaults. 
Also while using the computer it
randomly crashes (I have the feeling that recently it more often crashes on 
start up than during normal operation). Hence several the icons in the task 
tray are missing. With "xembedsniproxy&" i can restart it.
But if you don't know about that command this leads to serious usability 
issues! (some programs aren't accessible without their task tray icon anymore).
When starting up, I get for example that message:
[   49.752174] xembedsniproxy[5458]: segfault at 2 ip 561b56ae2232 sp 
7b32c330 error 4 in xembedsniproxy[561b56ad6000+14000]

That behaviour wasn't introduced with the newest version, but already exists 
since several months (I just always had urgent work to do, when it happened => 
no bug report)
Programs which I've got in the task tray and are using xembedsniproxy are:
workrave
gmusicbrowser (Is not started up automatically, so it shouldn't be able to 
trigger the start up crash)
task coach
tomboy

if there's anything else I can help with, just ask. I have no idea what exactly 
triggers the segfault, since it seems to happen completely randomly.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/4 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 plasma-workspace depends on:
ii  dbus-x11 1.10.16-1
ii  frameworkintegration 5.28.0-1
ii  gdb-minimal [gdb]7.12-6
ii  iso-codes3.74-1
ii  kactivitymanagerd5.8.4-1
ii  kde-cli-tools4:5.8.4-1
ii  kded55.28.0-1
ii  kinit5.28.0-1
ii  kio  5.28.0-1
ii  kpackagetool55.28.1-1
ii  libc62.24-9
ii  libcln6  1.3.4-2+b1
ii  libdbusmenu-qt5-20.9.3+16.04.20160218-1
ii  libgcc1  1:6.3.0-6
ii  libgps22 3.16-4
ii  libice6  2:1.0.9-2
ii  libkf5activities55.28.0-1
ii  libkf5auth5  5.28.0-1
ii  libkf5baloo5 5.28.0-2
ii  libkf5bookmarks5 5.28.0-1
ii  libkf5calendarevents55.28.0-1
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-1
ii  libkf5configgui5 5.28.0-1
ii  libkf5configwidgets5 5.28.0-1
ii  libkf5coreaddons55.28.0-1
ii  libkf5crash5 5.28.0-1
ii  libkf5dbusaddons55.28.0-1
ii  libkf5declarative5   5.28.0-1
ii  libkf5globalaccel-bin5.28.0-1
ii  libkf5globalaccel5   5.28.0-1
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.28.0-1
ii  libkf5iconthemes55.28.0-1
ii  libkf5idletime5  5.28.0-1
ii  libkf5itemviews5 5.28.0-1
ii  libkf5jobwidgets55.28.0-1
ii  libkf5js55.28.0-1
ii  libkf5jsembed5   5.28.0-1
ii  libkf5kdelibs4support5   5.28.0-1
ii  libkf5kiocore5   5.28.0-1
ii  libkf5kiofilewidgets55.28.0-1
ii  libkf5kiowidgets55.28.0-1
ii  libkf5networkmanagerqt6  5.28.0-1
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5package5   5.28.1-1
ii  libkf5plasma55.28.0-1
ii  libkf5plasmaquick5   5.28.0-1
ii  libkf5quickaddons5   5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5solid5 5.28.0-2
ii  libkf5texteditor55.28.0-1
ii  libkf5textwidgets5   5.28.0-1
ii  libkf5wallet-bin 5.28.0-3
ii  libkf5wallet55.28.0-3
ii  libkf5waylandclient5 4:5.28.0-1
ii  

Bug#856025: [pgadmin3] Please pack pg admin 4

2017-02-24 Thread Michael Meier
Package: pgadmin3
Version: 1.22.2-1
Severity: wishlist

pg admin 4 is out since a while and pg admin 3 is not supported anymore.
It would be great if you could pack the new version.

--- System information. ---
Architecture: Kernel:   Linux 4.9.0-1-amd64

Debian Release: 9.0
  900 testing pkg.adfinis-sygroup.ch   800 unstable
pkg.adfinis-sygroup.ch   500 xenial  ppa.launchpad.net   500
vivid   ppa.launchpad.net   400 testing
www.deb-multimedia.org
--- Package information. ---
Depends(Version) | Installed
-+-
pgadmin3-data   (= 1.22.2-1) | 1.22.2-1
libc6  (>= 2.15) | libgcc1   (>=
1:3.0) | libpq5 (>= 8.4~) | libssl1.0.2
(>= 1.0.2d) | libstdc++6  (>= 5.2) | libwxbase3.0-0v5
 (>= 3.0.2+dfsg) | libwxgtk3.0-0v5  (>= 3.0.2+dfsg) | libxml2
   (>= 2.7.4) | libxslt1.1   (>= 1.1.25) | zlib1g
  (>= 1:1.1.4) |

Recommends (Version) | Installed
-+-===
pgagent  | 3.4.1-4
postgresql-client| 9.6+179


Suggests(Version) | Installed
=-+-===
postgresql-contrib|



Bug#833135: profile-sync-daemon fails to work properly after system crash

2016-08-01 Thread Michael Meier
Package: profile-sync-daemon
Version: 6.25-1
Severity: important

After a system crash (or blackout), profile-sync-daemon doesn't work properly 
anymore, when using the overlay filesystem.
It does not sync any changes back anymore, maynly because of following message:

Aug  1 11:20:57 RMMbook profile-sync-daemon[5565]: ln: failed to create 
symbolic link '/home/rmm/.mozilla/firefox/rk7hh7a0.default/null': File exists
Aug  1 11:20:57 RMMbook profile-sync-daemon[5565]: mv: cannot overwrite 
directory '/home/rmm/.mozilla/firefox/rk7hh7a0.default-backup' with 
non-directory
Aug  1 11:21:04 RMMbook profile-sync-daemon[5565]: #033[01mfirefox resync 
successful#033[00m
Aug  1 11:21:04 RMMbook profile-sync-daemon[5565]: #033[01mfirefox unsync 
successful#033[00m

It says it is successfull, but in reality it didn't sync changes back, also the 
mounts still exist even after ending the daemon.
After deleting that null file, things seem to work again. I'm not sure what 
that "non-directory" message has to do with everything.

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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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 profile-sync-daemon depends on:
pn  rsync  

profile-sync-daemon recommends no packages.

Versions of packages profile-sync-daemon suggests:
ii  libpam-systemd  230-7
ii  systemd-sysv230-7

-- no debconf information



Bug#832760: krdc: "grab keys" function does not work

2016-07-28 Thread Michael Meier
Package: krdc
Version: 4:16.04.2-1
Severity: important

The grab key function does not seem to work. When pressing key combinations 
like ctrl-alt-delete, ctrl-escape, they are catched by my desktop.
Worse, even alt-f4 is catched by it, and closes KRDC even when running in full 
screen mode.
So it's basically impossible to control a remote desktop by keyboard.


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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 krdc depends on:
ii  libc6 2.23-2
ii  libkf5bookmarks5  5.23.0-1
ii  libkf5completion5 5.23.0-1
ii  libkf5configcore5 5.23.0-1
ii  libkf5configgui5  5.23.0-1
ii  libkf5configwidgets5  5.23.0-1
ii  libkf5coreaddons5 5.23.0-1
ii  libkf5dnssd5  5.23.0-1
ii  libkf5i18n5   5.23.0-1
ii  libkf5kcmutils5   5.23.0-1
ii  libkf5notifications5  5.23.0-1
ii  libkf5notifyconfig5   5.23.0-1
ii  libkf5service-bin 5.23.0-1
ii  libkf5service55.23.0-1
ii  libkf5wallet-bin  5.23.0-3
ii  libkf5wallet5 5.23.0-3
ii  libkf5widgetsaddons5  5.23.0-1
ii  libkf5xmlgui5 5.23.0-1
ii  libqt5core5a  5.6.1+dfsg-3
ii  libqt5gui55.6.1+dfsg-3
ii  libqt5widgets55.6.1+dfsg-3
ii  libqt5xml55.6.1+dfsg-3
ii  libstdc++66.1.1-9
ii  libvncclient1 0.9.10+dfsg-3+b1

Versions of packages krdc recommends:
ii  freerdp-x11  1.1.0~git20140921.1.440916e+dfsg1-10

Versions of packages krdc suggests:
ii  khelpcenter  4:16.04.2-2
pn  krfb 

-- no debconf information



Bug#832601: pulseaudio does recognize usb audio device only after restart

2016-07-27 Thread Michael Meier
Package: pulseaudio
Version: 9.0-1.1
Severity: normal

When I connect a usb audio device, pulseaudio does not notice that I connected 
it. I need to restart pulseaudio first, with "pulseaudio -k".
Then it works without problems. But after pluging it out and in again, it is 
necesary to restart pulseaudio again.

here dmesg, if it helps...
[11538.301243] usb 1-2: USB disconnect, device number 7
[11549.71] usb 1-2: new full-speed USB device number 8 using xhci_hcd
[11549.464521] usb 1-2: New USB device found, idVendor=24ae, idProduct=6000
[11549.464525] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[11549.464526] usb 1-2: Product: Rapoo Wireless Audio
[11549.464528] usb 1-2: Manufacturer: Rapoo
[11549.469950] input: Rapoo Rapoo Wireless Audio as 
/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.3/0003:24AE:6000.0009/input/input19
[11549.526033] hid-generic 0003:24AE:6000.0009: input,hidraw3: USB HID v1.00 
Device [Rapoo Rapoo Wireless Audio] on usb-:00:14.0-2/input3




-- Package-specific info:
File '/etc/default/pulseaudio' does not exist


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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 pulseaudio depends on:
ii  adduser  3.115
ii  libasound2   1.1.1-2
ii  libasound2-plugins   1.1.1-1
ii  libc62.23-2
ii  libcap2  1:2.25-1
ii  libdbus-1-3  1.10.8-1
ii  libfftw3-single3 3.3.4-2+b1
ii  libgcc1  1:6.1.1-9
ii  libice6  2:1.0.9-1+b1
ii  libltdl7 2.4.6-0.1
ii  liborc-0.4-0 1:0.4.25-1
ii  libpulse09.0-1.1
ii  libsm6   2:1.2.2-1+b1
ii  libsndfile1  1.0.25-10
ii  libsoxr0 0.1.2-1
ii  libspeexdsp1 1.2~rc1.2-1
ii  libstdc++6   6.1.1-9
ii  libsystemd0  230-7
ii  libtdb1  1.3.9-1
ii  libudev1 230-7
ii  libwebrtc-audio-processing1  0.3-1
ii  libx11-6 2:1.6.3-1
ii  libx11-xcb1  2:1.6.3-1
ii  libxcb1  1.11.1-1
ii  libxtst6 2:1.2.2-1+b1
ii  lsb-base 9.20160629
ii  pulseaudio-utils 9.0-1.1

Versions of packages pulseaudio recommends:
pn  pulseaudio-module-udev  
pn  pulseaudio-module-x11   
ii  rtkit   0.11-4

Versions of packages pulseaudio suggests:
ii  paman0.9.4-1+b2
pn  paprefs  
ii  pavucontrol  3.0-3+b2
pn  pavumeter

-- no debconf information
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for PulseAudio clients. See pulse-client.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; default-sink =
; default-source =
; default-server =
; default-dbus-server =

; autospawn = yes
; daemon-binary = /usr/bin/pulseaudio
; extra-arguments = --log-target=syslog

; cookie-file =

; enable-shm = yes
; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB

; auto-connect-localhost = no
; auto-connect-display = no
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .

## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
## more information. Default values are commented out.  Use either ; or # for
## commenting.

; daemonize = 

Bug#827780: beets should recommend or suggest libchromaprint-tools python3-acoustid

2016-06-20 Thread Michael Meier
Package: beets
Version: 1.3.8+dfsg-2
Severity: normal

The chromaprint/accousticId seems to need the packages libchromaprint-tools 
python3-acoustid .
would be nice to have tem as recommended or suggestes packages.


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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 beets depends on:
ii  libjs-backbone 0.9.10-3
ii  libjs-jquery   1.12.3-1
ii  libjs-underscore   1.7.0~dfsg-1
ii  python-enum34  1.1.5-1
ii  python-munkres 1.0.7-1
ii  python-musicbrainzngs  0.5-2
ii  python-mutagen 1.32-1
ii  python-pkg-resources   20.10.1-1
ii  python-unidecode   0.04.19-1
ii  python-yaml3.11-3+b1
pn  python:any 

beets recommends no packages.

Versions of packages beets suggests:
pn  beets-doc 
ii  gir1.2-gstreamer-1.0  1.8.2-1
ii  libav-tools   7:3.0.2-4
pn  mp3gain   
ii  python-acoustid   1.1.0-3
pn  python-bs4
pn  python-flask  
ii  python-gi 3.20.1-1
ii  python-gst0.100.10.22-3
ii  python-imaging3.2.0-2
pn  python-mpd
pn  python-pylast 
ii  python-requests   2.10.0-1

-- no debconf information



Bug#827183: gwenview: kipi-plugins do not work with gwenview anymore

2016-06-13 Thread Michael Meier
Package: gwenview
Version: 4:16.04.1-1
Severity: normal

Since the whole mess with the update to plasma 5 the kipi plugins, which should 
appear in the "extra" menu in gwenview, are not loaded anymore.
I tried out to install the newer libkf5kipi31.0.0 (you have to deinstall 
digikam thatfor) but they don't appear. they also don't appear when libkipi11 
is installed.


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

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 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 gwenview depends on:
ii  libc6   2.22-11
ii  libexiv2-14 0.25-3
ii  libgcc1 1:6.1.1-4
ii  libjpeg62-turbo 1:1.4.2-2
ii  libkf5activities5   5.22.0-2
ii  libkf5baloo55.22.0-2
ii  libkf5completion5   5.22.0-1
ii  libkf5configcore5   5.22.0-1
ii  libkf5configgui55.22.0-1
ii  libkf5configwidgets55.22.0-1
ii  libkf5coreaddons5   5.22.0-1
ii  libkf5filemetadata3 5.22.0-1
ii  libkf5i18n5 5.22.1-1
ii  libkf5iconthemes5   5.22.0-1
ii  libkf5itemmodels5   5.22.0-1
ii  libkf5itemviews55.22.0-1
ii  libkf5jobwidgets5   5.22.0-1
ii  libkf5kdelibs4support5  5.22.0-2
ii  libkf5kiocore5  5.22.0-1
ii  libkf5kiofilewidgets5   5.22.0-1
ii  libkf5kiowidgets5   5.22.0-1
ii  libkf5notifications55.22.0-1
ii  libkf5parts55.22.0-1
ii  libkf5service-bin   5.22.0-1
ii  libkf5service5  5.22.0-1
ii  libkf5textwidgets5  5.22.0-1
ii  libkf5widgetsaddons55.22.0-1
ii  libkf5xmlgui5   5.22.0-1
ii  liblcms2-2  2.7-1
ii  libphonon4qt5-4 4:4.9.0-2
ii  libpng16-16 1.6.22-1
ii  libqt5core5a5.5.1+dfsg-17
ii  libqt5gui5  5.5.1+dfsg-17
ii  libqt5opengl5   5.5.1+dfsg-17
ii  libqt5printsupport5 5.5.1+dfsg-17
ii  libqt5svg5  5.5.1-2
ii  libqt5widgets5  5.5.1+dfsg-17
ii  libqt5x11extras55.5.1-3
ii  libstdc++6  6.1.1-4
ii  libx11-62:1.6.3-1
ii  phonon4qt5  4:4.9.0-2

Versions of packages gwenview recommends:
ii  kamera 4:16.04.1-1
pn  kio-extras 
pn  qt5-image-formats-plugins  

gwenview suggests no packages.

-- no debconf information



Bug#814683: plasma-nm seems to have no support for network-manager-iodine plugin

2016-02-13 Thread Michael Meier
Package: plasma-nm
Version: 4:5.4.3-1
Severity: normal

I installed the network-manager-iodine plugin, but the plasma-nm does not seem 
to have any support for it.
When I try to add a connection it actually shows me a lot of connection types 
of which the plugin is not even installed, but there seems to be no way to add 
an iodine connection.


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 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 plasma-nm depends on:
ii  libc6   2.21-7
ii  libkf5completion5   5.16.0-1
ii  libkf5configcore5   5.16.0-1
ii  libkf5configwidgets55.16.0-1
ii  libkf5coreaddons5   5.16.0-1
ii  libkf5dbusaddons5   5.16.0-1
ii  libkf5i18n5 5.16.0-1
ii  libkf5iconthemes5   5.16.0-1
ii  libkf5itemviews55.16.0-1
ii  libkf5kdelibs4support5  5.16.0-1
ii  libkf5kiowidgets5   5.16.0-1
ii  libkf5modemmanagerqt6   5.16.0-1
ii  libkf5networkmanagerqt6 5.16.0-1
ii  libkf5notifications55.16.0-1
ii  libkf5service-bin   5.16.0-1
ii  libkf5service5  5.16.0-1
ii  libkf5solid55.16.0-1
ii  libkf5wallet-bin5.16.0-1
ii  libkf5wallet5   5.16.0-1
ii  libkf5widgetsaddons55.16.0-1
ii  libkf5windowsystem5 5.16.0-1
ii  libkf5xmlgui5   5.16.0-1
ii  libopenconnect5 7.06-2+b2
ii  libqt5core5a5.5.1+dfsg-13
ii  libqt5dbus5 5.5.1+dfsg-13
ii  libqt5gui5  5.5.1+dfsg-13
ii  libqt5network5  5.5.1+dfsg-13
ii  libqt5qml5  5.5.1-3
ii  libqt5widgets5  5.5.1+dfsg-13
ii  libqt5xml5  5.5.1+dfsg-13
ii  libstdc++6  5.3.1-8
ii  mobile-broadband-provider-info  20140317-1
ii  network-manager 1.0.10-2+b1
ii  plasma-framework5.16.0-1
ii  qml-module-org-kde-kcoreaddons  5.16.0-1

plasma-nm recommends no packages.

Versions of packages plasma-nm suggests:
pn  network-manager-openconnect  
ii  network-manager-openvpn  1.0.8-1
ii  network-manager-pptp 1.0.8-2
ii  network-manager-vpnc 1.0.8-1

-- no debconf information



Bug#812211: subliminal: provided subliminal version is completely outdated. please pack newer one (currently 1.1.1)

2016-01-21 Thread Michael Meier
Package: subliminal
Version: 0.7.4-1
Severity: wishlist

see subject. Please pack newer version of the package.


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 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 subliminal depends on:
ii  python3 3.4.3-7
ii  python3-subliminal  0.7.4-1

subliminal recommends no packages.

subliminal suggests no packages.

-- no debconf information



Bug#810384: crda: the udev script running /sbin/crda fails when network-manager brings an interface up

2016-01-08 Thread Michael Meier
Package: crda
Version: 3.13-1+b1
Severity: normal

I noticed that my regulatory domain is not set correclty anymore. The last time 
I looked into that - half a year ago - it still worked.
When network-manager tries to bring a wlan interface up, the world regulatory 
domain is set, and in syslog I find following message:
systemd-udevd[16722]: Process '/sbin/crda' failed with exit code 255.

I guess that's from the udev script 85-regulatory.rules which should run crda.
running crda by hand shows me following message:
COUNTRY environment variable not set.

When I set that variable I get the message 
Failed to set regulatory domain: -7

>From there on I don't know how to continue...

Anyway, as temporary solution I added following script to
/etc/NetworkManager/dispatcher.d/pre-up.d
which works for now.

#!/bin/sh

interface=$1 status=$2
if [ "$interface" = "wlan1" ]; then
/lib/crda/setregdomain
sleep 2
iwconfig wlan1 txpower 30
fi

maybe it would be better to call in the udev script also setregdomain, instead 
of crda.


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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 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 crda depends on:
ii  iw3.17-1
ii  libc6 2.21-6
ii  libnl-3-200   3.2.26-1
ii  libnl-genl-3-200  3.2.26-1
ii  libssl1.0.2   1.0.2e-1
ii  wireless-regdb2015.07.20-1

crda recommends no packages.

crda suggests no packages.

-- Configuration Files:
/etc/default/crda changed:
REGDOMAIN=VE


-- no debconf information



Bug#801461: outdated mirrors.*.kernel.org entries in mirrorlist

2015-10-10 Thread Michael Meier
Package: mirrors

mirrors.nl.kernel.org and mirrors.se.kernel.org do not exist anymore -
all names are now just an alias for mirrors.us.kernel.org (which is in
the list as mirrors.kernel.org).
It seems that for "Archive" these nonexistant mirrors have already been
unlisted, but they are still in Mirrors.masterlist as CDImage mirrors.
These should either be removed or at least disabled like the Archive
entries.



Bug#793502: workrave: Workrave doesn't show icon in system tray of kde plasma 5

2015-08-31 Thread Michael Meier

Sorry for the late reply

I guess that's something the upstream developpers would need to fix. it 
seems like the kde developpers decided - in their endless wisdom - to 
drop the support for xembbed systemtrays.
I guess workrave uses gtk and would need to use the appindicator library 
for the systemtray support. (most gtk application seem to already to 
that, installing the appindicator libraries on my system achieved that 
most gtk application had a working system tray icon again, but not 
workrave).

see also
http://blog.martin-graesslin.com/blog/2014/03/system-tray-in-plasma-next/

michael

Am 22.8.2015 16:22, schrieb Francois Marier:

On 2015-07-24 at 12:25:47, Michael Meier wrote:
workrave needs to be updated to show an icon in the new kde plasma 5 
system tray.

as a lot of older applications it can't show them there anymore.


I don't know anything about the KDE Plasma 5 system tray. Is that 
something
packaging-related (e.g. we need to install the existing files in a 
different
directory) or is that something that the upstream developers need to 
fix?


Francois




Bug#796184: libkdecorations2-5: updating libkdecorations2-5 to 4:5.3.2-2 breaks kwin

2015-08-19 Thread Michael Meier
Package: libkdecorations2-5
Version: 4:5.3.2-1
Severity: critical
Justification: breaks unrelated software

I'm using kde plasma 5 from testing with kwin-x11.
After updating libkdecorations2-5 from 4:5.3.2-1 to 4:5.3.2-2 kwin crashes all 
the time. Mostly after entering your credentials it even doesn't manage to 
start up the desktop. After a while a message appears, that kwin crashed 
several times, if you want to change to an other window manager. The kwin 
version installed is 4:5.3.2-3.
The stacktrace is following:

Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
[Current thread is 1 (Thread 0x7f37d2f4d940 (LWP 8047))]

Thread 2 (Thread 0x7f37b9368700 (LWP 8057)):
#0  0x7f37d22e5438 in pthread_cond_timedwait@@GLIBC_2.3.2 () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#1  0x7f37d0e2a918 in QWaitCondition::wait(QMutex*, unsigned long) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x7f37d0e269c4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x7f37d0e2987e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x7f37d22e10a4 in start_thread () from 
/lib/x86_64-linux-gnu/libpthread.so.0
#5  0x7f37d2a5107d in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f37d2f4d940 (LWP 8047)):
[KCrash Handler]
#6  0x7f37b89d9d90 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so
#7  0x7f37d1020da9 in QMetaObject::cast(QObject*) const () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x7f37b87aabb1 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so
#9  0x7f37cf7d4917 in 
KDecoration2::DecorationButtonGroup::DecorationButtonGroup(KDecoration2::DecorationButtonGroup::Position,
 KDecoration2::Decoration*, std::functionKDecoration2::DecorationButton* 
(KDecoration2::DecorationButtonType, KDecoration2::Decoration*, QObject*)) () 
from /usr/lib/x86_64-linux-gnu/libkdecorations2.so.5
#10 0x7f37b87b1ba0 in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so
#11 0x7f37b87b340a in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so
#12 0x7f37d268a0b1 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.5
#13 0x7f37d25730e9 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.5
#14 0x7f37d25734fb in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.5
#15 0x7f37d25be482 in ?? () from /usr/lib/x86_64-linux-gnu/libkwin.so.5
#16 0x7f37d255d61d in KWin::Workspace::createClient(unsigned int, bool) () 
from /usr/lib/x86_64-linux-gnu/libkwin.so.5
#17 0x7f37d2561171 in KWin::Workspace::init() () from 
/usr/lib/x86_64-linux-gnu/libkwin.so.5
#18 0x7f37d2561bcf in KWin::Workspace::Workspace(bool) () from 
/usr/lib/x86_64-linux-gnu/libkwin.so.5
#19 0x7f37d25976ae in KWin::Application::createWorkspace() () from 
/usr/lib/x86_64-linux-gnu/libkwin.so.5
#20 0x7f37d2d17e39 in ?? () from 
/usr/lib/x86_64-linux-gnu/libkdeinit5_kwin_x11.so
#21 0x7f37d1049aba in QMetaObject::activate(QObject*, int, int, void**) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x7f37d1e7802b in KSelectionOwner::Private::claimSucceeded() () from 
/usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5
#23 0x7f37d1e787b1 in KSelectionOwner::filterEvent(void*) () from 
/usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5
#24 0x7f37d1015c90 in 
QAbstractEventDispatcher::filterNativeEvent(QByteArray const, void*, long*) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#25 0x7f37bc738a3d in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#26 0x7f37bc739ecb in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#27 0x7f37d104ae8a in QObject::event(QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#28 0x7f37d1906adc in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#29 0x7f37d190bfb0 in QApplication::notify(QObject*, QEvent*) () from 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#30 0x7f37d10193ab in QCoreApplication::notifyInternal(QObject*, QEvent*) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#31 0x7f37d101b41b in QCoreApplicationPrivate::sendPostedEvents(QObject*, 
int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#32 0x7f37d106f802 in 
QEventDispatcherUNIX::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () 
from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#33 0x7f37bc7906dd in ?? () from 
/usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#34 0x7f37d1016b62 in 
QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#35 0x7f37d101e7ac in QCoreApplication::exec() () from 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#36 0x7f37d2d19320 in kdemain () from 

Bug#794415: tomboy: Tomboy icon does not appear in kde plasma 5 system tray

2015-08-02 Thread Michael Meier
Package: tomboy
Version: 1.15.4-1
Severity: important

Tomboy does not show it's tray icon in the kde plasma5 system tray. Which makes 
it a lot more difficult to use below kde...


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

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 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 tomboy depends on:
ii  gconf2  3.2.6-3
ii  libatk1.0-0 2.16.0-2
ii  libc6   2.19-19
ii  libcairo2   1.14.2-2
ii  libdbus-glib2.0-cil 0.6.0-1
ii  libdbus2.0-cil  0.8.1-1
ii  libfontconfig1  2.11.0-6.3
ii  libfreetype62.5.2-4
ii  libgconf2.0-cil 2.24.2-3
ii  libgdk-pixbuf2.0-0  2.31.5-1
ii  libglib2.0-02.44.1-1.1
ii  libglib2.0-cil  2.12.10-5.1
ii  libgmime2.6-cil 2.6.20-1
ii  libgtk2.0-0 2.24.28-1
ii  libgtk2.0-cil   2.12.10-5.1
ii  libgtkspell02.0.16-1.1
ii  libice6 2:1.0.9-1+b1
ii  libmono-addins-gui0.2-cil   1.0+git20130406.adcd75b-3
ii  libmono-addins0.2-cil   1.0+git20130406.adcd75b-3
ii  libmono-cairo4.0-cil3.2.8+dfsg-10
ii  libmono-corlib4.5-cil   3.2.8+dfsg-10
ii  libmono-posix4.0-cil3.2.8+dfsg-10
ii  libmono-system-core4.0-cil  3.2.8+dfsg-10
ii  libmono-system-xml4.0-cil   3.2.8+dfsg-10
ii  libmono-system4.0-cil   3.2.8+dfsg-10
ii  libpango-1.0-0  1.36.8-3
ii  libpangocairo-1.0-0 1.36.8-3
ii  libpangoft2-1.0-0   1.36.8-3
ii  libproxy1   0.4.11-4+b2
ii  libsm6  2:1.2.2-1+b1
ii  libx11-62:1.6.3-1
ii  mono-runtime3.2.8+dfsg-10

tomboy recommends no packages.

Versions of packages tomboy suggests:
pn  evolution  none
pn  tasque none

-- 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#794417: taskcoach: Task coach does not show it's icon in the kde plasma 5 system tray

2015-08-02 Thread Michael Meier
Package: taskcoach
Version: 1.4.2-1
Severity: important

Task Coach is not able to show its icon in the kde plasma 5 system tray. which 
makes it really dificult to use below that desktop environment.


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

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 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 taskcoach depends on:
ii  fonts-dejavu 2.35-1
ii  libxss1  1:1.2.2-1
ii  python   2.7.9-1
ii  python-chardet   2.3.0-1
ii  python-dateutil  2.2-2
ii  python-keyring   5.3-1
ii  python-lockfile  1:0.10.2-2
ii  python-pyparsing 2.0.3+dfsg1-1
ii  python-squaremap 1:1.0.4-2
ii  python-twisted-core  15.2.1-1
ii  python-wxgtk3.0  3.0.2.0+dfsg-1
ii  python-wxversion 3.0.2.0+dfsg-1
ii  python-xdg   0.25-4
ii  x11-utils7.7+3

Versions of packages taskcoach recommends:
pn  libavahi-compat-libdnssd1  none
ii  libgnome-2-0   2.32.1-5
ii  python-notify  0.1.1-4

Versions of packages taskcoach suggests:
pn  espeak   none
ii  python-kde4  4:4.14.0-1

-- 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#794126: plasma-widgets-addons: Digital clock widget does not show proper time

2015-07-30 Thread Michael Meier
Package: plasma-widgets-addons
Version: 4:5.3.2-2
Severity: important

After updating to kde plasma 5 the digital clock widget is showing the wrong 
time. The previous version (4.x) showed it correctly.
Also date and hwclock show the correct time. Also in the system settings, the 
date  time settings show the proper time. Fuzzy clock widget shows the propper 
time. I don't know about analog clclock widget, because it's just way to small 
to recognize anything.
The hwclock is set to utc. Timezone to venezuela.
The time shown is wrong for exactly one hour (one hour later than really is).
I hope the digital clock widget is part of plasma-widgets-addons, I did not 
know against what else to fill that bug.


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

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 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 plasma-widgets-addons depends on:
ii  kdeplasma-addons-data  4:5.3.2-2
ii  kpackagetool5  5.12.0-1
ii  libc6  2.19-19
ii  libkf5archive5 5.12.0-1
ii  libkf5completion5  5.12.0-1
ii  libkf5configcore5  5.12.0-1
ii  libkf5configgui5   5.12.0-1
ii  libkf5coreaddons5  5.12.0-1
ii  libkf5i18n55.12.0-1
ii  libkf5kiocore5 5.12.0-1
ii  libkf5kiowidgets5  5.12.0-1
ii  libkf5newstuff55.12.0-1
ii  libkf5notifications5   5.12.0-1
ii  libkf5plasma5  5.12.0-1
ii  libkf5widgetsaddons5   5.12.0-1
ii  libkf5windowsystem55.12.0-1
ii  libkf5xmlgui5  5.12.0-1
ii  libqt5core5a   5.4.2+dfsg-5
ii  libqt5gui5 5.4.2+dfsg-5
ii  libqt5qml5 5.4.2-4
ii  libqt5quick5   5.4.2-4
ii  libqt5widgets5 5.4.2+dfsg-5
ii  libqt5x11extras5   5.4.2-2
ii  libstdc++6 5.1.1-14
ii  plasma-dataengines-addons  4:5.3.2-2
ii  qml-module-org-kde-kio 5.12.0-2
ii  qml-module-qtwebkit5.4.2+dfsg-2

plasma-widgets-addons recommends no packages.

Versions of packages plasma-widgets-addons suggests:
pn  plasma-widget-kimpanel  none

-- 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#793502: workrave: Workrave doesn't show icon in system tray of kde plasma 5

2015-07-24 Thread Michael Meier
Package: workrave
Version: 1.10.6-2
Severity: normal

workrave needs to be updated to show an icon in the new kde plasma 5 system 
tray.
as a lot of older applications it can't show them there anymore.


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

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 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 workrave depends on:
ii  libatk1.0-0  2.16.0-2
ii  libatkmm-1.6-1   2.22.7-2.1
ii  libc62.19-19
ii  libcairo-gobject21.14.2-2
ii  libcairo21.14.2-2
ii  libcairomm-1.0-1 1.10.0-1.1
ii  libdbusmenu-glib412.10.2-1
ii  libdbusmenu-gtk3-4   12.10.2-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.5.2-4
ii  libgcc1  1:5.1.1-14
ii  libgdk-pixbuf2.0-0   2.31.4-2
ii  libgdome2-0  0.8.1+debian-6
ii  libglib2.0-0 2.44.1-1.1
ii  libglibmm-2.4-1c2a   2.44.0-1
ii  libgstreamer0.10-0   0.10.36-1.5
ii  libgtk-3-0   3.16.5-1
ii  libgtk2.0-0  2.24.28-1
ii  libgtkmm-3.0-1   3.16.0-1
ii  libice6  2:1.0.9-1+b1
ii  libindicator3-7  0.5.0-2
ii  libpanel-applet0 3.16.1-3
ii  libpango-1.0-0   1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpangoft2-1.0-01.36.8-3
ii  libpangomm-1.4-1 2.36.0-1
ii  libpulse-mainloop-glib0  6.0-2
ii  libpulse06.0-2
ii  libsigc++-2.0-0c2a   2.4.1-1
ii  libsm6   2:1.2.2-1+b1
ii  libstdc++6   5.1.1-14
ii  libx11-6 2:1.6.3-1
ii  libxfce4util74.12.1-2
ii  libxml2  2.9.1+dfsg1-5
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  workrave-data1.10.6-2
ii  xfce4-panel  4.12.0-3

workrave recommends no packages.

Versions of packages workrave suggests:
pn  gnome-panel  none
pn  gnome-shell  none

-- 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#793402: khotkeys: Custom shortcuts lost after update

2015-07-23 Thread Michael Meier

Hi Martin

Am 23.7.2015 18:37, schrieb Martin Steigerwald:

Hello Michael,

Am Donnerstag, 23. Juli 2015, 11:44:08 schrieb Michael Meier:

Package: khotkeys
Version: 4:5.3.2-2
Severity: normal

I'm using Debian testing. After the last update I've got a mixture of 
kde
4 and kde 5 components, which made a few things not working anymore. 
So I

update kde-plasma-desktop from 5:84 to 5:87 from unstable with all the
corresponding updates, also from unstable. Additionally I had to 
install
khotkeys, since it seems it was contained in an other kde package 
before.
After the update my custom global keyboard shortcuts dissappeared. 
They
don't work anymore, and they aren't shown in the system settings. In 
the
files khotkeysrc and kglobalshortcutsrc they still seem to be 
stored.
When I create new shortcuts the seem to be stored somewhere else (no 
idea

where). Since I've got a lot of shortcuts, also dbus calls, I really
don't want to restore them all one by one by hand...


JFYI what Martin, kwin maintainer writes about it:

http://blog.martin-graesslin.com/blog/2015/06/global-shortcut-handling-in-a-plasma-wayland-session/

I think from this they should still work for X11.

As with other settings it may be the config file is at a new location. 
Can
you check in ~/.local/share instead of ~./kde/share/config? Did it 
create a
new file for the newly defined shortcuts there? Maybe it suffices to 
copy

the old config files over.


Thanks a lot, you were right. Seems like kde does not use the ~/kde for 
all kde settings anymore. I've found the settings for khotkeys below 
~/.config/ . Copying the files worked.
But when changing the configuration path it should at least 
automatically check the old one, and copy settings from there to the new 
one. It's just annoying when after an update you loose all your 
settings...



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



Bug#793402: khotkeys: Custom shortcuts lost after update

2015-07-23 Thread Michael Meier
Package: khotkeys
Version: 4:5.3.2-2
Severity: normal

I'm using Debian testing. After the last update I've got a mixture of kde 4 and 
kde 5 components, which made a few things not working anymore.
So I update kde-plasma-desktop from 5:84 to 5:87 from unstable with all the 
corresponding updates, also from unstable. Additionally I had to install 
khotkeys, since it seems it was contained in an other kde package before.
After the update my custom global keyboard shortcuts dissappeared. They don't 
work anymore, and they aren't shown in the system settings.
In the files khotkeysrc and kglobalshortcutsrc they still seem to be stored.
When I create new shortcuts the seem to be stored somewhere else (no idea 
where). Since I've got a lot of shortcuts, also dbus calls, I really don't want 
to restore them all one by one by hand...


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

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 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 khotkeys depends on:
ii  khotkeys-data   4:5.3.2-2
ii  libc6   2.19-19
ii  libkf5completion5   5.12.0-1
ii  libkf5configcore5   5.12.0-1
ii  libkf5configwidgets55.12.0-1
ii  libkf5coreaddons5   5.12.0-1
ii  libkf5dbusaddons5   5.12.0-1
ii  libkf5globalaccel5  5.12.0-1
ii  libkf5i18n5 5.12.0-1
ii  libkf5kdelibs4support5  5.12.0-2
ii  libkf5kiowidgets5   5.12.0-1
ii  libkf5service5  5.12.0-1
ii  libkf5textwidgets5  5.12.0-1
ii  libkf5widgetsaddons55.12.0-1
ii  libkf5windowsystem5 5.12.0-1
ii  libkf5xmlgui5   5.12.0-1
ii  libkworkspace5-54:5.3.2-3
ii  libqt5core5a5.4.2+dfsg-4
ii  libqt5dbus5 5.4.2+dfsg-4
ii  libqt5gui5  5.4.2+dfsg-4
ii  libqt5widgets5  5.4.2+dfsg-4
ii  libqt5x11extras55.4.2-2
ii  libstdc++6  5.1.1-14
ii  libx11-62:1.6.3-1

khotkeys recommends no packages.

khotkeys 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#773462: plasma-nm: plasma nm does not save password of new wlan connections anymore

2015-05-31 Thread Michael Meier
Package: plasma-nm
Followup-For: Bug #773462

In the current version in debian testing 0.9.3.6-1. This bug doesn't occur 
anymore.


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



Bug#783494: mirror listing update for ftp.fau.de

2015-04-28 Thread Michael Meier (FTP Admin)
On Mon, 27 Apr 2015 19:30:44 -0400 Donald Norwood
dnorw...@portalus.com wrote:
 I don't know that the backports mirrors are going anywhere in the short
 term, if you want to mirror it it can be added as it was indicated on
 your original submission form.

Yes please.
(and since the last release that used the _seperate_ backports
repository instead of the one on the usual archive mirror network was
squeezy, the idea that it will disappear soon is probably not too far
fetched)

 The submission form stated:
 Archive-architecture: ALL amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 
 kfreebsd-i386 mips mipsel powerpc s390x sparc
 When checking the indices on your mirror however, all architectures were
 listed. As such I sought confirmation of which was correct. Some mirrors
 do drop architectures.

Yeah I realized that when I reread the message. However ALL is the
keyword here, and actually the only checkbox we ticked manually. The
mirror submission form then automatically selects all the individual
architectures it has. However, in the list on the mirror submission
form, arm64, ia64, ppc64el and s390 are missing; probably because they
are not supported by the current debian release, only by older releases.

  Some additional comments, mostly answers to some questions I often see
  asked in the large list of open mirror requests:
  - Available bandwidth is 5 GBit (why is that not asked on the form?
  Seems to be a pretty important piece of info.)
 Right beneath the comments box is a note that states:
 Note: if there is more than one sponsor, add the others in the comment.
 You may also want to note if the mirror gets updated less frequently
 than once a day, and how fast the site is (its maximum bandwidth).

Adding an extra selection box for the bandwidth that contains the usual
data rates would probably prevent more people from overlooking that like
we did :)
Even if your correct bandwidth is not available from the selection box,
it would make you remember to state i had to select 2 gbit above
because 5 gbit was not listed, 5 gbit is correct in the comment box.

 There is an unofficial listing of mirrors that serve https (that needs
 updating), though at this time there is no plan to publish an official
 listing or direction push as there are so few mirrors that provide the
 service. We have had a few discussions on the topic in the
 #debian-mirrors channel on IRC.

Though this discussion is a little off-topic here, my 2 cents are that
the fact that only few mirrors offer this service is not an argument not
to list it in the official list. On the contrary, if it would be listed,
more mirror admins could get the idea that this is a service worth offering.

Best regards,
-- 
Michael Meier, FTP-Admin
Friedrich-Alexander-Universitaet Erlangen-Nuernberg
Regionales Rechenzentrum Erlangen
Martensstrasse 1, 91058 Erlangen, Germany
Tel.: +49 9131 85-28973, Fax: +49 9131 302941
rrze-ftp-adm...@fau.de
blogs.fau.de/ftp/


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



Bug#783494: mirror listing update for ftp.fau.de

2015-04-27 Thread Michael Meier (FTP Admin)
 To confirm these changes are from: ftp.uni-erlangen.de to:
 ftp.fau.de?

correct. We're already in the mirror list as ftp.uni-erlangen.de. Please
change that entry to ftp.fau.de instead, as that is nowadays the
preferred corporate identity. (That said, the old URL should keep
working indefinitely)
We're not yet in the debian-cd mirror list.
We're also mirring debian-backports but as I guess that will go away
soon I'm not sure if its still worth adding to the official mirrorlist...

 And the dropping of the arm64, ia64, ppc64el, and s390 archives?

Uhm, no, where did you get that from? As stated in the submitted form,
we're NOT excluding any architectures. Is anything missing?

Some additional comments, mostly answers to some questions I often see
asked in the large list of open mirror requests:
- Available bandwidth is 5 GBit (why is that not asked on the form?
Seems to be a pretty important piece of info.)
- we're using ftpsync for mirroring debian and debian-backports.
- We're not using ftpsync for debian-cd because it really does not make
sense to do a 2stage-sync excluding the index files there. We do however
use our standard rsync options that include '--delay-updates', which
should make sure our CD image mirror is always as consistent as it gets.
- We're also offering https:// as protocol for all our mirrors, but I
guess the scripts generating your mirror websites can't handle that yet?

Best regards,
-- 
Michael Meier, FTP-Admin
Friedrich-Alexander-Universitaet Erlangen-Nuernberg
Regionales Rechenzentrum Erlangen
Martensstrasse 1, 91058 Erlangen, Germany
Tel.: +49 9131 85-28973, Fax: +49 9131 302941
rrze-ftp-adm...@fau.de
blogs.fau.de/ftp/


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



Bug#773454: network-manager: Network manager does not store passwords for new wlan connections anymore

2014-12-18 Thread Michael Meier
Package: network-manager
Version: 0.9.10.0-3
Severity: important

When connection to a new wlan, network manager does not store the password and 
the password needs to be reentered after every reconnect.
It does create the wlan config file below 
/etc/NetworkManager/system-connections , but it does not store the password in 
it.
Manually removing the line
psk-flags=1
and adding a line
psk=password
helps. After restarting the network manager service it can auto connect to the 
wlan without asking for the password again.
This behaviour already exists since about half a year, but it was just faster 
to edit the files, than reporting the bug. 
With the first version of network manager where that bug appeared I was able to 
enter the password by editing the connection in the plasma nm modul. But After 
the next update of network manager that was not possible anymore, since the ok 
button stays greyed out forever and it is impossible to save changes, thus 
editing the config file manually is necesary...
Below what the generated config file looks like, and afterwards the log output 
of network manager:

[connection]
id=FAMILI ARCOS REAL
uuid=22c6b842-5513-4b1e-a369-e7190d5951ad
type=wifi
permissions=user:rmm:;

[wifi]
ssid=FAMILI ARCOS REAL
mode=infrastructure
mac-address=C4:85:08:E0:C3:DD
security=802-11-wireless-security

[wifi-security]
key-mgmt=wpa-psk
auth-alg=open
psk-flags=1

[ipv4]
method=auto

[ipv6]
method=auto



Dec 18 08:54:19 RMMbook dbus[1425]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info NetworkManager (version 
0.9.10.0) is starting...
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info Read config: 
/etc/NetworkManager/NetworkManager.conf
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info WEXT support is enabled
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info VPN: loaded 
org.freedesktop.NetworkManager.vpnc
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info VPN: loaded 
org.freedesktop.NetworkManager.openvpn
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info VPN: loaded 
org.freedesktop.NetworkManager.pptp
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info init!
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info update_system_hostname
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info   interface-parser: 
parsing file /etc/network/interfaces
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info   interface-parser: 
finished parsing file /etc/network/interfaces
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info management mode: unmanaged
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info devices added (path: 
/sys/devices/pci:00/:00:1c.0/:01:00.0/net/wlan0, iface: wlan0)
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info device added (path: 
/sys/devices/pci:00/:00:1c.0/:01:00.0/net/wlan0, iface: wlan0): no 
ifupdown configuration found.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info devices added (path: 
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/eth0, iface: eth0)
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info device added (path: 
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/eth0, iface: eth0): no 
ifupdown configuration found.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info devices added (path: 
/sys/devices/virtual/net/lo, iface: lo)
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info device added (path: 
/sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info devices added (path: 
/sys/devices/virtual/net/virbr0, iface: virbr0)
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info device added (path: 
/sys/devices/virtual/net/virbr0, iface: virbr0): no ifupdown configuration 
found.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info end _init.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info Loaded plugin ifupdown: 
(C) 2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing 
list.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info Loaded plugin keyfile: 
(c) 2007 - 2013 Red Hat, Inc.  To report bugs please use the NetworkManager 
mailing list.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info (1140871616) ... 
get_connections.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info (1140871616) ... 
get_connections (managed=false): return empty list.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info new connection 
/etc/NetworkManager/system-connections/Yoga Vishnu Studio
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info new connection 
/etc/NetworkManager/system-connections/Movilnet
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info new connection 
/etc/NetworkManager/system-connections/JOSE BERROCAL
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info new connection 
/etc/NetworkManager/system-connections/APARTA ESTUDIO. 1
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info new connection 
/etc/NetworkManager/system-connections/59293779
Dec 

Bug#773454: [Pkg-utopia-maintainers] Bug#773454: network-manager: Network manager does not store passwords for new wlan connections anymore

2014-12-18 Thread Michael Meier
I am using kde. But I never ever used kwallet, and in previous versions 
it worked without problems. Network manager stored the passwords 
directly in the config files.


Am 18.12.2014 11:06, schrieb Michael Biebl:

Am 18.12.2014 um 14:51 schrieb Michael Meier:

Package: network-manager
Version: 0.9.10.0-3
Severity: important

When connection to a new wlan, network manager does not store the 
password and the password needs to be reentered after every reconnect.
It does create the wlan config file below 
/etc/NetworkManager/system-connections , but it does not store the 
password in it.

Manually removing the line
psk-flags=1



psk-flags means, the password is supposed to be saved in the user
session. What desktop environment do you use?
In case of GNOME, this would be gnome-keyring and for KDE, kwallet.



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



Bug#773462: plasma-nm: plasma nm does not save password of new wlan connections anymore

2014-12-18 Thread Michael Meier
Package: plasma-nm
Version: 0.9.3.4-2
Severity: important

I just filled a bug against network manager (Bug#773454), but they told me to 
fill it against plasma nm, so here we go...

When connection to a new wlan, network manager does not store the password and 
the password needs to be reentered after every reconnect.
It does create the wlan config file below 
/etc/NetworkManager/system-connections , but it does not store the password in 
it.
Manually removing the line
psk-flags=1
and adding a line
psk=password
helps. After restarting the network manager service it can auto connect to the 
wlan without asking for the password again.
This behaviour already exists since about 4 months if I remember right, but it 
was just faster to edit the files, than reporting the bug. 
With the first version of network manager where that bug appeared I was able to 
enter the password by editing the connection in the plasma nm modul. But After 
the next update of network manager that was not possible anymore, since the ok 
button stays greyed out forever and it is impossible to save changes, thus 
editing the config file manually is necesary...
I am not using kwallet in my system for anything. Also not for the network 
manager, and it used to work without it.
Below what the generated config file looks like, and afterwards the log output 
of network manager:

[connection]
id=FAMILI ARCOS REAL
uuid=22c6b842-5513-4b1e-a369-e7190d5951ad
type=wifi
permissions=user:rmm:;



[wifi]  


ssid=FAMILI ARCOS REAL  


mode=infrastructure 


mac-address=C4:85:08:E0:C3:DD   


security=802-11-wireless-security   





[wifi-security]
key-mgmt=wpa-psk
auth-alg=open
psk-flags=1

[ipv4]
method=auto

[ipv6]
method=auto



Dec 18 08:54:19 RMMbook dbus[1425]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info NetworkManager (version 
0.9.10.0) is starting...
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info Read config: 
/etc/NetworkManager/NetworkManager.conf
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info WEXT support is enabled
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info VPN: loaded 
org.freedesktop.NetworkManager.vpnc
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info VPN: loaded 
org.freedesktop.NetworkManager.openvpn
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info VPN: loaded 
org.freedesktop.NetworkManager.pptp
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info init!
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info update_system_hostname
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info   interface-parser: 
parsing file /etc/network/interfaces
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info   interface-parser: 
finished parsing file /etc/network/interfaces
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info management mode: unmanaged
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info devices added (path: 
/sys/devices/pci:00/:00:1c.0/:01:00.0/net/wlan0, iface: wlan0)
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info device added (path: 
/sys/devices/pci:00/:00:1c.0/:01:00.0/net/wlan0, iface: wlan0): no 
ifupdown configuration found.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info devices added (path: 
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/eth0, iface: eth0)
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info device added (path: 
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/eth0, iface: eth0): no 
ifupdown configuration found.
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info devices added (path: 
/sys/devices/virtual/net/lo, iface: lo)
Dec 18 08:54:19 RMMbook NetworkManager[25724]: info device added (path: 
/sys/devices/virtual/net/lo, iface: lo): no ifupdown 

Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-07-24 Thread Michael Meier
Package: network-manager
Version: 0.9.10.0-1
Followup-For: Bug #749191

I just installed the systemd-sysv package, so effectly switching to the systemd 
startup service.
With this service it reconnects automatically again.
So i guess there's somekind of depedency issue when using sysv. 
(Network-maanger gets started up to early. that's why a restart of it makes it 
working perfectly)

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.6-1
ii  init-system-helpers1.19
ii  isc-dhcp-client4.3.0+dfsg-1
ii  libc6  2.19-7
ii  libdbus-1-31.8.6-1
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt111.5.3-4
ii  libglib2.0-0   2.40.0-3
ii  libgnutls-deb0-28  3.2.15-3
ii  libgudev-1.0-0 208-6
ii  libmm-glib01.2.0-1
ii  libndp01.3-1
ii  libnewt0.520.52.17-1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-1
ii  libnm-util20.9.10.0-1
ii  libpam-systemd 208-6
ii  libpolkit-gobject-1-0  0.105-6
ii  libreadline6   6.3-6
ii  libsoup2.4-1   2.46.0-2
ii  libsystemd-daemon0 208-6
ii  libsystemd-login0  208-6
ii  libuuid1   2.20.1-5.8
ii  lsb-base   4.1+Debian13
ii  policykit-10.105-6
ii  udev   208-6
ii  wpasupplicant  1.1-1

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.71-1
ii  iptables  1.4.21-2
ii  modemmanager  1.2.0-1
ii  ppp   2.4.6-2

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-4

-- 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#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-07-22 Thread Michael Meier
Package: network-manager
Version: 0.9.10.0-1
Followup-For: Bug #749191

also after updating to 0.9.10.0-1 this bug still exists.
restarting the network manager service makes it auto connect...
service network-manager restart

Also for the new version there are no more information in the syslog. It just 
never even tries to connect.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.6-1
ii  init-system-helpers1.19
ii  isc-dhcp-client4.3.0+dfsg-1
ii  libc6  2.19-7
ii  libdbus-1-31.8.6-1
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt111.5.3-4
ii  libglib2.0-0   2.40.0-3
ii  libgnutls-deb0-28  3.2.15-3
ii  libgudev-1.0-0 208-6
ii  libmm-glib01.2.0-1
ii  libndp01.3-1
ii  libnewt0.520.52.17-1
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.10.0-1
ii  libnm-util20.9.10.0-1
ii  libpam-systemd 204-14
ii  libpolkit-gobject-1-0  0.105-6
ii  libreadline6   6.3-6
ii  libsoup2.4-1   2.46.0-2
ii  libsystemd-daemon0 204-14
ii  libsystemd-login0  204-14
ii  libuuid1   2.20.1-5.8
ii  lsb-base   4.1+Debian13
ii  policykit-10.105-6
ii  udev   208-6
ii  wpasupplicant  1.1-1

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.71-1
ii  iptables  1.4.21-2
ii  modemmanager  1.2.0-1
ii  ppp   2.4.6-2

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-4

-- 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#754862: xserver-xorg-input-evdev: Mouse movement very slow wince last upgrade

2014-07-16 Thread Michael Meier
Package: xserver-xorg-input-evdev
Version: 1:2.8.2-1+b2
Followup-For: Bug #754862

I've got exactly the same problem. I can get my touchpad moving the mouse 
cursor faster, by using synclient and setting
MinSpeed, MaxSpeed and AccelFactor to values around 5 times bigger than before.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Jan  8  2014 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 2356320 Jul  8 08:30 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09)

/etc/X11/xorg.conf does not exist.

Contents of /etc/X11/xorg.conf.d:
-
total 4
-rw-r--r-- 1 root root 1204 Mar 11 21:11 50-synaptics.conf

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 3.14-1-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.3 
(Debian 4.8.3-4) ) #1 SMP Debian 3.14.12-1 (2014-07-11)

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 23124 Jul 16 10:05 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[ 7.678] 
X.Org X Server 1.15.99.904 (1.16.0 RC 4)
Release Date: 2014-07-07
[ 7.678] X Protocol Version 11, Revision 0
[ 7.678] Build Operating System: Linux 3.14-1-amd64 x86_64 Debian
[ 7.678] Current Operating System: Linux RMMbook 3.14-1-amd64 #1 SMP Debian 
3.14.12-1 (2014-07-11) x86_64
[ 7.678] Kernel command line: BOOT_IMAGE=/vmlinuz-3.14-1-amd64 
root=UUID=d26e75e5-1bf8-4076-a8b2-ae6b80dd58fc ro quiet pcie_aspm=force 
i915.i915_enable_rc6=7 i915.i915_enable_fbc=1 i915.lvds_downclock=1 
resume=/dev/mapper/vghdd-swap
[ 7.678] Build Date: 08 July 2014  01:26:43PM
[ 7.678] xorg-server 2:1.15.99.904-1 (http://www.debian.org/support) 
[ 7.678] Current version of pixman: 0.32.4
[ 7.678]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 7.678] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.679] (==) Log file: /var/log/Xorg.0.log, Time: Wed Jul 16 10:05:17 
2014
[ 7.690] (==) Using config directory: /etc/X11/xorg.conf.d
[ 7.690] (==) Using system config directory /usr/share/X11/xorg.conf.d
[ 7.698] (==) No Layout section.  Using the first Screen section.
[ 7.698] (==) No screen section available. Using defaults.
[ 7.698] (**) |--Screen Default Screen Section (0)
[ 7.698] (**) |   |--Monitor default monitor
[ 7.698] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[ 7.698] (==) Automatically adding devices
[ 7.698] (==) Automatically enabling devices
[ 7.698] (==) Automatically adding GPU devices
[ 7.722] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[ 7.722]Entry deleted from font path.
[ 7.723] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[ 7.723] (==) ModulePath set to /usr/lib/xorg/modules
[ 7.723] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[ 7.723] (II) Loader magic: 0x7fb737948d80
[ 7.723] (II) Module ABI versions:
[ 7.723]X.Org ANSI C Emulation: 0.4
[ 7.723]X.Org Video Driver: 18.0
[ 7.724]X.Org XInput driver : 21.0
[ 7.724]X.Org Server Extension : 8.0
[ 7.724] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 7.725] (--) PCI:*(0:0:2:0) 8086:0166:144d:c0d7 rev 9, Mem @ 
0xf000/4194304, 0xe000/268435456, I/O @ 0x3000/64
[ 7.725] (II) LoadModule: glx
[ 7.739] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 7.769] (II) Module glx: vendor=X.Org Foundation
[ 7.769]compiled for 1.15.99.904, module version = 1.0.0
[ 7.769]ABI class: X.Org Server Extension, version 8.0
[ 7.769] (==) AIGLX enabled
[ 7.769] (==) Matched intel as autoconfigured driver 0
[ 7.769] (==) Matched intel as autoconfigured driver 1
[ 7.769] (==) Matched modesetting as autoconfigured driver 2
[ 7.769] (==) Matched fbdev as autoconfigured driver 3
[ 7.769] (==) Matched vesa as autoconfigured driver 4
[ 7.769] (==) Assigned the driver to the xf86ConfigLayout
[ 7.769] (II) LoadModule: intel
[ 7.769] (II) Loading 

Bug#749187: pulseaudio: When switching from HDMI to Analog output, sometimes no sound is heard

2014-05-24 Thread Michael Meier
Package: pulseaudio
Version: 5.0-2
Severity: important

When in pulse audio the output device is set to the HDMI connection of my 
laptop, and later on I unplug the HDMI cable and switch to analog stereo 
duplex or analog stereo output (using pavucontrol or the kde media center)
most of the time I wont hear any sound (sometimes it works, but mostly not).

In pavucontrol I can see how in the output devices tab, a built-in audio 
analog stereo device is added, but the HDMI devices stays, and all sound 
continues to get output on this one.
Opening and closing applications doesn't help.
The only way I manage to get the internal speakers of the laptop working again 
is a system restart.
There are no message in system.log or any other log file I could find.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages pulseaudio depends on:
ii  adduser   3.113+nmu3
ii  libasound21.0.27.2-4
ii  libasound2-plugins1.0.27-2.1
ii  libc6 2.18-5
ii  libcap2   1:2.22-1.2
ii  libdbus-1-3   1.8.2-1
ii  libfftw3-single3  3.3.4-1
ii  libgcc1   1:4.9.0-3
ii  libice6   2:1.0.8-2
ii  libltdl7  2.4.2-1.7
ii  liborc-0.4-0  1:0.4.19-1
ii  libpulse0 5.0-2
ii  libsamplerate00.1.8-7
ii  libsm62:1.2.1-2
ii  libsndfile1   1.0.25-9
ii  libspeexdsp1  1.2~rc1.1-1
ii  libstdc++64.9.0-3
ii  libsystemd-login0 204-8
ii  libtdb1   1.2.13-2
ii  libudev1  204-8
ii  libwebrtc-audio-processing-0  0.1-2
ii  libx11-6  2:1.6.2-2
ii  libx11-xcb1   2:1.6.2-2
ii  libxcb1   1.10-2
ii  libxtst6  2:1.2.2-1
ii  lsb-base  4.1+Debian12
ii  udev  204-8

Versions of packages pulseaudio recommends:
pn  pulseaudio-module-x11  none
ii  rtkit  0.11-1

Versions of packages pulseaudio suggests:
pn  paman none
pn  paprefs   none
ii  pavucontrol   2.0-2
pn  pavumeter none
ii  pulseaudio-utils  5.0-2

-- 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#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-24 Thread Michael Meier
Package: network-manager
Version: 0.9.8.10-2
Severity: normal

When starting the system network-manager does not automatically connect to 
wireless connections marked as connect automatically.
One has to connect to them by hand. Once connected it tries to automatically 
reconnect when it looses connection.
In previous verions that used to work.


-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages network-manager depends on:
ii  adduser3.113+nmu3
ii  dbus   1.8.2-1
ii  init-system-helpers1.18
ii  isc-dhcp-client4.2.4-7
ii  libc6  2.18-5
ii  libdbus-1-31.8.2-1
ii  libdbus-glib-1-2   0.102-1
ii  libgcrypt111.5.3-4
ii  libglib2.0-0   2.40.0-3
ii  libgnutls262.12.23-15
ii  libgudev-1.0-0 204-8
ii  libmm-glib01.0.0-4
ii  libnl-3-2003.2.24-2
ii  libnl-genl-3-200   3.2.24-2
ii  libnl-route-3-200  3.2.24-2
ii  libnm-glib40.9.8.10-2
ii  libnm-util20.9.8.10-2
ii  libpam-systemd 204-8
ii  libpolkit-gobject-1-0  0.105-5
ii  libsoup2.4-1   2.46.0-2
ii  libsystemd-daemon0 204-8
ii  libsystemd-login0  204-8
ii  libuuid1   2.20.1-5.7
ii  lsb-base   4.1+Debian12
ii  policykit-10.105-5
ii  udev   204-8
ii  wpasupplicant  1.1-1

Versions of packages network-manager recommends:
ii  crda  1.1.2-1
ii  dnsmasq-base  2.71-1
ii  iptables  1.4.21-1
ii  modemmanager  1.0.0-4
ii  ppp   2.4.6-2

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-4

-- 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#749191: [Pkg-utopia-maintainers] Bug#749191: network-manager does not auto connect to wireless connection after system start anymore

2014-05-24 Thread Michael Meier

Am 24.5.2014 19:28, schrieb Michael Biebl:

below the output of syslog.
When it connects at 18:50 it's because I manually told it so.
I'm not really sure how to get any output from wpa_supplicant at
systemstart...


you can simply restart wpa_supplicant.


wpa-supplicant is no service, at least not in my system, so I executed 
the dbus commands descriped in the wiki and
restarted NetworkManager... But i didn't get any log output, I also 
tried to add -f /var/log/wpa_supplicant.log to 
/usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service

but nothing happened.
But what I noticed, when I restart the network-manager service, it 
autoconnect. Also if I restart the computer and then restart the 
network-manager service, it auto connects. I will attach a log of that 
at the bottom...



Maybe it's not needed (as far as I understand the log it seems like it
even doesn't try to connect.



Please also includine the wpasupplicant log and the
/etc/NetworkManager/system-connections/59293779 connection file (make
sure to  the psk)

Is this specific to this particular wireless network or a general 
issue?


It's the same for at least 4 wireless conections, also one I added newly 
yesterday. So I guess it's a general issue.



Does autoconnect work for a lan connection?


My laptop got one of this stupid proprietary mini-lan ports. And I don't 
have an adapter...


All right.
First /etc/NetworkManager/system-connections/59293779
The ps is not stored in it but in 
~/.kde/share/config/plasma-networkmanagment . THere isn't written 
anything interesting besides the password.
In this connection definition there's nothing written about auto connect 
(don't know if it's necessary).
But if in the settings, I disable the checkmark at auto connect. Press 
apply. Enable the checkmark again. It starts connecting to this 
connection. But after the next restart I have to connect manually again.


[connection]
id=59293779
uuid=99062574-6bb6-4105-947b-dc2f39540848
type=802-11-wireless
permissions=user:rmm:;

[802-11-wireless]
ssid=59293779
mode=infrastructure
mac-address=C4:85:08:E0:C3:DD
security=802-11-wireless-security

[802-11-wireless-security]
key-mgmt=none
auth-alg=shared
wep-key-flags=1
wep-key-type=1

[ipv4]
method=auto

[ipv6]
method=auto


and here the log after restarting the network-manager service:

May 24 20:27:00 RMMbook NetworkManager[4823]: info NetworkManager 
(version 0.9.8.10) is starting...
May 24 20:27:00 RMMbook NetworkManager[4823]: info Read config file 
/etc/NetworkManager/NetworkManager.conf
May 24 20:27:00 RMMbook NetworkManager[4823]: info WEXT support is 
enabled
May 24 20:27:00 RMMbook NetworkManager[4823]: info VPN: loaded 
org.freedesktop.NetworkManager.vpnc
May 24 20:27:00 RMMbook NetworkManager[4823]: info VPN: loaded 
org.freedesktop.NetworkManager.openvpn
May 24 20:27:00 RMMbook NetworkManager[4823]: info VPN: loaded 
org.freedesktop.NetworkManager.pptp
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
init!
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
update_system_hostname
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPluginIfupdown: 
management mode: unmanaged
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
devices added (path: 
/sys/devices/pci:00/:00:1c.0/:01:00.0/net/wlan0, iface: 
wlan0)
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
device added (path: 
/sys/devices/pci:00/:00:1c.0/:01:00.0/net/wlan0, iface: 
wlan0): no ifupdown configuration found.
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
devices added (path: 
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/eth0, iface: eth0)
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
device added (path: 
/sys/devices/pci:00/:00:1c.3/:02:00.0/net/eth0, iface: 
eth0): no ifupdown configuration found.
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/lo, iface: lo)
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown 
configuration found.
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
devices added (path: /sys/devices/virtual/net/virbr0, iface: virbr0)
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: 
device added (path: /sys/devices/virtual/net/virbr0, iface: virbr0): no 
ifupdown configuration found.
May 24 20:27:00 RMMbook NetworkManager[4823]:SCPlugin-Ifupdown: end 
_init.
May 24 20:27:00 RMMbook NetworkManager[4823]: info Loaded plugin 
ifupdown: (C) 2008 Canonical Ltd.  To report bugs please use the 
NetworkManager mailing list.
May 24 20:27:00 RMMbook NetworkManager[4823]: info Loaded plugin 
keyfile: (c) 2007 - 2010 Red Hat, Inc.  To report bugs please use the 
NetworkManager mailing list.
May 24 20:27:00 RMMbook NetworkManager[4823]:Ifupdown: get 

Bug#747636: qemu: when using -smb parameter does not startup smbd

2014-05-10 Thread Michael Meier
Package: qemu
Version: 2.0.0+dfsg-4
Severity: normal

When using the -smb parameter, qemu does not start up the smbd service.
it creates the necessary config file in the /tmp/ folder though.
If I start it up by hand:
smbd -s /tmp/qemu-smb.19409-0$/smb.conf
smbd gets started up correctly and i can access it from the virtual machine 
using:
\\10.0.2.2\qemu   (not 10.0.2.4)
the command used to start up qemu is (generated by aqemu):
/usr/bin/kvm -monitor stdio -soundhw ac97 -k es -vga std -enable-kvm -m 2048 
-localtime -snapshot -drive file=/home/rmm/data/Virtual 
Machines/windows-7-x64.qcow2,if=virtio -boot once=c,menu=off -net 
nic,vlan=0,model=virtio -net 
user,vlan=0,smb=/home/rmm/data/tmp,smbserver=10.0.2.4 -name Windows 7 x64

not using kvm doesn't make any difference, also giving a fixed ip to the smb 
parameter (host). does not make any difference.
From the virtual machine I can't ping 10.0.2.4 (the default ip it should use) 
so I guess this virtual nic never gets created?

-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages qemu depends on:
ii  qemu-system  2.0.0+dfsg-4
ii  qemu-user2.0.0+dfsg-4
ii  qemu-utils   2.0.0+dfsg-4

qemu recommends no packages.

Versions of packages qemu suggests:
pn  qemu-user-static  none

-- 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#747522: network-manager sometimes segfaults when disabling and re-enabling wifi after loosing connection

2014-05-09 Thread Michael Meier
Package: network-manager
Version: 0.9.8.10-2
Severity: normal

Sometimes I loose the connection to the wireless network. 
Afterwards I soetimes disable and re-enable the wireless conection to reconnect 
to the network 
(it was necessary in older versions of network-manager or of the wifi driver, 
i'm not sure).
Since I installed 0.9.8.10-2 this sometimes ends in a segfault of the network 
manager.
Before I had installed 0.9.8.0-5 and this problem never appeared.
Here an excert from syslog:

May  9 08:00:59 RMMbook kernel: [ 3309.376970] wlan0: send auth to 
10:fe:ed:60:2a:f0 (try 3/3)
May  9 08:00:59 RMMbook kernel: [ 3309.396968] wlan0: authentication with 
10:fe:ed:60:2a:f0 timed out
May  9 08:00:59 RMMbook NetworkManager[2948]: info (wlan0): supplicant 
interface state: authenticating - disconnected
May  9 08:00:59 RMMbook NetworkManager[2948]: info (wlan0): supplicant 
interface state: disconnected - scanning
May  9 08:01:09 RMMbook dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 
67 interval 4
May  9 08:01:10 RMMbook NetworkManager[2948]: info (wlan0): device state 
change: ip-config - unavailable (reason 'none') [70 20 0]
May  9 08:01:10 RMMbook NetworkManager[2948]: info (wlan0): deactivating 
device (reason 'none') [0]
May  9 08:01:10 RMMbook NetworkManager[2948]: info (wlan0): canceled DHCP 
transaction, DHCP client pid 4091
May  9 08:01:10 RMMbook NetworkManager[2948]: info NetworkManager state is 
now DISCONNECTED
May  9 08:01:10 RMMbook NetworkManager[2948]: info (wlan0): taking down 
device.
May  9 08:01:11 RMMbook avahi-daemon[2914]: Interface wlan0.IPv6 no longer 
relevant for mDNS.
May  9 08:01:11 RMMbook avahi-daemon[2914]: Leaving mDNS multicast group on 
interface wlan0.IPv6 with address fe80::c685:8ff:fee0:c3dd.
May  9 08:01:11 RMMbook avahi-daemon[2914]: Withdrawing address record for 
fe80::c685:8ff:fee0:c3dd on wlan0.
May  9 08:01:11 RMMbook NetworkManager[2948]: info WiFi hardware radio set 
disabled
May  9 08:01:11 RMMbook kernel: [ 3320.797550] iwlwifi :01:00.0: RF_KILL 
bit toggled to disable radio.
May  9 08:01:11 RMMbook NetworkManager[2948]: info WiFi now disabled by radio 
killswitch
May  9 08:01:12 RMMbook NetworkManager[2948]: info (wlan0): bringing up 
device.
May  9 08:01:12 RMMbook NetworkManager[2948]: info WiFi hardware radio set 
enabled
May  9 08:01:12 RMMbook kernel: [ 3321.942119] iwlwifi :01:00.0: RF_KILL 
bit toggled to enable radio.
May  9 08:01:12 RMMbook NetworkManager[2948]: info WiFi now enabled by radio 
killswitch
May  9 08:01:12 RMMbook NetworkManager[2948]: info (wlan0): bringing up 
device.
May  9 08:01:12 RMMbook kernel: [ 3321.944472] iwlwifi :01:00.0: L1 
Disabled; Enabling L0S
May  9 08:01:12 RMMbook kernel: [ 3321.951726] iwlwifi :01:00.0: Radio 
type=0x2-0x1-0x0
May  9 08:01:12 RMMbook kernel: [ 3322.034469] IPv6: ADDRCONF(NETDEV_UP): 
wlan0: link is not ready
May  9 08:01:12 RMMbook NetworkManager[2948]: info (wlan0) supports 5 scan 
SSIDs
May  9 08:01:12 RMMbook NetworkManager[2948]: info (wlan0): supplicant 
interface state: starting - ready
May  9 08:01:12 RMMbook NetworkManager[2948]: info (wlan0): device state 
change: unavailable - disconnected (reason 'supplicant-available') [20 30 42]
May  9 08:01:12 RMMbook NetworkManager[2948]: warn Trying to remove a 
non-existant call id.
May  9 08:01:12 RMMbook NetworkManager[2948]: info (wlan0): supplicant 
interface state: ready - inactive
May  9 08:01:12 RMMbook NetworkManager[2948]: info (wlan0) supports 5 scan 
SSIDs
May  9 08:01:28 RMMbook kernel: [ 3338.129343] NetworkManager[2948]: segfault 
at 1 ip 7fb5ff357c7a sp 7fff7cd044e8 error 4 in 
libc-2.18.so[7fb5ff2d6000+1a]

or 1 day before:

May  8 19:48:21 RMMbook wpa_supplicant[4829]: wlan0: CTRL-EVENT-DISCONNECTED 
bssid=10:fe:ed:60:2a:f0 reason=4
May  8 19:48:22 RMMbook kernel: [34270.753279] cfg80211: Calling CRDA to update 
world regulatory domain
May  8 19:48:22 RMMbook NetworkManager[18749]: info (wlan0): supplicant 
interface state: completed - disconnected
May  8 19:48:22 RMMbook NetworkManager[18749]: info (wlan0): supplicant 
interface state: disconnected - scanning
May  8 19:48:22 RMMbook kernel: [34270.779848] cfg80211: World regulatory 
domain updated:
May  8 19:48:22 RMMbook kernel: [34270.779852] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May  8 19:48:22 RMMbook kernel: [34270.779854] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm)
May  8 19:48:22 RMMbook kernel: [34270.779855] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm)
May  8 19:48:22 RMMbook kernel: [34270.779856] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm)
May  8 19:48:22 RMMbook kernel: [34270.779857] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz), (N/A, 2000 mBm)
May  8 19:48:22 RMMbook kernel: [34270.779858] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm)
May  8 19:48:22 RMMbook kernel: [34270.779859] 

Bug#410054: liblzo2-dev: examples/portab.h is missing which most examples are using

2007-02-07 Thread Michael Meier
Package: liblzo2-dev
Version: 2.02-2
Severity: minor


In /usr/share/doc/liblzo2-dev/examples most examples include a file called 
examples/portab.h
without it, the examples aren't working directly. (They are still good 
examples, but it would be nice
if you could compile them to test it).


-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-4
Locale: LANG=de_CH.UTF8, LC_CTYPE=de_CH.UTF8 (charmap=UTF-8)


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



Bug#405100: smartmontools: smartctl is able do disable Automatic Offline Testing but unable to reenable it

2006-12-31 Thread Michael Meier
Package: smartmontools
Version: 5.37-1
Severity: normal

For some reason (curiosity) I disabled the the SMART Automatic Offline 
Testing for my harddrive with:
smartctl -d ata -o off /dev/sda
which worked fine. Now smartctl tells me that it is disabled (before it was 
enabled).
But now smartctl is unable to reenable it.
smartctl -d ata -o on /dev/sda only display following message:
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
Error SMART Enable Automatic Offline failed: Input/output error
Smartctl: SMART Enable Automatic Offline Failed.

There is no output on dmesg.

I'm using a Hitachi HTS541080G9AT00 from the Travelstar 5K100 series in a 
Thinkpad T43 Laptop connected over sata.


-- Package-specific info:
Ouput of /usr/share/bug/smartmontools:

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-4
Locale: LANG=de_CH.UTF8, LC_CTYPE=de_CH.UTF8 (charmap=UTF-8)

Versions of packages smartmontools depends on:
ii  debianutils  2.17Miscellaneous utilities specific t
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-19  GCC support library
ii  libstdc++6   4.1.1-19The GNU Standard C++ Library v3
ii  lsb-base 3.1-22  Linux Standard Base 3.1 init scrip

Versions of packages smartmontools recommends:
ii  mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent

-- no debconf information


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



Bug#401228: gnome-commander: Gnome-Commander 1.2.1 released

2006-12-01 Thread Michael Meier
Package: gnome-commander
Version: 1.2.0-3.2
Severity: wishlist

Gnome-Commander 1.2.1 was released already a while ago.
It would includes some nice new features...

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-3
Locale: LANG=de_CH.UTF8, LC_CTYPE=de_CH.UTF8 (charmap=UTF-8)


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



Bug#351530: rhythmbox: can't show some mp3 files with german umlaut in it

2006-03-19 Thread Michael Meier
Since i don't really want to send a part of a music file to the bugsystem (i
don't know if it would save it, but don't feel like checking it out right 
now),
i only send it to you directly.
 
 
  (It's fine to send things in the order of one megabyte to the bug
  system.)
 
  Importing and searching the MP3 works for me (see attached screenshot
  :-P), so it's quite certainly related to your environment.

strange, so far rhythmbox is the only application with this problem...


  Could you please try to launch rhythmbox from a terminal with:
 LC_ALL=C rhythmbox

Doesnt help...

  How are do you login in GNOME?  Gdm?  Could you please try to login via

yes i am using GDM to login into gnome

  a console, and type startx to login, check whether the bug still
  appears.

tried it out. Still the same behaviour

greetings


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



Bug#351530: rhythmbox: can't show some mp3 files with german umlaut in it

2006-02-27 Thread Michael Meier
  Ok, well it seems your system is correclty configured, your files are
  named in ISO-8859, so it's probably a rhythmbox bug.  Since they were a
  lot of tags related fixes in gstreamer0.10-plugins-good, could you
  confirm that you still have the bug with version 0.10.2-1?

yes it still exists with this version.


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



Bug#351530: rhythmbox: can't show some mp3 files with german umlaut in it

2006-02-13 Thread Michael Meier
  To confirm, could you please run from a terminal ls /some/directory/ 
  output.dat and attach output.dat to your reply?  (Where
  /some/directory/ is a directory with your problematic files.)
Done

   Could you also try to run from a terminal:
 G_FILENAME_ENCODING=ISO-8859-15 gedit
Done: I see the correct filenames

  and:
 G_FILENAME_ENCODING=ISO-8859-15 gedit
if i'm not completly wrong then that's exactly the same string as above...

  from gedit, type ^O and browse to a directory with your files: in which
  case do you see the correct names?  Do you see the correct names when
  you launch gedit from your terminal without any G_FILENAME_ENCODING?
I also see the correct filenames when i launch gedit without the
g_filename_encoding stuff.


output.dat
Description: MPEG movie


Bug#351530: rhythmbox: can't show some mp3 files with german umlaut in it

2006-02-05 Thread Michael Meier
Package: rhythmbox
Version: 0.9.3-1
Severity: normal

Some files which have german umlauts in it (ö, ä or ü) are not 
properly displayed. (some work)
The Titel is shown as ungültiger Dateiname, what means invalid filename,
genre, artists are shown as unknown.
But it is able to play the files anyway.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (990, 'testing'), (600, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.15-5
Locale: LANG=de_CH, LC_CTYPE=de_CH (charmap=ISO-8859-15)

Versions of packages rhythmbox depends on:
ii  dbus   0.60-5simple interprocess messaging syst
ii  gconf2 2.12.1-8  GNOME configuration database syste
ii  gstreamer0.10-alsa [gs 0.10.1-1  ALSA plugin for GStreamer
ii  gstreamer0.10-gnomevfs 0.10.1-1  Gnome VFS plugin for GStreamer
ii  gstreamer0.10-plugins- 0.10.1-1  Collection of various GStreamer pl
ii  gstreamer0.10-plugins- 0.10.1-1  Collection of various GStreamer pl
ii  gstreamer0.10-plugins- 0.10.1-1  Collection of various GStreamer pl
ii  libart-2.0-2   2.3.17-1  Library of functions for 2D graphi
ii  libatk1.0-01.10.3-1  The ATK accessibility toolkit
ii  libaudiofile0  0.2.6-6   Open-source version of SGI's audio
ii  libavahi-client3   0.6.6-1   Avahi client library
ii  libavahi-common3   0.6.6-1   Avahi common library
ii  libavahi-compat-howl0  0.6.6-1   Avahi Howl compatibility library
ii  libavahi-glib1 0.6.6-1   Avahi glib integration library
ii  libbonobo2-0   2.10.1-1  Bonobo CORBA interfaces library
ii  libbonoboui2-0 2.10.1-1  The Bonobo UI library
ii  libc6  2.3.5-8   GNU C Library: Shared libraries an
ii  libcairo2  1.0.2-3   The Cairo 2D vector graphics libra
ii  libdbus-1-20.60-5simple interprocess messaging syst
ii  libdbus-glib-1-2   0.60-5simple interprocess messaging syst
ii  libesd-alsa0 [libesd0] 0.2.36-3  Enlightened Sound Daemon (ALSA) - 
ii  libexpat1  1.95.8-3  XML parsing C library - runtime li
ii  libfontconfig1 2.3.2-1.1 generic font configuration library
ii  libfreetype6   2.1.7-2.4 FreeType 2 font engine, shared lib
ii  libgconf2-42.12.1-8  GNOME configuration database syste
ii  libgcrypt111.2.2-1   LGPL Crypto library - runtime libr
ii  libglade2-01:2.5.1-2 library to load .glade files at ru
ii  libglib2.0-0   2.8.6-1   The GLib library of C routines
ii  libgnome-keyring0  0.4.6-2   GNOME keyring services library
ii  libgnome2-02.12.0.1-5The GNOME 2 library - runtime file
ii  libgnomecanvas2-0  2.12.0-2  A powerful object-oriented display
ii  libgnomeui-0   2.12.0-2  The GNOME 2 libraries (User Interf
ii  libgnomevfs2-0 2.12.2-5  GNOME virtual file-system (runtime
ii  libgnutls111.0.16-14 GNU TLS library - runtime library
ii  libgpg-error0  1.1-4 library for common error values an
ii  libgpod0   0.3.0-2   a library to read and write songs 
ii  libgstreamer0.10-0 0.10.2-1  Core GStreamer libraries, plugins,
ii  libgtk2.0-02.8.10-1  The GTK+ graphical user interface 
ii  libhal10.5.6-2   Hardware Abstraction Layer - share
ii  libice66.8.2.dfsg.1-11   Inter-Client Exchange library
ii  libjpeg62  6b-11 The Independent JPEG Group's JPEG 
ii  libmusicbrainz4c2a 2.1.2-2   Second generation incarnation of t
ii  libnautilus-burn2  2.12.2-3  Nautilus Burn Library - runtime ve
ii  libnotify1 0.3.2-1   sends desktop notifications to a n
ii  liborbit2  1:2.12.4-1libraries for ORBit2 - a CORBA ORB
ii  libpango1.0-0  1.10.2-1  Layout and rendering of internatio
ii  libpng12-0 1.2.8rel-5PNG library - runtime
ii  libpopt0   1.7-5 lib for parsing cmdline parameters
ii  libsm6 6.8.2.dfsg.1-11   X Window System Session Management
ii  libsoup2.2-8   2.2.6-1   an HTTP library implementation in 
ii  libtasn1-2 0.2.17-1  Manage ASN.1 structures (runtime)
ii  libtotem-plparser0 1.2.1-3   Totem Playlist Parser library - ru
ii  libx11-6   6.8.2.dfsg.1-11   X Window System protocol client li
ii  libxcursor11.1.3-1   X cursor management library
ii  libxext6   6.8.2.dfsg.1-11   X Window System miscellaneous exte
ii  libxi6 6.8.2.dfsg.1-11   X Window System Input extension li
ii  

Bug#351530: rhythmbox: can't show some mp3 files with german umlaut in it

2006-02-05 Thread Michael Meier
I tried around a bit.
As it seems that only appears for files where the mp3-tag is not set.
When i set the tag it works. it also works when i remove the umlaut in the
filename without setting the mp3tag.
So when no mp3-tag is set, it wants to take the filename as title, but then it
fails because of the umlaut in the filename.

greetings

Loïc Minier wrote:
 Hi,
 
 On dim, fév 05, 2006, Michael Meier wrote:
 
Some files which have german umlauts in it (ö, ä or ü) are not 
properly displayed. (some work)
The Titel is shown as ungültiger Dateiname, what means invalid filename,
genre, artists are shown as unknown.
But it is able to play the files anyway.
 
 
  Are the umlauts in file names or in tags?  Did you try renaming the
  files?  Perhaps it's simply a tag encoding issue?
 
Cheers,
 



Bug#351530: rhythmbox: can't show some mp3 files with german umlaut in it

2006-02-05 Thread Michael Meier
This should be: ISO-8859-15


Loïc Minier wrote:
 Hi,
 
 On dim, fév 05, 2006, Michael Meier wrote:
 
As it seems that only appears for files where the mp3-tag is not set.
When i set the tag it works. it also works when i remove the umlaut in the
filename without setting the mp3tag.
So when no mp3-tag is set, it wants to take the filename as title, but then it
fails because of the umlaut in the filename.
 
 
  Good, that clears a lot of combinations.
 
  Now, in what encoding are your filenames?
 
Cheers,