-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Control: tag -1 +moreinfo Control: severity -1 normal
Hello, On Tue, 2017-02-07 at 15:24 +0100, martintxo wrote: > Package: laptop-mode-tools > Version: 1.70-2 Why have you filed it against 1.70 when the latest version in Debian testing/unstable is 1.71 ? > Severity: grave This severity is unjustified. There are many many users of Laptop Mode Tools and I've not heard of any serious issue as such. > Justification: renders package unusable > > Dear Maintainer, > > * What led up to the situation? > > I'm in a Acer Emachines EM355, with Debian Testing. In the last dist-upgrade, > the last week, I end with a mostly unusable machine. The symptom was that at > the boot put some messages about some services than didn't start, and ends in > a > console login without more explanations. Later I know that the root filesystem > was mounted read-only, and that I can mount it read-write, but in every boot > it > mounts read-only... > Hmmm. Were you able to find the cause why your root file system was being mounted read-only ? This to me sounds like your operating system was not shutdown clean, and on consecutive reboot, it found the file system inconsistent. WHat does your file system layout look like ? Can you give the output of `df -h` and `mount` ? > * What exactly did you do (or not do) that was effective (or > ineffective)? > > I investigate some things, but it was hard to know. I try to install passed > versions of systemd, udev... > > In some moment, I realized that the battery was to be exhausted, and I put the > box on AC... Later reboot, and all was good!! Miracle :-D > > This carry me to investigate in the powersaving packages, and view that > laptop- > mode-tools has an update with some tings related to boot. I uninstall it an > voila! The box boot in all the cases. > It could just be that laptop-mode-tools is uncovering some bug elsewhere. But this still needs to be investigated first. > Now I installed the old version 1.70-2 from snapshot.debian.org, and it works > good for me. > Ah. Now I see why you filed against 1.70-2 :-) > * What was the outcome of this action? > > I spend some hours looking at this problem. But now all is working well with > this old version. I hope that you can fix the problem in the new version. > In its current form for this bug report, unfortunately there isn't enough information for me to investigate. What I can give you is some data points. I use Laptop Mode Tools on all my machines without any issues (version 1.71). My laptop is mostly run on Battery. I only charge it when it is sleeping. So your "Boot on Battery" example is not correct because I've been able to run without any issues. Are you good with syslog and remote logging ? What you could do in this case is to install rsyslog and enable remote logging to a different machine. And then share those logs. If you are on systemd, systemd-journald must have a similar remote logging mechanism. You could try that too. I am afraid but without any logs it is hard for me to do any diagnosis. - -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEQCVDstmIVAB/Yn02pjpYo/LhdWkFAliaDssACgkQpjpYo/Lh dWlU4RAApyMnpiHfojIAez/sysoN/xhvVryUlv52v1kaf48Pk8Z0MwgtHpGIZudV GmErFORGbyYUFbc5qeUScT/Q2by5za2ar9OlqmCKBe2IlrbfiNgPLVoNW2BBUtkA NSHJOIMCYUB6dW/2zGYQdWq52wM13snvLEtMvS0DTLBTIgmFhHV+lG7cXLCui2ty ugP5MA5HAtIYluDGq++XOjaJmRh36Mx8LircxnubEK7QucVninmZJvibMvpwm+EV yPqXWxQVJqWrysdCdt7qPdOSQjmyYpEaA0Glv1pid4PMk/MhqhIarhRU5tMDUJEN w1lrY+i+RYC/LMiaqjY6Iz7TB8PEa+wMH0rUbLbkn4pdSEu+3R2yVTv7SvSMlLOT qGa3LHZN0jm5Zh2kzuig6JW2y0oqfRM2CwZwazWqWge948tyB1t0fxE3WdlAEG0L HQ+QI6D4KXjl1/St8Kc4lf7L/QTQIg1B3Ak4RfNBLqy3Uvz0rP2hpxJojMg1oidK /EiJarpjnWL79fwFkwaTLDVwZAZ2vPlZ95FRF7qS7fBXLWPRtMgGuJD59HilGrbf oPOva7i+rdz+WCuyER2WzeFK2mVkyCFmTzMUrQ/AiWW5/yJHaNVY8xK1PGKSEN7P EiMwDEsizH6itdrnMn7u9CoEn4I4YiGyGCuOcxnsE7GdOaeieIQ= =A2IG -----END PGP SIGNATURE-----
