Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Screen does not lock or turn off with lock switch anymore (N900) #86

Closed
sicelo opened this issue Feb 23, 2018 · 6 comments
Assignees
Labels

Comments

@sicelo
Copy link
Collaborator

@sicelo sicelo commented Feb 23, 2018

After the recent upgrade of most packages, the lock switch does not cause the screen to be locked and turned off. It seems that mce does not run automatically at boot.

Related: the battery status also does not show up on the menu until it is manually killed and restarted.

Dbus?

@sicelo

This comment has been minimized.

Copy link
Collaborator Author

@sicelo sicelo commented Feb 23, 2018

Related discussion on IRC:

23:37 < Wizzup> so the issue seems to be mce or dbus related
23:38 < Wizzup> sicelo: so, what I did, is start mce by hand (mce --force-syslog) then restart hildon-status-menu, and then start (it wasn't running) systemui
23:38 < Wizzup> now it all 'works'
23:38 < Wizzup> going to reboot and see why this happens
23:40 < sicelo> systemui handles lock switch too? i know it handles power button, which wasn't working too
23:40 < Wizzup> apparently.
23:57 < Wizzup> # cat /tmp/session_bus_address.user
23:57 < Wizzup> export DBUS_SESSION_BUS_ADDRESS=
23:57 < Wizzup> seems mce block on this
23:57 < Wizzup> . /tmp/session_bus_address.user
23:57 < Wizzup> /usr/sbin/waitdbus session
23:57 < Wizzup> so then the question is why that is not written properly
23:59 < freemangordon> Wizzup: it is again that dbus shit :(
00:00 < Wizzup> yes, but why
00:00 < Wizzup> I don't understand why it fails
00:00 < Wizzup> seems like /etc/X11/Xsession.d/01dbus doesn't produce the right file
00:00 < Wizzup> as in /tmp/dbus-info is OK
00:00 < Wizzup> but then when it cats it's empty
00:01 < freemangordon> Wizzup: we hit that back then
00:01 < freemangordon> thje reason is that stderr is not being flushed
00:02 < freemangordon> anyway we should get rid of bdus being started by init system
00:02 < freemangordon> *dbus
00:02 < freemangordon> and leave only the one started by xsession
00:03 < freemangordon> which would mean that mce should be started as part of xsession as well, or at least it should wait for X

@MerlijnWajer MerlijnWajer self-assigned this Feb 23, 2018
@MerlijnWajer

This comment has been minimized.

Copy link
Member

@MerlijnWajer MerlijnWajer commented Feb 23, 2018

It seems that apt zealously adds extra init scripts to the default runlevel, causing multiple dbus session busses to run.

This command will fix it for now, after update:

rm /etc/runlevels/default/{af-base-apps,af-startup,dundee,hulda,ofono}

I will leave it to apt experts to figure out what to do -- either fix the dbus usage or have these init scripts not be installed.

@MerlijnWajer

This comment has been minimized.

Copy link
Member

@MerlijnWajer MerlijnWajer commented Feb 23, 2018

Here is a diff of the default-image /etc/runlevels/default and the one after the update:

0a1,3
> 
> ./etc/runlevels/default/
> ./etc/runlevels/default/af-base-apps
1a5
> ./etc/runlevels/default/af-startup
8a13
> ./etc/runlevels/default/dundee
10a16
> ./etc/runlevels/default/hulda
14a21
> ./etc/runlevels/default/ofono

@MerlijnWajer

This comment has been minimized.

Copy link
Member

@MerlijnWajer MerlijnWajer commented Feb 25, 2018

@parazyd - want to remove at least af-startup? Maybe on the fly also decide the same for af-base-apps?

I don't know what dundee and hulda are (yet). ofono can remain, of course.

@MerlijnWajer

This comment has been minimized.

Copy link
Member

@MerlijnWajer MerlijnWajer commented Feb 26, 2018

@parazyd said that he removed the init scripts from the packages. I had to remove them from my install manually, but once I removed the ones in /etc/init.d/ they did not come back.

Apt still complains:

update-rc.d: error: initscript does not exist: /etc/init.d/af-startup
update-rc.d: error: initscript does not exist: /etc/init.d/af-base-apps

Once that is fixed we can close the issue I think.

MerlijnWajer referenced this issue in maemo-leste/ke-recv-extra Feb 26, 2018
@MerlijnWajer

This comment has been minimized.

Copy link
Member

@MerlijnWajer MerlijnWajer commented Mar 8, 2018

Should be fixed now. On update (if you had the bad one installed) apt doesn't seem to remove the init scripts, but if you remove them manually (or use a recent image) you should be fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants
You can’t perform that action at this time.