Bug#1016747: kea: Adjust log file in default config to match Debian config
Package: kea
Version: 2.0.2-3
Severity: normal
Dear Maintainer,
the package will install
/etc/kea/kea-{ctrl-agent,dhcp4,dhcp6,dhcp-ddns}.conf
files which all have set
> "loggers": [
> {
> "output_options": [
> {
> // Specifies the output file. There are several
special values
> // supported:
> // - stdout (prints on standard output)
> // - stderr (prints on standard error)
> // - syslog (logs to syslog)
> // - syslog:name (logs to syslog using specified name)
> // Any other value is considered a name of the file
> "output":
"/var/log/kea-{ctrl-agent,dhcp4,dhcp6,dhcp-ddns}.log"
> }
> ]
> }
> ]
However, default kea services cannot write to this location because they
are running as "_kea" user on Debian by default.
You are already creating /var/log/kea so I would suggest to update
default config to use that directory by default.
I run into this when I increased severity of log messages to debug an
issue but didn't find any logs. After adjusting paths I got the logs
I was looking for.
Thanks!
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-3-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.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 kea depends on:
ii kea-admin 2.0.2-3
ii kea-ctrl-agent2.0.2-3
ii kea-dhcp-ddns-server 2.0.2-3
ii kea-dhcp4-server 2.0.2-3
ii kea-dhcp6-server 2.0.2-3
kea recommends no packages.
kea suggests no packages.
-- no debconf information
Bug#805310: libsasl2-modules: Annoying message "DIGEST-MD5 common mech free" with slapd
Dear Maintainer, I can confirm that this is still a bug in Debian 9.5. I get this message all the time on my subversion server. Any advice on how to get rid of this message for now? And what plans are there to fix this in future releases? BR Thomas
Bug#870214: Status on 870214
Hi, I can confirm this problem exists in stable. Any plans on fixing this? Or at least provide a means of suppressing the warnings? BR Thomas
Bug#879664: backupninja cron jobs does not behave nicely with systemd - resulting in lots of errors in the logs
Package: backupninja Version: 1.0.1-2 Severity: normal Dear Maintainer, I have been using backupninja for a long time and it is really helpful. After upgrading to Debian 9 I started seing a lot of errors such as these in my syslog: 2017-10-23T01:00:15.795982+02:00 fer systemd[1]: user@500.service: Start request repeated too quickly. 2017-10-23T01:00:15.796132+02:00 fer systemd[1]: Failed to start User Manager for UID 500. 2017-10-23T01:00:15.796271+02:00 fer systemd[1]: user@500.service: Unit entered failed state. 2017-10-23T01:00:15.796409+02:00 fer systemd[1]: user@500.service: Failed with result 'start-limit-hit'. 2017-10-23T01:00:15.796702+02:00 fer su[11455]: pam_systemd(su:session): Failed to create session: Start job for unit user@500.service failed with 'failed' 2017-10-23T01:00:21.594947+02:00 fer systemd[1]: user@500.service: Start request repeated too quickly. 2017-10-23T01:00:21.595070+02:00 fer systemd[1]: Failed to start User Manager for UID 500. 2017-10-23T01:00:21.595212+02:00 fer systemd[1]: user@500.service: Failed with result 'start-limit-hit'. 2017-10-23T01:00:21.596172+02:00 fer su[11486]: pam_systemd(su:session): Failed to create session: Start job for unit user@500.service failed with 'failed' A bit of investigation with help from the IRC lead to the conclusion that this is caused by backupninja's postgresql jobs. Backupninja includes ninjahelper - a tool that makes it easier to create backup jobs for backupninja. Including dump jobs for various RDBMS. The above errors seem to be caused by the PG dump job running via cron. Backupninja seems to be running via cron every hours. And when it notices that some backup job is to be run, it starts the appropriate backup job. Something seems to go wrong when it does this for the PG dump job. Maybe it is due to the way it uses su/sudo - I am not sure. But it does give a lot of noise in the syslog. I have tried deleting the PG dump jobs I had that was created in Debian 8 and then create a new one using ninjahelper. The hope was that maybe there were some old stuff in the debian 8 version that did not work in debian 9. However, the newly created job produces the same errors. -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8), LANGUAGE=en_DK:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages backupninja depends on: ii bash 4.4-5 ii dialog 1.3-20160828-2 ii gawk 1:4.1.4+dfsg-1 ii mailutils [mailx] 1:3.1.1-1 ii mawk 1.3.3-17+b3 backupninja recommends no packages. Versions of packages backupninja suggests: ii bzip2 1.0.6-8.1 ii debconf-utils 1.5.61 ii duplicity 0.7.11-1 pn genisoimage ii hwinfo 21.38-1 ii mdadm 3.4-4+b1 ii rdiff-backup 1.2.8-7 ii rsync 3.1.2-1 ii subversion 1.9.5-1+deb9u1 ii trickle1.07-10+b1 pn wodim -- Configuration Files: /etc/backupninja.conf [Errno 13] Permission denied: '/etc/backupninja.conf' -- no debconf information
Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session
2017-09-19 20:21 GMT+02:00 Michael Biebl <bi...@debian.org>: > Am 19.09.2017 um 09:36 schrieb Thomas D: > > Dear maintainers, > > > > I can confirm this bug is present in an up-to-date Stretch as of today. > > Are there any plans on this being fixed in Stretch? > > Not that I'm aware of. Do you want to work on it? > > > I am not sure I have the skills needed to fix this. I mean, Christian Kastner mentions that it works in systemd 222-2: > I can successfully trace this back to systemd 223-1 (with 222-2, > everything is still fine). So I can do a diff between 222-2 and current systemd. However, if the change is non-trivial I would probably not be able to fix it. BR Thomas
Bug#825949: pam_systemd(su:session): Cannot create session: Already running in a session
Dear maintainers, I can confirm this bug is present in an up-to-date Stretch as of today. Are there any plans on this being fixed in Stretch? BR Thomas
Bug#777534: Please do _NOT_ change postgrey text
Hi, while I agree that an information about the reject reason could be helpful for the administrator of the sending system please don't forget that postgrey is more like a check to test if you are dealing with a real mail system (i.e. something with a queue). Nothing more. So while this information can be useful for real administrators of legitimate systems it could also help the bad guys because they could adjust the retry frequency based on the reject message. In the current status when the sender doesn't know the exact block time, there's a chance that other mechanism will be triggered by bad guys (i.e. limits) when the sender is retrying to fast. tl;dr If the reporter wants to provide helpful information for the sender's mail system administrator he can change the text in "/etc/default/postgrey" for his setup. But such a change wouldn't be great default for most people. -Thomas
Bug#754288: /sbin/kexec: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y
Hi intrigeri, you wrote: Did you test this again with current kexec-tools from Jessie or testing/sid? The problem was resolved upstream (kernel) with commit From f285f4a21c3253887caceed493089ece17579d59 Mon Sep 17 00:00:00 2001 From: Kees Cook Date: Thu, 15 Jan 2015 16:51:46 -0800 Subject: x86, boot: Skip relocs when load address unchanged On 64-bit, relocation is not required unless the load address gets changed. Without this, relocations do unexpected things when the kernel is above 4G. Link: http://marc.info/?l=linux-kernelm=142136953524246 This patch is now included in every stable kernel. For Jessie the patch was first included in 3.16.7-ckt6. So this bug can be closed I guess. -Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#761300: libc6: Printf(%c,'x') does not follow stdio
Package: libc6
Version: 2.13-38+rpi2+deb7u3
Severity: normal
Dear Maintainer,
* What led up to the situation?
Redirecting stdout in C code does not work for printf(%c,'x')
I ssh into the system. I want to redirect all output to stdout to
the local terminal. This works as expected for everything except
when printing a single character.
* What exactly did you do (or not do) that was effective (or
ineffective)?
FILE *display_fp;
if ((display_fp = fopen(/dev/tty1,r+)) == NULL) {
perror(Open /dev/tty1);
return -1;
}
stdout = display_fp;
Then,
printf(%s,asdfasdf); /* output to /dev/tty1 */
printf(%c,'x'); /* output to original terminal */
* What was the outcome of this action?
All the output except for the %c case went to /dev/tty1. The
output in the %c case went to the ssh terminal
* What outcome did you expect instead?
I expected all the output to go to /dev/tty1
-- System Information:
Debian Release: 7.6
Architecture: armhf (armv6l)
Kernel: Linux 3.12.22+ (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=ANSI_X3.4-1968)
(ignored: L
C_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Versions of packages libc6 depends on:
ii libc-bin 2.13-38+rpi2+deb7u3
ii libgcc1 1:4.7.2-5+rpi1
libc6 recommends no packages.
Versions of packages libc6 suggests:
ii debconf [debconf-2.0] 1.5.49
pn glibc-doc none
ii locales2.13-38+rpi2+deb7u3
-- debconf information:
glibc/upgrade: true
glibc/restart-services:
* libraries/restart-without-asking: true
glibc/disable-screensaver:
glibc/restart-failed:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#757287: pdns-server: Please add tinydns backend
Package: pdns-server Version: 3.3.1-4 Severity: wishlist Dear Maintainer, please consider adding the tinydns backend. This would make migrating from djbdns to PowerDNS less painful because you can migrate step by step (servers, backends, tooling). No need to upgrade all at once... Thanks! -Thomas -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pdns-server depends on: ii adduser 3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii libboost-program-options1.55.0 1.55.0+dfsg-2 ii libboost-serialization1.55.01.55.0+dfsg-2 ii libbotan-1.10-0 1.10.8-1 ii libc6 2.19-7 ii libcrypto++95.6.1-6 ii libgcc1 1:4.9.1-1 ii libgmp102:6.0.0+dfsg-4 ii liblua5.1-0 5.1.5-5 ii libpolarssl61.3.7-2.1 ii libsqlite3-03.8.5-2 ii libstdc++6 4.9.1-1 ii lsb-base4.1+Debian13 ii ucf 3.0030 ii zlib1g 1:1.2.8.dfsg-1 pdns-server recommends no packages. Versions of packages pdns-server suggests: pn pdns-backend none pn pdns-recursor none -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754288: /sbin/kexec: kexec fails to boot kernels where CONFIG_RANDOMIZE_BASE=y
Package: kexec-tools Version: 1:2.0.4-1 Severity: important File: /sbin/kexec Dear Maintainer, after creating my own kernel with CONFIG_RANDOMIZE_BASE=y (that's not a debian default) I noticed that the system won't reboot using kexec. I am getting a black screen/CPU will be halted. The machine will need a power cycle. # zgrep 'RANDOMIZE' /proc/config.gz CONFIG_RANDOMIZE_BASE=y CONFIG_RANDOMIZE_BASE_MAX_OFFSET=0x4000 Recompiling the same kernel (I tried 3.4.11 and 3.15.4) without CONFIG_RANDOMIZE_BASE will make kexec work again. I also tested upstream's kexec-tools v2.0.7 to see if this problem is fixed already in a newer version but it isn't. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kexec-tools depends on: ii debconf [debconf-2.0] 1.5.53 ii libc6 2.19-4 kexec-tools recommends no packages. kexec-tools suggests no packages. -- debconf information: kexec-tools/use_grub_config: false * kexec-tools/load_kexec: true -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714929: Still doesn't work with 3.10-2
Hi, I am experience the same issue with Debian running as guest OS in VMware Workstation 9.0.2. Happens with: - 3.9-1 - 3.10-1 - and still with 3.10-2 The mentioned workaround from Bernhard (setting kernel parameter vmwgfx.enable_fbdev=1) works for me. Another solution might be installing a modprobe.d conf file containing options vmwgfx enable_fbdev=1. -- Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701511: [squeeze] At boot, the wrong b43 driver is loaded. I installed compat-drivers-3.7.6-1
On 02/24/13 00:56, Jonathan Nieder wrote: # hardware support severity 701511 important quit Hi, tomdean wrote: The b43 driver installed at boot does not work. I have included a work around. I installed the b43 driver from compat-drivers-3.7.6-1 and it works. Thanks for testing (and thanks to Holger for passing on the report). Am I correct in guessing that the 3.2.y kernel from wheezy or squeeze-backports works fine? We might be able to backport the missing support to the 2.6.32.y kernel in a future squeeze point release if it's simple. Pursuing that would require a little information about your wifi card (its PCI id) and some help testing it. Output from reportbug --template linux-image-$(uname -r) should be enough to get started. Hope that helps, Jonathan sudo update-initramfs -u Fixed the problem. I appropriate, please close the PR. Tom Dean -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701511: [squeeze] At boot, the wrong b43 driver is loaded. I installed compat-drivers-3.7.6-1
On 02/24/13 01:15, Jonathan Nieder wrote: Thomas D. Dean wrote: tomdean wrote: The b43 driver installed at boot does not work. I have included a work around. I installed the b43 driver from compat-drivers-3.7.6-1 and it works. [...] sudo update-initramfs -u Fixed the problem. Um, do you mean that when installing squeeze on your hardware: 1. The b43 driver does not work out of the box 2. Running sudo update-initramfs -u is enough to get it working 3. An alternative way to get it working is to install the b43 driver from compat-drivers ? In any case, please attach output from reportbug --template linux-image-$(uname -r). It is useful context. Puzzled, Jonathan Include network configuration and status from this computer? Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: tomdean tomd...@speakeasy.org To: Debian Bug Tracking System sub...@bugs.debian.org Subject: none X-Debbugs-Cc: tomd...@speakeasy.org Package: linux-2.6 Version: 2.6.32-46 Severity: wishlist -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-46) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 09:49:36 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID=ee88c460-9819-4828-94f2-9ef39ae70c16 ro quiet ** Not tainted ** Kernel log: [8.309650] nouveau :01:00.0: putting AGP V3 device into 8x mode [8.309678] [drm] nouveau :01:00.0: 128 MiB GART (aperture) [8.309969] [drm] nouveau :01:00.0: Allocating FIFO number 0 [8.310829] [drm] nouveau :01:00.0: nouveau_channel_alloc: initialised FIFO 0 [8.310839] [drm] nouveau :01:00.0: Initial CRTC_OWNER is 0 [8.310846] [drm] nouveau :01:00.0: Saving VGA fonts [8.381046] intel8x0_measure_ac97_clock: measured 54026 usecs (2603 samples) [8.381052] intel8x0: clocking to 48000 [8.383428] Intel ICH Modem :00:1f.6: PCI INT B - GSI 17 (level, low) - IRQ 17 [8.383455] Intel ICH Modem :00:1f.6: setting latency timer to 64 [8.388490] [drm] nouveau :01:00.0: Detected a LVDS connector [8.494451] [drm] nouveau :01:00.0: Detected a VGA connector [8.494517] [drm] nouveau :01:00.0: Detected a TV connector [8.496836] [drm] nouveau :01:00.0: Setting dpms mode 3 on lvds encoder (output 0) [8.496843] [drm] nouveau :01:00.0: Calling LVDS script 1: [8.496848] [drm] nouveau :01:00.0: Calling LVDS script 6: [8.496852] [drm] nouveau :01:00.0: 0xDD31: Parsing digital output script table [8.736045] MC'97 0 converters and GPIO not ready (0x1) [9.47] [drm] nouveau :01:00.0: Setting dpms mode 3 on vga encoder (output 1) [9.55] [drm] nouveau :01:00.0: Setting dpms mode 3 on TV encoder (output 2) [9.092245] [drm] nouveau :01:00.0: allocated 1440x900 fb: 0x49000, bo d7b52600 [9.104477] [drm] nouveau :01:00.0: Output LVDS-1 is running on CRTC 1 using output A [9.104481] [drm] nouveau :01:00.0: Calling LVDS script 2: [9.104485] [drm] nouveau :01:00.0: 0xDE4E: Parsing digital output script table [9.160028] [drm] nouveau :01:00.0: Setting dpms mode 0 on lvds encoder (output 0) [9.160031] [drm] nouveau :01:00.0: Calling LVDS script 5: [9.160035] [drm] nouveau :01:00.0: 0xDD1A: Parsing digital output script table [9.160046] [drm] nouveau :01:00.0: Output LVDS-1 is running on CRTC 1 using output A [9.164195] Console: switching to colour frame buffer device 180x56 [9.168345] fb0: nouveaufb frame buffer device [9.168348] registered panic notifier [9.168355] [drm] Initialized nouveau 0.0.15 20090420 for :01:00.0 on minor 0 [9.672085] Adding 1004020k swap on /dev/sda7. Priority:-1 extents:1 across:1004020k [ 10.265197] EXT3 FS on sda1, internal journal [ 10.445029] loop: module loaded [ 12.609711] kjournald starting. Commit interval 5 seconds [ 12.609978] EXT3 FS on sda9, internal journal [ 12.609985] EXT3-fs: mounted filesystem with ordered data mode. [ 12.647497] kjournald starting. Commit interval 5 seconds [ 12.647736] EXT3 FS on sda8, internal journal [ 12.647742] EXT3-fs: mounted filesystem with ordered data mode. [ 12.695301] kjournald starting. Commit interval 5 seconds [ 12.695560] EXT3 FS on sda5, internal journal [ 12.695566] EXT3-fs: mounted filesystem with ordered data mode. [ 12.732744] kjournald starting. Commit interval 5 seconds [ 12.732997] EXT3 FS on sda6, internal journal [ 12.733005] EXT3-fs: mounted filesystem with ordered data mode. [ 14.932069] b43-phy0: dea29de4 [ 14.997538] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 17.260348] wlan0: authenticate with 08:86:3b:d6:f5:c8 [ 17.272169] wlan0: send auth to 08:86:3b:d6:f5:c8 (try 1/3) [ 17.273657] wlan0: authenticated [ 17.277015] wlan0: associate with 08:86:3b:d6:f5:c8 (try 1/3) [ 17.279563] wlan0: RX AssocResp
Bug#675763: gnome-settings-daemon: gnome-setting-daemon segfaults in libmouse.so
Message-ID: 20120611154318.11059.52169.report...@julia.dial.org X-Mailer: reportbug 6.3.1 Date: Mon, 11 Jun 2012 11:43:18 -0400 Package: gnome-settings-daemon Version: 3.4.2-3 Followup-For: Bug #675763 Dear Maintainer, On 6/11 04:03 GMT I did a dist-upgrade to pick up wheezy/sid changes for the last week or so. This upgraded gnome-settings-daemon:i386 3.2.2-3 to 3.4.2-3. Hardware is an Asus EEEPC 1000HE. Results appear to match Bug #675763 exactly, and I make two additional observations that may or may not be significant. 1. The fault occurs only for one particular user. Operation is normal for two others. 2. Probably a result of #1: Can't turn off touchpad using the Fn-F4 key combination for the affected user. This also works correctly for other users. So it looks like the problem may result from or interact with per-user gnome settings. If the user configuration details will be useful, please feel free to ask. Tom Dial tdd...@world.oberlin.edu -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-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 Versions of packages gnome-settings-daemon depends on: ii dconf-gsettings-backend [gsettings-backend] 0.12.1-1 ii dpkg 1.16.3 ii gsettings-desktop-schemas3.4.2-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-33 ii libcairo-gobject21.12.2-1 ii libcairo21.12.2-1 ii libcanberra-gtk3-0 0.28-4 ii libcanberra0 0.28-4 ii libcolord1 0.1.18-1 ii libcomerr2 1.42.2-2 ii libcups2 1.5.3-1 ii libdbus-glib-1-2 0.98-1 ii libfontconfig1 2.9.0-5 ii libgcrypt11 1.5.0-3 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgnome-desktop-3-2 3.4.2-1 ii libgnomekbd7 3.4.0.2-1 ii libgnutls26 2.12.19-1 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libgtk-3-0 3.4.2-1 ii libgudev-1.0-0 175-3.1 ii libk5crypto3 1.10.1+dfsg-1 ii libkrb5-31.10.1+dfsg-1 ii liblcms2-2 2.2+git20110628-2.2 ii libnotify4 0.7.5-1 ii libnspr4 2:4.9-3 ii libnspr4-0d 2:4.9-3 ii libnss3 2:3.13.4-3 ii libnss3-1d 2:3.13.4-3 ii libpackagekit-glib2-14 0.7.4-3 ii libpango1.0-01.30.0-1 ii libpolkit-gobject-1-00.104-2 ii libpulse-mainloop-glib0 2.0-3 ii libpulse02.0-3 ii libsqlite3-0 3.7.12.1-1 ii libupower-glib1 0.9.16-2 ii libwacom20.4-1 ii libx11-6 2:1.4.99.901-2 ii libxfixes3 1:5.0-4 ii libxi6 2:1.6.1-1 ii libxklavier165.2.1-1 ii libxtst6 2:1.2.1-1 ii nautilus-data3.4.2-1 ii zlib1g 1:1.2.7.dfsg-11 Versions of packages gnome-settings-daemon recommends: ii pulseaudio 2.0-3 Versions of packages gnome-settings-daemon suggests: ii gnome-screensaver3.4.1-1 ii metacity [x-window-manager] 1:2.34.3-2 ii x11-xserver-utils7.7~3 -- 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#658816: flashplugin-nonfree may leave old library, breaking operation in Iceweasel
Package: flashplugin-nonfree Version: 1:2.8.2 Severity: normal s problem may result from my error, but will submit in case it is not. To upgrade flash from 10.0.21.1 to the current 11.1.102.55, I reinstalled flashplugin-nonfree, rather than the presumably more correct update-flashplugin-nonfree (8). This appeared to do something approximately correct and installed libflashplayer.so in /usr/lib/flashplugin-nonfree/libflashplayer.so, but left the old libflashplayer.so (Version 10.0.21.1) in /usr/lib/iceweasel/plugins/. For some sites (e. g., www.southparkstudios.com) attempting to execute the flashplayer in Iceweasel failed until I moved the 10.0.21.1 library aside and after some testing, removed it. Additional environment information: Iceweasel 3.5.16 (About ID string: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20120131 Iceweasel/3.5.16 (like Firefox/3.5.16)) I installed flashplayer using Adobe's installer script at least once in the past before learning of the Debian package. However, at least the last two were done with flashplugin-nonfree. *** -- Package-specific info: Debian version: 6.0.4 Architecture: amd64 Package version: 1:2.8.2 Adobe Flash Player version: LNX 11,1,102,55 MD5 checksums: 57f36b399d861b604611f045fc23cf8c /var/cache/flashplugin-nonfree/install_flash_player_11_linux.x86_64.tar.gz d4d48f1ad3995a698025dcd33e471aff /usr/lib/flashplugin-nonfree/libflashplayer.so Alternatives: flash-mozilla.so - auto mode link currently points to /usr/lib/flashplugin-nonfree/libflashplayer.so /usr/lib/flashplugin-nonfree/libflashplayer.so - priority 50 Current 'best' version is '/usr/lib/flashplugin-nonfree/libflashplayer.so'. lrwxrwxrwx 1 root root 34 Feb 5 18:13 /usr/lib/mozilla/plugins/flash-mozilla.so - /etc/alternatives/flash-mozilla.so /usr/lib/mozilla/plugins/flash-mozilla.so: symbolic link to `/etc/alternatives/flash-mozilla.so' -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-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 flashplugin-nonfree depends on: ii debconf [debconf-2.0 1.5.36.1Debian configuration management sy ii gnupg1.4.10-4GNU privacy guard - a free PGP rep ii libatk1.0-0 1.30.0-1The ATK accessibility toolkit ii libcairo21.8.10-6The Cairo 2D vector graphics libra ii libcurl3-gnutls 7.21.0-2.1+squeeze1 Multi-protocol file transfer libra ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.2-2.1+squeeze3 FreeType 2 font engine, shared lib ii libgcc1 1:4.4.5-8 GCC support library ii libglib2.0-0 2.24.2-1The GLib library of C routines ii libgtk2.0-0 2.20.1-2The GTK+ graphical user interface ii libnspr4-0d 4.8.6-1 NetScape Portable Runtime Library ii libnss3-1d 3.12.8-1+squeeze4 Network Security Service libraries ii libpango1.0-01.28.3-1+squeeze2 Layout and rendering of internatio ii libstdc++6 4.4.5-8 The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-4 X11 client-side library ii libxext6 2:1.1.2-1 X11 miscellaneous extension librar ii libxt6 1:1.0.7-1 X11 toolkit intrinsics library ii wget 1.12-2.1retrieves files from the web flashplugin-nonfree recommends no packages. Versions of packages flashplugin-nonfree suggests: pn flashplugin-nonfree-extrasoun none (no description available) ii iceweasel 3.5.16-12 Web browser based on Firefox pn konqueror-nsplugins none (no description available) pn msttcorefonts none (no description available) ii ttf-dejavu2.31-1 Metapackage to pull in ttf-dejavu- pn ttf-xfree86-nonfree none (no description available) ii x-ttcidfont-conf 32 TrueType and CID fonts configurati -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#638004: lsb-core: Should depend on cron-daemon instead of cron
Subject: lsb-core: Should depend on cron-daemon instead of cron Package: lsb-core Severity: wishlist *** Please type your report below this line *** Currently, lsb-core depends on the package cron, which will prevent you from using a drop-in-replacement. We have a virtual cron-daemon package, so we should use it. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#607705: update-rc.d: warning: pure-ftpd stop runlevel arguments do not match LSB Default-Stop values
Package: pure-ftpd Version: 1.0.28-3 Severity: normal Today I upgraded pure-ftpd from 1.0.28-2 to 1.0.28-3 using aptitude update aptitude full-upgrade and got the message update-rc.d: warning: pure-ftpd stop runlevel arguments (1) do not match LSB Default-Stop values regarding http://piuparts.debian.org/sid/initdscript_lsb_header_issue.html I am reporting this as a bug. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) 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 Versions of packages pure-ftpd depends on: ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib ii libcap2 1:2.19-3 support for getting/setting POSIX. ii libpam0g1.1.1-6.1Pluggable Authentication Modules l ii libssl0.9.8 0.9.8o-4 SSL shared libraries ii lsb-base3.2-23.1 Linux Standard Base 3.2 init scrip ii openbsd-inetd [inet-superse 0.20080125-6 The OpenBSD Internet Superserver ii pure-ftpd-common1.0.28-3 Pure-FTPd FTP server (Common Files pure-ftpd recommends no packages. pure-ftpd 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#151820: What's the current status?
Hi, I run into the same issue. I am currently on Debian Squeeze and the isc-dhcp-client package is still at version 4.1.1 (4.1.1-P1-15 in detail). So what's the current status? Will Debian Squeeze be finally able to identify itself correctly via DHCP? -- Regards Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
