Concerning the UPG group membership: As it is not necessary (and
redundant) and gives problems I believe users should not be made members
of their main groups.
As a result of adding the user to its main group deluser thinks the
primary group is not one adduser has created automatically as a user
p
Hi,
what a nice coincidence. :) Thank you for your feedback. I have now updated the
wiki to match the adduser behaviour as well.
I've seen now, that only useradd/groupadd is part of the debian passwd
package, but adduser uses it.
> (But still, adduser could be smarter and remove the group if the
Public bug reported:
Binary package hint: gnome-system-tools
splitting this from #488158
>we implement user profiles in users-admin. Those allow the
distribution/admin to present users with typical account types, which
set sensible default values for home dir, shell, groups membership (esp.
admi
All right, has been a pleasure.
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
You can refer to the relevant discussion in
Bug:488158 users-admin should leave adduser handle main group creation
and
Bug:488913 users-admin defaults to override system wide defaults from
/etc/login.defs, /adduser.conf
--
kuser is violating debian policy
https://bugs.launchpad.net/bugs/3793
Even better then. :)
(yes adduser.conf and adduser.local.conf together provide only "one
profile" )
** Summary changed:
- users-admin's profiles feature forces [GU]ID, home dir, shell and groups to
adduser
+ users-admin profiles default to force [GU]ID, home dir, shell and groups to
adduser
-
AFAIK the firehol init script is present and has not changed.
The suspecting package IMHO may well be an incomplete/broken upstart /
-compat init procedure.
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because y
*** This bug is a duplicate of bug 490317 ***
https://bugs.launchpad.net/bugs/490317
AFAIK the firehol init script is present and has not changed. (And works
as expected when called.)
The suspecting package IMHO may well be an incomplete/broken upstart /
-compat init procedure.
--
compat: u
maybe related: http://sourcecode.de/content/fun-upstart
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bu
Johnathon, can you reproduce this bug?
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
*** This bug is a duplicate of bug 490317 ***
https://bugs.launchpad.net/bugs/490317
maybe related: http://sourcecode.de/content/fun-upstart
--
compat: upstart not starting /etc/init.d/firehol and no log available
https://bugs.launchpad.net/bugs/490286
You received this bug notification beca
*** This bug is a duplicate of bug 250938 ***
https://bugs.launchpad.net/bugs/250938
** Changed in: acpi-support (Ubuntu)
Status: New => Fix Released
--
/etc/acpi/power.sh overrides user settings
https://bugs.launchpad.net/bugs/244836
You received this bug notification because you are
*** This bug is a duplicate of bug 250938 ***
https://bugs.launchpad.net/bugs/250938
not present in 9.10 anymore
** Changed in: acpi-support (Ubuntu)
Status: New => Fix Released
--
/etc/acpi/power.sh overrides user scripts
https://bugs.launchpad.net/bugs/244831
You received this bug
Hi Steve,
thank you for working on this. I have checked the integration in 9.10.
My observation is:
* laptop-mode-tools ships with scripts under /etc/power/*. Is this location
still valid in some way or are scripts supposed
to be installed under /etc/pm/* now (as /etc/ scripts to override
Micheal (Rooney), was that a desktop/server machine or a laptop on
battery where the disk failed to spin up again?
--
remove laptop-mode settings from /etc/default/acpi-support
https://bugs.launchpad.net/bugs/244838
You received this bug notification because you are a member of Ubuntu
Bugs, which
*** This bug is a duplicate of bug 59695 ***
https://bugs.launchpad.net/bugs/59695
In 9.10: hdparm -B gets set correctly (from another package apparently,
/etc/acpi/power.sh rightly so does not mess with this any more)
** Changed in: acpi-support (Ubuntu)
Status: Incomplete => Fix Rele
According to
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/239419/comments/5
the kernel's laptop_mode has been hardcoded to be enabled on battery all the
time anyway.
So it should be fine to just remove checking ENABLE_LAPTOP_MODE
in /etc/default/acpi-support from /etc/init.d/laptop-mod
According to
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/239419/comments/5
the kernel's laptop_mode has been hardcoded to be enabled on battery all the
time anyway.
So it should be fine to just remove checking ENABLE_LAPTOP_MODE
in /etc/default/acpi-support from /etc/init.d/laptop-mod
*** This bug is a duplicate of bug 59695 ***
https://bugs.launchpad.net/bugs/59695
In 9.10: /etc/acpi/power.sh rightly so does not mess with hdparm any
more.
I can't test if hdparm -B is set correctly after a resume by another
package, if not open new bug on that package.
** Changed in: acp
*** This bug is a duplicate of bug 244844 ***
https://bugs.launchpad.net/bugs/244844
pm-utils no longer ships on laptop-mode script
** Changed in: pm-utils (Ubuntu)
Status: New => Fix Released
--
pm-utils has laptop-tools script which conflicts with laptop-mode-tools
https://bugs.lau
*** This bug is a duplicate of bug 487729 ***
https://bugs.launchpad.net/bugs/487729
** This bug has been marked a duplicate of bug 487729
/etc/login.defs propagates incorrect information
--
/etc/login.defs umask cleanup
https://bugs.launchpad.net/bugs/71295
You received this bug notifica
See the following wiki page for more info about managing user
collaboration and related bugs.
https://wiki.ubuntu.com/MultiUserManagement
--
/etc/login.defs propagates incorrect information
https://bugs.launchpad.net/bugs/487729
You received this bug notification because you are a member of Ubun
Didn't mention this is on a *fresh* 9.10 installation.
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
Public bug reported:
Scripts that monitor system health for example need a way to notify all
users.
But libnotify and notify-send currently only support to notify the user
under which ID it is running.
So something like notify-send --broadcast or --to-user is needed.
** Affects: libnotify (Ubun
please forward upstream wherever that is
--
option to notify other/all users needed
https://bugs.launchpad.net/bugs/491433
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://
I second this,
and note that as different deamons exist already (notification-daemon,
notify-osd) patching wall might be preferable.
** Summary changed:
- [wishlist] notify-osd support for wall
+ [wishlist] desktop notification support for wall
--
[wishlist] desktop notification support for w
Public bug reported:
Binary package hint: mdadm
When mdadm monitors arrays and an event occurs it should not only send out an
email (not configured by default) but use "wall" and libnotify/notify-send to
to promt local (console/desktop) users.
** Affects: mdadm (Ubuntu)
Importance: Undec
Public bug reported:
Binary package hint: upstart
Many problems arise from the current initramfs scripts not being event
driven or a flexible state machine.
Might it be reasonable to use upstart code and configs within the
initramfs to get the rootfs up instead of reimplementing and maintaining
What about using the event driven upstart mechanisms within initramfs,
too? (LP: #491463)
(We need somthing that can handle any hotplugging sequence and stacking
of lvm,raid,crypt,...)
--
boot impossible due to missing initramfs failure hook integration
https://bugs.launchpad.net/bugs/251164
You
Public bug reported:
Binary package hint: laptop-mode-tools
Steve Langasek wrote (https://bugs.launchpad.net/ubuntu/+source/laptop-
mode-tools/+bug/244844/comments/16)
/etc/power/ appears to be a configuration directory for the pbbuttonsd
daemon, which is powerpc-specific
** Affects: laptop-mod
The package might just wrongly restrict the installation of /etc/default
/laptop-mode only to powerpc instead of restricting the install of
/etc/power only to powerpc.
--
/etc/power/ directory and files (used on powerpc) get installed on all platforms
https://bugs.launchpad.net/bugs/491804
You re
This bug as about the ENABLE_LAPTOP_MODE having nothing to do in package
acpi-support (another package).
(It was introduced there because some ubuntu dev once stuck an old unmaintained
laptop_mode scipt into acpi-support instead of using proper laptop-mode-tools
package, and later laptop-mode-to
Public bug reported:
Binary package hint: laptop-mode-tools
Because letters sort after numbers it is not possible to adequately sort
a script like "anacon" behind it using numbers.
** Affects: laptop-mode-tools (Ubuntu)
Importance: Undecided
Status: New
--
not following numbering
96laptop-mode as in sleep.d might be correct
--
not following numbering scheme in /usr/lib/pm-utils/power.d
https://bugs.launchpad.net/bugs/491831
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
If the /etc/acpi/events/lm_lid script has been removed from the ubuntu
package of laptop-mode-tools (as the laptop-mode-tools are adapted to
the invocation by pm-utils used in ubuntu), do pm-tools not provide a
replacement hook for the lid closed event?
I wonder because as aunt carry would have sa
Thanks, for getting back and finding out about /etc/power.
I'm sure we want to give a good impression of tidy, easily
understandable and functional ubuntu packages for acpi, powermanagment
and disk idleing (laptop-mode) support unlike with the bugload
unfortunately introduced before.
-> Because l
> Why would you not simply set a policy of suspending the laptop on lid
close, instead of turning on laptop-mode?
Because laptop-mode (with all the additional disk idleing features of
the laptop-mode-tools) is different from suspending into a unresponsive
state.
And doesn't gnome-power provide on
I got the firehol output into a file by modifying the init script.
The iptables commands fail because domains are not being resolved to ip
addresses.
Now I am not sure. Starting the firewall before the network is up might
be adequate behaviour. How can the init scripts handle this? Do firehol
sav
Corresponding --log-pid, --log-sid and --log-cmd options (like --log-
uid) for iptables are also missing.
--
PID and CMD filtering missing
https://bugs.launchpad.net/bugs/492612
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Public bug reported:
Binary package hint: iptables
iptables (and the kernel probably) are not compiled with support for pid and
cmd filtering.
So it can not grant connections only for selected processes or commands.
--pid-owner processid
Matches if the packet was created by a process with
the
This failure to load with domain names in the config may have arisen
with the network now set up by upstarts native /etc/init mechanism
(instead of with symlinks in/ets/rc?.d) or been present all the time.
However, a proper fix should no be now to ship two firehol upstart
definitions:
One /etc/i
Sorry typo has made it unclear: I mean "a proper fix should now be
to..."
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mail
*** This bug is a duplicate of bug 379397 ***
https://bugs.launchpad.net/bugs/379397
Ah, thank you for clearing this.
I must have missed the "copy skeleton" option when I first noticed that
users created with kuser where set up so differently from other methods
(independenly from the debian m
Reasoning: Not using the debian mechanims results in not executing
useradd hooks, different filepermissions, possibly not copying /etc/skel
etc. (duplicates of this bug.)
--
kuser is violating debian policy
https://bugs.launchpad.net/bugs/379397
You received this bug notification because you are
Public bug reported:
Disabling/locking a user account will not prevent a user from logging into your
server remotely if they have previously set up public key authentication.
A workaround is to restrict access to a sshlogin group and parallely
maintaining it,
https://help.ubuntu.com/9.10/serve
Oh, I just realized that adduser supports user profiles, maybe even
since its first version.
System wide profiles can be provided as adduser.conf. and the profile
is selected with:
# adduser --conf adduser.conf.
--
users-admin profiles default to force [GU]ID, home dir, shell and groups to
ad
>From viewing users I created with adduser I just noticed that in the
g-s-t edit group window the users name is of course not checked when
viewing any UPG created with adduser.
It may be nice to remove that user from the list and have some sort of
indicator that a group is a (possibly private) pri
s / remove that user from the list / remove that checkbox from the list
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Alternativly adduser.conf can be shipped as a symlink to a
adduser.conf.dist (distribution) profile.
This allows to switch the symlink to an admin provided profile, so that
it will be used as a adduser default, without having to touch the .dist
profile.
--
users-admin profiles default to force [
Just came across this answer.
http://lists.alioth.debian.org/pipermail/adduser-devel/2008-February/003161.html
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: adduser
Currently different frontends have implement and configure user profiles
differently, easily leading to inconsistencies when users are created with
different tools. Even if they use adduser to create users, they have override
much, somtimes ev
In order to mimic the user profiles currently shiped with gnome-system-
tools:
* mv /etc/adduser.conf /etc/adduser.conf.unprivileged
* create adduser.conf.desktop
- with EXTRA_GROUPS="cdrom floppy dialout tape dip adm plugdev fax audio
scanner fuse video"
- andADD_EXTRA_GROUPS=1
* create
I could not reproduce this on 9.10.
** Changed in: adduser (Ubuntu)
Status: New => Incomplete
--
adduser silently removes users from groups
https://bugs.launchpad.net/bugs/260086
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
addgroup is implemented within adduser
** Package changed: shadow (Ubuntu) => adduser (Ubuntu)
--
Let groupadd create /home/group/ sgid directories
https://bugs.launchpad.net/bugs/379421
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
-
** Summary changed:
- Let groupadd create /home/group/ sgid directories
+ addgroup option to create /home/group/ sgid directories
** Description changed:
-
- Let groupadd have the option to create /home/group/ sgid
directories.
+ Let groupadd have the option to create /home/group/ sgid
+ direc
** Description changed:
- Ubuntu uses private user groups.
+
+ Current behaviour is:
+ The "users" group exists but when setting up a (set group ID) groupdirectory
(i.e. /home/group/users) it does not work as expected, because the users group
is not populated (empty).
+
+ Changed behaviour wou
Changing package because the profiles with default groups in ubuntu are
currently maintained in g-s-t (not adduser).
** Package changed: pam (Ubuntu) => gnome-system-tools (Ubuntu)
** Changed in: gnome-system-tools (Ubuntu)
Status: Invalid => New
** Description changed:
-
Current beha
This is my first try at using bzr.
I created an own branch from the lucid brach, changed what I could while
browsing through the files, committed and used send -o to produce the
attatched file. Was that correct?
Any recomendations welcome.
** Attachment added: "initial patch to support adduser
I have actually produced a patch to adduser now, as far as I could.
Since it is my first one I'd appreciate any feedback. Its in LP: #489136
--
users-admin profiles default to force [GU]ID, home dir, shell and groups to
adduser
https://bugs.launchpad.net/bugs/488913
You received this bug notific
The init script should handle/pass on the status option as expected from
an init script. For the other options howeverver, calling the firehol
script directly seems just all right.
# firehol panic
--
init.d script not supporting option "status"
https://bugs.launchpad.net/bugs/185978
You received
** Summary changed:
- The rcS.d script for firehol is missing some options
+ init.d script not supporting option "status"
** Description changed:
Binary package hint: firehol
- DISTRIB_ID=Ubuntu
- DISTRIB_RELEASE=7.10
- DISTRIB_CODENAME=gutsy
- DISTRIB_DESCRIPTION="Ubuntu 7.10"
+ The init.d
firhol should be made to source firehol.conf and parts from a directory
like /etc/firehol.d, where other packages can drop config snippets.
While firehol still sets up the firewall as early a possible in the boot
up process.
--
The rcS.d script for firehol starts before NFS and NIS
https://bugs.
Does what the reporter posted mean that NIS/NFS scipts are flushing
iptables?
--
The rcS.d script for firehol starts before NFS and NIS
https://bugs.launchpad.net/bugs/28906
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
howto at: https://wiki.ubuntu.com/InitScriptStatusActions
--
init.d script not supporting option "status"
https://bugs.launchpad.net/bugs/185978
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
status could check if current iptables match those firehol generates
from its configuration ("firehol debug") else dispay the diff.
--
init.d script not supporting option "status"
https://bugs.launchpad.net/bugs/185978
You received this bug notification because you are a member of Ubuntu
Bugs, wh
I have had a look into /usr/share/system-tools-
backends-2.0/scripts/Users/Users.pm. Unfortunatly I am not at all
familliar with perl.
If it is currently reading in settings from /etc/adduser.conf it should
work with a linked profile as well, what you mean is probably reading in
other installed pr
Public bug reported:
Binary package hint: nautilus
9.10: Nautilus 2.28.1
A file/directory without write permissions shows a lock emblem even
though you can access it.
And this icon/emblem just looks the same as a file/directory that can
not even be read.
The difference in permissions should re
Public bug reported:
Binary package hint: firehol
ubuntu 9.10
* /etc/init.d/firehol script is there
* /etc/firehol/firehol.conf is in place
* firehol can be started with "/etc/init.d/firehol start"
(START_FIREHOL in /etc/defaults/firehol is set to yes) and the iptables
are set ok.
* symli
Public bug reported:
Binary package hint: gnome-system-monitor
The monitor shows network activity over time (last x seconds)
It should also show the list of processes that had network traffic (in
the last x seconds).
Possibly clicking on a traffic peak in the network graph could identify
the co
Thanks for pointing out that the bug belongs to the compat scripts then.
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Package changed: firehol (Ubuntu) => ubuntu
** Summary changed:
- upstart not starting /etc/init.d/firehol and no log available
+ compat: ups
affects set to upstart-compat-sysv (ubuntu)
--
compat: upstart not starting /etc/init.d/firehol and no log available
https://bugs.launchpad.net/bugs/490286
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
>> mdadm should not just sync the disk slower to appear to the first one,
>> because the parts
>> are inconsistent!
>
>This statement does not make sense.
Oh, right, yes. To put it better: They should not be synced if they
"contain conflicting changes"
If I read the case originally reported, the
** Description changed:
Using the latest beta-2 server ISO and following
- http://testcases.qa.ubuntu.com/Install/ServerRAID1, booting out of sync
- RAID1 array fails with ext3 (comes up as syncd).
+ http://testcases.qa.ubuntu.com/Install/ServerRAID1
+
+ Booting out of sync RAID1 array fails wi
Raid systems introduce redundancy to be able to keep working even if
parts of the system fail.
I think the init.d/mdadm scripts (early/late or simillar) that debian
uses to assemble and run degraded arrays on boot have been removed
because all arrays are set up using udev. But we don't have any
re
** Summary changed:
- mdadm monitor feature broken, not depending on local MTA/MDA or using
wall/notify-send
+ mdadm monitor feature broken, not depending on local MTA/MDA nor using
beep/wall/notify-send
** Description changed:
Binary package hint: mdadm
Anybody who cares about redundan
** Summary changed:
- booting out of sync RAID1 array comes up as already in sync (data-corruption)
+ array with conflicting changes is assembled with data corruption/silent loss
--
array with conflicting changes is assembled with data corruption/silent loss
https://bugs.launchpad.net/bugs/55742
** Also affects: mdadm
Importance: Undecided
Status: New
--
array with conflicting changes is assembled with data corruption/silent loss
https://bugs.launchpad.net/bugs/557429
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Though I can sure understand it would be easier if we could just dismiss this
to be taken care of by users, data-loss/corruption will allways come back heavy
on ubuntu/mdadm.
With ubunu systems in particular, we can not assume there will always be
an admin available. And if there is an admin, a
> Ok... how does that alter the fact that we should not be automatically
> adding devices to arrays that have been explicitly removed?
Not at all, we agree that explicitly --remove(ing) a device is a good
way to tell mdadm --incremental (its hotplug control mechanism) not to
re-add automatically.
Always auto-removing as a means to drop auto-re-add features simply
isn't an answer for conflict detection.
--
array with conflicting changes is assembled with data corruption/silent loss
https://bugs.launchpad.net/bugs/557429
You received this bug notification because you are a member of Ubuntu
Currently mdadm does not seem to distingush manual --removed status from
the status a drive that is missing gets when the array is run degraded.
Especially with write intent bitmaps regulary being used for faster
syncing in hotplug setups, and mdadm only comparing if "eventcount is in
range of bit
The last couple of comments sound like it's bug #252345
The following will recreate a static mdadm.conf (possible workaround)
but is not a fix to the issue (disfunctional hotpluging):
# /usr/share/mdadm/mkconf force-generate /etc/mdadm/mdadm.conf
# update-initramfs -k all -u
--
mdadm cannot as
I checked, and "login" keyring is "set as default".
On another machine I saw the "login" keyring containing the password for
unlocking the "default" keyring. So the functionality seems to be there.
Is it an option that could just be disabled somewhere?
--
gksu uses keyring "default" but only "lo
*** This bug is a duplicate of bug 495370 ***
https://bugs.launchpad.net/bugs/495370
** This bug has been marked a duplicate of bug 495370
Please upgrade to 3.1.x for lucid
--
mdadm package far outdated from upstream version
https://bugs.launchpad.net/bugs/563349
You received this bug not
** Description changed:
Binary package hint: mdadm
"mdadm --incremental" will save state in a map file under
/var/run/mdadm/map.
But in initramfs and early boot this directory does not exist.
The state is then saved in /var/run/mdadm.map.new (man page incorrectly
- says /var/run
I see that we were stumbling about confusing wording in mdadm.
Upon disappearance, a real failure, mdadm --fail or running an array
degraded: mdadm -E shows *missing* disks marked as "removed". (What you
probably referred to all the time.) Even though nobody actually issued
"mdadm --removed" on t
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen it before (since 7.10).
The i
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen it before (since 7.10).
The i
** Attachment added: "acpidump.txt"
http://launchpadlibrarian.net/44261320/acpidump.txt
--
Ubuntu 9.04 laptop overheat and shutdown
https://bugs.launchpad.net/bugs/370173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
** Attachment added: "dmidecode.txt"
http://launchpadlibrarian.net/44261482/dmidecode.txt
--
Ubuntu 9.04 laptop overheat and shutdown
https://bugs.launchpad.net/bugs/370173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-b
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
+ (confirmed also with 9.10)
+
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
** Summary changed:
- Ubuntu 9.04 laptop overheat and shutdown
+ laptop overheats and suddenly shuts down/off
--
laptop overheats and suddenly shuts down/off
https://bugs.launchpad.net/bugs/370173
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
Ubuntu 9.04, fresh install on Acer Aspire 5005.
(confirmed also with 9.10)
Not sure about package, but it seems the problem is with CPU frequency
adjustment or fan control.
Laptop shuts down right in the middle of CPU-greedy operation overheated. I
haven't seen
Hi Jools,
wow, you know to roll packages, and fixed some of the longstanding bugs
allready. Could you upload them or have them build in your Personal Package
Archive (PPA) https://help.launchpad.net/Packaging/PPA
I think maybe the initramfs creation hook (/debian/initramfs/hook) of the mdadm
pa
501 - 600 of 1101 matches
Mail list logo
