| Summary: | 'service dm stop' not stopping dm but reporting success | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Herbert Poetzl <herbert> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | dmorganec, herbert, mageia, marja11, tmb |
| Version: | Cauldron | Keywords: | NEEDINFO |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | initscripts-9.34-4.mga2.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Herbert Poetzl
2012-01-28 14:53:59 CET
you are not using systemd ? AFAIK no, it didn't get enabled when I upgraded from Mageia 1 # pidof systemd # systemctl Failed to get D-Bus connection: No connection to service manager. how can I tell for sure? seems no :) As we want to support both initscripts & systemd, added the committers of the first one CC:
(none) =>
dmorganec, mageia, tmb Over 3 months later, a lot changed in cauldron. is this bug still valid? Keywords:
(none) =>
NEEDINFO still valid! # service dm stop Stopping display manager: [ OK ] # pidof gdm-binary 1353 # pidof X 1501 sysvinit-legacy-2.87-17.mga2 sysvinit-legacy-tools-2.87-17.mga2 CC:
(none) =>
herbert I presume this is only under sysvinit right? i.e. it works find under the default systemd? correct
Manuel Hiebel
2012-05-07 16:05:10 CEST
Keywords:
NEEDINFO =>
(none) Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja Keywords:
(none) =>
NEEDINFO sysvinit is being removed from cauldron, closing as wontfix https://www.mageia.org/pipermail/mageia-dev/2012-June/016996.html Status:
NEW =>
RESOLVED Well it is still a bug in MGA2, but to be perfectly honest, I'm unlikely to get around to fixing it considering it's not the default init system and it's not all that critical for most users. Not ideal, so I'd be happy to help anyone who does want to fix it. (In reply to comment #10) > Well it is still a bug in MGA2, but to be perfectly honest, I'm unlikely to get > around to fixing it considering it's not the default init system and it's not > all that critical for most users. Not ideal, so I'd be happy to help anyone who > does want to fix it. You're right, but since nobody complained about having this bug in Mageia 2, and because this bug was only filed against cauldron, I thought we might as well close it. @ Anyone who thinks this bug should stay open: Feel free to reopen it and change version to "2" |