Bug#1086943: vim-scripts: vimplate does not list templates without .vimplaterc
Package: vim-scripts
Version: 20210124.2
Severity: normal
Tags: upstream
X-Debbugs-Cc: d...@syn-net.org
Dear Maintainer,
calling `:Vimplate ` (in vim after `:plugadd! vimplate`) caused the
following error message:
:Vimplate Use of uninitialized value in opendir at /usr/bin/vimplate line 216.
The problem seems to occur because the `vimplate -listtemplate` command /
option fails:
❯ vimplate -listtemplates
Use of uninitialized value in opendir at /usr/bin/vimplate line 216.
readdir() attempted on invalid dirhandle DIR at /usr/bin/vimplate line 218.
❯ vimplate -listtemplates -d .
Use of uninitialized value in opendir at /usr/bin/vimplate line 216.
readdir() attempted on invalid dirhandle DIR at /usr/bin/vimplate line 218.
I expected the template files (*.tt) files to be listed of the current
/ given directory.
I then created a .vimplaterc file with `vimplate -createconfig` and adjusted
$Config:opt:dir option:
$Config::opt = {
dir => '/home/jkirk/.vim/vimplate-templates',
[...]
},
Vimplate then listed the template files nicely:
❯ vimplate -listtemplates
ansible-role
network-definition
ddj
new-kopano-user
journal
doc-review
helios-update
The man page vimplate(1) + /usr/share/doc/vim-scripts/README.Debian do not
mention the need of the .vimplaterc.
(I only then found the "Installation" section in
/usr/share/doc/vim-scripts/html/vimplate.html).
So there are two issues:
* I am not sure where I should have started reading the documentation
but maybe we could improve the documentation somehow?
* Vimplate does not list templates with the `-d` option without a .vimplaterc
file
As a side note:
# This is an example configuration.
# please see: http://napali.ch/vimplate
http://napali.ch/vimplate does not exist anymore.
Thanks for maintaining vim-scripts!
Best,
- Darsha
-- System Information:
Debian Release: 12.7
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-26-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vim-scripts depends on:
ii vim 2:9.0.1378-2
ii vim-gtk3 [vim] 2:9.0.1378-2
vim-scripts recommends no packages.
Versions of packages vim-scripts suggests:
pn ctags
ii libtemplate-perl 2.27-1+b5
pn perlsgml
-- no debconf information
Bug#1085517: kthresher: KeyError: "The cache has no package named 'linux-image-...'"
forwarded 1085517 https://github.com/rackerlabs/kthresher/issues/93 stop OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1085517: kthresher: KeyError: "The cache has no package named 'linux-image-...'"
Package: kthresher
Version: 1.4.1-2
Severity: normal
Tags: upstream
X-Debbugs-Cc: d...@syn-net.org
Dear Maintainer,
kthresher fails on systems (container) where the running kernel is
not installed:
root@tranquility:/tmp/autopkgtest.wBbOzr/build.4Yl/src# kthresher
INFO: No kernel packages available for autoremoval.
root@tranquility:/tmp/autopkgtest.wBbOzr/build.4Yl/src# kthresher -d
INFO: Attempting to read /etc/kthresher.conf.
INFO: Options found: ['include'].
INFO: Valid setting found "include"
INFO: include = /etc/kthresher.d/*.conf
INFO: Options: {'dry_run': True, 'headers': False, 'keep': 1, 'purge': False,
'verbose': False, 'include': '/etc/kthresher.d/*.conf'}
INFO: - DRY RUN -
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apt/cache.py", line 277, in __getitem__
rawpkg = self._cache[key]
~~~^
KeyError: 'linux-image-6.1.0-26-amd64'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/bin/kthresher", line 33, in
sys.exit(load_entry_point('kthresher==1.4.1', 'console_scripts',
'kthresher')())
^^
File "/usr/lib/python3/dist-packages/kthresher.py", line 475, in main
kthreshing(purge=False, headers=options["headers"], keep=options["keep"])
File "/usr/lib/python3/dist-packages/kthresher.py", line 266, in kthreshing
kernel_pkg = apt_cache["linux-image-%s" % current_kernel_ver]
~^^^
File "/usr/lib/python3/dist-packages/apt/cache.py", line 279, in __getitem__
raise KeyError("The cache has no package named %r" % key)
KeyError: "The cache has no package named 'linux-image-6.1.0-26-amd64'"
root@tranquility:/tmp/autopkgtest.wBbOzr/build.4Yl/src# uname -a
Linux tranquility 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1
(2024-09-30) x86_64 GNU/Linux
root@tranquility:/tmp/autopkgtest.wBbOzr/build.4Yl/src# dpkg -l | grep
linux-image
root@tranquility:/tmp/autopkgtest.wBbOzr/build.4Yl/src#
We enabled autopkgtest for this package and noticed this problem.
Yes, kthresher should handle this case, but I think this is a minor
issue for most systems where kthresher is used.
I will file a bug upstream and declare a autopkgtest restriction flaky
to prevent a RC bug for this.
Best,
- Darsha
Bug#1080999: cloud-init: Make dhcpcd the default dhcp client
Source: cloud-init Version: 22.4.2-1+deb12u1 Severity: normal X-Debbugs-Cc: d...@syn-net.org Dear Maintainer, as of v24.1 cloud-init made dhcpcd the default dhcp client, see: https://github.com/canonical/cloud-init/releases/tag/24.1 Please consider adjusting the Depends line to make dhcpcd the preferred choice (along with udhcpc and isc-dhcp-client). Thank you for maintaining cloud-init! Best, - Darsha
Bug#1069605: cifs-utils: When mounting a samba-share by a client with kernel 6.1.0-20-amd64, some subdirectories and files within the mounted share are missing
Hi, On Sun, 21 Apr 2024 13:39:36 +0200 mt22j wrote: > > When mounting a samba-share by a Debian Bookworm client, kernel > 6.1.0-20-amd64, on this client some subdirectories and files within the > mounted share are missing. Interesting. Can you tell us, what you mean by "some"? Or can you provide a before and after directory/file listing? Thx! Regards, - Darsha OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1053121: calamares: Welcome screen does not update power source status
Package: calamares Version: 3.2.61-1+b1 Severity: minor Dear Maintainer, when starting the Calamares installer is started (in Debian Live/Cinnamon), if the system is not connected to a power source, the installer reports "The system is not plugged in to a power source". This is fine. But when the user then connects a power source, the message does not disappear, making the user wonder if the power source is really connected. The message should disappear as soon as the power source is plugged in (and most probably vice-versa). Thanks for maintaining calamares! Best, - Darsha -- System Information: Debian Release: 12.1 APT prefers bookworm APT policy: (500, 'bookworm'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages calamares depends on: ii kpackagetool55.103.0-1 ii libboost-python1.74.0 [libboost-python1.74.0-py311] 1.74.0+ds1-21 ii libc62.36-9+deb12u1 ii libcrypt11:4.4.33-2 ii libgcc-s112.2.0-14 ii libkf5configcore55.103.0-2 ii libkf5coreaddons55.103.0-1 ii libkf5package5 5.103.0-1 ii libkf5parts5 5.103.0-1 ii libkpmcore12 22.12.3-1 ii libparted2 3.5-3 ii libpwquality11.4.5-1+b1 ii libpython3.113.11.2-6 ii libqt5core5a 5.15.8+dfsg-11 ii libqt5dbus5 5.15.8+dfsg-11 ii libqt5gui5 5.15.8+dfsg-11 ii libqt5network5 5.15.8+dfsg-11 ii libqt5qml5 5.15.8+dfsg-3 ii libqt5quick5 5.15.8+dfsg-3 ii libqt5quickwidgets5 5.15.8+dfsg-3 ii libqt5svg5 5.15.8-3 ii libqt5webkit55.212.0~alpha4-30 ii libqt5widgets5 5.15.8+dfsg-11 ii libqt5xml5 5.15.8+dfsg-11 ii libstdc++6 12.2.0-14 ii libyaml-cpp0.7 0.7.0+dfsg-8+b1 ii os-prober1.81 Versions of packages calamares recommends: ii btrfs-progs 6.2-1 ii squashfs-tools 1:4.5.1-1 calamares suggests no packages. -- no debconf information
Bug#990028: /usr/bin/mogrify-im6.q16: raw support requires ufraw-batch which is no longer in Debian
Hi, On Fri, 03 Sep 2021 22:00:12 + Debian FTP Masters wrote: > Source: imagemagick > Source-Version: 8:6.9.12.20+dfsg1-1 > Done: Bastien Roucariès If just stumbled over this: ❯ identify -format "%f: %wx%h\n" "DSC_0597.NEF" identify-im6.q16: delegate failed `'ufraw-batch' --silent --create-id=also --out-type=png --out-depth=16 --output='%u.png' '%i'' @ error/delegate.c/InvokeDelegate/1966. identify-im6.q16: unable to open image `/tmp/magick-vD_smqp7YJHGABZ2bxgam6OJlqxQ5NMN.ppm': No such file or directory @ error/blob.c/OpenBlob/2924. I am still running Debian/bullseye, but as far as I can see version 6.9.12.20+dfsg1-1 is only in experimental. Any plans to bring it to unstable? Apart from that, imagemagick-6.q16 + imagemagick-6.q16hdri do still have "Suggests: ufraw-batch"[1][2]. This should be removed. [1] https://salsa.debian.org/debian/imagemagick/-/blob/debian/lastest/debian/control?ref_type=heads#L200 [2] https://salsa.debian.org/debian/imagemagick/-/blob/debian/lastest/debian/control?ref_type=heads#L411 And finally: is there a workaround for this problem, as Debian/bullseye + bookworm still seem to be affected by this bug? Should we open a new issue or re-open this bug? Thx for maintaining! Best, - Darsha OpenPGP_signature Description: OpenPGP digital signature
Bug#1027136: xdg-desktop-portal: User service is not stopped when uninstalling xdg-desktop-portal
On 2022-12-28 19:11, Simon McVittie wrote: > On Wed, 28 Dec 2022 at 12:23:46 +0100, Darshaka Pathirana wrote: >> ❯ systemctl status --user stop xdg-desktop-portal >> Unit stop.service could not be found. > > This is the wrong command, hence the error message. Use: > > systemctl --user stop xdg-desktop-portal.service > > You can omit the .service extension as a shorthand, but you can't combine > status and stop in one command. Oh, thx for the pointer, "status" was added by mistake. I was in the "belief" (*sigh*, sorry!), that the service can not be stopped, once the service file / package has been removed. I took the error message as is. FTR, this it how it looks like after the packages is removed (and after the user service was started before): ❯ sudo apt remove xdg-desktop-portal ❯ ps -ax | grep xdg-desktop-portal 223206 ?Ssl0:00 /usr/libexec/xdg-desktop-portal 224646 pts/50 S+ 0:00 grep --color=auto xdg-desktop-portal ❯ systemctl --user status xdg-desktop-portal Warning: The unit file, source configuration file or drop-ins of xdg-desktop-portal.service changed on disk. Run 'systemctl --user daemon-reload' to reload units. ● xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; bad; vendor preset: enabled) Active: active (running) since Wed 2023-01-04 15:26:29 CET; 15min ago Main PID: 223206 (xdg-desktop-por) Tasks: 5 (limit: 18880) Memory: 1.7M CPU: 374ms CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/xdg-desktop-portal.service └─223206 /usr/libexec/xdg-desktop-portal Jan 04 15:26:29 executor systemd[4802]: Starting Portal service... Jan 04 15:26:29 executor systemd[4802]: Started Portal service. ❯ systemctl --user stop xdg-desktop-portal Warning: The unit file, source configuration file or drop-ins of xdg-desktop-portal.service changed on disk. Run 'systemctl --user daemon-reload' to reload units. ❯ systemctl --user status xdg-desktop-portal Unit xdg-desktop-portal.service could not be found. at 2023-01-04 15:39:42 +01:00 ❯ ps -ax | grep xdg-desktop-portal 238026 pts/50 S+ 0:00 grep --color=auto xdg-desktop-portal >> I think (the) xdg-desktop-portal user service(s) should be stopped before >> removing the package. Is that possible? > > Not really: maintainer scripts happen in the context of the overall system > (as root) and there is not really a good way to inject service-management > commands into user sessions. Other per-user services like PulseAudio, > Pipewire, gpg-agent and so on are not stopped when you remove them either. Ok. After all, the user one *can* manually stop the service after the package has been removed. And: "Failed connect to PipeWire: Couldn't connect to PipeWire" was also not shown anymore, after I started "xdg-desktop-portal". All is good. Please close the bug (and mark it as obsolete/invalid, if possible. I could not find how to do it). Thx for your support! Best, - Darsha OpenPGP_signature Description: OpenPGP digital signature
Bug#1027136: xdg-desktop-portal: User service is not stopped when uninstalling xdg-desktop-portal
Package: xdg-desktop-portal Version: 1.8.1-1 Severity: normal X-Debbugs-Cc: d...@syn-net.org Dear Maintainer, after uninstalling xdg-desktop-portal I noticed that the xdg-desktop-portal service was not stopped and could not be stopped after the package has been removed: ❯ systemctl status --user xdg-desktop-portal Warning: The unit file, source configuration file or drop-ins of xdg-desktop-portal.service changed on disk. Run 'systemctl --user daemon-reload' to reload units. ● xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; bad; vendor preset: enabled) Active: active (running) since Sun 2022-11-27 02:24:45 CET; 1 months 0 days ago Main PID: 26406 (xdg-desktop-por) Tasks: 6 (limit: 18880) Memory: 49.6M CPU: 13min 24.337s CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/xdg-desktop-portal.service └─26406 /usr/libexec/xdg-desktop-portal Nov 27 02:24:45 executor xdg-desktop-portal[26406]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Nov 27 02:24:45 executor xdg-desktop-portal[26406]: No module "libpipewire-module-adapter" was found Nov 27 02:24:45 executor xdg-desktop-portal[26406]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Nov 27 02:24:45 executor xdg-desktop-portal[26406]: No module "libpipewire-module-metadata" was found Nov 27 02:24:45 executor xdg-desktop-portal[26406]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Nov 27 02:24:45 executor xdg-desktop-portal[26406]: No module "libpipewire-module-session-manager" was found Nov 27 02:24:45 executor xdg-desktop-portal[26406]: core 0x55e09d2e9f10: can't find protocol 'PipeWire:Protocol:Native': Operation not supported Nov 27 02:24:45 executor xdg-desktop-por[26406]: Failed connect to PipeWire: Couldn't connect to PipeWire Nov 27 02:24:45 executor systemd[4802]: Started Portal service. Nov 27 02:25:15 executor xdg-desktop-por[26406]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list ❯ systemctl --user daemon-reload ❯ systemctl status --user stop xdg-desktop-portal Unit stop.service could not be found. ● xdg-desktop-portal.service Loaded: not-found (Reason: Unit xdg-desktop-portal.service not found.) Active: active (running) since Sun 2022-11-27 02:24:45 CET; 1 months 0 days ago Main PID: 26406 (xdg-desktop-por) CPU: 13min 24.353s CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/xdg-desktop-portal.service └─26406 /usr/libexec/xdg-desktop-portal I did the following to fix that: ❯ sudo apt install xdg-desktop-portal ❯ systemctl --user daemon-reload ❯ systemctl stop --user xdg-desktop-portal ❯ systemctl status --user xdg-desktop-portal ● xdg-desktop-portal.service - Portal service Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static) Active: inactive (dead) [...] ❯ sudo apt remove xdg-desktop-portal I think (the) xdg-desktop-portal user service(s) should be stopped before removing the package. Is that possible? Some rational: I do not use flatpak, but xdg-desktop-portal somehow got installed (either through steam or through chromium) and I noticed the following log entries: Jun 12 15:44:06 executor systemd[5560]: Starting Portal service... Jun 12 15:44:06 executor xdg-desktop-portal[14190]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Jun 12 15:44:06 executor xdg-desktop-portal[14190]: No module "libpipewire-module-protocol-native" was found Jun 12 15:44:06 executor xdg-desktop-portal[14190]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Jun 12 15:44:06 executor xdg-desktop-portal[14190]: No module "libpipewire-module-client-node" was found Jun 12 15:44:06 executor xdg-desktop-portal[14190]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Jun 12 15:44:06 executor xdg-desktop-portal[14190]: No module "libpipewire-module-client-device" was found Jun 12 15:44:06 executor xdg-desktop-portal[14190]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Jun 12 15:44:06 executor xdg-desktop-portal[14190]: No module "libpipewire-module-adapter" was found Jun 12 15:44:06 executor xdg-desktop-portal[14190]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Jun 12 15:44:06 executor xdg-desktop-portal[14190]: No module "libpipewire-module-metadata" was found Jun 12 15:44:06 executor xdg-desktop-portal[14190]: could not open /usr/lib/x86_64-linux-gnu/pipewire-0.3: No such file or directory Jun 12 15:44:06 executor xdg-desktop-portal[14190]: No module "libpipewire-module-session-manager" was found
Bug#1008887: .xsession-errors: ATTENTION! Currently cached group 1 is not equal to the current group
Package: cinnamon Version: 4.8.6-2+deb11u1 Severity: normal X-Debbugs-Cc: d...@syn-net.org Control: forwarded -1 https://github.com/linuxmint/cinnamon/issues/10083 Dear Maintainer, My `~/.xsession-errors:` (sometimes) gets spammed with the following lines: ``` ![1620829855,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1620829855,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1620829862,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1620829862,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1620829866,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1620829866,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ![1620829870,000,xklavier_evt_xkb.c:xkl_xkb_process_x_event/] ATTENTION! Currently cached group 1 is not equal to the current group from the event: 0 ``` ❯ grep "ATTENTION! Currently cached group" .xsession-errors.old | wc -l 269288 ❯ grep "ATTENTION! Currently cached group" .xsession-errors | wc -l 1133060 My inxi output currently looks like this: ❯ inxi -G -S System:Host: executor Kernel: 5.10.0-10-amd64 x86_64 bits: 64 Desktop: Cinnamon 4.8.6 Distro: Debian GNU/Linux 11 (bullseye) Graphics: Device-1: Intel UHD Graphics 620 driver: i915 v: kernel Device-2: Chicony Integrated Camera (1280x720@30) type: USB driver: uvcvideo Display: x11 server: X.Org 1.20.11 driver: loaded: modesetting unloaded: fbdev,vesa resolution: 1: 3840x2160 2: 3840x2160 OpenGL: renderer: Mesa Intel UHD Graphics 620 (KBL GT2) v: 4.6 Mesa 20.3.5 I currently can't reproduce the problem, there are times where the log file is quiet, but out of the sudden the lines get spammed into .xsession-errors. I already created an upstream issue (https://github.com/linuxmint/cinnamon/issues/10083) a while ago, but it got closed. (I asked the maintainer to re-open the issue, though.) I need help debugging this issue. I'd be glad for any pointers. Thank you and thx for maintaining Cinnamon in Debian! Best, - Darsha -- System Information: Debian Release: 11.3 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (99, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-10-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cinnamon depends on: ii cinnamon-common 4.8.6-2+deb11u1 ii cinnamon-control-center 4.8.2-1 ii cinnamon-desktop-data4.8.1-2 ii cinnamon-screensaver 4.8.1-3 ii cinnamon-session 4.8.0-3 ii cinnamon-settings-daemon 4.8.5-1 ii cjs 4.8.2-1 ii cups-pk-helper 0.2.6-1+b1 ii dbus 1.12.20-2 ii dconf-gsettings-backend [gsettings-backend] 0.38.0-2 ii gir1.2-accountsservice-1.0 0.6.55-3 ii gir1.2-caribou-1.0 0.4.21-7.1 ii gir1.2-clutter-1.0 1.26.4+dfsg-2 ii gir1.2-cmenu-3.0 4.8.3-1 ii gir1.2-cogl-1.0 1.22.8-2 ii gir1.2-cvc-1.0 4.8.1-2 ii gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1 ii gir1.2-gkbd-3.0 3.26.1-1 ii gir1.2-glib-2.0 1.66.1-1+b1 ii gir1.2-gnomedesktop-3.0 3.38.5-3 ii gir1.2-gtk-3.0 3.24.24-4+deb11u2 ii gir1.2-gtkclutter-1.01.8.4-4 ii gir1.2-keybinder-3.0 0.3.2-1.1 ii gir1.2-nemo-3.0 4.8.6-2 ii gir1.2-nm-1.01.30.0-2 ii gir1.2-nma-1.0 1.8.30-1 ii gir1.2-notify-0.70.7.9-3 ii gir1.2-pango-1.0 1.46.2-3 ii gir1.2-polkit-1.00.105-31+deb11u1 ii gir1.2-soup-2.4 2.72.0-2 ii gir1.2-timezonemap-1.0 0.4.6-2 ii gir1.2-upowerglib-1.00.99.1
Bug#1000822: ntpsigndsocket configuration option missing in ntp.conf(5) man page
Package: ntp Severity: normal X-Debbugs-Cc: d...@syn-net.org Dear Maintainer, the ntpd configuration option `ntpsigndsocket` is mentioned in the Samba Wiki "Time Synchronisation / Configuring Time Synchronisation on a DC": https://wiki.samba.org/index.php/Time_Synchronisation I had / have a hard time finding any documentation about it. It is definitely missing in the ntp.conf(5) man page, but also in the official(?) docs (so ntp-doc is most probably also affected): * https://www.eecis.udel.edu/~mills/ntp/html/miscopt.html * https://support.ntp.org/bin/view/Support/WebSearch?search=ntpsigndsocket&scope=all The option does exist in the ntp source though: https://salsa.debian.org/pkg-ntp-team/ntp/-/tree/master/html (search for `ntpsigndsocket`). Oh, and while writing this bug report I found an entry in the chrony.conf(5) man page: https://manpages.debian.org/bullseye/chrony/chrony.conf.5.en.html Can we use this in the ntp.conf too or did I miss something? Thanks very much for maintaining ntp! Best, - Darsha -- System Information: Debian Release: 11.1 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable'), (99, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-9-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ntp depends on: ii adduser3.118 ii libc6 2.31-13+deb11u2 ii libcap21:2.44-1 ii libedit2 3.1-20191231-2+b1 pn libopts25 ii libssl1.1 1.1.1k-1+deb11u1 ii lsb-base 11.1.0 ii netbase6.3 ii tzdata 2021a-1+deb11u1 Versions of packages ntp recommends: ii perl 5.32.1-4+deb11u2 pn sntp Versions of packages ntp suggests: pn ntp-doc
Bug#996035: AttributeError: 'NoneType' object has no attribute 'section'
forwarded 996035 https://github.com/rackerlabs/kthresher/issues/86 stop Hi Matus + Mika, thanks for your report. The issues has already been filed upstream: https://github.com/rackerlabs/kthresher/issues/86 Best, - Darsha OpenPGP_signature Description: OpenPGP digital signature
Bug#681694: brasero: Properly watch the child process state
forwarded 681694 https://gitlab.gnome.org/GNOME/brasero/-/issues/274 tags 681694 - fixed-upstream thanks The bug has been migrated to GNOME's GitLab instance and was incorrectly tagged as fixed-upstream. OpenPGP_signature Description: OpenPGP digital signature
Bug#680989: brasero: [libburnia plugin] Use traditional trailing padding of 300kB for TAO tracks
forwarded 680989 https://gitlab.gnome.org/GNOME/brasero/-/issues/275 tags 680989 - fixed-upstream The bug has been migrated to GNOME's GitLab instance and was incorrectly tagged as fixed-upstream. thanks OpenPGP_signature Description: OpenPGP digital signature
Bug#926476: apt search vs apt-cache search package list / output format
Hey, reviewing old bugs at the end of the (virtual) Debian-BSP 2021.. :) As it seems things haven't changed so far, but just wanted to send a ping to ask about the current status. Also two years later, I still think 'apt search x-window-manager' should at least list the available x-window-manager. Hope you are doing fine. All the best, - Darsha OpenPGP_signature Description: OpenPGP digital signature
Bug#987574: smartmontools: NVMe devices are scanned by default
Package: smartmontools Version: 7.2-1 Severity: normal Tags: upstream Dear Maintainer, after upgrading to Debian/bullseye I had to adapt/revert `/etc/smartd.conf`. For Debian/buster I had added a local modification to monitor my NVMe device. While reviewing the config file I learned that smartmontools/smartd is built with `--with-nvme-devicescan` (on Linux and Windows) since v7.0: https://github.com/smartmontools/smartmontools/releases/tag/RELEASE_7_0 So NVMe devices should work out-of-the-box. But I think the man page does not reflect that or is at least a bit confusing on that. Quoting smartd.conf(5): , | In the absence of a configuration file smartd will try to open all | available devices (see smartd(8) man page). A configuration file with | a single line 'DEVICESCAN -a' would have the same effect. ` So far so good, but quoting smartd(8): , | On startup, in the absence of the configuration file | /etc/smartd.conf, the smartd daemon first scans for all devices that | support SMART. The scanning is done as follows: | | LINUX: Examine all entries "/dev/hd[a-t]" for IDE/ATA devices, |and "/dev/sd[a-z]", "/dev/sd[a-c][a-z]" for ATA/SATA or SCSI/SAS |devices. Disks behind RAID controllers are not included. | |If directive '-d nvme' or no '-d' directive is specified, |examine all entries "/dev/nvme[0-99]" for NVMe devices. ` The default `/etc/smartd.conf` looks like this: ❯ grep "^DEVICESCAN" /etc/smartd.conf DEVICESCAN -d removable -n standby -m root -M exec /usr/share/smartmontools/smartd-runner So the directive `-d removable` is given, which makes the statement above confusing. What about rephrasing the "LINUX" part to: , |LINUX: Examine all entries "/dev/hd[a-t]" for IDE/ATA devices, | "/dev/sd[a-z]", "/dev/sd[a-c][a-z]" for ATA/SATA or SCSI/SAS | devices, and "/dev/nvme[0-99]" for NVMe devices. Disks | behind RAID controllers are not included. ` And later in smartd.conf(5): , | -a Equivalent to turning on all of the following Directives: | '-H' to check the SMART health status, '-f' to report failures of | Usage (rather than Prefail) Attributes, '-t' to track changes in | both Prefailure and Usage Attributes, '-l error' to report increases | in the number of ATA errors, '-l selftest' to report increases in | the number of Self- | Test Log errors, '-l selfteststs' to report changes of | Self-Test execution status, '-C 197' to report nonzero values | of the current pending sector count, and '-U 198' to report | nonzero values of the offline pending sector count. | | Note that -a is the default for ATA devices. If none of | these other Directives is given, then -a is assumed. ` As none of the Directives above are set in the default DEVICESCAN line, I assume "-a" kicks in which is "default for ATA devices". But what about NVMe devices, is -a assumed there too? As you can clearly see, I have not much knowledge about the internals of smartmontools/smartd, so please bear with me and lets try to phrase the documentation as clear as possible. Thank you very much. Best, - Darsha -- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages smartmontools depends on: ii debianutils 4.11.2 ii libc62.31-11 ii libcap-ng0 0.7.9-2.2+b1 ii libgcc-s110.2.1-6 ii libselinux1 3.1-3 ii libstdc++6 10.2.1-6 ii libsystemd0 247.3-3 ii lsb-base 11.1.0 smartmontools recommends no packages. Versions of packages smartmontools suggests: ii bsd-mailx [mailx] 8.1.2-0.20180807cvs-2 ii curl 7.74.0-1.2 ii gpg2.2.27-1 pn gsmartcontrol pn smart-notifier ii wget 1.21-1+b1 -- no debconf information
Bug#987513: vim-voom: Voomhelp can not be called if modeline is set
Package: vim-voom Version: 5.3-8 Severity: normal Dear Maintainer, after upgrading to Debian/bullseye I noticed the following error when calling :Voomhelp: Error detected while processing function voom#Help[39]..function voom#Help[34]..modelines: line 4207: E992: Not allowed in a modeline when 'modelineexpr' is off: foldtext=getline(v:foldstart).'...'.(v:foldend-v:foldstart ) I tried to debug the problem and could pin point the problem to the 'set modeline' option in my .vimrc. After removing that line or calling "set nomodeline" before ":Voomhelp" can be called without an error. I added "set modeline" into my .vimrc because it defaults to off in Debian for security reasons. (FTR, modelineexpr is not set in my configuration and defaults to off.) So now I wonder if this can be fixed somehow so that :Voomhelp can be called with modeline set. Thank you for maintaining vim-voom! Best, - Darsha -- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-voom depends on: ii vim 2:8.2.2434-3 ii vim-gtk3 [vim] 2:8.2.2434-3 ii vim-nox [vim] 2:8.2.2434-3 vim-voom recommends no packages. vim-voom suggests no packages. -- no debconf information
Bug#987498: vim-scripts: VimSokoban is broken in Debian/bullseye
Package: vim-scripts Version: 20210124 Severity: normal Dear Maintainer, just updated to Debian/bullseye and tested VimSokoban. Loaded and started Sokoban (in vim) with: :packadd VimSokoban :Sokoban but received: VIM SOKOBAN === ScoreKey ---- Level: 1»·X = soko# = wall Moves: 0$ = package . = home Pushes: 0 Options: h(left),j(down),k(up),l(right),u(undo),r(restart),n(next),p(previous) Could not find file /usr/share/vim-scripts/sokoban-levels/level1.sok Pressing any key leads to the following errors: Error detected while processing function 54_MoveDown[1]..54_MakeMove: line1: E121: Undefined variable: b:manPosLine line2: E121: Undefined variable: b:manPosCol line3: E121: Undefined variable: newManPosLine E116: Invalid arguments for function IsWall(newManPosLine, newManPosCol) line4: E121: Undefined variable: newManPosIsWall It think this is caused by this change: https://salsa.debian.org/vim-team/vim-scripts/-/commit/74839fc4a59b216e280fa1bf96add53f6b40c5da but unfortunately https://salsa.debian.org/vim-team/vim-scripts/-/blob/debian/sid/debian/patches/sokoboan_path.diff was not adjusted. My workaround is to set "g:SokobanLevelDirectory" manually: :packadd VimSokoban :let g:SokobanLevelDirectory = "/usr/share/vim-scripts/VimSokoban/plugin/VimSokoban/" :Sokoban Please adjust "g:SokobanLevelDirectory" in `sokoboan_path.diff`. Thanks for maintaining vim-scripts. Best, - Darsha -- System Information: Debian Release: bullseye/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-scripts depends on: ii vim 2:8.2.2434-3 ii vim-gtk3 [vim] 2:8.2.2434-3 ii vim-nox [vim] 2:8.2.2434-3 vim-scripts recommends no packages. Versions of packages vim-scripts suggests: pn ctags pn libtemplate-perl pn perlsgml -- no debconf information
Bug#982097: devede: Update devede to 4.16.0
Package: devede Severity: normal Dear Maintainer, please update devede to version 4.16.0: * version 4.16.0 (2019/10/13) Added support for creating HEVC video in Matroska files Changed distribution permissions to GPLv3 only Thank you! Best, - Darsha
Bug#977586: diodon: list of clipboard items not updating (database or disk is full)
Package: diodon Version: 1.10.0-1 Severity: normal Dear Maintainer, just noticed that Diodon stopped working quite a while ago (the list of clipboard items is very outdated and does not get updated). Restarted Diodon via shell: % diodon ** (diodon:30236): WARNING **: 11:36:53.137: zeitgeist-clipboard-storage.vala:438: Failed to clear items: GDBus.Error:org.gnome.zeitgeist.EngineError.DatabaseError: sql.vala:253: SQL Error: 13, database or disk is full But the disk is not full (yet :)): % df -h . FilesystemSize Used Avail Use% Mounted on /dev/mapper/vg0-home 50G 46G 1.6G 97% /home I *think* I can fix this by finding and deleting the database but it is unclear what caused this problem. Can you help? Thanks for your work! Regards, - Darsha -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages diodon depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2 ii libayatana-appindicator3-1 0.5.3-4 ii libc62.28-10 ii libdiodon0 1.10.0-1 ii libglib2.0-0 2.58.3-2+deb10u2 ii libgtk-3-0 3.24.5-1 ii libpeas-1.0-01.22.0-4 ii zeitgeist-core 1.0.1-1 diodon recommends no packages. diodon suggests no packages. -- no debconf information
Bug#977369: igerman98: "Tablet" missing in German (hunspell-de-at) dictionary
Source: igerman98 Severity: normal Dear Maintainer, just noticed that the word "Tablet" is missing: [1] https://www.duden.de/rechtschreibung/Tablet I believe the word belongs in "anglizismen-de_all.txt". Thx. Regards, - Darsha -- System Information: Debian Release: 10.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-0.bpo.2-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#961490: fwupd: version in stable too old, no updates possible
Hi, just wanted to let you know that I do *not* get the "Not compatible with org.freedesktop.fwupd version 1.2.5, requires >= 1.2.7" output/error here: % sudo fwupdmgr refresh Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz Downloading… [***] Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc % sudo fwupdmgr get-updates 2>/dev/null | grep -e "has firmware updates" -e "^ID" -e "^Update Version" UEFI Device Firmware has firmware updates: ID: com.lenovo.ThinkPadN20HT.firmware Update Version: 0.1.13 ID: com.lenovo.ThinkPadN20HT.firmware Update Version: 0.1.12 ID: com.lenovo.ThinkPadN20HT.firmware Update Version: 0.1.11 ID: com.lenovo.ThinkPadN20HT.firmware Update Version: 0.1.10 (Yes, I have a pending update). FYI: Package: fwupd Version: 1.2.5-2 and: % sudo fwupdmgr --version client version: 1.2.5 compile-time dependency versions gusb: 0.3.0 efivar: 37 daemon version: 1.2.5 20KF001GGE System Firmware (0.1.40) and UEFI Device Firmware (184.70.3626) have been updated recently. But my main reason for coming here is the fact that the (critical[1]) Firmware-Update for the Thunderbolt Controller[1][2] and the NVMe[2] is not detected: [1] https://pcsupport.lenovo.com/fi/en/solutions/ht508988 [2] https://fwupd.org/lvfs/devices/com.lenovo.ThinkPadN20TF.firmware [3] https://fwupd.org/lvfs/devices/com.lenovo.PM981.512GB_1TB.firmware % sudo fwupdmgr get-devices | grep -v Serial ThinkPad X280 Thunderbolt Controller DeviceId: a4ff56667c8863bbfec8c52b6aa02b51a98a8fb2 Guid: 4808eca4-fd4a-50e6-9e8d-bfd813f063da <- TBT-01091704-native Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|registered Vendor: Lenovo VendorId: TBT:0x0109 Version: 12.00 Icon: computer Created: 2020-06-29 20KF001GGE System Firmware DeviceId: 5a566863d357fb728a620cdf235632fb9bc99f5f Guid: 508f7539-1ad6-48b9-8680-38377535009d Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Version: 0.1.40 VersionLowest:0.0.1 Icon: computer Created: 2020-06-29 UEFI Device Firmware DeviceId: 093ef0be8328a2c4ed2fe55cd36aae3171b92ade Guid: 6d28cd9f-7bcd-4fb9-9f10-0372e2962fc4 Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Version: 184.70.3626 VersionLowest:0.0.1 Icon: audio-card Created: 2020-06-29 UEFI Device Firmware DeviceId: ca368aebcf7da847029e9f2520ec55fb7a036b31 Guid: 3f4a527b-6588-45b8-b2d3-dc61189b63cb Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Version: 0.1.4 VersionLowest:0.1.4 Icon: audio-card Created: 2020-06-29 SAMSUNG MZVLB512HAJQ-000L7 DeviceId: e11623b2caa18fee292058a5c09ca4e6152f7ecf Guid: 47335265-a509-51f7-841e-1c94911af66b <- NVME\VEN_144D&DEV_A808 Guid: 8fd4ca73-d0ae-52e8-8977-461435c6f4cf <- NVME\VEN_144D Guid: 79d6cfae-a5a2-5936-9248-5aebd23480f7 <- SAMSUNG MZVLB512HAJQ-000L7 Summary: NVM Express Solid State Drive Plugin: nvme Flags: internal|updatable|require-ac|supported|registered|needs-reboot Vendor: Samsung Electronics Co Ltd VendorId: NVME:0x144D Version: 3L2QEXA7 Icon: drive-harddisk Created: 2020-06-29 ST2000LM007-1R8174 DeviceId: 8b2e996216566cd71a3ec9c03bce8a9827a277e0 Guid: fe3873a5-8d96-5cd6-ae8e-aec49f11ed82 <- IDE\ST2000LM007-1R8174__EB01 Guid: a3cbe2af-31fd-5848-a7f9-44a95fa5f44d <- IDE\0ST2000LM007-1R8174__ Guid: 0f5e4f1e-1732-52a1-88d9-118952f0ffb3 <- ST2000LM007-1R8174 Summary: ATA Drive Plugin: ata Flags:updatable|require-ac|registered|needs-reboot Version: EB01 Icon: drive-harddisk Created: 2020-06-29 % sudo fwupdmgr get-updates 1>/dev/null No upgrades for 20KF001GGE System Firmware, current is 0.1.40: 0.1.30=older, 0.1.29=older, 0.1.28=older,
Bug#954173: vlc: man page and help should mention MRL/URL v4l2:// to open webcam
Package: vlc
Version: 3.0.8-0+deb10u1
Severity: minor
Dear Maintainer,
the documentation is missing a few words on how to open a webcam.
I tried the (advanced) help:
% vlc --longhelp --advanced | grep -i webcam
VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)
% vlc --longhelp --advanced | grep -i v4l2://
VLC media player 3.0.8 Vetinari (revision 3.0.8-0-gf350b6b5a7)
and the man page but could not find anything.
The "URL syntax" section seems like a good place to add a line:
% vlc --longhelp --advanced
[...]
URL syntax:
file:///path/file Plain media file
http://host[:port]/fileHTTP URL
ftp://host[:port]/file FTP URL
mms://host[:port]/file MMS URL
screen:// Screen capture
dvd://[device] DVD device
vcd://[device] VCD device
cdda://[device]Audio CD device
udp://[[]@[][:]]
UDP stream sent by a streaming server
vlc://pause: Pause the playlist for a certain time
vlc://quit Special item to quit VLC
[...]
I would suggest:
v4l2://[device]Video4Linux capture device (i.e. USB webcams,
TV tuners)
Mentioning 'v4l2' in the 'ITEMS' of vlc(1) would be nice too:
ITEMS
VLC recognizes several URL-style items:
*.mpg, *.vob, *.avi, *.mp3, *.ogg, *.opus
Various multimedia file formats
dvd://[][@][#[][:[][:]]]
DVD device (for instance dvd:///dev/dvd). The raw device is
optional and must have been prepared beforehand.
vcd://[][@{E|P|E|T|S}[]]
VCD device (for instance vcd:///dev/cdrom).
udp://[@[][:]]
UDP stream, such as one sent by VLS or another VLC. Usually
"udp://" is enough.
http://[:]/[]
HTTP stream
rtsp://[:]/
RTSP Video On Demand stream
vlc://
Execute a playlist command. Commands are: pause (pause execution
of other items), and quit (close VLC).
I would suggest:
v4l2://[device]
Video4Linux capture device (i.e. USB webcams, TV tuners). The
device defaults to "/dev/video0".
I am fine with providing a patch if you are ok with my suggestion. I didn't
file an upstream bug (yet).
Please let me know what you think.
Regards && thank you for maintaining vlc,
- Darsha
-- System Information:
Debian Release: 10.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-8-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vlc depends on:
ii vlc-bin 3.0.8-0+deb10u1
ii vlc-plugin-base 3.0.8-0+deb10u1
ii vlc-plugin-qt3.0.8-0+deb10u1
ii vlc-plugin-video-output 3.0.8-0+deb10u1
Versions of packages vlc recommends:
ii vlc-l10n 3.0.8-0+deb10u1
pn vlc-plugin-notify
pn vlc-plugin-samba
pn vlc-plugin-skins2
pn vlc-plugin-video-splitter
pn vlc-plugin-visualization
vlc suggests no packages.
Versions of packages libvlc-bin depends on:
ii libc62.28-10
ii libvlc5 3.0.8-0+deb10u1
Versions of packages libvlc5 depends on:
ii libc62.28-10
ii libvlccore9 3.0.8-0+deb10u1
Versions of packages libvlc5 recommends:
ii libvlc-bin 3.0.8-0+deb10u1
Versions of packages vlc-bin depends on:
ii libc6 2.28-10
ii libvlc-bin 3.0.8-0+deb10u1
ii libvlc5 3.0.8-0+deb10u1
Versions of packages vlc-plugin-base depends on:
ii liba52-0.7.4 0.7.4-19
ii libaom0 1.0.0-3
ii libarchive13 3.3.3-4+deb10u1
ii libaribb24-0 1.0.3-2
ii libasound2 1.1.8-1
ii libass9 1:0.14.0-2
ii libavahi-client3 0.7-4+b1
ii libavahi-common3 0.7-4+b1
ii libavc1394-0 0.5.4-5
ii libavcodec58 7:4.1.4-1~deb10u1
ii libavformat587:4.1.4-1~deb10u1
ii libavutil56 7:4.1.4-1~deb10u1
ii libbasicusageenvironment12018.11.26-1.1
ii libbluray2 1:1.1.0-1
ii libc62.28-10
ii libcairo21.16.0-4
ii libcddb2 1.3.2-6
ii libchromaprint1 1.4.3-3
ii libcrystalhd31:0.0~git20110715.fdd2f19-13
ii libdbus-1-3 1.12.16-1
ii libdc1394-22 2.2.5-1
ii libdca0 0.0.6-1
ii li
Bug#931024: kthresher: Uses Package.section, incompatible with python-apt 1.9
forwarded 931024 https://github.com/rackerlabs/kthresher/issues/80 thanks Hi Julian, On 6/24/19 7:11 PM, Julian Andres Klode wrote: > Package: kthresher > Severity: normal > User: de...@lists.debian.org > Usertags: apt-1.9.0 > > According to codesearch.d.n, kthresher contains trhe line: > > "kernel" in pkg.section and re.match(kernel_image_regex, pkg_name) > > The use of the section on packages has been deprecated ages ago, as > it can vary between versions. > > This causes kthresher to stop working with apt 1.9, so please migrate to > using a version's section after the buster release. Thanks for the bug report. I've opened an upstream issue[1] to handle this bug. [1] https://github.com/rackerlabs/kthresher/issues/80 Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#928886: iwgetid: document exit codes in man page
Package: wireless-tools Version: 30~pre9-12+b1 Severity: minor Dear Maintainer, please document the Exit Codes of iwgetid. For example, if the wireless network is not connected then iwgetid returns the exit code 255: # sudo iwgetid -r # echo $? 255 Are there more? Thank you for maintainting wireless-tools! Regards, - Darsha -- System Information: Debian Release: 9.9 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-0.bpo.4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages wireless-tools depends on: ii libc62.24-11+deb9u4 ii libiw30 30~pre9-12+b1 wireless-tools recommends no packages. wireless-tools suggests no packages. -- no debconf information
Bug#924270: O: keepassx -- Cross Platform Password Manager
On 3/11/19 4:29 AM, Shengjing Zhu wrote:> On Mon, Mar 11, 2019 at 3:15 AM Reinhard Tartler wrote: >> >> Package: wnpp >> Severity: normal >> >> Keepassx is a graphical password manager, using the Qt4 toolkit. I'm no >> longer using this package and have personally switched to >> 'password-store'. Unfortunately, I've also failed to get a response >> from upstream from >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920616 - which >> recommends to replace keepassx with keepassxc, a community fork, >> possibly because of unresponsive upstream. >> >> I am undecided whether or not this package should be included in Debian >> 10 (aka buster). It clearly is useful to many people, but its long-term >> maintenance is unclear. >> >> I'd encourage people interested in picking up this package to coordinate >> with Julian Klode (CC'ed), the Debian keepassxc maintainer. >> > > I'm also long-time user of keepassx. > > I checked the upstream. In surprise, I found the master version has > switched to Qt-5. And the upstream author is Felix Geyer, who is DD as > well. > > Felix, could you have some inputs here? > > In person, I hope keepassx is in buster. I can help uploading the > master version(with Qt-5) if Qt-4 is really needed to be removed from > buster. However I'm unsure if RT is fine with this big change(I assume > it's not ok). Whoever cares: I've been using keepassx for years now and switched to keepassxc just because of this issue without any troubles. If long-term maintenance is unclear we (Debian) maybe should avoid going that way... JM2C && HAND, - Darsha signature.asc Description: OpenPGP digital signature
Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)
Hey, On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk wrote: > On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote: > > Hello Everyone, > > I own a qnap ts-119pII with a similar cpu. > > > > See attached file with several debugging attempts. I took some time and wanted to reproduce and test this issue. > > If I read [1] right, then the UXTH instruction is just supported > > on ARMv6 or later. > > Looking at the code, the bug seems to be in > https://sources.debian.org/src/ghc/8.4.4+dfsg1-2/debian/patches/llvm-arm-unknown-linux-gnueabi.patch/ > > ARM1136JF-S is ARM11, which is ARMv6. > arm9e would be correct here instead of arm1136jf-s. > > Due to the static-only nature of the ghc ecosystem the fix would then > require a complete rebuild of all Haskell packages on armel, but with > the buildds otherwise mostly idle now this should be finished within > 2-3 days. First I tried to reproduce the crash on one of our porterboxes[4] `amdahl` (where I could not reproduce the bug, git-annex runs just fine), but I only much later figured out that it run armv8l: [4] https://db.debian.org/machines.cgi?host=amdahl dpat@amdahl ~ % export sessionid=913555 dpat@amdahl ~ % schroot -b -c sid_armel-dchroot -n $sessionid I: 00check: Untarring chroot environment. This might take a minute or two. I: 99porterbox-extra-sources: o To install build dependencies run I: 99porterbox-extra-sources: dd-schroot-cmd -c 915333 apt-get update I: 99porterbox-extra-sources: followed by build-dep/install as appropriate in the host system. I: 99porterbox-extra-sources: o If you started this session with schroot -b, please do not forget to run I: 99porterbox-extra-sources: schroot --end-session -c 915333 I: 99porterbox-extra-sources: when you no longer need this environment. 915333 schroot -b -c sid_armel-dchroot -n $sessionid 9.08s user 5.17s system 126% cpu 11.293 total (sid_armel-dchroot)dpat@amdahl ~ % uname -a Linux amdahl 4.9.0-8-arm64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) armv8l GNU/Linux I also tried on `abel` but its a armv7l. I then wanted to setup a qemu-arm environment but I am stuck finding out which machine/cpu option would be correct. I found [1] and [2] which states that the CPU "Feroceon 88FR131 rev 1 (v5l)" is a actually a Marvell Kirkwood 88F6281. (Ok, [3] says that qnap ts-11x runs on Kirkwood system-on-chip (SoC) from Marvell). [1] https://www.chainsawonatireswing.com/2012/01/07/find-out-which-cpu-your-synology-diskstation-uses/ [2] https://www.7-cpu.com/cpu/Kirkwood.html [3] https://www.debian.org/releases/stable/armel/ch02s01.html.en (see 2.1.4) So, is it possible to emulate a armv5 and if yes, how? Thanks. Regards from the Debian BSP201904, Salzburg, - Darsha signature.asc Description: OpenPGP digital signature
Bug#926476: apt search vs apt-cache search package list / output format
Package: apt Version: 1.4.9 Severity: normal Dear Maintainer, Please look at the following output: % apt search x-window-manager Sorting... Done Full Text Search... Done matchbox-themes-extra/stable,stable 0.3-4 all extra themes for matchbox-window-manager matchbox-window-manager/stable 1.2-osso21-2+b1 amd64 window manager for resource-limited systems xorg/stable,now 1:7.7+19 amd64 [installed,automatic] X.Org X Window System % apt-cache search x-window-manager 9wm - X11 window manager inspired by Plan 9's rio aewm - minimalist window manager for X11 aewm++ - minimal window manager written in C++ afterstep - window manager with the NEXTSTEP look and feel awesome - highly configurable X window manager blackbox - Window manager for X bspwm - Binary space partitioning window manager [...] wm2 - small, unconfigurable window manager wmaker - NeXTSTEP-like window manager for X wmii - lightweight tabbed and tiled X11 window manager, version 3 xfwm4 - window manager of the Xfce project xmonad - Lightweight X11 window manager written in Haskell xorg - X.Org X Window System amiwm - The Amiga look alike window manager notion - tiling tabbed window manager designed for keyboard users % apt-cache search x-window-manager | wc -l 59 There are two issues here: * [1] The list of packages differ (3 vs 59 packages) * [2] The output format is not the same (2 lines + empty line vs 1 line per package) Given that the man page of apt(8) states the following , | The apt(8) commandline is designed as an end-user tool and it may change behavior between | versions. While it tries not to break backward compatibility this is not guaranteed either if a | change seems beneficial for interactive use. | | All features of apt(8) are available in dedicated APT tools like apt-get(8) and apt-cache(8) as | well. apt(8) just changes the default value of some options (see apt.conf(5) and specifically | the Binary scope). So you should prefer using these commands (potentially with some additional | options enabled) in your scripts as they keep backward compatibility as much as possible. ` we should be ok with [2] but we should document why the output looks different and - if possible - how to change the output format. But shouldn't the package list be the same? Or shouldn't there be a setting to archive that and shouldn't that be documented? After browsing the source (together with zeha, thx!), we found how to force apt search to output in the "traditional" way: apt -oAPT::Cache::Search::Version=1 search x-window-manager Thank you for looking into this and please tell us what we can do to help. Regards from the Debian-BSP, Salzburg :), - Darsha -- Package-specific info: -- apt-config dump -- APT ""; APT::Architecture "amd64"; APT::Build-Essential ""; APT::Build-Essential:: "build-essential"; APT::Install-Recommends "false"; APT::Install-Suggests "0"; APT::Sandbox ""; APT::Sandbox::User "_apt"; APT::Authentication ""; APT::Authentication::TrustCDROM "true"; APT::NeverAutoRemove ""; APT::NeverAutoRemove:: "^firmware-linux.*"; APT::NeverAutoRemove:: "^linux-firmware$"; APT::NeverAutoRemove:: "^linux-image-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^linux-image-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^linux-image-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^linux-headers-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^linux-headers-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^linux-image-extra-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^linux-signed-image-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^kfreebsd-image-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^kfreebsd-headers-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^gnumach-image-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^gnumach-image-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^.*-modules-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^.*-modules-4\.19\.0-0\.bpo\.1-amd64-unsigned$"; APT::NeverAutoRemove:: "^.*-modules-4\.19\.0-0\.bpo\.2-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-4\.18\.0-0\.bpo\.1-amd64$"; APT::NeverAutoRemove:: "^.*-kernel-4\.19\.0-0\.bpo\
Bug#919457: [kthresher] cron job ERROR: No argument used
Hi Leandro, On 1/16/19 10:19 AM, Leandro Penz wrote: > Package: kthresher > Version: 1.3.1-2 > Severity: important > > --- Please enter the report below this line. --- > > Cron job output received by email: > /etc/cron.daily/kthresher: > ERROR: No argument used. > usage: kthresher [-h] [-c FILE] [-d] [-H] [-k [N]] [-p] [-s] [-v] [-V] > > Purge Unused Kernels. > > optional arguments: > -h, --helpshow this help message and exit > -c FILE, --config FILE > Config file, default is /etc/kthresher.conf > -d, --dry-run List unused kernel images available to > purge(dry run). > Is always verbose. > -H, --headers Include the search for kernel headers. > -k [N], --keep [N]Number of kernels to keep, default 1. > -p, --purge Purge Unused Kernels. > -s, --show-autoremoval > Show kernel packages available for autoremoval. > -v, --verbose Be verbose. > -V, --version Print version. > run-parts: /etc/cron.daily/kthresher exited with return code 1 > > Package was just installed. Looks like there's something missing in > the cron job. Thank you for your feedback. I am in contact with upstream and we are talking about how the default behavior should look like and he is currently working on a solution for this. Apart from that, the usage description looks like every argument is optional, so kthresher should at least do "something" without an argument or the usage description should be updated to reflect that. Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#918607: ITP: kthresher -- Purge Unused Kernels
Hi Philipp, On 1/16/19 12:51 AM, Philipp Kern wrote: > Am 07.01.2019 um 19:30 schrieb Darshaka Pathirana: >> * Package name: kthresher >> Version : 1.3.1 >> Upstream Author : Rackspace US, Inc. >> * URL : https://github.com/rackerlabs/kthresher >> * License : Apache >> Programming Lang: Python >> Description : Purge Unused Kernels >> >> Tool to remove unused kernels that were installed automatically >> This tool removes those kernel packages marked as candidate for autoremoval. >> Those packages are generally installed via Unattended upgrade or >> meta-packages. By default the latest kernel and manual installations are >> marked to Never Auto Remove. > > it looks like this doesn't support Python 3 yet and I suspect that new > packages should. I'd suggest that instead of distutils' LooseVersion, > which was never meant for that, you use apt_pkg.version_compare. To be > fair it's not quite a Debian revision to parse but it's close enough > that the tokenization from our algorithm should work fine to sort kernel > versions. Thank you for your feedback (I have forwarded your comment to the upstream issue/PR[2]). Apart of the distutils.LooseVersion problem, there have been also some other things in kthresher with Python 3 problems. So yes, kthresher is currently lacking Python 3 support. But upstream is working on it[1][2] and a new release is on the way. [1] https://github.com/rackerlabs/kthresher/issues/53 [2] https://github.com/rackerlabs/kthresher/pull/61/ Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#918607: ITP: kthresher -- Purge Unused Kernels
Hi Eduard,
On 1/7/19 10:53 PM, Eduard Bloch wrote:> * Darshaka Pathirana [Mon, Jan 07
2019, 07:30:24PM]:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Darshaka Pathirana
>>
>> * Package name: kthresher
>> Version : 1.3.1
>> Upstream Author : Rackspace US, Inc.
>> * URL : https://github.com/rackerlabs/kthresher
>> * License : Apache
>> Programming Lang: Python
>> Description : Purge Unused Kernels
>>
>> Tool to remove unused kernels that were installed automatically
>> This tool removes those kernel packages marked as candidate for autoremoval.
>> Those packages are generally installed via Unattended upgrade or
>> meta-packages. By default the latest kernel and manual installations are
>> marked to Never Auto Remove.
>
> Please point out the difference to "deborphan --guess-kernel" somewhere
> along the lines.
I've forwarded your question to the upstream developer Tony Garcia
and this is his answer:
,
| Here the response with deborphan, first of all I acknowledge I was not aware
of
| this package, but after poking a bit with it I wasn't able to find a way to do
| what kthresher does, few points:
|
| - kthresher is focused on kernel images and headers
| - deborphan is focused on libraries with extension to other type of packages,
| there is one related to kernels but is only kernel modules:
|
| # deborphan --help | grep kernel
| --guess-kernel Try to report kernel modules.
|
| Man pages explains that it tries to find kernel modules only, not kernel
| images:
|
| --guess-kernel This option tries to find kernel-modules. It tries to match
(-modules|^nvidia-kernel)-.*[0-9]+\.[0-9]+\.[0-9]+.
|
|
| - kthresher will only remove packages listed as candidates for autoremoval,
| will not remove: running kernel, latest kernel nor unexplicitly kernels
| installed.
| - Did not find a way to remove kernels with deborphan.
| - kthresher is meant to be executed through a cronjob/timer to purge old
| kernels on a nightly basis
|
| This is an example of both (kthresher and deborphan) being executed on a
server with multiple kernels:
|
| # deborphan --guess-kernel
| libxapian30
| libxenstore3.0
|
| ## Here kthresher is showing the available kernel packages for autoremoval:
|
| # python3 kthresher.py -s
| INFO: List of kernel packages available for autoremoval:
| INFO:Version Package
| INFO:4.9.30-2+deb9u5 linux-headers-4.9.0-3-all-amd64
| INFO:4.9.30-2+deb9u5 linux-headers-4.9.0-3-amd64
| INFO:4.9.30-2+deb9u5 linux-headers-4.9.0-3-common
| INFO:4.9.30-2+deb9u5 linux-headers-4.9.0-3-common-rt
| INFO:4.9.30-2+deb9u5 linux-headers-4.9.0-3-rt-amd64
| INFO:4.9.65-3+deb9u1 linux-headers-4.9.0-4-all-amd64
| INFO:4.9.65-3+deb9u1 linux-headers-4.9.0-4-amd64
| INFO:4.9.65-3+deb9u1 linux-headers-4.9.0-4-common
| INFO:4.9.65-3+deb9u1 linux-headers-4.9.0-4-common-rt
| INFO:4.9.65-3+deb9u1 linux-headers-4.9.0-4-rt-amd64
| INFO:4.9.65-3+deb9u2 linux-headers-4.9.0-5-all-amd64
| INFO:4.9.65-3+deb9u2 linux-headers-4.9.0-5-amd64
| INFO:4.9.65-3+deb9u2 linux-headers-4.9.0-5-common
| INFO:4.9.65-3+deb9u2 linux-headers-4.9.0-5-common-rt
| INFO:4.9.65-3+deb9u2 linux-headers-4.9.0-5-rt-amd64
| INFO:4.9.88-1+deb9u1 linux-headers-4.9.0-6-all-amd64
| INFO: 4.9.110-3+deb9u2 linux-headers-4.9.0-7-all-amd64
| INFO:4.9.30-2+deb9u5 linux-image-4.9.0-3-amd64
| INFO:4.9.30-2+deb9u5 linux-image-4.9.0-3-rt-amd64
| INFO:4.9.65-3+deb9u1 linux-image-4.9.0-4-amd64
| INFO:4.9.65-3+deb9u1 linux-image-4.9.0-4-rt-amd64
| INFO:4.9.65-3+deb9u2 linux-image-4.9.0-5-amd64
| INFO:4.9.65-3+deb9u2 linux-image-4.9.0-5-rt-amd64
|
| ## Here kthresher is attempting to remove all the candidates of headers and
| ## images for autoremoval keeping 0 (dry-run)
|
| # python3 kthresher.py -v -d -H -k0
| INFO: Attempting to read /etc/kthresher.conf.
| INFO: Config file /etc/kthresher.conf is empty or does not exist, ignoring.
| INFO: Options: {'purge': False, 'headers': True, 'keep': 0, 'verbose': True,
'dry_run': True}
| INFO: - DRY RUN -
| INFO: Running kernel is linux-image-4.9.0-7-amd64 v[4.9.110-1]
| INFO: Attempting to keep 0 kernel package(s)
| INFO: Found 5 kernel image(s) installed and available for autoremoval
| INFO: Pre-sorting: ['4.9.88-1+deb9u1', '4.9.65-3+deb9u1', '4.9.30-2+deb9u5',
'4.9.65-3+deb9u2', '4.9.110-3+deb9u2']
| INFO: Post-sorting: ['4.9.30-2+deb9u5', '4.9.65-3+deb9u1', '4.9.65-3+deb9u2',
'4.9.88-1+deb9u1', '4.9.110-3+deb9u2']
| INFO: Purging packages from version: 4.9.30-2+deb9u5
| INFO: Purging: linux-image-4.9.0-3-amd64
| INFO: Purgin
Bug#919247: kthresher: cronjob exits with error after package removal
Hi Andreas, On 1/14/19 5:33 AM, Andreas Beckmann wrote: > Package: kthresher > Version: 1.3.1-2 > Severity: important > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your packages cronjob exits with > error after the package has been removed. > > From the attached log (scroll to the bottom...): > > 0m28.1s INFO: Package kthresher contains cron file: /etc/cron.daily/kthresher > 0m28.1s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmpTGHRnl', > '/etc/cron.daily/kthresher'] > 0m28.1s ERROR: Command failed (status=1): ['chroot', > '/srv/piuparts/tmp/tmpTGHRnl', '/etc/cron.daily/kthresher'] Thanks for the pointer. I'll have a look at this and will fix it! Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#918607: ITP: kthresher -- Purge Unused Kernels
Package: wnpp Severity: wishlist Owner: Darshaka Pathirana * Package name: kthresher Version : 1.3.1 Upstream Author : Rackspace US, Inc. * URL : https://github.com/rackerlabs/kthresher * License : Apache Programming Lang: Python Description : Purge Unused Kernels Tool to remove unused kernels that were installed automatically This tool removes those kernel packages marked as candidate for autoremoval. Those packages are generally installed via Unattended upgrade or meta-packages. By default the latest kernel and manual installations are marked to Never Auto Remove.
Bug#918603: ITP: recap -- Generates reports of various information about the server
Package: wnpp Severity: wishlist Owner: Darshaka Pathirana * Package name: recap Version : 1.3.1 Upstream Author : Rackspace US, Inc. * URL : https://github.com/rackerlabs/recap * License : GPL-2.0+ Description : Generates reports of various information about the server This program is intended to be used as a companion for the reporting provided by sysstat. It will create a set of reports summarizing hardware resource utilization. The script also provides optional reporting on a web server, MySQL and network connections.
Bug#904726: wpasupplicant: Problem switching wireless/WIFI networks: No beacon heard and the time event is over already...
Package: wpasupplicant Version: 2:2.4-1+deb9u1 Severity: normal Dear Maintainer, "Sometimes" I have problems switching the wireless networks. (Sometimes means, that this problem does not occur every time but I could not figure out when it happens). For example, when connecting from SSID: Debconf18 to DebConf18-TP-5GHz: % nmcli c show | grep DebConf DebConf18-TP-5GHz 6c9c0d46-4c94-4d8f-a03f-86c8d36416f5 802-11-wireless -- Auto DebConf18 a6ec957f-425c-4f3f-a9b5-5e14abfeb0a9 802-11-wireless wlp59s0 DebConf18-1 836e3919-070a-4fc1-8b5e-4e2cb66c511a 802-11-wireless -- % nmcli c up 6c9c0d46-4c94-4d8f-a03f-86c8d36416f5 The log shows me the following lines: Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.5910] manager: NetworkManager state is now DISCONNECTED Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.5912] device (wlp59s0): Activation: starting connection 'DebConf18-TP-5GHz' (6c9c0d46-4c94-4d8f-a03f-86c8d 36416f5) Jul 27 08:08:09 executor kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready Jul 27 08:08:09 executor nm-dispatcher[8676]: req:6 'down' [wlp59s0]: new request (1 scripts) Jul 27 08:08:09 executor nm-dispatcher[8676]: req:6 'down' [wlp59s0]: start running ordered scripts... Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.5980] sup-iface[0x7fb6a4004f10,wlp59s0]: connection disconnected (reason -3) Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.5981] device (wlp59s0): supplicant interface state: completed -> disconnected Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.5999] device (wlp59s0): state change:disconnected -> prepare (reason 'none') [30 40 0] Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6000] manager: NetworkManager state is now CONNECTING Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6038] device (wlp59s0): set-hw-addr: reset MAC address to A0:C5:89:A4:36:DE (preserve) Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6085] device (wlp59s0): state change:prepare -> config (reason 'none') [40 50 0] Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6086] device (wlp59s0): Activation: (wifi) access point 'DebConf18-TP-5GHz' has security, but secrets are required. Jul 27 08:08:09 executor kernel: IPv6: ADDRCONF(NETDEV_UP): wlp59s0: link is not ready Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6086] device (wlp59s0): state change:config -> need-auth (reason 'none') [50 60 0] Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6122] device (wlp59s0): state change:need-auth -> prepare (reason 'none') [60 40 0] Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6135] device (wlp59s0): state change:prepare -> config (reason 'none') [40 50 0] Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6137] device (wlp59s0): Activation: (wifi) connection 'DebConf18-TP-5GHz' has security, and secrets exist. No new secrets needed. Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6137] Config: added 'ssid' value 'DebConf18-TP-5GHz' Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6137] Config: added 'scan_ssid' value'1' Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6137] Config: added 'key_mgmt' value 'WPA-PSK' Jul 27 08:08:09 executor NetworkManager[4720]: [1532671689.6137] Config: added 'psk' value '' --- [3x the following] --- Jul 27 08:08:27 executor kernel: iwlwifi :3b:00.0: No beacon heard and the time event is over already... Jul 27 08:08:27 executor kernel: wlp59s0: Connection to AP d4:6e:0e:65:ab:70 lost Jul 27 08:08:32 executor kernel: wlp59s0: aborting authentication with d4:6e:0e:65:ab:70 by local choice(Reason: 3=DEAUTH_LEAVING) Jul 27 08:08:32 executor NetworkManager[4720]: [1532671712.2425] device (wlp59s0): supplicant interface state: authenticating -> disconnected Jul 27 08:08:32 executor NetworkManager[4720]: [1532671712.3425] device (wlp59s0): supplicant interface state: disconnected -> scanning Jul 27 08:08:34 executor wpa_supplicant[950]: wlp59s0: SME: Trying to authenticate with d4:6e:0e:65:ae:bb (SSID='DebConf18-TP-5GHz' freq=5500 MHz) Jul 27 08:08:34 executor kernel: wlp59s0: authenticate with d4:6e:0e:65:ae:bb Jul 27 08:08:34 executor kernel: wlp59s0: send auth to d4:6e:0e:65:ae:bb (try 1/3) Jul 27 08:08:34 executor kernel: wlp59s0: authenticated Jul 27 08:08:34 executor NetworkManager[4720]: [1532671714.4895] device (wlp59s0): supplicant interface state: scanning -> authenticating --- Jul 27 08:08:35 executor NetworkManager[4720]: [1532671715.0616] device (wlp59s0): Activation: (wifi) association took too long, failing activation Jul 27 08:08:35 executor NetworkManager[4720]: [1532671715.0616] device (wlp59s0): state change:config -> failed (reason 'ssid-not-foun
Bug#891077: kpartx -d doesn't cleanup
Hey,
any progress on that? Just stumbled over this issue and asked myself
if there is a fix or at least a reliable workaround available.
Regards from DebConf18, Taiwan :),
- Darsha
On 02/22/2018 03:29 PM, Ritesh Raj Sarraf wrote:
> Control: tag -1 +confirmed
>
>
> Hello Xavier,
>
> Thanks for the bug report. I'm aware of the problem but haven't had
> time to root cause it, yet. Hopefully soon.
>
> On Thu, 2018-02-22 at 09:50 +0100, Xavier Bestel wrote:
>> Package: kpartx
>> Version: 0.7.4-3
>> Severity: important
>>
>> Hi,
>>
>> If I execute the following testcase:
>> #!/bin/bash -xe
>> IMAGE_PATH=bug.img
>> truncate -s 3608M "${IMAGE_PATH}"
>> /sbin/sfdisk "${IMAGE_PATH}" <<-__EOF__
>> 4M,512M,L,*
>> 516M,512M,,
>> 1028M,512M,,
>> 1540M,,E,
>> ,64M,,
>> ,64M,,
>> ,,,
>> __EOF__
>> sudo kpartx -l "${IMAGE_PATH}"
>> sudo kpartx -a "${IMAGE_PATH}"
>> sudo kpartx -d "${IMAGE_PATH}"
>> then kpartx won't cleanup its loop devices:
signature.asc
Description: OpenPGP digital signature
Bug#903260: python3-sphinx: Add depends / recommends for make
Package: python3-sphinx Version: 1.4.9-2 Severity: normal Dear Maintainer, I just installed a plain Debian/stretch system and python-sphinx / python3-sphinx is usually one of the first packages I install. After running `sphinx-quickstart` I noticed the following:: [...] Finished: An initial directory structure has been created. You should now populate your master file ./index.rst and create other documentation source files. Use the Makefile to build the docs, like so: make builder where "builder" is one of the supported builders, e.g. html, latex or linkcheck. But `make` was missing. I wonder if there shouldn't be a 'depends' or at least a 'recommends' on the package make? Thank you for maintaining and have a nice day! Regards, - Darsha -- System Information: Debian Release: 9.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-6-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-sphinx depends on: ii python33.5.3-1 ii python3-alabaster 0.7.8-1 ii python3-babel 2.3.4+dfsg.1-2 ii python3-docutils 0.13.1+dfsg-2 ii python3-imagesize 0.7.1-1 ii python3-jinja2 2.8-1 ii python3-pygments 2.2.0+dfsg-1 ii python3-six1.10.0-3 ii sphinx-common 1.4.9-2 Versions of packages python3-sphinx recommends: ii python3-pil 4.0.0-4 Versions of packages python3-sphinx suggests: pn dvipng pn libjs-mathjax pn python3-sphinx-rtd-theme pn sphinx-doc pn texlive-fonts-recommended pn texlive-generic-extra pn texlive-latex-extra pn texlive-latex-recommended -- no debconf information
Bug#664014: gnome-screenshot: Segmentation fault in interactive mode
Hi, still at Debian/jessie but interactive mode works fine here: % gnome-screenshot --version gnome-screenshot 3.14.0 % gnome-screenshot --interactive (gnome-screenshot:21894): Gtk-WARNING **: Symbolic icon pan-down-symbolic-ltr of size 16 is in an icon theme directory of size 128 (gnome-screenshot:21894): Gtk-WARNING **: Symbolic icon pan-down-symbolic-ltr of size 16 is in an icon theme directory of size 128 ** Message: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11. (Except for a few glitches.) But I think this bug can be closed now. Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#764263: linux-image-3.16-2-amd64: WARNING at drivers/base/firmware_class.c:1109 _request_firmware+0x521/0xaf0() [btusb?]
Hi, I know, this is a very old bug report but as I am still running Debian/jessie (and others might too), I thought my findings would still be helpful and/or lead to closing this bug. On 10/07/2014 09:18 AM, Bjørn Mork wrote: > Ben Hutchings writes: >> On Mon, 2014-10-06 at 20:15 +0200, Julien Cristau wrote: >>> Package: src:linux >>> Version: 3.16.3-2 >>> Severity: normal >>> >>> Hi, >>> >>> I get the following trace in my kernel log, which I don't think I've >>> seen in pre-3.16 versions: >>> >>> Sep 29 19:12:49 betterave kernel: [ 7696.920600] PM: resume of devices >>> complete after 508.149 msecs >>> Sep 29 19:12:49 betterave kernel: [ 7696.921181] [ cut here >>> ] >>> Sep 29 19:12:49 betterave kernel: [ 7696.921188] WARNING: CPU: 2 PID: 3533 >>> at /build/linux-P15SNz/linux-3.16.3/drivers/base/firmware_class.c:1109 >>> _request_firmware+0x521/0xaf0() >> [...] >>> Sep 29 19:12:49 betterave kernel: [ 7696.921405] [] ? >>> request_firmware+0x2c/0x40 >>> Sep 29 19:12:49 betterave kernel: [ 7696.921412] [] ? >>> btusb_setup_bcm_patchram+0x85/0x430 [btusb] >>> Sep 29 19:12:49 betterave kernel: [ 7696.921419] [] ? >>> rpm_check_suspend_allowed+0x6a/0xc0 >> [...] >>> Sep 29 19:12:49 betterave kernel: [ 7696.921528] bluetooth hci0: firmware: >>> brcm/BCM20702A0-0a5c-21e6.hcd will not be loaded >> [...] >> >> This means: btusb tries to load firmware during its resume operation, >> when userland is not yet available. This doesn't work if firmware >> loading depends on the userland firmware agent. >> >> The warning won't appear if the firmware is installed in the usual >> place, as direct loading will work. And the firmware agent is npw >> deprecated and not even enabled in Debian kernels. We could remove this >> warning, but it would be papering over a driver bug. > > Are you sure about this? FWIW I've occasionally seen similar warnings > from another btusb device with firmware (using kernels I've built > myself, so not reported here of course). And I haven't really bothered to > look at the root cause before, so I haven't reported it upstream either. > [...] I also got this kernel backtrace log, especially after resume from suspend. So I tested the following configurations: * Kernel: 3.16.43-2+deb8u2 / without firmware * Kernel: 3.16.43-2+deb8u2 / with firmware * Kernel: 4.9.30-2+deb9u2~bpo8+1 / without firmware * Kernel: 4.9.30-2+deb9u2~bpo8+1 / with firmware Finding the correct firmware is a complete different story (see my comments in #801084 for details) but I only got the kernel backtrace log with the first configuration (Kernel: 3.16.43-2+deb8u2 / without firmware). So I think this issue is fixed in the jessie-backports kernel. If you need more information on this, please let me know. If Julien can confirm that the kernel log is not shown with the new kernel version, this bug can be closed. Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#801084: regression from jessie
Hi, On 06/13/2017 02:03 PM, Juha Jäykkä wrote: > > I upgraded from jessie to stretch a few days ago and bluetooth stopped > working. With some digging around, it seems I'm affected by this bug. > > The trouble is exacerbated by the fact that the firmware file from the github > link does not work on my bt adapter. It loads fine, no error messages, no > nothing. No working hci0 either. > > I actually get a hci0: > > hci0: Type: Primary Bus: USB > BD Address: 34:23:87:FF:76:12 ACL MTU: 1021:8 SCO MTU: 64:1 > DOWN > RX bytes:3374 acl:0 sco:0 events:409 errors:0 > TX bytes:36217 acl:0 sco:0 commands:408 errors:0 > > but it cannot be brought up: > > # hciconfig hci0 up > Can't init device hci0: Invalid request code (56) Which firmware did you choose? I found it very difficult to find the correct one[1] because the firmware driver from winterheart @ github does not work for my notebook (Lenovo X230). I recently installed the jessie-backports kernel (to fix another firmware-related kernel bug, see: #764263) and can confirm that the bluetooth adapter does work even without a firmware driver loaded. But be aware: if you load the wrong firmware driver you have to poweroff the system to unload the firmware (rmmod/modprobe and/or restarting the system after deleting the firmware from `/lib/firmware/brcm` is *not* enough). (Side question: Does anyone know a way to unload the firmware?) [1] Finding the correct firmware was not easy. On my research I stumbled over this: https://www.slackwiki.com/Btfirmware-nonfree He basically downloads the Windows drivers and extracts the firmware as hex file (BCM20702A1_001.002.014.0449.0462.hex) and converts it to the hcd format (BCM20702A1-0a5c-21e6.hcd) (via hex2hcd from jessesung @ github). As the Thinkpad T430s and my X230 seem to have the same firmware I attached them for your convenience. Maybe is works for you too. (Note for Debian/jessie users with Kernel 3.16: BCM20702A0-0a5c-21e6.hcd is expected as firmware filename). @Fabian: does the drivers provided by plugable.com really work? Because they have the ID 0a5c:21e8 whereas your system has a 0a5c:21e6. @winterheart (aka Azamat): what is difference of the firmware drivers in your collection and the drivers which are provided by Lenovo? @bluez-firmware-maintainers: What needs to be done to bring these firmware drivers in this package? How can we help? Regards, - Darsha :02040009F1 :2800010800694204204EB1FD0400400600A0027020020A00280009001D :FB002800411A0042726F6164636F6D20426C7565746F6F74682044657669636500980100035C010001720600030800017A0208930400200068040012000C006A360003001200B000A000400052008000900060007000C100D00020003000690200CE015D0C000A64E6B08898425A33435F09003C280100040004F70C0A6F0098160800C600F3025D0066033000C900E10268005C033600C300E2026A0053033C00C200E1026C004E034100C500D60272004A034300C300CE02790042034800C500C00283003A034E00C800BF0282003B034E00C900BC02840037035200FF :FB0123000808070707070707060606060505050502C0F00094FC0E005E0230FC0E000F00630400FD0E000F00680288FC0E0000022CFC0E00490470FC0E000B0974FC0E002E01D8FF0E006219D0FC0E0020C9C8FC0E003885DCFC0E001CC8CCFD0E0004805CFC0E00020020FC0E001921E0FC0E80C0FC0E002200948F080000100010988F080000109C8F08FF00040404CCFC0ED4 :FB021E2B45D07B0001040A08FC0E002E360CFC0E002CAE10FC0E002AAC14FC0E00A22218FC0E001D201CFC0E000D1520FC0E00858D24FC0E00831128FC0E00000198FF0E003E41C316001269141F310870047836047430607180764A3108290ACF0900100F0C6EF0B009F060D10900010403036B1420206B1A2400FF010808041EFC0CF80AF408F006EC04E802041EFC0CF80AF408F006EC04E8020301000182D600040602020A233C5A6E7D800080008000800080008026 :FB031980028002800280028002800214FF1F880AFF610014FF1F820AFF610014FF1F000AFF610014FF1F080AFF610014FF1F0B0AFF610014FF1F100AFF61004068027B4068027B4068027B4068027B4069027B4069027B82D600FF0602020A233C5A6E7D80008000800080008000800080028002800280028002800214FF1F880AFF20001422 :FB041400FF1F820AFF430014FF1F000AFF660014FF1F080AFF660014FF1F0B0AFF430014FF1F100AFF2000417B417B417B417B417B417B861200041300400840130001000180FF000113C15E0044041422A244041422A2
Bug#832999: "ping: icmp open socket: Operation not permitted" as non-root in Debian Live
On Tue, 8 Nov 2016 05:55:02 -0800 Noah Meyerhans wrote: > On Sat, Jul 30, 2016 at 10:12:13AM +, Askar Safin wrote: >> I downloaded Debian Live from this link: >> http://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-8.5.0-amd64-kde-desktop.iso >> I booted into this KDE live system, opened Konsole terminal >> emulator, typed "ping debian.org" (as non-root) into it and saw: >> "ping: icmp open socket: Operation not permitted". >> "sudo ping debian.org" works. > > ping uses Linux capabilities(7) to work as a non-suid binary. What seems > to be happening is that the initial base installation performed by > debootstrap is done on a filesystem that supports capabilities, but then > the capabilities are lost when the files are copied to the CD image > filesystem. I'm not sure if that's because the target filesystem doesn't > support capabilities or that the process of copying fails to preserve > them. > > I'm re-assigning this to the cdimage.debian.org team so they can > investigate. Just tested ping with "debian-live-9.1.0-amd64-kde-desktop.iso" and with "debian-live-9.1.0-amd64-cinnamon-desktop.iso". Ping performs correctly on both systems. @Asker: mind trying it again and close the bug it works for you? Thx. Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#839985: bluetooth: cannot receive files from android 5.1.1 / no obvious idea how to send
On Sat, 8 Oct 2016 02:26:46 +1100 Fulano Diego Perez wrote: > > this is logs when trying to receive file: > > Oct 08 02:23:23 local obexd[26073]: CONNECT(0x0), (null)(0x) > Oct 08 02:23:23 local obexd[26073]: CONNECT(0x0), (null)(0x0) > Oct 08 02:23:23 local obexd[26073]: PUT(0x2), (null)(0x) > Oct 08 02:23:23 local obexd[26073]: PUT(0x2), FORBIDDEN(0x43) > Oct 08 02:23:23 local obexd[26073]: DISCONNECT(0x1), (null)(0x) > Oct 08 02:23:23 local obexd[26073]: DISCONNECT(0x1), SUCCESS(0x20) > Oct 08 02:23:23 local obexd[26073]: disconnected: Transport got disconnected > Oct 08 02:23:23 local bluetoothd[23051]: Unable to get io data for > Object Push: getpeername: Transport endpoint is not connected (107) > > eventually i could send to the phone - i had to change phone settings I get the same log output too. After trying a multiple things the solution seems to be that the mobile phone needs to be paired first. Can you confirm that? JFTR: I am (still) running Debian/Jessie with blueman from jessie-backports: -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable'), (99, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) ii blueman 2.0.4-1~bpo8+1 ii bluetooth5.23-2 ii bluez5.23-2+b1 ii bluez-obexd 5.23-2+b1 ii cinnamon [notification-daemon] 3.2.7+betsy ii dbus 1.8.20-0+deb8u1 ii dconf-gsettings-backend [gsettings-backend] 0.22.0-1 ii gir1.2-appindicator3-0.1 0.4.92-3.1 ii gir1.2-gdkpixbuf-2.0 2.31.1-2+deb8u5 ii gir1.2-glib-2.0 1.42.0-2.2 ii gir1.2-gtk-3.0 3.14.5+4 ii gir1.2-notify-0.70.7.6-2 ii gir1.2-pango-1.0 1.36.8-3 ii gnome-icon-theme 3.12.0-1 ii libbluetooth35.23-2+b1 ii libc62.19-18+deb8u9 ii libglib2.0-0 2.42.1-1+b1 ii libpulse-mainloop-glib0 5.0-13 ii libpython3.4 3.4.2-1 ii librsvg2-common 2.40.5-1+deb8u2 ii python3 3.4.2-2 ii python3-cairo1.10.0+dfsg-4+b1 ii python3-dbus 1.2.0-2+b3 ii python3-gi 3.14.0-1 ii python3-gi-cairo 3.14.0-1 Versions of packages blueman recommends: ii policykit-1 0.105-15~deb8u2 Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#863490: unblock: uanytun/0.3.6-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package uanytun
The /etc/init.d/uanytun script did not source /lib/lsb/init-functions. The
systemd package provides /lib/lsb/init-functions.d/40-systemd to redirect
/etc/init.d/$script calls to systemctl.
When a init script sources the /lib/lsb/init-functions utility
we have to declare a dependency on lsb-base (>= 3.0-6).
See:
https://lintian.debian.org/tags/init.d-script-needs-depends-on-lsb-base.html
This patch includes an upstream commit which was commited after the release of
v0.3.6
Source:
https://git.spreadspace.org/anytun/uanytun.git/commit/?id=e84f028444822b2a185395a640c5e12da4db8454
And below the source debdiff. Thank you very much!
Regards,
- Darsha
% debdiff uanytun_0.3.6-1.dsc uanytun_0.3.6-2.dsc
diff -Nru uanytun-0.3.6/debian/changelog uanytun-0.3.6/debian/changelog
--- uanytun-0.3.6/debian/changelog 2017-01-26 08:47:07.0 +0100
+++ uanytun-0.3.6/debian/changelog 2017-05-08 01:11:49.0 +0200
@@ -1,3 +1,9 @@
+uanytun (0.3.6-2) unstable; urgency=medium
+
+ * [45680e6] Fix lintian-warning: init.d-script-does-not-source-init-functions
+
+ -- Darshaka Pathirana Mon, 08 May 2017 01:11:49 +0200
+
uanytun (0.3.6-1) unstable; urgency=medium
* [43e4474] Bump debian compat version to 9
diff -Nru uanytun-0.3.6/debian/control uanytun-0.3.6/debian/control
--- uanytun-0.3.6/debian/control2017-01-26 08:47:07.0 +0100
+++ uanytun-0.3.6/debian/control2017-05-08 01:11:49.0 +0200
@@ -13,6 +13,7 @@
Package: uanytun
Architecture: any
Depends: adduser,
+ lsb-base (>= 3.0-6),
${misc:Depends},
${shlibs:Depends}
Description: tiny implementation of the secure anycast tunneling protocol
diff -Nru uanytun-0.3.6/debian/patches/01_source-init-functions.diff
uanytun-0.3.6/debian/patches/01_source-init-functions.diff
--- uanytun-0.3.6/debian/patches/01_source-init-functions.diff 1970-01-01
01:00:00.0 +0100
+++ uanytun-0.3.6/debian/patches/01_source-init-functions.diff 2017-05-08
01:11:49.0 +0200
@@ -0,0 +1,22 @@
+From e84f028444822b2a185395a640c5e12da4db8454 Mon Sep 17 00:00:00 2001
+From: Christian Pointner
+Date: Mon, 16 Jan 2017 05:53:34 +0100
+Subject: source init-functions at initscript
+
+
+diff --git a/etc/init.d/uanytun b/etc/init.d/uanytun
+index 9071e5a..b8a8573 100755
+--- a/etc/init.d/uanytun
b/etc/init.d/uanytun
+@@ -22,6 +22,8 @@ if [ -f /etc/default/uanytun ] ; then
+ . /etc/default/uanytun
+ fi
+
++. /lib/lsb/init-functions
++
+ start_vpn () {
+ STATUS="OK"
+ if [ -f $CONFIG_DIR/$VPNNAME/config ] ; then
+--
+cgit v0.10.2
+
diff -Nru uanytun-0.3.6/debian/patches/series
uanytun-0.3.6/debian/patches/series
--- uanytun-0.3.6/debian/patches/series 1970-01-01 01:00:00.0 +0100
+++ uanytun-0.3.6/debian/patches/series 2017-05-08 01:11:49.0 +0200
@@ -0,0 +1 @@
+01_source-init-functions.diff
unblock uanytun/0.3.6-2
-- System Information:
Debian Release: 8.6
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable'), (99, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Bug#842532: rsnapshot: multiple per-backup-point +rsync_long_args don't work
Hey, On Sun, 30 Oct 2016 17:38:09 +1100 Jayen Ashar wrote: > Package: rsnapshot > Version: 1.4.2-1 > Severity: normal > > Dear Maintainer, > >* What led up to the situation? > > I have been using `+rsync_long_args=--rsync-path="sudo rsync"` for some time > with success. I recently added `+rsync_long_args=--compress`. Did you try: `+rsync_long_args=--rsync-path="sudo rsync" --compress` Just tested this line and it works for me with rsnapshot 1.4.2-1. Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#849457: update-inetd: README is obsolete / not update-to-date
Package: update-inetd Version: 4.43 Severity: minor Dear Maintainer, the README contains the following: update-inetd is in the process of being deprecated. If you're the maintainer of a package that depends on update-inetd, please migrate to reconf-inetd, as documented in DEP9 (http://dep.debian.net/deps/dep9/) -- Serafeim Zanikolas Sun, 20 May 2012 16:24:48 +0200 But DEP9 is obsolete. Please update or remove the README. Thank you. Thank you for maintaining update-inetd! Regards, - Darsha -- System Information: Debian Release: 8.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-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 update-inetd depends on: ii debconf [debconf-2.0] 1.5.56 ii libfile-copy-recursive-perl0.38-1 ii perl-base [libfile-temp-perl] 5.20.2-3+deb8u6 update-inetd recommends no packages. update-inetd suggests no packages. -- debconf information excluded
Bug#848869: Error: could not create default cluster. Please create it manually with
On 2016-12-21 11:38, Christoph Berg wrote: > Control: tags -1 moreinfo > > Re: Darshaka Pathirana 2016-12-20 > <20161220110151.19348.48480.reportbug@invincible> >> Error: The locale requested by the environment is invalid. > >> Locale looks like this: >> >> % locale >> LANG=en_US.UTF-8 >> LANGUAGE=en_US:en > > on package installation (only), the locale used for pg_createcluster > (= initdb) is not determined by your environment (which "locale" looks > at), but by the system configuration in /etc/environment and > /etc/default/locale. > > Could you check what you have configured in these files? Hmm. The files look like this: % cat /etc/environment % cat /etc/default/locale # File generated by update-locale LANG=en_US.UTF-8 LANGUAGE=en_US:en Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#848869: Error: could not create default cluster. Please create it manually with
Package: postgresql Version: 9.4+165+deb8u1 Severity: normal Dear Maintainer, when installing postgresql on a freshly setup Debian/Jessie system the following error is shown: Setting up postgresql-common (165+deb8u1) ... Creating config file /etc/postgresql-common/createcluster.conf with new version Creating config file /etc/logrotate.d/postgresql-common with new version Building PostgreSQL dictionaries from installed myspell/hunspell packages... Removing obsolete dictionary files: Setting up postgresql-9.4 (9.4.9-0+deb8u1) ... Error: The locale requested by the environment is invalid. Error: could not create default cluster. Please create it manually with pg_createcluster 9.4 main --start or a similar command (see 'man pg_createcluster'). update-alternatives: using /usr/share/postgresql/9.4/man/man1/postmaster.1.gz to provide /usr/share/man/man1/postmaster.1.gz (postmaster.1.gz) in auto mode Setting up postgresql (9.4+165+deb8u1) ... Locale looks like this: % locale LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=en_US.UTF-8 Why is this happening? Anything I can do to help to pinpoint the problem? Thank you for maintaining and your help! Regards, - Darsha -- System Information: % lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux 8.6 (jessie) Release:8.6 Codename: jessie Kernel: Linux 3.16.0-4-amd64 #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux Init: % /sbin/init -> /lib/systemd/systemd
Bug#847287: roundcube: Roundcube 1.2.2: Remote command execution via malicious email composing
On Wed, 07 Dec 2016 12:16:14 +0100 Vincent Bernat wrote: > ⦠7 décembre 2016 12:08 +0100, Guilhem Moulin  : > > >> Is the tag for debian/1.1.5+dfsg.1-1_bpo8+1? The diff for it is pretty > >> big. > > > > 1.1.5+dfsg.1-1_bpo8+1 is the current version from jessie-backports (since > > April 29). The diff between 1.1.5+dfsg.1-1_bpo8+1 and 1.1.5+dfsg.1-1_bpo8+2 > > is merely the upstream fix > > > > > > https://anonscm.debian.org/cgit/pkg-roundcube/roundcube.git/diff/?id=debian/1.1.5%2bdfsg.1-1_bpo8%2b2&id2=debian/1.1.5%2bdfsg.1-1_bpo8%2b1 > > I deleted the tag on my side, fetched it again and the diff is now > OK. I'll upload in the next hour. Wow. That was quick! Thanks to you all. What about wheezy / wheezy-backports? Are these packages affected too? Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#842605: sane-utils depends on update-inetd but it should not (anymore)
Hi Jörg, Yes, DEP9 is marked obsolete. I somehow missed that. But still: do we need to depend on "update-inetd"? Regards, - Darsha On 2016-11-01 08:26, Jörg Frings-Fürst wrote: > Hello Darahaka, > > thank you for spending your time helping to make Debian better with > this bug report. > > From [1]: > > As of Feb 2014: With a dynamic init system in Debian finally being > adopted, inetd is irrelevant, hence reconf-inetd too, so I mark this > DEP as obsolete, since it's not worth the migration effort. > > > So I close this bug. > > CU > Jörg > > [1] http://dep.debian.net/deps/dep9/ > > signature.asc Description: OpenPGP digital signature
Bug#842605: sane-utils depends on update-inetd but it should not (anymore)
Package: sane-utils Version: 1.0.24-8+deb8u1 Severity: normal Dear Maintainer, sane-utils depends on update-inetd, but according to it's README it shouldn't: , | update-inetd is in the process of being deprecated. If you're the maintainer | of a package that depends on update-inetd, please migrate to reconf-inetd, | as documented in DEP9 (http://dep.debian.net/deps/dep9/) | | -- Serafeim Zanikolas Sun, 20 May 2012 16:24:48 +0200 ` That said I am not even sure if depending on update-inetd is even necessary... What do you think? Regard and thanks for your work, - Darsha -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages sane-utils depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.56 ii init-system-helpers1.22 ii libavahi-client3 0.6.31-5 ii libavahi-common3 0.6.31-5 ii libc6 2.19-18+deb8u6 ii libieee1284-3 0.2.11-12 ii libsane1.0.24-8+deb8u1 ii libsystemd0215+12+betsy ii libusb-1.0-0 2:1.0.19-1 ii update-inetd 4.43 sane-utils recommends no packages. Versions of packages sane-utils suggests: ii avahi-daemon 0.6.31-5 pn unpaper -- debconf information excluded signature.asc Description: OpenPGP digital signature
Bug#723071: evince: Send To dunction does nothing
On 2016-10-11 05:01, Jason Crain wrote: > Control: tags -1 + moreinfo > > On Tue, Sep 13, 2016 at 06:18:31PM +0200, Darshaka Pathirana wrote: >> just wanted to tell you that the problem still exists in Debian/Jessie. But >> this time it does not fail silently but displays a big red banner with "Could >> not send current document" and "Failed to execute child process "(null)" (No >> such file or directory)". See attached screenshot. > > Do you have the "nautilus-sendto" program installed? Nice. After installing "nautilus-sendto" my default mailer (Thunderbird) is opened and the PDF is attached. But: % apt-cache show evince | grep "Depends\|Recommends\|Suggests" Depends: libatk1.0-0 (>= 1.12.4), libc6 (>= 2.4), libcairo-gobject2 (>= 1.10.0), libcairo2 (>= 1.14.0), libevdocument3-4 (= 3.14.1-2+deb8u1), libevview3-3 (= 3.14.1-2+deb8u1), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.37.3), libgtk-3-0 (>= 3.13), libnautilus-extension1a (>= 2.91), libpango-1.0-0 (>= 1.20.0), libpangocairo-1.0-0 (>= 1.14.0), libsecret-1-0 (>= 0.7), libxml2 (>= 2.6.27), zlib1g (>= 1:1.1.4), evince-common (>= 3.14), evince-common (<< 3.15), gnome-icon-theme-symbolic (>= 2.17.1), shared-mime-info Recommends: dbus-x11, gvfs Suggests: unrar, poppler-data, nautilus But: shouldn't there be at least a "Suggests" to "nautilus-sendto" to make the "Send To" work? Thx! Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#723071: evince: Send To dunction does nothing
Package: evince Version: 3.14.1-2+deb8u1 Severity: normal Control: retitle -1 evince: Send To... reports "Could not send current document" Hi, just wanted to tell you that the problem still exists in Debian/Jessie. But this time it does not fail silently but displays a big red banner with "Could not send current document" and "Failed to execute child process "(null)" (No such file or directory)". See attached screenshot. Regards, - Darsha -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages evince depends on: ii evince-common 3.14.1-2+deb8u1 ii gnome-icon-theme-symbolic 3.12.0-1 ii libatk1.0-02.14.0-1 ii libc6 2.19-18+deb8u4 ii libcairo-gobject2 1.14.0-2.1+deb8u1 ii libcairo2 1.14.0-2.1+deb8u1 ii libevdocument3-4 3.14.1-2+deb8u1 ii libevview3-3 3.14.1-2+deb8u1 ii libgdk-pixbuf2.0-0 2.31.1-2+deb8u5 ii libglib2.0-0 2.42.1-1+b1 ii libgtk-3-0 3.14.5+4 ii libnautilus-extension1a3.14.1-2 ii libpango-1.0-0 1.36.8-3 ii libpangocairo-1.0-01.36.8-3 ii libsecret-1-0 0.18-1+b1 ii libxml22.9.1+dfsg1-5+deb8u2 ii shared-mime-info 1.3-1 ii zlib1g 1:1.2.8.dfsg-2+b1 Versions of packages evince recommends: ii dbus-x11 1.8.20-0+deb8u1 ii gvfs 1.22.2-1 Versions of packages evince suggests: pn nautilus ii poppler-data 0.4.7-1 ii unrar 1:5.2.7-0.1 -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#656179: pdfposter should allow for printing overlap
JFTR: Upstream seems to track this issue here: [1] https://gitlab.com/pdftools/pdfposter/issues/1 (after moving to their project to gitlab) Regards, - Darsha signature.asc Description: OpenPGP digital signature
Bug#811504: system-config-printer: core dump when trying to add printer Dell C3760DN Color Laser
Package: system-config-printer
Version: 1.4.6-1
Severity: normal
Dear Maintainer,
when trying to add the printer Dell C3760DN Color Laser s-c-p either
hangs or core dumps.
The printer is correctly shown in the "New Printer"-window but after
selecting the printer and choosing a connection ("AppSocket/JetDirect
network printer via DNS-SD" in this case) and pressing "Forward" s-c-p
crashes.
Here the debug output after pressing the "Forward"-Button:
Next clicked on page 1
nextNPTab: need PPDs loaded
+
Asking PackageKit to install drivers
Failed to talk to PackageKit: DBusException('The name
org.freedesktop.PackageKit was not provided by any .service files',)
Asking CUPS for PPDs
Using polkit-1 connection class
+
New IPPConnection
+<_IPPConnectionThread(Thread-2, initial daemon)>
+
+
+
Awaiting further instructions
: chaining up to >
+
: calling
+_PK1AsyncMethodCall:
: calling
at 0x7fe8b2aa19b0>
+
Next task: (, (), {},
>, >, >)
-
Call
...success
Awaiting further instructions
: chaining up
to >
: to
reply_handler at >
DESTROY:
: chaining up to >
Dell C3760dn Color Laser
Trying make/model names
init_makes: 0.488s
mfgl: dell
mdll: c3760dn color laser
make: Dell
re-split mdll: c 3760 dn color laser
Trying best match
C1765 <= C3760dn Color Laser <= M5200
C1765: match length 1
Searching for model ID 'c3760dn', 'c%ddn' % 3760
Ignoring 0 of 4 digits, trying c3760dn
Ignoring 1 of 4 digits, trying c3760dn
Ignoring 2 of 4 digits, trying c3700dn
Ignoring 3 of 4 digits, trying c3000dn
Checking CMD field
Trying best match
OAKT <= PCL 3 <= PCL 3
PCL 3: match length 5
generic:
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Generic-PCL_3_Printer-pcl3.ppd
No ID match for device
dnssd://Dell%20C3760dn%20Color%20Laser%20(BD%3A27%3A8D)._pdl-datastream._tcp.local/:
MFG:Dell;MDL:C3760dn Color Laser;CMD:PDF,PS,PCL,URF;
Valid driver types for this printer in priority order:
['manufacturer-cmd', 'foomatic-recommended-nonpostscript',
'manufacturer-ricoh-ps', 'manufacturer-ricoh-pxl', 'manufacturer',
'pdf', 'foomatic-recommended-postscript', 'hpcups', 'splix',
'foomatic-postscript', 'gutenprint-simplified', 'gutenprint-expert',
'foomatic-gutenprint', 'foomatic', 'cups', 'generic-postscript',
'generic-foomatic-recommended', 'generic-pcl6', 'generic-pcl5e',
'generic-pcl5', 'generic-pcl', 'generic-escp', 'ghostscript',
'generic', 'foomatic-recommended-hpijs', 'hpijs', 'foomatic-hpijs',
'hpcups-plugin', 'hpijs-plugin', 'turboprint']
PPDs with assigned driver types in priority order:
[('generic-foomatic-recommended',
u'foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Generic-PCL_3_Printer-pcl3.ppd')]
Resulting PPD list in priority order:
[u'foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Generic-PCL_3_Printer-pcl3.ppd']
Asking Jockey to install drivers
Got Jockey error: DBusException('The name com.ubuntu.DeviceDriver was
not provided by any .service files',)
DESTROY:
DESTROY:
DESTROY:
: stored error is None
DESTROY:
Loaded PPDs this time; try nextNPTab again...
Next clicked on page 1
Dell C3760dn Color Laser
Trying make/model names
mfgl: dell
mdll: c3760dn color laser
make: Dell
re-split mdll: c 3760 dn color laser
Trying best match
C1765 <= C3760dn Color Laser <= M5200
C1765: match length 1
Searching for model ID 'c3760dn', 'c%ddn' % 3760
Ignoring 0 of 4 digits, trying c3760dn
Ignoring 1 of 4 digits, trying c3760dn
Ignoring 2 of 4 digits, trying c3700dn
Ignoring 3 of 4 digits, trying c3000dn
Checking CMD field
Trying best match
OAKT <= PCL 3 <= PCL 3
PCL 3: match length 5
generic:
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Generic-PCL_3_Printer-pcl3.ppd
No ID match for device
dnssd://Dell%20C3760dn%20Color%20Laser%20(BD%3A27%3A8D)._pdl-datastream._tcp.local/:
MFG:Dell;MDL:C3760dn Color Laser;CMD:PDF,PS,PCL,URF;
Suitable PPDs found:
{u'foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Generic-PCL_3_Printer-pcl3.ppd':
'generic'}
Valid driver types for this printer in priority order:
['manufacturer-cmd', 'foomatic-recommended-nonpostscript',
'manufacturer-ricoh-ps', 'manufacturer-ricoh-pxl', 'manufacturer',
'pdf', 'foomatic-recommended-postscript', 'hpcups', 'splix',
'foomatic-postscript', 'gutenprint-simplified', 'gutenprint-expert',
'foomatic-gutenprint', 'foomatic', 'cups', 'generic-postscript',
'generic-foomatic-recommended', 'generic-pcl6', 'generic-pcl5e',
'generic-pcl5', 'generic-pcl', 'generic-escp', 'ghostscript',
'generic', 'foomatic-recommended-hpijs', 'hpijs', 'foomatic-hpijs',
'hpcups-plugin', 'hpijs-plugin', 'turboprint']
PPDs with assigned driver types in priority order:
[('generic-foomatic-recommended',
u'foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Generic-PCL_3_Printer-pcl3.ppd')]
Resulting PPD list in priority order:
[u'foomatic-db-compressed-ppds:0/ppd/foom
Bug#807689: apcupsd: ups-monitor is never run to killpower the UPC (when using systemd)
Hi,
after examining the problem a bit further, I figured out that
"/etc/init.d/ups-monitor" is executed by "/etc/init.d/halt" (which
belongs to the package "initscripts")! I really do not understand how
and why that happened but #670094 already handles that.
I am not really sure but it seems that "/etc/init.d/halt" is not
executed by systemd (which makes sense for me).
So I wrote a systemd-service "/etc/systemd/system/apcupsd-killpower.service"
[Unit]
Description=apcupsd: Ordering UPS to kill power (if onbattery/powerfail)
DefaultDependencies=no
Before=shutdown.target
[Service]
ExecStart=/etc/init.d/ups-monitor killpower
Type=oneshot
[Install]
WantedBy=shutdown.target
and did:
# systemctl enable apcupsd-killpower.service
Created symlink from
/etc/systemd/system/shutdown.target.wants/apcupsd-killpower.service to
/etc/systemd/system/apcupsd-killpower.service
But my first killpower-test gave me errors:
# journalctl | grep ups-monitor
Dec 11 18:50:42 server ups-monitor[2780]: apcupsd: Ordering UPS to kill
power... wall: cannot get tty name: Inappropriate ioctl for device
Dec 11 18:50:42 server ups-monitor[2780]: wall: /dev/pts/0: No such file or
directory
So I fixed "/etc/apcupsd/apccontrol" (see #709612):
# git diff /etc/apcupsd/apccontrol
diff --git a/apcupsd/apccontrol b/apcupsd/apccontrol
index 136ff36..b296f82 100755
--- a/apcupsd/apccontrol
+++ b/apcupsd/apccontrol
@@ -62,10 +62,10 @@ fi
case "$1" in
killpower)
- echo "Apccontrol doing: ${APCUPSD} --killpower on UPS ${2}" | ${WALL}
+ echo "Apccontrol doing: ${APCUPSD} --killpower on UPS ${2}"
sleep 10
${APCUPSD} --killpower
- echo "Apccontrol has done: ${APCUPSD} --killpower on UPS ${2}" |
${WALL}
+ echo "Apccontrol has done: ${APCUPSD} --killpower on UPS ${2}"
;;
commfailure)
echo "Warning communications lost with UPS ${2}" | ${WALL}
(I don't think that "wall" was ever needed so late in the shutdown process).
Please note that I first named the service "ups-monitor.service" which
seemed to conflict with "/etc/init.d/ups-monitor" but I didn't know
how to fix that...
As I am by far a systemd expert I would love to hear some comments on
this solution but at least this works for us. Thank you.
Regards,
- Darsha
signature.asc
Description: OpenPGP digital signature
Bug#807689: apcupsd: ups-monitor is never run to killpower the UPC (when using systemd)
Package: apcupsd Version: 3.14.12-1.1 Severity: normal Dear Maintainer, we have configured apcupsd to shutdown the server if the battery TIMEOUT is reached. (We do not want to stress the battery and the server does also not run all the time). After the TIMEOUT is reached the server shuts down but unfortunately - after our upgrade to / fresh install of Debian/Jessie which now uses systemd - killpower (to shutdown the UPC) is never run. It seems like a systemd problem. Any idea how to fix this? Please note that the root-fs is on a raid1 but /var and /usr are NOT seperated: # mount | grep "on / " /dev/md0 on / type ext3 (rw,relatime,errors=remount-ro,data=ordered) so #316932, #701809 and #709612 do not seem to be the problems. The service is starting fine too (so not #752195): # systemctl list-units | grep apc apcupsd.service loaded active running LSB: Starts apcupsd daemon root@server ~ # systemctl status apcupsd.service ● apcupsd.service - LSB: Starts apcupsd daemon Loaded: loaded (/etc/init.d/apcupsd) Active: active (running) since Fri 2015-12-11 13:18:17 CET; 33min ago Process: 833 ExecStart=/etc/init.d/apcupsd start (code=exited, status=0/SUCCESS) CGroup: /system.slice/apcupsd.service └─889 /sbin/apcupsd Dec 11 13:18:17 server apcupsd[889]: apcupsd 3.14.12 (29 March 2014) debian startup succeeded Dec 11 13:18:17 server apcupsd[889]: NIS server startup succeeded Dec 11 13:18:18 server apcupsd[833]: Starting UPS power management: apcupsd. Regards, - Darsha -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.16.0-4-686-pae (SMP w/2 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 apcupsd depends on: ii libc6 2.19-18+deb8u1 ii libgcc1 1:4.9.2-10 ii libwrap0 7.6.q-25 Versions of packages apcupsd recommends: ii apcupsd-doc 3.14.12-1.1 Versions of packages apcupsd suggests: ii apcupsd-cgi 3.14.12-1.1 ii udev 215-17+deb8u2 -- Configuration Files: /etc/apcupsd/apcupsd.conf changed: UPSNAME APCUPS UPSCABLE smart UPSTYPE apcsmart DEVICE /dev/ttyS0 LOCKFILE /var/lock SCRIPTDIR /etc/apcupsd PWRFAILDIR /etc/apcupsd NOLOGINDIR /etc ONBATTERYDELAY 6 BATTERYLEVEL 5 MINUTES 3 TIMEOUT 15 ANNOY 0 ANNOYDELAY 0 NOLOGON disable KILLDELAY 0 NETSERVER on NISIP 127.0.0.1 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 10 UPSCLASS standalone UPSMODE disable STATTIME 0 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 0 BATTDATE 06/11/15 /etc/default/apcupsd changed: APCACCESS=/sbin/apcaccess ISCONFIGURED=yes -- no debconf information signature.asc Description: OpenPGP digital signature
Bug#793109: ansible: (apt-module) install_recommends=yes does not override APT::Install-Recommends "false"
Package: ansible
Version: 1.7.2+dfsg-2
Severity: normal
Tags: upstream
Dear Maintainer,
I have an ansible task like this:
- name: Ensure docker.io is installed
apt: name={{ item }} state=present install_recommends=yes
with_items:
- docker.io
and/but I also have the following in '/etc/apt/apt.conf.d/00recommends':
APT::Install-Recommends "false";
Aptitude::Recommends-Important "false";
The recommended packages of docker.io for instance are:
% apt-cache show docker.io | grep Recommends
Recommends: aufs-tools, ca-certificates, cgroupfs-mount | cgroup-lite, git,
xz-utils
But after running the ansible task (with install_recommends=yes) the
recommended packages (i.e. aufs-tools) are not installed.
FTR: apt-get --install-recommends would override APT::Install-Recommends
"false";
# apt-get --install-recommends install docker.io
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
aufs-tools cgroupfs-mount
Suggested packages:
btrfs-tools debootstrap lxc rinse
The following NEW packages will be installed:
aufs-tools cgroupfs-mount docker.io
0 upgraded, 3 newly installed, 0 to remove and 9 not upgraded.
Need to get 0 B/4,489 kB of archives.
After this operation, 22.3 MB of additional disk space will be used.
I believe that the apt-module option install_recommends=yes does not run
apt-get --install-recommends (but install_recommends=no would run apt-get
--no-install-recommends)
Any idea how to overcome this problem? The followup question would be how can I
install the recommended packages if the package was installed with
--no-install-recommends (without uninstalling the package).
Thanks for your time!
Regards,
- Darsha
-- System Information:
Debian Release: 8.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.0-4-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: sysvinit (via /sbin/init)
Versions of packages ansible depends on:
ii python2.7.9-1
ii python-crypto 2.6.1-5+b2
ii python-httplib2 0.9+dfsg-2
ii python-jinja2 2.7.3-1
ii python-paramiko 1.15.1-1
ii python-pkg-resources 5.5.1-1
ii python-yaml 3.11-2
Versions of packages ansible recommends:
pn python-selinux
Versions of packages ansible suggests:
pn ansible-doc
pn sshpass
-- 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#700368: debootstrap does not work with local file mirror (apt-move)
Package: debootstrap Version: 1.0.44 Severity: normal Dear Maintainer, 1. I created a local mirror with apt-move: I changed the following settings in /etc/apt-move.conf: LOCALDIR=/opt/apt-mirror DIST=wheezy COPYONLY=yes and did % apt-move update 2. I then tried to use the local file mirror with debootstrap % debootstrap --arch amd64 --no-check-gpg wheezy /mnt/test file:///opt/apt-mirror I: Retrieving InRelease I: Failed to retrieve InRelease I: Retrieving Release E: Invalid Release file, no entry for main/binary-amd64/Packages The Release file in /opt/apt-mirror/dists/wheezy/Release looks like: Origin: APT-Move Label: APT-Move Suite: wheezy Codename: unknown Date: Mon, 11 Feb 2013 22:04:48 UTC Architectures: amd64 Components: main contrib non-free Description: unknown MD5Sum: c44087a2947345e53ad77acb6e1e1137 1420853 main/binary-amd64/Packages b11ea469384e3eb1768254cd30688b6f 365497 main/binary-amd64/Packages.gz db1ad326cd5b23c672799f9b9c8016c8 85 main/binary-amd64/Release b4b5d9fa3fe62a17a7c03ccb466e4c26 2704 contrib/binary-amd64/Packages afc4118e90e063a0301b5c75f3e9eaf6 1326 contrib/binary-amd64/Packages.gz eb7767fb225316c2a5df26d7a164dc44 88 contrib/binary-amd64/Release aa594c3e1a4776480b0dbcbcd7992098 2883 non-free/binary-amd64/Packages e342c7267a808dd9fe8aff31b9829762 1088 non-free/binary-amd64/Packages.gz d59693d446c475da6670bb7638f5ca6a 89 non-free/binary-amd64/Release SHA1: 2126d979f9c8b1e70bb0186c04014c40a6ee9531 1420853 main/binary-amd64/Packages c7063cef7a381cc2770f93423624876d48108191 365497 main/binary-amd64/Packages.gz 7df7ab3097cd1125839cc2839ceb5273d315f8c5 85 main/binary-amd64/Release c7f5871575136c4cb96c9147667c963c95f99008 2704 contrib/binary-amd64/Packages 5595ffcba40fb3a81becbb4e35a841869efe49ef 1326 contrib/binary-amd64/Packages.gz b74f8d11da5ca2afc19230017c9f7b96c7b0e379 88 contrib/binary-amd64/Release 1d7fb1ac7d6baeee5a373ce0fe7d71a34722dc5b 2883 non-free/binary-amd64/Packages 9c05cdfb4461589d30dca13a578a86b83dda7ffb 1088 non-free/binary-amd64/Packages.gz edec9eeb9c55dd3f999cc6abdd50615ec4129c1a 89 non-free/binary-amd64/Release I even tried signing the local apt repository and used the --keyring option to verify the signature but it still failed. Did I do something wrong or does anyone know what the problem is? Can I provide any additional information to get this problem solved? Thank you for any assistance. Regards, - Darsha -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-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 debootstrap depends on: ii wget 1.13.4-3 Versions of packages debootstrap recommends: ii debian-archive-keyring 2012.4 ii gnupg 1.4.12-7 debootstrap 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#664249: mutt: Error allocating SASL connection when using imaps
Hi Jonathan!
On Fri, Mar 16, 2012 at 10:25:38PM -0500, Jonathan Nieder wrote:
> Darshaka Pathirana wrote:
>
>> Reading imaps://$MYUSERNAME@imap.$MYIMAPSERVER.org/INBOX...
>> Looking up imap.$MYIMAPSERVER.org...
>> Connecting to imap.$MYIMAPSERVER.org...
>> SSL/TLS connection using TLS1.0 (DHE-RSA/AES-128-CBC/SHA1)
>> Connected to imap.$MYIMAPSERVER.org:993 on fd=4
>> 4< * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
>> AUTH=PLAIN] Dovecot ready.
>> imap_authenticate: Using any available method.
>> SASL local ip: 10.0.0.188;58868, remote ip:xxx.yyy.zzz.254;993
>> Error allocating SASL connection
>
> Thanks.
Thank You for your help!
> sasl_client_new() was called like so:
>
> rc = sasl_client_new("imap", "imap.$MYIMAPSERVER.org",
> "10.0.0.188;58868", "xxx.yyy.zzz.2554;993",
> mutt_sasl_get_callbacks(&conn->account), 0, saslconn);
>
> It didn't return SASL_OK. Maybe it returned SASL_NOMECH instead.
Very nice pointer to help debugging the problem:
> - does "ldd /usr/bin/mutt" show it pointing to the right sasl lib?
I already had checked that:
% ldd /usr/bin/mutt | grep sasl
libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x7f5174d9e000)
Seemed ok.
> - based on tracing with "ltrace -o /tmp/log mutt", what does
>sasl_client_new actually return?
So this gave me the right track:
,
| <... sasl_client_init resumed> ) = 0
| getsockname(3, 0x7fff0752dd20, 0x7fff0752de4c, 0, 64) = 0
| getnameinfo(0x7fff0752dd20, 16, "\305\336eO", 1025, "\001", 32, 3) = 0
| snprintf("\001\200\255\373\001", 4964065, "")= 16
| getpeername(3, 0x7fff0752dda0, 0x7fff0752de4c, 0x4bbee1, 0) = 0
| getnameinfo(0x7fff0752dda0, 16, "10.0.0.188", 1025, "", 32, 3) = 0
| snprintf("\001\200\255\373\001", 4964065, "")= 18
| sasl_client_new(0x4b7457, 0x25db690, 0x7fff0752d520, 0x7fff0752d920,
| 0x6dbe20) = 0x
`
Although getnameinfo() seems to successfully return with 0. I tried
% hostname
intrepid
and
% hostname -f
hostname: Name or service not known
I then quickly added something like:
127.0.1.1 intrepid.lanintrepid
in my '/etc/hosts' file and tried again:
% hostname -f
intrepid.lan
Then I restarted mutt and was able to read my mails. *yeah* ;)
Just a quick note on my setup here: My machine is in a simple
home-network using a Thomson TG585 v7 as my router and DHCP-Server.
So a few things I am curious about (maybe a bit OT):
- why did fqdn-lookup fail on my setup? (read: what did I do wrong
when installing my system?)
- why does mutt fail so miserably without a fqdn? (read: shouldn't
it give me a better error message?)
- is my workaround ok? (This is a home-network. I can not and do not
want to setup a DNS-Server and also do not want set static IPs).
So thank you very much Jonathan!
But: I am still not sure if this is a bug in the code, the
documentation or a misleading error message. What do you think?
Regards,
- Darsha
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664249: mutt: Error allocating SASL connection when using imaps
Hi Jonathan! On 03/17/2012 02:55 AM, Jonathan Nieder wrote: > Darshaka Pathirana wrote: > >> Mutt then asked me to accept my (self-signed) certificate. Which I accepted >> (always). The certificate was saved and the status line showed: >> >> SSL/TLS connection using TLS1.0 (DHE-RSA/AES-128-CBC/SHA1) >> >> and then showed the error: >> >> Error allocating SASL connection >> >> I also stripped down everything else just leaving this: >> >> set spoolfile="imaps://$MYUSERNAME@imap.$MYIMAPSERVER.org/INBOX" > > If you run 'mutt -d 2' and try again, does ~/.muttdebug0 say anything > interesting? > This is the relevant part of the debug-log: [2012-03-17 03:05:07] Reading imaps://$MYUSERNAME@imap.$MYIMAPSERVER.org/INBOX... [2012-03-17 03:05:07] Looking up imap.$MYIMAPSERVER.org... [2012-03-17 03:05:07] Connecting to imap.$MYIMAPSERVER.org... [2012-03-17 03:05:08] SSL/TLS connection using TLS1.0 (DHE-RSA/AES-128-CBC/SHA1) [2012-03-17 03:05:09] Connected to imap.$MYIMAPSERVER.org:993 on fd=4 [2012-03-17 03:05:09] 4< * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. [2012-03-17 03:05:09] imap_authenticate: Using any available method. [2012-03-17 03:05:09] SASL local ip: 10.0.0.188;58868, remote ip:xxx.yyy.zzz.254;993 [2012-03-17 03:05:09] Error allocating SASL connection [2012-03-17 03:05:09] imap_auth_sasl: Error allocating SASL connection. [2012-03-17 03:05:11] Closing connection to imap.$MYIMAPSERVER.org... [2012-03-17 03:05:11] 4> a LOGOUT^M [2012-03-17 03:05:11] 4< * BYE Logging out [2012-03-17 03:05:11] Handling BYE [2012-03-17 03:05:11] 4< a OK Logout completed. Does not seem very helpful. What do you think? Thx && Regards, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#664249: mutt: Error allocating SASL connection when using imaps
Package: mutt Version: 1.5.21-5 Severity: important Dear Maintainer, I tried to configure mutt (on Debian/wheezy) to connect to my IMAP(S)-Server (using dovecot on Debian/Squeeze). I therefor copied my working mutt configuration file from my notebook running Debian/Squeeze. Mutt then asked me to accept my (self-signed) certificate. Which I accepted (always). The certificate was saved and the status line showed: SSL/TLS connection using TLS1.0 (DHE-RSA/AES-128-CBC/SHA1) and then showed the error: Error allocating SASL connection I also stripped down everything else just leaving this: set spoolfile="imaps://$MYUSERNAME@imap.$MYIMAPSERVER.org/INBOX" And also tried various combinations of set ssl_starttls=yes|no set ssl_force_tls=yes|no without success. Do you have any suggestions to pin down the problem? Please note that the given configuration file used to work with mutt in Debian/Squeeze (v1.5.20-9+squeeze2). I did NOT try the squeeze-backport (yet). Thx for any help. Regards, - Darsha -- Package-specific info: Mutt 1.5.21 (2010-09-15) Copyright (C) 1996-2009 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 3.2.0-1-amd64 (x86_64) ncurses: ncurses 5.9.20110404 (compiled with 5.9) libidn: 1.23 (compiled with 1.20) hcache backend: tokyocabinet 1.4.37 Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP +USE_SMTP -USE_SSL_OPENSSL +USE_SSL_GNUTLS +USE_SASL +USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN +HAVE_GETSID +USE_HCACHE -ISPELL SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/usr/share/mutt" SYSCONFDIR="/etc" EXECSHELL="/bin/sh" MIXMASTER="mixmaster" To contact the developers, please mail to . To report a bug, please visit http://bugs.mutt.org/. misc/am-maintainer-mode features/ifdef features/xtitles features/trash-folder features/purge-message features/imap_fast_trash features/sensible_browser_position features-old/patch-1.5.4.vk.pgp_verbose_mime features/compressed-folders features/compressed-folders.debian debian-specific/Muttrc debian-specific/Md.etc_mailname_gethostbyname.diff debian-specific/use_usr_bin_editor.diff debian-specific/correct_docdir_in_man_page.diff debian-specific/dont_document_not_present_features.diff debian-specific/document_debian_defaults debian-specific/assumed_charset-compat debian-specific/467432-write_bcc.patch debian-specific/566076-build_doc_adjustments.patch misc/define-pgp_getkeys_command.diff misc/gpg.rc-paths misc/smime.rc upstream/531430-imapuser.patch upstream/537818-emptycharset.patch upstream/543467-thread-segfault.patch upstream/542817-smimekeys-tmpdir.patch upstream/548577-gpgme-1.2.patch upstream/553321-ansi-escape-segfault.patch upstream/568295-references.patch upstream/547980-smime_keys-chaining.patch upstream/528233-readonly-open.patch upstream/228671-pipe-mime.patch upstream/383769-score-match.patch upstream/578087-header-strchr.patch upstream/603288-split-fetches.patch upstream/537061-dont-recode-saved-attachments.patch upstream/608706-fix-spelling-errors.patch upstream/620854-pop3-segfault.patch upstream/611412-bts-regexp.patch upstream/624058-gnutls-deprecated-set-priority.patch upstream/624085-gnutls-deprecated-verify-peers.patch upstream/584138-mx_update_context-segfault.patch upstream/619216-gnutls-CN-validation.patch upstream/611410-no-implicit_autoview-for-text-html.patch upstream/path_max mutt.org -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages mutt depends on: ii libc6 2.13-27 ii libcomerr21.42.1-2 ii libgnutls26 2.12.16-1 ii libgpg-error0 1.10-3 ii libgpgme111.2.0-1.4 ii libgssapi-krb5-2 1.10+dfsg~beta1-2 ii libidn11 1.23-2 ii libk5crypto3 1.10+dfsg~beta1-2 ii libkrb5-3 1.10+dfsg~beta1-2 ii libncursesw5 5.9-4 ii libsasl2-22.1.25.dfsg1-4 ii libtokyocabinet8 1.4.37-9 Versions of packages mutt recommends: ii libsasl2-modules2.1.25.dfsg1-4 ii locales 2.13-27 ii mime-support3.52-1 ii postfix [mail-transport-agent] 2.8.7-1 Versions of packages mutt suggests: pn aspell
Bug#655559: apticron: Error in script, "Mailx" instead of "mailx"
Hi!
On 20:59, Andrew Baines wrote:
> Package: apticron
> Version: 1.1.42
> Severity: important
>
>
> I was not receiving emails from apticron, so I took a look at the
> script it is using, found something strange...
>
> In the script at /usr/sbin/apticron the command for sending the
> email is used as "Mailx". When this is typed at the command line -->
> Command not found." What the true command should be is "mailx"
> without the capital "M".
>
> Surprising is I cant find anyone else who has come accross this
> issue.
Mailx is a shell-function which is used in the script:
# Character set handling differs between the different mailx
# implementations in Debian. Make sure we send proper headers, and a
# text/plain content type.
Mailx() {
if [ "x`readlink -e /usr/bin/mailx`" = "x/usr/bin/heirloom-mailx" ]
then
# heirloom-mailx creates correct headers, but needs help
# if the terminal charset (LC_CTYPE) is no UTF-8 locale
/usr/bin/mailx -S ttycharset=utf-8 "$@"
else
# bsd-mailx/mailutils' mailx don't do character set
# conversion, but do not support MIME either.
/usr/bin/mailx -a "MIME-Version: 1.0" \
-a "Content-type: text/plain; charset=UTF-8" \
-a "Content-transfer-encoding: 8bit" \
"$@"
fi
}
The reason why you didn't receive emails from apticron should be
something else...
Regards,
- Darsha
Tags: wontfix
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#571331: [network-manager] stale state file disables networking (after suspend)
Hi! Just stumbled over this... (hard to find this bug, when networking is disabled btw.. ;)) After updating my Squeeze system my grub-config got messed up. (I have a Dual-Boot system Debian/Squeeze and Ubuntu 10.04 - but the Ubuntu-Kernel was reassigned to Debian; anyone knows if there is bug for this - could not find one so far.) Anyway: forgot to fix my grub.cfg before I suspended to disk. I started up my notebook booted wrong kernel and the system stalled somewhere... After rebooting the right kernel my network was not working anymore. Reboot did not help. Found this. Deleted "/var/lib/NetworkManager/NetworkManager.state" and did a: $ service network-manager restart All good again. (So reboot after deleting is not necessary.) But: The bug still persists. If the system can not get up from suspend for any reason network-manager failes to bring up the network because of the stalled state-file Regards, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#580504: workaround for wrong keyboard layout problem with synergy
Package: synergy Version: 1.3.1-5 Severity: normal Hi! I actually run synergy with quicksynergy in gnome (2.28+7). I have setup two Debian/squeeze (amd64) machines. And my keyboard layout is set to "Germany Eliminate dead keys" (on both machines). When working on the client a english keyboard layout was also used with this setup. Just found a workaround (which works for me): *server-side*: 0. Stop synergy-server 1. go to System -> Preferences -> Keyboard -> Layout 2. add United States / USA (Country / Variant) 3. (you should see "Deu" or "USA" in notification-area) 4. switch to "Deu" 5. Start Synergy-Server 6. working on the client should give you a german layout (You can also switch to the english layout on-thy-fly). HTH && HAND, - Darsha -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (650, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (SMP w/2 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 synergy depends on: ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.4-1 GCC support library ii libice6 2:1.0.6-1 X11 Inter-Client Exchange library ii libsm62:1.1.1-1 X11 Session Management library ii libstdc++64.4.4-1The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-3 X11 client-side library ii libxext6 2:1.1.1-3 X11 miscellaneous extension librar ii libxinerama1 2:1.1-3X11 Xinerama extension library ii libxtst6 2:1.1.0-2 X11 Testing -- Resource extension synergy recommends no packages. synergy 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#345127: iFolder packaging
Hi! I am also highly interested in getting iFolder into Debian. There are currently some efforts in Ubuntu and google-groups to get the packaging done: [1] https://bugs.launchpad.net/ubuntu/+bug/87122 [2] http://groups.google.com/group/ifolder-ubuntu-debian-dev Looking forward to have iFolder in Debian! Regards, - Darsha P.s. I've sent: reopen 345127 stop to cont...@bugs.debian.org a few minutes ago but the bug status did not change so far... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#578498: RFP: clonezilla -- Clonezilla, based on DRBL, partclone, Partition Image, ntfsclone and udpcast, allows you to do bare metal backup and recovery.
Package: wnpp Severity: wishlist * Package name: clonezilla Version : 1.2.4-28 Upstream Author : Steven Shiau * URL : http://clonezilla.org * License : GPL Programming Lang: bash, perl Description : Clonezilla, based on DRBL, partclone, Partition Image, ntfsclone and udpcast, allows you to do bare metal backup and recovery. Seems like an interesting piece of software. I wonder why this is not in Debian and why there is no RFP for it. Greetings, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513240: wrong usage of fcopy
Hi! Took a while to retest this again, sorry! I misinterpreted the "-r" option and therefor misused the "fcopy"-command. This is what I did and how it looked like before (just sample-files created with touch): Used classes: DEFAULT,LAB % ls -laR $FAI/files root: total 2 drwxr-xr-x 2 root root 1024 2009-09-22 23:52 ./ drwxr-xr-x 5 root root 1024 2009-09-22 23:52 ../ -rw-r--r-- 1 root root0 2009-09-22 23:52 .screenrc -rw-r--r-- 1 root root0 2009-09-22 23:52 .zsh This is how it SHOULD look like: % ls -laR $FAI/files root: total 4 drwxr-xr-x 4 root root 1024 2009-09-22 23:47 ./ drwxr-xr-x 5 root root 1024 2009-09-22 23:52 ../ drwxr-xr-x 2 root root 1024 2009-09-22 23:47 .screenrc/ drwxr-xr-x 2 root root 1024 2009-09-22 23:47 .zsh/ root/.screenrc: total 2 drwxr-xr-x 2 root root 1024 2009-09-22 23:47 ./ drwxr-xr-x 4 root root 1024 2009-09-22 23:47 ../ -rw-r--r-- 1 root root0 2009-09-22 23:47 LAB root/.zsh: total 2 drwxr-xr-x 2 root root 1024 2009-09-22 23:47 ./ drwxr-xr-x 4 root root 1024 2009-09-22 23:47 ../ -rw-r--r-- 1 root root0 2009-09-22 23:47 LAB This issue can therefor be closed! That said, filling a directory with a lot of files can be somehow cumbersome. Any trick to get a couple of files into the directory with the correct classname? Like: filename -> filename/CLASSNAME filename -> filename2/CLASSNAME Greetings, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#533079: asterisk: start-stop-daemon should have --make-pid
Hi Fadion! On 14.06.2009 17:39, Faidon Liambotis wrote: > Darshaka Pathirana wrote: > #!/bin/sh > set -e > > .. /usr/share/debconf/confmodule Copy&paste mistake. The confmodule line should read like this: . /usr/share/debconf/confmodule >> --- /etc/init.d/asterisk.orig 2009-06-14 17:01:23.0 +0200 >> +++ /etc/init.d/asterisk2009-06-14 16:31:44.0 +0200 >> @@ -170,7 +170,7 @@ >> echo "$DESC is already running. Use restart." >> exit 0 >> fi >> - start-stop-daemon --start --group $GROUP --pidfile >> "$PIDFILE" \ >> + start-stop-daemon --start --group $GROUP --make-pidfile >> --pidfile "$PIDFILE" \ >> $CHDIR_PARM \ >> --exec $REALDAEMON -- $PARAMS >> >> After adding the option my postinst-script run fine. > > That's incorrect. --make-pidfile is for programs that don't create their > own pidfile. This is usually the wrong way to do things because of > processes forking into the background and changing pids. Ok. It was just a guess after comparing the way how asterisk is started with RUNASTSAFE=yes. > Asterisk creates its own pidfile, and there's no reason that we should > switch from it to start-stop-daemon. Ok. >> Please note that running "/etc/init.d/asterisk restart" on the command line >> caused no problems. So there must be something wrong in combination with >> debconf. >> (But I have no idea what why.) > > Right, we'd have a much bigger issue if "restart" didn't work :-) > I'm not sure what's the problem with your setup. > > I'll try to have a look with your example postinst at some point. Thx. That would be fine. Greetings, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#533079: asterisk: start-stop-daemon should have --make-pid
Package: asterisk Version: 1:1.4.21.2~dfsg-3 Severity: normal Tags: patch Hi! I am maintaining a local asterisk-config package and had a problem with my postinst script. The relevant sniplet looks like this (call it test.postinst): #!/bin/sh set -e .. /usr/share/debconf/confmodule # summary of how this script can be called: #* `configure' #* `abort-upgrade' #* `abort-remove' `in-favour' # #* `abort-remove' #* `abort-deconfigure' `in-favour' #`removing' # # for details, see http://www.debian.org/doc/debian-policy/ or # the debian-policy package if [ -x "/etc/init.d/asterisk" ]; then /etc/init.d/asterisk restart fi exit 0 While RUNASTSAFE was not set (and therefore defaults to "NO") the script used to hang after the postinst-process. Setting RUNASTSAFE=yes (in /etc/default/asterisk) the problem vanished. The script exited normally. This can be tested with (set RUNASTSAFE to "yes" and "no"): % sh -x ./test.postinst Curious what the problem is I found out that "--make-pid" was missing in the "start"-section without RUNASTSAFE: --- /etc/init.d/asterisk.orig 2009-06-14 17:01:23.0 +0200 +++ /etc/init.d/asterisk2009-06-14 16:31:44.0 +0200 @@ -170,7 +170,7 @@ echo "$DESC is already running. Use restart." exit 0 fi - start-stop-daemon --start --group $GROUP --pidfile "$PIDFILE" \ + start-stop-daemon --start --group $GROUP --make-pidfile --pidfile "$PIDFILE" \ $CHDIR_PARM \ --exec $REALDAEMON -- $PARAMS After adding the option my postinst-script run fine. Please note that running "/etc/init.d/asterisk restart" on the command line caused no problems. So there must be something wrong in combination with debconf. (But I have no idea what why.) Thanks for maintaining. Greetings, - Darsha -- System Information: Debian Release: 5.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-486-voyage (PREEMPT) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508616: BUG: Cacti is not displaying graphs on Debian Lenny (wrong selection of RRDTool version on default install)
Hi! FYI: this is also happens after upgrading Debian/etch to Debian/lenny. Greetings, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#492560: lvm2 should depend on busybox
Hi! Just stumbled over this problem. I also just booted a plain Debian/Lenny (using a minimal FAI-client setup). The HDD-layout looks like this: % cat /etc/fstab /dev/mapper/vg-root / ext3rw,errors=remount-ro0 1 UUID=494a0679-66ef-428e-aeab-c87ee038d0ed /boot ext3rw 0 2 /dev/mapper/vg-home /home ext3rw,nosuid 0 2 /dev/mapper/vg-tmp/tmpext3rw 0 2 /dev/mapper/vg-usr/usrext3rw 0 2 /dev/mapper/vg-var/varext3rw 0 2 /dev/mapper/vg-swap noneswapsw 0 2 % uname -a Linux faiclient 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux Although the system boots fine I got the error messages with the missing "sed" and "tr" reported by Petter. Sheridan already mentioned that the missing busybox caused that issue but I thought it would help to report my simple workaround: % aptitude install busybox % update-initramfs -u Then reboot. So the solution would be to depend lvm2 on busybox (or tr and sed). Greetings && HTH, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#513240: fai-doc: copy default dotfiles for root account without effect
Package: fai-doc Version: 3.1.8 Severity: normal Hi! After filling /files/root with some dotfiles I expected that /scripts/FAIBASE/10-misc which is provided as an example in fai-doc would copy these files into to /root of my new fai-client by using this line: # copy default dotfiles for root account fcopy -ir /root Unfortunatly that did not bring the expected success. In fact not even a log message is shown. I then tried to use ftar by creating the FAIBASE.tar.gz in /files/root with the according dotfiles and applying the following patch: --- 10-misc.orig2009-01-27 14:02:14.0 +0100 +++ 10-misc 2009-01-27 16:38:25.0 +0100 @@ -29,7 +29,7 @@ chmod 0700 $target/root chown root:root $target/root # copy default dotfiles for root account -fcopy -ir /root +ftar /root # create keyboard layout table $ROOTCMD bash -c "echo 'console-data console-data/keymap/full select $KEYMAP' | debconf-set-selections" This actually works but fails fatally if /files/root does not exists due to the fact that no -i option is available. Acctually we have three issues then: * why does fcopy does not work? (how is the fcopy-command supposed to be used to copy the dotfiles?) * if fcopy is actually is ok please update the sample or docs to clarify * ftar should have an -i option Thanks for maintaining and thanks for help! Greetings, - Darsha -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- 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#492641: hal: Mounting SATA partitions fails with insufficient privileges
On 14/08/2008 20:59, Michael Biebl wrote: > Bernd Böckmann wrote: >> Package: hal >> Version: 0.5.11-2 >> Severity: important >> >> I can not mount SATA partitions of any filesystem type by using >> gnome-mount or > > Is that a local partition or a partition on a removable device? > Mounting local partitions is forbidden (deliberately) due to security > reasons, even if the user is in group plugdev. Argl! After trying to mount a local (ntfs) partition without success I finally found this one. Could you pleaseprovide a pointer to some documentation? Any way to come around this limitation? JFTR: At first I got "Invalid mount option when attempting to mount the volume 'data' by using nautilus which itself uses gnome-mount and therefor trying to debug with: % gnome-mount -vntd /dev/sdc1 gnome-mount 0.7 ** (gnome-mount:23972): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_0AA04FACA04F9CD7 ** (gnome-mount:23972): DEBUG: read default option 'locale=' from gconf strlist key /system/storage/default_options/ntfs-3g/mount_options ** (gnome-mount:23972): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_0AA04FACA04F9CD7 with mount_point='data', fstype='ntfs-3g', num_options=1 ** (gnome-mount:23972): DEBUG: option='locale=en_US.UTF-8' ** (gnome-mount:23972): WARNING **: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_0AA04FACA04F9CD7 org.freedesktop.Hal.Device.Volume.InvalidMountOption : The option 'locale=en_US.UTF-8' is not allowed for uid=1000 After removing "locale=" from the ntfs-3g mount-options (see below) by issuing (is this is a ntfs-3g or hal bug?): % gconf-editor /system/storage/default_options/ntfs-3g and retrying the gnome-mount I then got this: gnome-mount 0.7 ** (gnome-mount:24003): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_0AA04FACA04F9CD7 ** (gnome-mount:24003): DEBUG: Mounting /org/freedesktop/Hal/devices/volume_uuid_0AA04FACA04F9CD7 with mount_point='data', fstype='ntfs-3g', num_options=0 ** (gnome-mount:24003): WARNING **: Mount failed for /org/freedesktop/Hal/devices/volume_uuid_0AA04FACA04F9CD7 org.freedesktop.Hal.Device.Volume.PermissionDenied : Refusing to mount device /dev/sdc1 for uid=1000. (where nautlius gave me "You are not privileged to mount the volume 'data'") Here the initial gconf-settings for ntfs and ntfs-3g: % gconftool --dump /system/storage/default_options/ntfs fstype_override /schemas/system/storage/default_options/ntfs/fstype_override ntfs-3g mount_options /schemas/system/storage/default_options/ntfs/mount_options umask=222 and % gconftool --dump /system/storage/default_options/ntfs-3g mount_options /schemas/system/storage/default_options/ntfs-3g/mount_options locale= *My* workaround: * removed "locale=" from "/system/storage/default_options/ntfs-3g/mount-options" % chown root:root /usr/bin/ntfs-3g % chmod 4755 /usr/bin/ntfs-3g and added the following line to /etc/fstab: /dev/sdc1 /media/data01 ntfs-3g user,noauto 0 2 Ok. Nice. But is there nonice way to mount the internal partitions without touching the fstab-file? Thanks for any help. Greetings && HAND, - Darsha -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505863: nvidia-glx: error opening libnvidia-cfg.so.1 when running nvidia-xconfig --separate-x-screens
Package: nvidia-glx Version: 173.14.09-3 Severity: normal Hi! I have a problem when running the following command: % nvidia-xconfig --no-twinview --xinerama --separate-x-screens Using X configuration file: "/etc/X11/xorg.conf". VALIDATION ERROR: Data incomplete in file /etc/X11/xorg.conf. Device section "Configured Video Device" must have a Driver line. WARNING: error opening libnvidia-cfg.so.1: libnvidia-cfg.so.1: cannot open shared object file: No such file or directory. ERROR: Unable to determine number or location of GPUs in system; cannot honor '--separate-x-screens' option. Backed up file '/etc/X11/xorg.conf' as '/etc/X11/xorg.conf.backup' New X configuration file written to '/etc/X11/xorg.conf' To reproduce this output do the following: % dpkg-reconfigure xserver-xorg # get a clean xorg.conf % nvidia-xconfig --no-twinview --xinerama --separate-x-screens Creating a symlink of libnvidia-cfg.so.1 in /usr/lib solved the problem: % ln -s /usr/lib/nvidia/libnvidia-cfg.so.173.14.09 /usr/lib/libnvidia-cfg.so.1 I may or may not be a problem of nvidia-xconfig but I can not judge that. I did a strace and figured that nvidia-xconfig was looking for libnvidia-cfg.so.1 in various places. But as there is no (version independent)libnvidia-cfg.so.1 file in the nvidia-glx package my first guess was to file bug here. I you need any more infos please let me know. Thanks for maintaining and have a nice day, - Darsha -- Package-specific info: uname -r: Linux enterprise 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 GNU/Linux /proc/version: Linux version 2.6.26-1-686 (Debian 2.6.26-8) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Oct 9 15:18:09 UTC 2008 /proc/driver/nvidia/version: 01:00.0 VGA compatible controller: nVidia Corporation GeForce 8600 GT (rev a1) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages nvidia-glx depends on: ii libc6 2.7-15 GNU C Library: Shared libraries ii libgcc1 1:4.3.2-1GCC support library ii libgl1-mesa-glx [li 7.0.3-6 A free implementation of the OpenG ii libx11-62:1.1.5-2X11 client-side library ii libxext62:1.0.4-1X11 miscellaneous extension librar ii nvidia-kernel-2.6.2 173.14.09-3+2.6.25-7 NVIDIA binary kernel module for Li ii nvidia-kernel-2.6.2 173.14.09-3+2.6.26-8 NVIDIA binary kernel module for Li ii x11-common 1:7.3+18 X Window System (X.Org) infrastruc ii zlib1g 1:1.2.3.3.dfsg-12compression library - runtime nvidia-glx recommends no packages. Versions of packages nvidia-glx suggests: ii nvidia-kernel-source 173.14.09-3 NVIDIA binary kernel module source ii nvidia-settings 173.14.09-1 Tool of configuring the NVIDIA gra -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#503887: Toshiba Portege M100 works fine with fnfxd
Package: fnfxd Version: 0.3-12 Severity: minor Tags: patch Hi! Just wanted to drop a line telling you that fnfxd works fine on my Toshiba Portege M100. --- a/READMEWed Oct 29 02:37:57 2008 +0100 +++ b/READMEWed Oct 29 02:38:13 2008 +0100 @@ -114,6 +114,7 @@ every new Toshiba laptop really should w - Toshiba Portege 3440CT - Toshiba Portege 4000 - Toshiba Portege 7020ct +- Toshiba Portege M100 - Toshiba Portege R100 - Toshiba Satellite 1410-303 - Toshiba Satellite 1410-604 Greetings and thanks for maintaining, - Darsha -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.23-grml (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages fnfxd depends on: ii libc6 2.7-5 GNU C Library: Shared libraries fnfxd recommends no packages. -- no debconf information -- I use grml (http://grml.org/) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#503885: splashy fails to detect framebuffer-mode if used with lilo
Package: splashy Version: 0.3.10-2 Severity: normal Hi! /etc/init.d/splashy tries to detect a valid framebuffer mode by looking in "/proc/cmdline" (to start splashy if not started in initramfs). The problem is that lilo has it's own "vga=" line and therefore "/proc/cmdline" does neither contain "vga" nor "video". I tried a few thing to get the current framebuffer video mode but without success. The only thing coming close to it is "fbset -s". The code in subject is: for x in $(cat /proc/cmdline); do case $x in single) SINGLE="true" ;; splash) SPLASH="true" ;; nosplash) SPLASH="false" ;; vga=*|video=*) FBMODESET="true" ;; esac done [ "$SPLASH" = "true" -a "$FBMODESET" = "true" ] && ENABLE=1 If more informations is needed please let me know. Have a nice day and thanks for maintaining, - Darsha -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.23-grml (SMP w/1 CPU core; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages splashy depends on: ii initramfs-tools 0.91ctools for generating an initramfs ii libc6 2.7-5GNU C Library: Shared libraries ii libdirectfb-1.0-0 1.0.1-11 direct frame buffer graphics - sha ii libgcc1 1:4.2.2-4GCC support library ii libglib2.0-02.16.3-2 The GLib library of C routines ii libmagic1 4.21-4 File type determination library us ii libsplashy1 0.3.7-1 Library to draw splash screen on b ii lsb-base3.1-24 Linux Standard Base 3.1 init scrip ii zlib1g 1:1.2.3.3.dfsg-8 compression library - runtime splashy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#502276: isdnutils-base: copy/paste typo in init-script
Package: isdnutils-base Version: 1:3.9.20060704-3.4 Severity: minor Tags: patch Hi! Just a minor thing I've just seen in the init-script. Here's the patch: --- a/init.d/isdnutils Wed Oct 15 00:33:45 2008 +0200 +++ b/init.d/isdnutils Wed Oct 15 10:00:30 2008 +0200 @@ -39,7 +39,7 @@ service="$2" case "$service" in ipppd|isdnlog) ;; - *) log_failure_msg "Unknown ISDN service to stop: $2"; exit 1 + *) log_failure_msg "Unknown ISDN service to start: $2"; exit 1 esac [ -s /usr/sbin/$service ] || exit 0 log_begin_msg "Starting $service..." Greetings, - Darsha -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages isdnutils-base depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii libc6 2.7-14 GNU C Library: Shared libraries ii libncurses5 5.6+20080830-1 shared libraries for terminal hand ii lsb-base 3.2-20 Linux Standard Base 3.2 init scrip ii makedev 2.3.1-88 creates device files in /dev isdnutils-base recommends no packages. Versions of packages isdnutils-base suggests: pn ipppd (no description available) ii isdnlog 1:3.9.20060704-3.4 ISDN connection logger pn isdnutils-doc (no description available) pn isdnutils-xtools (no description available) ii isdnvboxclient1:3.9.20060704-3.4 ISDN answering machine, client ii isdnvboxserver1:3.9.20060704-3.4 ISDN answering machine, server -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#370050: /var/log/btmp and /var/log/wtmp permission
Here we go... After wondering why logrotate.conf wants to set the file-permission to 0660 of the /var/log/btmp after the upgrade I looked around a bit... Altough I think 0660 of /var/log/btmp AND /var/log/wtmp is a good idea it seems that the default permission of these files is 0664. IMHO this default should not be changed by logrotate. Also"tiger" now ignores the 0664 permissions of these files (see /etc/tiger/tiger.ignore). I don't know why and when this changed but it may be worth a try to ask the tiger-guys. Greetings and thanks for maintaining, - Darsha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#335544: rdesktop: Copy/paste doesn't work in fullscreen
On 20:59, Tomas Fasth wrote:
> There is a registered bug (1198945) at sourceforge about a clipboard
> problem. It doesn't mention anything about full-screen mode, so I
> decided to register a new bug. The request is:
[snip]
Maybe it's just a ("the") RDP-Server-clipboard-problem:
[1]
http://brennan.offwhite.net/blog/2007/01/18/fixing-copypaste-for-remote-desktop-sessions/
Quote:
- Use Task Manager to kill the rdpclip.exe process
- Run rdpclip.exe to restart it
HTH && HAND,
- Darsha
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#500168: php5-common: magic_quotes_gpc should be off
Package: php5-common Version: 5.2.0-8+etch11 Severity: important Hi! /etc/php5/apache2/php5.ini contains magic_quotes_gpc = On but should be magic_quotes_gpc = Off because it's deprecated and is "highly discouraged": [1] http://at2.php.net/manual/en/info.configuration.php#ini.magic-quotes-gpc Greetings, - Darsha -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-5-xen-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages php5-common depends on: ii sed 4.1.5-1The GNU sed stream editor php5-common recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413548: shorewall: NAT (masquerade) rules lost after reboot
On 09.04.2008 22:00, Roberto C. Sánchez wrote: > On Wed, Apr 09, 2008 at 07:28:19PM +0200, Darshaka Pathirana wrote: >> On 07.04.2008 23:00, Roberto C. Sánchez wrote: >>> On Mon, Apr 07, 2008 at 12:36:51PM +0200, Darshaka Pathirana wrote: >>>> JFTR: I've sent you the logs I have directly to you... >>>> >>> I have spoken with Tom Eastep about it and forwarded the logs to him as >>> well. His assessment was that something is causing ip forwarding to be >>> turned off (or at least keeping it from being turned on). >>> >>> In the Debian package, IP_FORWARD defaults to "Keep", instead of "On". >>> This is so that values set manually or via /etc/sysctl.conf are not >>> disrupted by Shorewall. In your case, you would want Shorewall to >>> enable it unconditionally since you are not enabling it elsewhere. >>> >>> Please confirm if this works for you so that this bug report can be >>> closed. >> Yes. IP_FORWARD=On works perfectly for me on Debian/Etch. >> > Excellent. > >> BUT: I just found an old Debian/Sarge machine... >> >> And there IP_FORWARD is set to "Keep" AND /etc/sysctl.conf is empty >> (so there is no "/proc/sys/net/ipv4/ip_forward = 1"). Just being >> curious as we are talking about an old shorewall version (2.2.3-2). >> Why does that work? >> > That I could not tell you. Perhaps something else (like one of the > networking scripts) is turning off ip_forward and Shorewall is > respecting the setting made by that script. Ok. Doesn't matter. I just wanted to let you know. Just close the bug. One bug less! Yipee! ;) Greetings, - Darsha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413548: shorewall: NAT (masquerade) rules lost after reboot
On 07.04.2008 23:00, Roberto C. Sánchez wrote: > On Mon, Apr 07, 2008 at 12:36:51PM +0200, Darshaka Pathirana wrote: >> JFTR: I've sent you the logs I have directly to you... >> > I have spoken with Tom Eastep about it and forwarded the logs to him as > well. His assessment was that something is causing ip forwarding to be > turned off (or at least keeping it from being turned on). > > In the Debian package, IP_FORWARD defaults to "Keep", instead of "On". > This is so that values set manually or via /etc/sysctl.conf are not > disrupted by Shorewall. In your case, you would want Shorewall to > enable it unconditionally since you are not enabling it elsewhere. > > Please confirm if this works for you so that this bug report can be > closed. Yes. IP_FORWARD=On works perfectly for me on Debian/Etch. BUT: I just found an old Debian/Sarge machine... And there IP_FORWARD is set to "Keep" AND /etc/sysctl.conf is empty (so there is no "/proc/sys/net/ipv4/ip_forward = 1"). Just being curious as we are talking about an old shorewall version (2.2.3-2). Why does that work? Greetings, - Darsha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413548: shorewall: NAT (masquerade) rules lost after reboot
Hi! On 14.03.2008 12:11, Roberto C. Sánchez wrote: > On Fri, Mar 14, 2008 at 11:18:53AM +0100, Darshaka Pathirana wrote: > >> I also had the same problem yesterday. >> >> After the reboot I had to issue >> >> % shorewall clear >> % shorewall restart >> >> So I created a "shorewall dump" directly after rebooting and one >> directly after clearing and restarting. The main difference I found was: >> >> - /proc/sys/net/ipv4/ip_forward = 0 >> + /proc/sys/net/ipv4/ip_forward = 1 >> > The best thing would be if you could send a compressed shorewall dump > from each of the following times: > > - just after reboot > - after shorewall clear > - after shorewall restart > > If you are not comfortable sending it to the bug, then send to my email > directly. > >> Ok, now it all makes sense. After researching the shorewall-doc I >> found this: >> >> [1] http://www.shorewall.net/two-interface.htm#SNAT >> >> and >> >> /usr/share/doc/shorewall/README.Debian.gz >> >> which states to set "IP_FORWARD=On" in the shorewall.conf. >> >> So the problem seemed to be RTFM! Don't you think that this is the actual solution to this problem? JFTR: I've sent you the logs I have directly to you... Greetings, - Darsha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413548: shorewall: NAT (masquerade) rules lost after reboot
Hi Roberto! On 14.03.2008 12:11, Roberto C. Sánchez wrote: > On Fri, Mar 14, 2008 at 11:18:53AM +0100, Darshaka Pathirana wrote: >> >> I also had the same problem yesterday. >> >> After the reboot I had to issue >> >> % shorewall clear >> % shorewall restart >> >> So I created a "shorewall dump" directly after rebooting and one >> directly after clearing and restarting. The main difference I found was: >> >> - /proc/sys/net/ipv4/ip_forward = 0 >> + /proc/sys/net/ipv4/ip_forward = 1 >> > The best thing would be if you could send a compressed shorewall dump > from each of the following times: > > - just after reboot > - after shorewall clear > - after shorewall restart > > If you are not comfortable sending it to the bug, then send to my email > directly. I am sorry, but the system was already in production at the time I wrote the Bug-Message. So I am not able to do any reboots anymore. Moreover, I feel a little unconfortable submitting a customers log (altough I possibly could mask the IP-Adresses etc.) If you think it would really, really be helpfull to have these logs let me know, I'll try to send you the logs I have (just after reboot and after shorewall restart; I didn't dump the log after clearing). >> Ok, now it all makes sense. After researching the shorewall-doc I >> found this: >> >> [1] http://www.shorewall.net/two-interface.htm#SNAT >> >> and >> >> /usr/share/doc/shorewall/README.Debian.gz >> >> which states to set "IP_FORWARD=On" in the shorewall.conf. >> >> So the problem seemed to be RTFM! >> >> BUT.. >> >> As I just copied the files from >> "/usr/share/doc/shorewall/examples/two-interfaces" I think there >> should be some kind of "README.Debian" too where this issue should >> be mentioned! > > I will certainly look into this. Thx and thx for maintaining shorewall! Nice work! Greetings, - Darsha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#413548: shorewall: NAT (masquerade) rules lost after reboot
Hi! I also had the same problem yesterday. After the reboot I had to issue % shorewall clear % shorewall restart So I created a "shorewall dump" directly after rebooting and one directly after clearing and restarting. The main difference I found was: - /proc/sys/net/ipv4/ip_forward = 0 + /proc/sys/net/ipv4/ip_forward = 1 Ok, now it all makes sense. After researching the shorewall-doc I found this: [1] http://www.shorewall.net/two-interface.htm#SNAT and /usr/share/doc/shorewall/README.Debian.gz which states to set "IP_FORWARD=On" in the shorewall.conf. So the problem seemed to be RTFM! BUT.. As I just copied the files from "/usr/share/doc/shorewall/examples/two-interfaces" I think there should be some kind of "README.Debian" too where this issue should be mentioned! HTH && HAND - Darsha -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#430940: "Warning: preg_replace_callback() ... markdown.php on line 826" on every page
Package: flyspray Version: 0.9.8-10 Severity: important After installing and configuring flyspray the following warning is shown on every page: Warning: preg_replace_callback() [function.preg-replace-callback]: Unknown modifier '|' in /usr/share/flyspray/htdocs/includes/markdown.php on line 826 After replacing markdown.php with the latest version (1.0.1f) of php-Markdown [1] it seems work. [1] http://www.michelf.com/projects/php-markdown/ I'm not sure what the problem is, but I think Ñ–t has something to do with the current php-version, since the same file did work in Debian/sarge with php4 (4.3.10-16). I hope somebody can reproduce the problem. If anything is missing please let me know! Thx. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-xen-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages flyspray depends on: ii apache22.2.3-4 Next generation, scalable, extenda ii apache2-mpm-prefork [httpd 2.2.3-4 Traditional model for Apache HTTPD ii debconf [debconf-2.0] 1.5.11Debian configuration management sy ii libapache2-mod-php55.2.0-8+etch1 server-side, HTML-embedded scripti ii libphp-adodb 4.93a-1.1 The 'adodb' database abstraction l ii php5 5.2.0-8+etch1 server-side, HTML-embedded scripti ii php5-mysql 5.2.0-8+etch1 MySQL module for php5 ii ucf2.0020Update Configuration File: preserv ii wwwconfig-common 0.0.48Debian web auto configuration Versions of packages flyspray recommends: pn graphviz (no description available) pn php5-cli | php4-cli(no description available) -- debconf information: * flyspray/database_name: flyspray * flyspray/database_user: root * flyspray/databasemgr_type: MySQL * flyspray/purge_removes_data: true flyspray/webgroup: www-data * flyspray/dbmyadmin: root * flyspray/welcome: flyspray/database_upgrade: * flyspray/webserver_type: Apache2 * flyspray/databasemgr_server: localhost flyspray/webuser: www-data flyspray/database_downgrade: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
