On 28/02/19 16:44, Thorsten Glaser wrote:
please do consider uploading 4.19.24 to buster/sid with some haste.
We have headless virtualisation hosts being unreachable/frozen now,
and while these are “only” development systems, this is untenable.
Like you I'm looking forward for that kernel.
On 13/02/19 18:21, Dragan Milenkovic wrote:
This patch is already on its way to stable branches. I have tested it
and confirmed that it resolves the problem.
Hello Dragan, do you know if the patch was eventually included upstream
and possibly in which version?
Cesare.
On Sun, 23 Dec 2018 15:58:50 +0100 Piotr Jurkiewicz
wrote:
On two machines running sid I observed errors during the upgrade to
2.03.01-2. One of these machines became practically unusable immediately
after the update (disk IO operations became so slow that even closing
aptitude took 2 minutes
Package: samba
Version: 2:4.1.11+dfsg-1
Followup-For: Bug #740942
I'm experiencing the same problem: 5 minute to shutdown samba service
and the same if i try to stop it on the command line.
I believed it was related to the fact that i use samba also to login in
an active domain but this bug
Package: samba
Version: 2:4.1.11+dfsg-1
Followup-For: Bug #740942
Some notes.
On shutdown/reboot, occasionally i see this message from systemd,
with a countdown and a moving asterisk:
-
A stop job is running for LSB: ensure samba daemons are started (nmbd
and smbd) ( 3 min 2 s / 5 min
Still not working for me with 0.7.4-2: No Data.
Cesare.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I just upgraded to the latest lenny perdition package. The upgrade resulted in
the /etc/perdition/popmap.*.db files being removed and not regenerated.
I confirm this too.
Today i upgraded from 1.17.1-2 to 1.17.1-2+lenny2 and after a reboot for
a kernel upgrade, some user started complaining
On 09/11/2010 06:24 PM, Robert Scott wrote:
Blacklisting the 855GM from KMS in 2.6.32-21 to fix bugs like 582105
seems to be causing my system to hard lock when X starts up. Magic
sysrq key does nothing, and of course the 855GM being totally
blacklisted means modeset=1 is powerless.
Hi Robert,
On 08/28/2010 02:10 PM, Julien Cristau wrote:
Could you guys test the driver pointed at
http://lists.freedesktop.org/pipermail/intel-gfx/2010-August/007910.html?
(probably with the 2.6.32-20 kernel)
Situation summary:
- the latest intel drivers and the latest kernel kms blacklisting cause
On 08/29/2010 05:18 PM, Julien Cristau wrote:
There are i386 packages at
http://people.debian.org/~jcristau/intel-shadow/ which work for me
on minimal testing.
Hi Julien.
As long as you provide .deb packages, i can test whatever you want! ;-)
Here is my results.
Now i'm writing with:
- i855
For Chris Wilson: you can follow this bug history here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594623
On 08/29/2010 05:18 PM, Julien Cristau wrote:
Although it looks like they crash the X server in dri2 code when I run
glxinfo, so I put xserver packages with a fix for that crash at
On 18/05/2010 16:24, Debian Bug Tracking System wrote:
Your message dated Tue, 18 May 2010 14:22:58 +
with message-ide1oenhc-0002ga...@ries.debian.org
and subject line Bug#572618: fixed in linux-2.6 2.6.32-13
has caused the Debian Bug report #572618,
regarding libata missing workaround for
Same for me (Debian Sid), and it's the second time in some week.
The first time i cannot remember precisely how i've resolved.
Today i have solved doing this:
1) rm ~/.local/share/mime/mime.cache
2) update-mime-database ~/.local/share/mime/
3) logout
But i think 2) is unnecessary.
Unsure if the
Marco d'Itri wrote:
reassign 361741 initramfs-tools
thanks
Sorry, i don't know udev in details, but i don't understand why you have
reassigned this bug to initramfs-tools.
The aptitude's log of that day is the following:
to go the sea. ;-)
Have someone any suggestion?
Regards.
Cesare.
---
-[ MESSAGE 2 ]-
Cesare Leonardi wrote:
As you can see the modules to mount my ATA (not sata) drive are in
place. I have tryed to mount root manually:
mount /dev/hda2 /
but it fails.
I wrote
Package: initramfs-tools
Version: 0.59
Severity: serious
Some minutes ago i have run aptitude to update my Debian Sid and the
installation of the latest kernel has failed with the following messages:
Setting up
Juan Piñeros wrote:
In machine1 hdparm is not currently installed, but it was 1 year ago when the
machine1 had woody installed. I suppose hdparm does not change anything to
the disk itself but only to the ide modules of the kernel?
Hdparm is a powerful tool that can activate/deactivate some
Juan Piñeros wrote:
I do not find any logical explanation. No strange message in syslog, we used
normal programs (konqueror, thunderbird, oowriter) when sudenly when try to
save a file or read mail, an error appears just saying that the directories
did not exist any more.
In the past i had a
Today i have fallen in the these bug caused by zeroconf an i want to
contribute with information to confirm them and hoping to be useful to
solve them.
Also for me zeroconf was not installed on my choice but as a recommended
package. This package was present on my system since some week but
Hi Otavio.
Recently i've talked with someone else that cannot purge 2.6.14, as
described in #344767.
I know that now it is solved for 2.6.15, but for people that still use
2.6.14 or have used it, the problem of purging it completely still
exist. For example on my machine, the various kernel
Sven Luther wrote:
Ok, 2.6.15 is arrived.
I've tryed to install linux-image-2.6.15-1-486 (version 2.6.15-1), then
to purge it and the operation failed. But now, it doesn't hang as stated
in the bug reports, but fails with an error:
Indeed, this is a grub RC bug, which need to fix their
Sven Luther wrote:
It would be great if you could confirm the exact version of those two
packages, and could provide us some log of what is happening, as this bug
report doesn't seem to be very informative.
For me, i have provided information in bug #344767, as i explained in
the previous
Cesare Leonardi wrote:
I haven't tested 2.6.15 because it isn't available in my mirror yet. But
the Nathanael posts tell us that the problem is still present in the
latest kernel.
As soon as it will be available on the mirror i use, i'll test 2.6.15.
Ok, 2.6.15 is arrived.
I've tryed
Thanks to the clear Erik's step by step guide, i've applayed his patch
and here is my results.
Erik van Konijnenburg wrote:
On Tue, Dec 13, 2005 at 12:52:34AM +0100, Cesare Leonardi wrote:
Step by step:
[...]
** Comment out any work-arounds (MODULE ide-generic) you may have made
Erik van Konijnenburg wrote:
To help pin down the cause, could you post the output of:
uname -a
dpkg -l yaird
yaird -v -o crap.img 2.6.14-2-686
yaird -v -o crap.img 2.6.14-5-686
(assuming these are the last kernel that boots and the first that works)
To avoid
Paulo Marcel Coelho Aragao wrote:
Package: linux-image-2.6.14-2-686
Version: 2.6.14-5
Severity: critical
Justification: breaks the whole system
Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and rebooted, boot
is interrupted with repeated messages:
/bin/cat:
26 matches
Mail list logo
