Bug#524999: libpam-modules: memlock setting from limits.conf ignored in 1.0.1-9

2009-04-23 Thread Daniel Kraft
Well. So that was kind of a brown-paper-bag bugreport. I had been certain that I had checked the hard limits for the first report, but I can't reproduce any problem now either, even with the old kernel. I'm sorry. Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#524999: libpam-modules: memlock setting from limits.conf ignored in 1.0.1-9

2009-04-23 Thread Daniel Kraft
Actually, the line I already posted was the whole non-comment content of my /etc/security/limits.conf. I'm logging in to the machine where I noticed the problem via ssh, so I guess this determines the PAM service used. I switched to a 2.6.29 kernel, but the problem persists. I also reproduced th

Bug#524999: libpam-modules: memlock setting from limits.conf ignored in 1.0.1-9

2009-04-21 Thread Daniel Kraft
Package: libpam-modules Version: 1.0.1-9 I have a manually changed setting for memlock in /etc/security/limits.conf: myselfhardmemlock 10 After upgrading to 1.0.1-9 (maybe already with 1.0.1-7, though I didn't notice) this setting was ignored and the default of 64K us

Bug#411651: epstopdf: embedding all fonts (small patch)

2007-02-20 Thread Daniel Kraft
Hi, Hilmar wrote: > Did you consider do use a2ping, the successor of epstopdf? It has an > option "--gsextra= extra arg to gs", which might do, what you > want. I didn't know a2ping, thanks for mentioning it. Its --gsextra options probably should do what I need; at least if it ran properly,

Bug#411651: epstopdf: embedding all fonts (small patch)

2007-02-20 Thread Daniel Kraft
Package: tetex-bin Version: 3.0-29 Severity: normal Tags: patch The following small patch adds an option --embed to epstopdf which makes epstopdf embed all fonts into the generated PDF. This is very useful when using pdflatex to compile a document with figures from EPS sources. Otherwise, if the

Bug#345457: linphone 1.2.0 should depend on liblinphone1 >= 1.2.0

2005-12-31 Thread Daniel Kraft
Package: linphone Version: 1.2.0-1 Severity: important Linphone 1.2.0 doesn't run with liblinphone1 1.1.0, even though it only has "liblinphone1 (>= 1.1.0)" in its "Depends:". Regards, Daniel -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (905, 'testing'), (103, '

Bug#327795: linphone_1.1.0 depends on liblinphone1_1.1.0 and libortp0_1.1.0

2005-09-12 Thread Daniel Kraft
Hi, sorry, I have overlooked the liblinphone1->libortp0 dependency. However, liblinphone1 1.1.0 only depends on libortp0 (>= 1.0.1) which seems not to be enough. I had libortp0 1.0.1 installed and linphone still failed after I had upgraded linphone and (manually) liblinphone1 to 1.1.0. It worked a

Bug#327795: linphone_1.1.0 depends on liblinphone1_1.1.0 and libortp0_1.1.0

2005-09-12 Thread Daniel Kraft
Package: linphone Version: 1.1.0-1 Severity: important Linphone segfaults with an older liblinphone1 and fails (symbol lookup error) without libortp0. The liblinphone1 depends given in the control file is unversioned and there is none for libortp0. Regards, Daniel -- System Information: Debian

Bug#305926: netlink_lookup problem with pidentd

2005-04-26 Thread Daniel Kraft
I had the same problem with pidentd and found that it apparently tries to use a NETLINK-socket with "protocol" NETLINK_TCPDIAG, probably to inquire about the "owners" of tcp connections. For this to work, the kernel needs to have CONFIG_IP_TCPDIAG, called "IP: TCP socket monitoring interface" in

Bug#156161: invoke-rc.d is OK

2005-01-10 Thread Daniel Kraft
Sorry for the confusion, I'll try to make it more clear. In my first message I was proposing to change the behavior of "invoke-rc.d restart" to do "stop" for floating services as a short term (and not ideal) solution to the question of how to manage a service manually, and because it seems more se

Bug#156161: invoke-rc.d is OK

2005-01-10 Thread Daniel Kraft
Thomas Hood <[EMAIL PROTECTED]> said: > We are talking here, after all, about how invoke-rc.d handles an > invalid setup. Well, but making this invalid setup a "locally valid" one by defining the most useful invoke-rc.d behavior for it is one of two ways to solve the (otherwise still unsolvable, r

Bug#156161: invoke-rc.d is OK

2005-01-10 Thread Daniel Kraft
Thomas mentioned three possible behaviors of invoke-rc.d in case of a missing symlink, all of which are somehow bad: 1) starting a manually stopped service on upgrade, 2) stopping a manually started service on upgrade, and 3) not restarting a manually started service on upgrade. Option 3) may be a