tags 524940 - help
tags 524940 patch
thanks
Hello,
On trečiadienis 05 Rugpjūtis 2009 03:05:06 Marco d'Itri wrote:
On Aug 05, Eli Mackenzie eli.macken...@gmail.com wrote:
With this bug marked important, apt-listbugs didn't notify me that
there was anything wrong with this package. A failure
severity 524940 critical
thanks
With this bug marked important, apt-listbugs didn't notify me that
there was anything wrong with this package. A failure to boot seems to
fit the makes unrelated software on the system (or the whole system)
break description of critical more than important.
If you
On Aug 05, Eli Mackenzie eli.macken...@gmail.com wrote:
With this bug marked important, apt-listbugs didn't notify me that
there was anything wrong with this package. A failure to boot seems to
fit the makes unrelated software on the system (or the whole system)
break description of critical
I have the same symptoms with module-init-tools 3.9-2. Reverting to the stable
version 3.4-1 fixes the problem.
r...@hibisco:~/sound$ ps -ef | grep modprobe
root 7943 5501 0 19:34 pts/200:00:00 modprobe snd_via82xx
root 7955 7943 0 19:34 pts/200:00:00 sh -c modprobe
On Apr 26, Carl Miller c...@energoncube.net wrote:
I can corroborate this bug. I just upgraded to module-init-tools
3.7-pre9-1, and oss-compat 0.0.4+nmu3, and had the exact same thing
happen to me.
Please provide the complete content of /etc/modprobe.d/ and
/lib/modules/$(uname
I can corroborate this bug. I just upgraded to module-init-tools
3.7-pre9-1, and oss-compat 0.0.4+nmu3, and had the exact same thing
happen to me.
I found that the minimal way out of it was to comment out any line
in any /etc/modprobe.d/* file that began with install and referenced
any
On Apr 21, Matthew J. Lockner mlock...@iastate.edu wrote:
I suspect this will be unreproducible since it hasn't been reported yet that
I definitely never experienced this on my system.
Anyway, I have no reason to believe this to be a m-i-t bug.
Please show the content of
Marco d'Itri wrote:
On Apr 21, Matthew J. Lockner mlock...@iastate.edu wrote:
I suspect this will be unreproducible since it hasn't been reported yet that
I definitely never experienced this on my system.
Anyway, I have no reason to believe this to be a m-i-t bug.
The strongest
On Apr 22, Matthew Lockner mlock...@iastate.edu wrote:
The strongest evidence is that if I downgrade module-init-tools to the
prior version and hold the prior version and hold the package, the
problem goes away. I'd find the next most likely candidate to be
Not very compelling evidence.
On Apr 22, Matthew Lockner mlock...@iastate.edu wrote:
Since its postinst is my means of demonstrating the problem, then of
course removing the package will prevent the problem from appearing, at
least in this context.
You can remove it and manually run modprobe.
Anyway, I am quite sure
Marco d'Itri wrote:
On Apr 22, Matthew Lockner mlock...@iastate.edu wrote:
The strongest evidence is that if I downgrade module-init-tools to the
prior version and hold the prior version and hold the package, the
problem goes away. I'd find the next most likely candidate to be
Marco d'Itri wrote:
On Apr 22, Matthew Lockner mlock...@iastate.edu wrote:
Since its postinst is my means of demonstrating the problem, then of
course removing the package will prevent the problem from appearing, at
least in this context.
You can remove it and manually run
On Apr 22, Matthew Lockner mlock...@iastate.edu wrote:
What kind of crap am I looking for?
Anything related to snd* modules for a start.
properly. If we as users can't expect to be able to use this file
anymore, it would be user-friendlier for the package upgrade to tell us
so and state
Marco d'Itri wrote:
On Apr 22, Matthew Lockner mlock...@iastate.edu wrote:
What kind of crap am I looking for?
Anything related to snd* modules for a start.
properly. If we as users can't expect to be able to use this file
anymore, it would be user-friendlier for the package
Package: module-init-tools
Version: 3.7-pre9-1
Severity: important
I recently did an aptitude upgrade. I found that when the postinst of the
oss-compat package was run during configuration of packages, I got a
screenful of warnings, and found a long list of modprobe and sh modprobe
processes
15 matches
Mail list logo
