Hello Jonas,
> A new release 2.3-1 has just been released. It would be helpful if you
> could test whether the problem has been fixed.
I can confirm that the Debian package 2.3-1 works without segfault (have it
running for > 10 hours without a problem). Thanks for the quick packaging!
>
Package: iwd
Version: 2.2-1
Severity: important
Dear Maintainer,
on a Raspberry Pi 4 with armhf, version 2.2-1 segfaults when starting.
2.1-1 works without segfault.
(gdb) run
Starting program: /usr/libexec/iwd
[Thread debugging using libthread_db enabled]
Using host libthread_db library
Package: systemd
Version: 252-2
Severity: normal
Dear Maintainer,
similar to #749268 there seems to be again the problem, that when logging
out, the systemd user process and sd-pam are not killed.
Take, e.g., this example:
# loginctl kill-session 34
# pgrep -a -u pat
11499 /lib/systemd/systemd
The specific problem can be avoided with:
mkdir -p /var/lib/sddm/.config/systemd/user
chown -R sddm: /var/lib/sddm/.config/systemd
ln -s /dev/null /var/lib/sddm/.config/systemd/user/pulseaudio.service
ln -s /dev/null /var/lib/sddm/.config/systemd/user/pulseaudio.socket
Adding something like this
Package: sddm
Version: 0.19.0-3
Severity: normal
Dear Maintainer,
I am not really sure, if this is a sddm, pulseaudio or systemd bug, as all
three seem somehow involved:
Pulseaudio installs pulseaudio.service and pulseaudio.socket below
/usr/lib/systemd/user/ i.e. pulseaudio is started for
Hello,
> Testing with versions in between from snapshot.debian.org reveals that
> it's still OK with 21.1.6-1 and the issue starts with 21.2.0-1.
>
> Other related reports that look like they might be about the same
> problem, all related to Mesa 21.2 (I'm seeing artifacts in Firefox and
> in
Hello Bernhard,
yes, thanks, it probably is the same, although in my journal I have traps from
kded5 and not from kde5, but this is probably a copy-paste issue in #996726.
Unfortunately, it's not mentioned, what the fix was, but when I look at the
diffoscope of 4:5.23.0-2 and 4:5.23.0-3 it looks
Package: kde-config-gtk-style
Version: 4:5.23.0-2
Severity: normal
Dear Maintainer,
I am not sure, whether this is a kded5 or kde-config-gtk-style packaging
problem, but both can currently be installed in an incompatible way leading
to repeatedly crashing kded5 (like 10 Dr.Konqi windows on login
Hi Felix,
> > force_load efivarfs || true
>
> That invokes the following function when the initramfs is
> created (from /usr/share/initramfs-tools/hook-functions):
>
> # force_load module [args...]
> force_load()
> {
> manual_add_modules "$1"
> echo "${@}"
Package: libkdecorations2-5v5
Version: 4:5.23.0-2
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
as of 2021-10-17T06:09:05+00:00 Debian testing contains 4:5.23.0-2, although
the rest of Plasma is still on 5.21. Therefore, apt update installs
Package: mdadm
Version: 4.2~rc2-7
Severity: normal
Dear Maintainer,
due to #962844 and #995093, /usr/share/initramfs-tools/hooks/mdadm does a
force_load efivarfs || true
which results on trying to load efivarfs on every boot. However, this
obviously does not work on a non-UEFI system and
On Sun, 21 Mar 2021 18:53:12 +0100 Patrice Duroux
wrote:
> Package: fish
> Version: 3.1.2-3
> Severity: wishlist
>
Dear Maintainer,
meanwhile, version 3.3.1 is available for some time.
Kind regards
Patrick
signature.asc
Description: This is a digitally signed message part.
Hi,
> > ii libkf5plasma5 5.78.0-3
>
> The problem is that this packages (and several others) from the
> frameworks are not updated.
>
> I guess we have to introduce a breaks somewhere ... this incompatibility
> is somehow surprising, because it is not documented
This is the link for k2pdfopt I wanted to send (needs to solve a CAPTCHA on
the left): https://www.willus.com/k2pdfopt/download/
Am Sonntag, 10. Januar 2021, 07:27:40 CET schrieb Patrick Häcker:
> Hi,
>
> I can confirm the bug for
> http://people.math.harvard.edu/~ctm/home/text/ot
Hi,
I can confirm the bug for
http://people.math.harvard.edu/~ctm/home/text/others/shannon/entropy/
entropy.pdf
with only exactly converting 10 pages from the source file.
The bug does not occur with the k2pdfopt version from
http://people.math.harvard.edu/~ctm/home/text/others/shannon/entropy/
Package: spectre-meltdown-checker
Version: 0.43-3
Severity: normal
Dear Maintainer,
I get two vulnerabilities shown when using spectre-meltdnown-checker for this
Skylake system:
CVE-2018-3640 aka 'Variant 3a, rogue system register read'
* CPU microcode mitigates the vulnerability: NO
>
Package: ardentryst
Version: 1.71-7
Severity: normal
Dear Maintainer,
I cannot start ardentryst any more:
pat@mmm ~> cd /usr/share/games/ardentryst
/usr/bin/python3 /usr/share/games/ardentryst/ardentryst.py
pygame 1.9.6
Hello from the pygame community.
> In summary, this is not a bug - the log uses the package architecture, not
> the version architecture. If you need the version architecture, you need
> to reconstruct it in a different way.
Thanks for the information, I understand, that this is not a bug and already
found a workaround.
Is there
You can use apt-revert from Salsa (https://salsa.debian.org/PatH/apt-revert)
to view the history.
Kind regards
Patrick
On Mon, 20 Feb 2017 06:25:47 +0530 =?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?
= wrote:
> Package: apt
> Version: 1.4~rc1
> Severity: wishlist
>
> Dear Maintainer,
>
> Looking
Package: apt
Version: 2.1.6
Severity: normal
Dear Maintainer,
the log file /var/log/apt/history.log shows all packages with the main
architecture even for architecture:all packages as in the following example:
> Downgrade: libkf5libkleo-data:amd64 (4:20.04.1-1, 4:19.08.3-1)
But executing
>
Package: libcec4
Version: 4.0.4.1~stretch
Severity: wishlist
Dear Maintainer,
the Debian package of libcec does not support the Raspberry Pi's (RPI) HDMI
port in version 4.0.3+dfsg1-1.
Version 4.0.4.1~stretch in Rasbian does support it (you can find it here:
Hi Tom,
> On 20 Dec 2018, at 17:10, Patrick Häcker wrote:
> > Maybe you can elaborate on your working setup.
>
> I've just run a dist-upgrade and 72.0.3626.7-6 installed and works.
I can confirm, that version 72.0.3626.7-6 is fixing the issue. Thanks a lot for
pointing me
Am Freitag, 4. Januar 2019, 12:22:46 CET schrieb Michael Biebl:
> Am 04.01.19 um 11:48 schrieb Patrick Häcker:
> > Hello,
> >
> >> Can you post the output of
> >> ls -ld /var/lib/systemd/timesync
> >> ls -la /var/lib/private/systemd/
> >
>
Hello,
> Can you post the output of
> ls -ld /var/lib/systemd/timesync
> ls -la /var/lib/private/systemd/
root@mmm /h/pat# ls -ld /var/lib/systemd/timesync
lrwxrwxrwx 1 root root 27 Jan 3 2018 /var/lib/systemd/timesync -> ../
private/systemd/timesync/
root@mmm /h/pat# ls -la
Hi,
the problem seems to be mixing two approaches in an incompatible way:
1) /var/lib/systemd/timesync can either be a directory (a) or a symlink to
/var/lib/private/systemd/timesync (b)
2) systemd-timesyncd.service may either contain DynamicUser=yes (a) or not
(b).
1a together with 2b should
Package: systemd
Version: 240-2
Severity: normal
Dear Maintainer,
after updating systemd from 239-15 to 240-2 timesyncd stopped touching
/var/lib/private/systemd/timesync/clock any more and its time stamps
stay at the time of the package upgrade.
Additionally the file is no longer used to update
Hi Tom,
you wrote on the upstream bug tracker that you have resolved the issue with an
upgrade and version 70.0.3538.67-2. Did you upgrade to testing? Maybe you can
elaborate on your working setup.
I upgraded to testing, but to no avail. As there is no testing or unstable
armhf version of
Package: chromium
Version: 68.0.3440.75-1~deb9u1
Severity: important
Dear Maintainer,
Chromium on Debian stable (68.0.3440.75-1~deb9u1r) crashes with a
SEGV_MAPERR on startup on a Raspberry Pi since the last security update
(the system is Debian stable with some Raspbian packages).
Version
Package: chromium
Version: 67.0.3396.87-1~deb9u1
Severity: important
Dear Maintainer,
the version in stable crashes after the security update on a Raspberry Pi
on startup. The system ist mainly Debian stable with some Raspbian packages.
I couldn't find the dbgsym package, so please point me to
Hi,
> I suspect this is because of the recent update of libequinox-osgi-java.
your suspicion is correct. Downgrading libequinox-osgi-java with
> apt install libequinox-osgi-java/stable
fixes the issue (although it removes eclipse if that is not downgraded as
well).
Kind regards
Patrick
Hi,
> See
> https://github.com/yontalcar/util-linux/commit/
> e9ca294aeeec9b32a979024a5f9c23e73325f2b0
> for patch.
thanks for the fix.
I can confirm, that it works and is more elegant than the version I came up
with (appended only for the record).
So from my point of view this bug can be
Hi,
calling partx with the libblkid debug environment variable like
> env LIBBLKID_DEBUG=all partx --show /dev/sda
results in the following:
6729: libblkid: INIT: library debug mask: 0x
6729: libblkid: INIT: library version: 2.31.1 [19-Dec-2017]
Available "LIBBLKID_DEBUG=[,...]|"
Appending the MBR for replicating the problem, using
> fdisk -l MBR
or
> partx --show MBR
Regards
Patrick
MBR
Description: Binary data
Package: util-linux
Version: 2.31.1-0.4
Severity: normal
Dear Maintainer,
the command
> partx --show /dev/sda
prints
> partx: /dev/sda: failed to read partition table
However,
> fdisk -l /dev/sda
results in
> Disk /dev/sda: 119,2 GiB, 128035676160 bytes, 250069680 sectors
> Units: sectors of 1
Hi James,
thanks for taking care of Gerbera and mediatomb's bug reports.
Unfortunately, I do not have a UPnP setup anymore, so I can't test it.
However, with /etc/default being removed, I can't see how this bug could still
occur, so even without testing, I am very positive, that the bug is
On Sun, 25 Dec 2016 14:23:30 +0100 Bill Allombert <ballo...@debian.org> wrote:
> On Thu, Dec 22, 2016 at 06:44:42PM +0100, Patrick Häcker wrote:
> > Package: consolation
> > Version: 0.0.4-1
> > Severity: minor
> > Tags: patch
> > the pointer acceleratio
Package: consolation
Version: 0.0.4-1
Severity: minor
Tags: patch
Dear Maintainer,
the pointer acceleration speed option is named as "--set-speed=" when
entering "--help" and in the man page. Albeit, the program searches for the
variable named "--speed". Please correct either the documentation
I looked a bit into the problem in version 0.22.7 and found the following via
perl -d:
In line 198, the directory /var/lib/apt/lists (the content of $list_dir) is
searched for files _ending_ with "Packages" (note the dollar sign after
Packages):
> files = map { $list_dir . $_} grep
Package: muon-updater
Version: 4:5.4.3-1
Severity: normal
Dear Maintainer,
when selecting a package in the Muon Update Manager, I always get the text
"The list of changes is not yet available.",
instead of the expected changelog delta.
Kind regards
Patrick
-- System Information:
Debian
Package: digikam
Version: 4:4.14.0-3
Severity: important
Tags: patch
Dear Maintainer,
after installing digikam, no existing albums could be viewed. The error
message was:
Couldn't create slave: "Unable to create io-slave:
klauncher said: Unknown protocol: digikamdates
After calling
Package: skrooge
Version: 1.9.3-1
Severity: wishlist
Dear Maintainer,
version 1.10.0 is available for three months now. In the mean time, version
1.10.91 became available. It would be great, if you could package it.
To do not disrupt Jessie, an upload to experimental might be the best option.
I just found out, that 1.10.91 is a development version, so packaging 1.10.0
might be more appropriate, though either of both versions would be fine in
experimental, I think.
Patrick
signature.asc
Description: This is a digitally signed message part.
Hi Michael,
That means, depending on the timing, anacron-resume.service might be
triggered just before suspend not on resume, and it's not guaranteed
that anacron has finished before systemd-sleep is called.
I don't think the patch was intended this way?
thanks for the analysis. Is there
Hi Tobias,
On Fri, 02 Jan 2015 16:15:27 0100 Tobias Scherer tobias.scherer@neuland-
bfi.de wrote:
I altered the package according to Patricks proposal.
Please find attached the diff-file.
thank you very much for implementing this. Such small little details really
make a difference.
Patrick
Dear Héctor,
sorry for the delay until I found the time to answer.
So this is definitely inconsistent (using the port number from
/etc/default/mediatomb in systemd and using the port number from
/etc/mediatomb/config.xml in the init script) and completely
non-transparent to the user.
Of course, my proposed patches would requires that the machine is
turned on at xx:00 at least once a day.
Although that patch is much better than the current behavior, I don't think
that the solution is general enough.
It's perfectly legitimate to use a device only for some minutes every time
Dear maintainer,
I reopened this bug, as I think that there is a regression in current
versions, because the observed behavior is the same as in this bug report (and
in #485070), i.e. there is an alarming message on boot without showing a
problem otherwise. I think the problem is well
Issue is a false positive then, as Dario said. I've build package on my
machine (Debian Jessie, amd64).
Yes, thanks for the information.
Executing
apt-get -b source djmount
in a newly created directory works indeed, while
apt-get source djmount
cd djmount-0.71
./configure
make
cd ..
severity 701680 grave
tag 701680 - moreinfo unreproducible
thanks
signature.asc
Description: This is a digitally signed message part.
If anyone could tell me how to build djmount with debug information (a simple
./configure; make does not work, see #772630 for the details), I think I can
produce a more useful stack trace.
Kind regards
Patrick
signature.asc
Description: This is a digitally signed message part.
Package: abtransfers
Version: 0.0.5.0-2
Severity: minor
Tags: patch
Dear Maintainer,
I've seen the patch for adding a menu entry for AB-Transfers. Thanks a lot
for that (thanks to Tobias Scherer, too).
I suggest to also add an icon by using the following content for
Package: djmount
Version: 0.71-6
Severity: serious
Justification: Policy 4.9 (Package does not successfully run build)
Dear Maintainer,
djmount FTBFS on Jessie (amd64) during linking. The last warning before the
error:
fuse_main.c: In function ‘main’:
fuse_main.c:621:2: warning: implicit
Hello,
thanks for answering this bug report and sorry for reporting back this late.
Even if it started, it wouldn't work, as it does not read the
configuration file /etc/mediatomb/config.xml
Additionally, it does not seem to make sense to have
/etc/default/mediatomb, as nearly all
Package: mediatomb
Version: 0.12.1-7
Severity: grave
Tags: patch
Justification: renders package unusable
Dear Maintainer,
version 0.12.1-7 does not start when using systemd without a useable error
message:
Process: 2788 ExecStart=/usr/bin/mediatomb -d -u $MT_USER -g $MT_GROUP -P
When I then rebooted my computer after an update of grub, I could still
select the correct kernel in the grub menu at boot, but then grub gave an
error (partition not found or similar).
Could you please check if the device your firmware (BIOS/EFI/…) boots from is
really selected in the list
On Thu, 23 Oct 2014 18:20:00 -0500 Mike ctrl...@yahoo.com wrote:
Greetings, anything else needed from me?
Thanks.
This is complete guessing, but could the file, util/deviceiter.c, i.e. the
iteration over devices, have something to do with it? In version
grub2-2.02~beta2, there is this block
Package: grub2-common
Version: 2.02~beta2-15
Severity: normal
Dear Maintainer,
normally it's possible with Grub to use
GRUB_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT=0
in /etc/default/grub to have Grub hidden during normal boots with the
default boot entry being selected immediately. To my knowledge this
Thanks for fixing that bug.
I just wanted to add, that version 1.10.3-3 also fixes the bug that the
selected user is not remembered anymore (I was just going to report that
one). So if anyone wonders how to get rid of that bug, just install 1.10.3-3.
Kind regards
Patrick
signature.asc
Package: unattended-upgrade
Version: 0.83
Severity: normal
Dear Maintainer,
with /etc/apt/apt.conf.d/50unattended-upgrades containing
Unattended-Upgrade::Origins-Pattern {
origin=*;
};
and /etc/apt/preferences containing
Package: *
Pin: release o=Debian,a=stable
Pin-Priority: 950
Package: konqueror
Version: 4:4.14.1-1
Severity: grave
Tags: security
Justification: user security hole
Dear Maintainer,
according to https://www.poodletest.com/ Konqueror is still vulnerable to the
Poodle attack.
If this is only fixable in KHTML or WebKit, please move the bug there.
As all the
I'd like to have his input on what we need to do within systemd.
With kexec-tools 1:2.0.7-3 kexec works with systemd when using the reboot
command.
I notice systemd also has a systemctl kexec command. Have you tried
that? If that doesn't work, we probably need to fix that integration as
I have just upgraded all the packages in my Debian Testing to the latest
ones and I don't know which one did the trick, but auto-unlock of
kwallet now works. It works with kdm as well as lightdm.
Ok, this is good news. So the checklist should include system is up-to-
date.
This would be a
On Wed, 2 Jul 2014 10:45:17 0200 Petter Reinholdtsen p...@hungry.com
wrote:
Package: konqueror
Version: 4:4.12.4-1
Severity: normal
When I visit youtube on a freshly installed Jessie desktop and try to
watch a video, the video player seem to start as it should, show the
duration and
Hi Rahul,
Did you check this on Debian?
yes, I have this working on two Debian testing systems.
1. Recompiled pam-kwallet_0.0~git20140429-0ubuntu1 in Debian testing and
installed it
Instead of recompiling it, I installed the binary package provided by Ubuntu
without modifying it. I haven't
control: severity -1 grave
Arora started to open and then immediately closed. The message
Segmentation fault appeared.
I can confirm this behavior. The following is the gdb output. As I found
neither arora nor libqtgui debugging packages, it might not be that helpful,
though.
(gdb) file
On Thu, 02 Oct 2014 22:02:15 -0400 Brendon Higgins
bren...@quantumfurball.net wrote:
I'm also experiencing this, on three different computers.
Do you know when this behavior started? Are you using testing or unstable?
According to
https://packages.qa.debian.org/k/kde-baseapps.html
there are
Anyway, doing the same with version 4:4.13.3-1 could be interesting, but
resolving the dependencies could be more tricky. If you want to try it, that
is the approach for 4:4.14.0-1 (the last one obviously needs root
permissions):
debsnap --architecture all kde-baseapps-data 4:4.14.0-1
So now we know, that 4:4.13.3-1 is the last known good package and
4:4.14.0-1 the first known bad package. We also know, that saving, not
loading the session really is the problem.
Unfortunately, it does not seem to be easily possible to track the exact
package down. According to
find *.deb
control: tags -1 patch
So now we know, that 4:4.13.3-1 is the last known good package and
4:4.14.0-1 the first known bad package. We also know, that saving, not
loading the session really is the problem.
So there seems to be another idea needed to further debug the problem.
As all 5
The problematic line in my setup is
greeter-session=lightdm-kde-greeter
This one has been manually added. You're basically saying lightdm the
greeter is lightdm-kde-greeter. If you don't have it installed, then it
obviously can't start it, so it might be worth double checking that.
On Sun, 28 Sep 2014 21:43:08 +0200 Yves-Alexis Perez cor...@debian.org
wrote:
sorry for the delayed reply. I could indeed confirm that the problem is
in the config file. Keeping the old config files breaks the upgrade,
while installing the new ones has no problem.
Here is the offending
Package: imwheel
Version: 1.0.0pre12-10
Severity: important
Tags: patch
Dear Maintainer,
updating the package from 1.0.0pre12-9 to 1.0.0pre12-10 let imwheel fail at
startup. As written in the changelog, I tried some variants of quotes in
/etc/X11/imwheel/startup.conf and especially the variant
. September 2014, 23:58:09 schrieb Patrick Häcker:
Package: wnpp
Severity: wishlist
* Package name: pam-kwallet
Version : 0.0~git20140429-0ubuntu1
Upstream Author : Alejandro Fiestas Olivares (afies...@kde.org)
* URL :
https://www.dennogumi.org/2014/04/unlocking
I do not have gnome-keyring-daemon installed. Why is it trying to
start it?
You are correct that in an ideal solution this line should only be present if
gnome-keyring-daemon is installed. However, the rest of the configuration
should be in the responsibility of the lightdm package (or other
Package: konqueror
Version: 4:4.14.1-1
Severity: normal
Dear Maintainer,
on two different computers, the session management does not work any longer
for Konqueror, i.e. logging out and in again does not restore the opened tabs
in Konqueror.
Kind regards
Patrick
-- System Information:
Debian
On Sonday, 28. September 2014, 21:47:43 Yves-Alexis Perez wrote:
On dim., 2014-09-28 at 10:28 +0200, Patrick Häcker wrote:
So change the lines
auth optional pam_gnome_keyring.so
session optional pam_gnome_keyring.so auto_start
into
-auth optional pam_gnome_keyring.so
Package: wnpp
Severity: wishlist
* Package name: pam-kwallet
Version : 0.0~git20140429-0ubuntu1
Upstream Author : Alejandro Fiestas Olivares (afies...@kde.org)
* URL :
https://www.dennogumi.org/2014/04/unlocking-kwallet-with-pam/
* License : GPL
Programming
I found the root problem and could fix it. It was a configuration problem
(nearly) unrelated to netfilter-persistent. Due to netfilter-persistent's
systemd file, modules have been loaded via a systemd dependency.
This caused /etc/modules being executed, which contained the line
snd_hda_intel
Package: netfilter-persistent
Version: 1.0.2
Severity: normal
Tags: ipv6
Dear Maintainer,
installing netfilter-persistent (systemd active) results in the following error:
dependency job for netfilter-persistent.service failed. See 'journalctl -xn'
for details.
invoke-rc.d: initscript
it would be nice, if Debian installer would support GeoIP to use default
values where appropriate.
I don't think we're going to set up networking without asking, let alone
contacting some service on the internets to figure out what country the
user might be in.
Good point, I didn't think
Package: debian-installer
Severity: wishlist
Tags: d-i l10n
Dear Maintainer,
it would be nice, if Debian installer would support GeoIP to use default
values where appropriate. See
http://henrich-on-debian.blogspot.de/2014/07/geoip-support-for-installer-is-really.html
for an example.
This would
Package: abtransfers
Version: 0.0.4.1-2
Severity: minor
Dear Maintainer,
abTransfers does not appear in the KDE menu after installing the abtransfers
package (it should be below Applications/Office, but there is no entry
there).
This is strange, as the file /usr/share/menu/abtransfers exists and
Package: src:linux
Version: 3.15~rc7-1~exp1
Severity: normal
Dear Maintainer,
some seconds or minutes after waking up from suspend to disk after the NMI
watchdog has been disabled (e.g. with powertop or with echo 0
/proc/sys/kernel/nmi_watchdog) before suspend, I get the following message
from
Package: skrooge
Version: 1.9.0-1+b1
Severity: minor
Dear Maintainer,
the account type wallet is translated in the German localization of skrooge
as Passwortspeicher which means password safe (maybe due to the existance
of KWallet?), which is a completely wrong translation. According to
Package: kgpg
Version: 4:4.13.1-1
Severity: normal
Dear Maintainer,
nowadays a generated GPG key has a main key and at least one subkey. When
exchanging fingerprints, one normally uses the fingerprint of the main key and
not of the subkey(s). However, KGpg does not show the fingerprint of the
Just for the records: The pm-utils bug is already reported in #659260 (and not
fixed, yet, although a patch is available for more than two years *sigh*).
signature.asc
Description: This is a digitally signed message part.
I've also been hit by this bug which wasted not only my, but also a
developer's time (see #749330).
I can only agree with the other reporters: Arbitrarily resetting kernel
variables (even on a desktop computer) is out of scope of this package.
Implementing solution 1 from message #5 needs
The bug seems to be triggered from the digikam-nepomuk-synchronization which I
activated a long time ago when Digikam had a GUI option for that (this option
is gone in the mean time). The synchronization seems to be broken:
https://bugs.kde.org/show_bug.cgi?id=305079#c2 (I do not know how
I guess the value dirty_writeback_centisecs defaults to 500. Other values
defined via sysctl have their (suspected) default value, too.
Which other values?
Values like
vm.dirty_background_bytes = 16777216
vm.dirty_bytes = 100663296
which I have defined in sysctl.conf, too. Yet, the output
Package: systemd
Version: 208-1
Severity: normal
Dear Maintainer,
I have a file
/etc/sysctl.d/98-save-power.conf
containing the line
vm.dirty_writeback_centisecs = 1500
which is used as an example to describe the bug in the following.
After boot,
cat /proc/sys/vm/dirty_writeback_centisecs
vm.dirty_writeback_centisecs = 1500
which is used as an example to describe the bug in the following.
After boot,
cat /proc/sys/vm/dirty_writeback_centisecs
returns
500,
Do you use any power management tools, like acpi-support,
laptop-mode-tools or pm-utils? If so, one of those might
I added a small systemd unit file to avoid this bug. The unit file is
unconventional, as it calls the shell script instead of replacing it. Note,
that my experience with systemd is quite limited.
The systemd unit file contains the following:
[Unit]
Description=Loads iptables rules from
Forgot to mention in my last mail how to use it as an user:
systemctl daemon-reload
systemctl start iptables-persistent.service
systemctl enable iptables-persistent.service
The last line is used to have it activated in future boots.
signature.asc
Description: This is a digitally signed message
Package: pulseaudio
Version: 5.0-1
Severity: minor
Tags: patch
Dear Maintainer,
when using KDE and systemd (other combinations not tested), with every login
into KDE the following error gets logged for pulseaudio:
Daemon already running.
This is annoying when calling something like journalctl
Thanks a lot for this detailed analysis (my file has exactly the predicted
size) and your suggestions for further improvements. Please apologize my wrong
conclusion and your waste of time as a result. I try to do better in the
future.
The question remains why the file system size and the
Package: src:linux
Version: 3.11.8-1
Severity: normal
Dear Maintainer,
due to the changed kernel configuration to disable the ext2 module and
to enable
CONFIG_EXT4_USE_FOR_EXT23=y
the support for small ext2 file systems has been (accidently?) removed.
Small file systems here are file systems
Dear Ted,
as you probably have the best overview of the context of this bug (#731072),
I wanted to bring it to your attention.
I think it would be especially interesting to know if this is a known upstream
problem (sooner or later other distributions should be affected as well), and
what you
Hi,
depending on your needs, you might be able to circumvent the problem by
disabling the problematic buttons completely for imwheel.
I had problems with scrolling in konsole using the mouse wheel (scrolling
downwards was too coarse) and with zooming in okular (zooming outwards while
holding
Package: wajig
Version: 2.7.3
Severity: wishlist
Dear Maintainer,
please add support for apt-get's --solver option, e.g., that you can write
wajig install --solver aspcud fish
instead of
su -c apt-get install --solver aspcud fish
(see
Hi,
I do not know if it is related, but here vlc sometimes (4 out of 10 times)
segfaults when opening a directory from the command line, i.e. vlc ..
Valgrind complains about an Unrecognised instruction, so it does not help
so much.
This is the gdb output:
(gdb) run
Starting program:
1 - 100 of 112 matches
Mail list logo
