Feature request: kdm.conf requires a "text" flag

Bug #893764 reported by mstfa cmly
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
upstart
New
Undecided
Unassigned
kde-workspace (Ubuntu)
Won't Fix
Low
Unassigned

Bug Description

This mainly affects users who wish to use the "text" GRUB flag on bootup for KDE users. I have found that opting to boot using the "text" option simply fails to stop KDM from starting.

Users on the forums have suggested the use of a manual override in /etc/init/kdm.override, but this would also affect a regular boot.

Adding the following lines to the "script" portion of the kdm.conf file would fix this without affecting regular users:

    if [ -n "$UPSTART_EVENTS" ]
    then
        # Check kernel command-line for inhibitors, unless we are being called
        # manually
        for ARG in $(cat /proc/cmdline); do
            if [ "$ARG" = "text" ]; then
                plymouth quit || :
                stop
                exit 0
            fi
        done

Changed in kdebase-workspace (Ubuntu):
importance: Undecided → Low
affects: kdebase-workspace (Ubuntu) → kde-workspace (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kde-workspace (Ubuntu):
status: New → Confirmed
Revision history for this message
Harald Sitter (apachelogger) wrote :

hardly seems appropriate to do this on a per-dm basis, something at upstart level would be better.

Changed in kde-workspace (Ubuntu):
status: Confirmed → Won't Fix
Revision history for this message
Steve Langasek (vorlon) wrote :

> hardly seems appropriate to do this on a per-dm basis, something at upstart level would be better.

There are currently no plans to implement such policy in the upstart package. I think you should reconsider addressing this in kde-workspace.

Revision history for this message
Mike Bianchi (mbianchi-foveal) wrote :

> There are currently no plans to implement such policy in the upstart package.

Is that an answer?

How is booting to "text" mode any different from booting to Unity, KDE, Gnome, or any of a dozen other possible modes? Demanding that each of those implement the "text" mode sounds wrong to me.

Deciding whether or not to boot into X, text, single-user or some other mode strikes me as _exactly_ what upstart should implement. So a bug like this should turn into a PLAN to modify Upstart to implement such a POLICY.

Revision history for this message
Steve Langasek (vorlon) wrote : Re: [Bug 893764] Re: Feature request: kdm.conf requires a "text" flag

On Sun, Nov 04, 2012 at 07:30:36PM -0000, Mike Bianchi wrote:
> > There are currently no plans to implement such policy in the upstart
> > package.

> Is that an answer?

Yes, it is. This CANNOT be implemented without changes to the kdm job; the
only thing that upstart can do is provide an abstraction that simplifies the
logic expressed within the kdm job. Such refactoring might be nice, but
lightdm and gdm already have support for this without such refactoring, and
this bug report is a request that kdm implement the same logic as those
other display managers - logic that can easily be implemented by cut and
paste.

If the Kubuntu developers think this is an important feature to provide to
their users, they should implement it - not block on a new abstraction being
implemented first in upstart.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.