Package: apache2
Version: 2.4.54-2
Severity: important
X-Debbugs-Cc: debian-bu...@l8r.net
Dear Maintainer,
A single apache2 thread was hit by the linux kernel OOM killer, and was killed.
Systemd "helpfully" decided to then halt apache2 completely.
As per this bug report:
https://bugzilla.re
Can confirm this bug here, and an updated patch fixes this.
See:
https://bugzilla.redhat.com/show_bug.cgi?id=2090926
And:
https://github.com/logrotate/logrotate/commit/31cf1099ab8514dfcae5a980bc77352edd5292f8
Suggest at the very least, this is updated in Debian for the next point
release.
Package: needrestart
Version: 3.4-5
Severity: normal
buster's behaviour, in terms of ENV setup differs, when one performs 'su
-' versus 'su root'.
Due to this, 'sbin' paths are not in a 'su root' $PATH. This means that
this happens, when one does an apt-get upgrade as 'su root':
Restarting se
Package: coreutils
Version: 8.30-3
Severity: minor
ls adds a space at the start of some output. Seems to only happen when extra
quoting is in the output:
root@hmm:/tmp/oo# ls
a b 'sd '
root@hmm:/tmp/oo# rm sd\
root@hmm:/tmp/oo# ls
a b
root@hmm:/tmp/oo# touch c
root@hmm:/tmp/oo# ls
a b
Attached is a snapshot of the banner, as it appears on all versions of
Firefox I use that have disabled add-ons.
This is on debian stable, 60.6.1esr-1~deb9u1.
Are you running this version? Do you have add-ons installed?
If so, you should probably submit a separate bug, either to mozilla or
her
> installing the STUDIES "hotfix" from Mozilla by hand on each one is not
> feasible.
Not to mention, this requires that other features of Firefox's 'phone
home' framework are turned on, which 'studies' uses. For example, in the
GUI, the 'studies' option is under:
"Allow Firefox to send techn
While I agree an unknown disabling of plugins, not just noscript (there
are others like noscript) is a security concern...
There is a big, yellow banner that appears and stays at the top of your
browser, informing you if any plugins/add-ons are disabled.
So for me, the 'big deal' is being infor
Ack, should have thought of that.
Just tested. OK kernel:
4.9.0-8-amd64 #1 SMP Debian 4.9.144-3 (2019-02-02) x86_64 GNU/Linux
Borked kernel:
4.9.0-9-amd64 #1 SMP Debian 4.9.168-1 (2019-04-12) x86_64
Hmm. Just noticed GNU/Linux tag is missing too..
On Sun, 28 Apr 2019 19:41:47 +0200
Mic
FYI, I'm running sysvinit.
Package: udev
Version: 232-25+deb9u11
After today's upgrade to debian 9.9, I attempted to create a disk image.
I have a script, it does the following:
###
dd if=/dev/zero of=/tmp/ff1.raw bs=1G seek=8 count=0
sync
sleep 1
parted /tmp/ff1.raw mklabel msdos
parted -s /tmp/ff1.raw mkpart primary l
Package: installation-reports
Boot method: iso in virtualbox
Image version:
https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/debian-testing-amd64-netinst.iso
Date: September 21, 2019
Machine: 64bit Virtualbox with 'debian' selected
Processor: N/A (I worry about CPU info now, thanks
Package: telnet
Version: 0.17-41
After an upgrade from jessie to stretch, and moving my jessie .telnetrc
file into my homedir, I noticed that it was no longer parsed correctly.
# cat .telnetrc
172.16.1.1
mode char
Yet stretch's version of telnet does not switch to character mode.
A bit of
Some info.
It seems that the default for probesize might be 500:
https://ffmpeg.org/ffprobe-all.html
probesize integer (input)
Set probing size in bytes, i.e. the size of the data to analyze to
get stream information. A higher value will enable detecting more
information in cas
Package: mplayer
Version: 2:1.3.0-6
I've recently been playing more 4k / 2160p video files, 8 bit encoded.
All have been fine with the exception of two of them.
$ uname -a
Linux xsdfsdf 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28) x86_64 GNU/Linux
$ /usr/bin/mplayer -fs
filename.2160p
Package: dpkg
Version: 1.18.23
Newer versions of dpkg have colourized output.
I can see the usage case for this, and I can see the value for some.
However, for others, it is a major detractor.
One of the issues with the recent colourization of the userland, is that
each has its own way to disab
that luck resulted in
that memspace not being used for anything I noticed.
Sorry for the issue guys, very sorry to waste your time.
And thanks for the help.
On Fri, 21 Apr 2017 18:00:25 -0400
Brad Barnett wrote:
>
>
>
> > Can you reproduce the segfault reliably by run
> Can you reproduce the segfault reliably by running:
>
> "deb-systemd-helper unmask cgmanager.service >/dev/null"
>
> With Perl 5.24?
>
Hmm.
root@newoldbe:/var/cache/apt/archives# deb-systemd-helper unmask
cgmanager.service >/dev/null /usr/bin/deb-systemd-helper was not called
from dpkg.
> Could you perhaps include the following information:
>
> * Which architecture are you using? If you have multi-arch enabled,
>please list the architecture of the perl packages (e.g. in the form
>of "dpkg -l" if you don't mind including a list of all packages
>installed)
amd64, n
Package: perl
Version: 5.24.1-2
When installing packages right after a fresh stretch install, perl started to
segfault.
EG:
Setting up cgmanager (0.41-2) ...
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segmentation fault
Segm
Package: redmine
Version: 3.3.1-4
Severity: normal
During a jessie to stretch upgrade:
1)
ln: /var/lib/redmine/default/log: cannot overwrite directory
dpkg: error processing package redmine (--configure):
A rm of existing log dir, then allowed the link to be created..
2)
The DB install prompt
ichael Tokarev wrote:
> Control: tag -1 moreinfo unreproducible
>
> 28.10.2016 17:30, Brad Barnett wrote:
> > Package: qemu-system-x86
> > Version: 1:2.1+dfsg-12+deb8u6
> >
> > I've been unable to find anything about this via Google searches,
> > mailing list se
Package: qemu-system-x86
Version: 1:2.1+dfsg-12+deb8u6
I've been unable to find anything about this via Google searches,
mailing list searches, IRC, you name it. Nor, does the documentation
seem to indicate I'm doing anything wrong.
Additional queries to qemu-devel and qemu-discuss fell flat, wi
I view this bug as very high priority. I see more than a decade of
documentation out there, and of user experience familiar with a process.
A process that changed for code correctness, and for absolutely no other
reason.
A process than in changing, broke the existing process.
And when the proc
On Sun, 21 Apr 2013 19:30:48 +0200
Guillem Jover wrote:
> What I'm planning to do to try to improve the situation is:
>
> * Document the change in the man page in master targetting 1.17.x
> (perhaps 1.16.x too).
> * Probably add a single warning at the end of the --set-selections
>
I might add, that I attempted to use Guillem's suggestion in that email.
I get borked at the whole:
apt-cache dumpavail && dpkg --update-avail / --merge-avail
How on earth is that even supposed to work? Doesn't seem to function
here...
On Sun, 21 Apr 2013 11:41:35
Uh, yeah... great.
Ok, so we have a regression that is "OK", because it is based on whether
a behaviour is technically correct. I've seen this bug for months and
months, but thought it was a well known bug that just wasn't resolved.
In fact, I didn't even look for bug reports. I didn't even lo
The upstream bug report, targeted in this bug report, is closed. It's
marked as OUT OF DATE version.
This means that the upstream bug report, will not help Debian Lenny's
version of Pidgin. Either a patch must be backported, or there needs to
be a volatile update to Pidgin.
It's what volatile
Package: kvm
Version: 72+dfsg-5~lenny2
Severity: important
Scratch that. This:
vdekvm -net nic,model=i82559er -net vde,sock=/var/run/vde2/mytap.ctl
resulted in an instant segfault of KVM, when trying to write any data to
an NFS share.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@l
Package: kvm
Version: 72+dfsg-5~lenny2
Severity: important
I have precisely the same issue, but using VDE2 as well.
The following worked:
vdekvm -net nic,model=i82559er -net vde,sock=/var/run/vde2/mytap.ctl
The following NIC models failed:
"ne2k_pci", "pcnet", "rtl8139"
That is, after brief
I believe all of my installs are RC1 or beta2 Lenny's. I've checked with
a few people, and they do not have this package as default on released
Lenny.
Such as it is, I imagine this was removed from the default install, and
if so I apologise for this report.
Thanks
--
To UNSUBSCRIBE, email
I have several post etch systems, that have this installed by default on
them.
This should not be the case, as its behaviour is quite destructive,
dependant upon what you are doing.
That is, it prevents your machine from booting. For example:
1) I did not ask for this package to be installed
This bug occurs here, and in fact also exists when I try to play any file
from the command line. I used to use XMMS in stable for playing voice
messages that I receive in my email, but I can't now...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Cont
Hi,
I believe I have found a method to reproduce this bug via ssh port
forwarding.
1) use SSH to create a port forward tunnel for jabber
eg: -L 5222:some.remote.host:5222
2) connect to the remote server via the tunnel (that is, set the jabber
prefs to connect to localhost:5222)
3) afte
Package: xtightvncviewer
Version: 1.2.9-21
Severity: important
When xtightvncviewer connects to localhost, it automatically assumes that it
should use raw encoding. For example, the output states "Same machine:
preferring raw encoding".
However, this should not be the case, as many people u
The same problem exists for me, using standard 32bit stable.
The problem is that perl sees a symlink as a directory, if it points to a
directory. Perhaps this is a change since 5.005 -> newer versions of
perl?
Anyhow, update-jail creates directories if it sees that they are such, via
-d.. and
On Wed, 13 Dec 2006 19:49:48 +0100
Mike Hommey <[EMAIL PROTECTED]> wrote:
> On Wed, Dec 13, 2006 at 11:13:56AM -0500, Brad Barnett <[EMAIL PROTECTED]>
> wrote:
> > On Wed, 13 Dec 2006 14:08:22 +0100
> > Alexander Sack <[EMAIL PROTECTED]> wrote:
> >
>
On Wed, 13 Dec 2006 14:08:22 +0100
Alexander Sack <[EMAIL PROTECTED]> wrote:
> On Mon, Dec 11, 2006 at 12:57:05PM -0500, Brad Barnett wrote:
> > Package: iceape-browser
> > Version: 1.0.6-1
> >
> > Iceape fails to use openURL correctly. For example:
>
> M
On Tue, 12 Dec 2006 16:40:58 -0500
James Vega <[EMAIL PROTECTED]> wrote:
> tag 402691 unreproducible moreinfo
> thanks
Please close this bug, sorry to bother you over it.
It seems that I mistook an (annoying) new Vim70 feature, parenthesis
highlighting, for syntax highlighting. If others want
2006 at 11:21:00PM -0500, Brad Barnett wrote:
> > For some reason, syntax highlighting is now on by default with vim.
>
> That's not the case as evidenced by the lack of syntax highlighting when
> starting Vim as "vim -u /etc/vim/vimrc -N".
Hmm. When I start vim like t
On Tue, 12 Dec 2006 16:40:58 -0500
James Vega <[EMAIL PROTECTED]> wrote:
> tag 402691 unreproducible moreinfo
> thanks
>
> On Mon, Dec 11, 2006 at 11:21:00PM -0500, Brad Barnett wrote:
> > For some reason, syntax highlighting is now on by default with vim.
>
> Th
Package: vim-full
Version: 1:7.0-122+1
For some reason, syntax highlighting is now on by default with vim.
Fair enough, perhaps enough people prefer it...
However, I am unable to turn off syntax highlighting at all. Editing
/etc/vim/vimrc, and uncommenting:
"syntax on
and changing it to:
syn
Package: iceape-browser
Version: 1.0.6-1
Iceape fails to use openURL correctly. For example:
-remote "openURL(http://domain.com/)"
Opens a new window, whereas it should open in an existing window.
-remote "openURL(http://domain.com/,newwindow)"
Generally results in a "The requested URL /,neww
Package: mozilla
Version: 2:1.7.12
Followup-For: Bug #336441
Here is my bug report to moz.org, they kicked me back here with lame
excuses about them no longer taking 1.7.x bug reports...
If I set the cache to "every time I view the page", Mozilla crashes when
I view a page the second time.
Thi
43 matches
Mail list logo
