This is basically the same as bug #870297, but for LXDM.
Systems using LXDM have no entries in the utmp record for logins, so tools like ’w’ and ’who’ do not show LXDM sessions.
Testcase:
1. Start Lubuntu system
2. Log into session
3. Open gnome-terminal
4. Run ’who’ command
Expected result:
You should see TWO entries (the first is from LXDM, the second is from gnome-terminal):
tty7 YYYY-MM-DD HH:MM
pts/0 YYYY-MM-DD HH:MM (:0)
Observed result:
You see only one entry:
pts/0 YYYY-MM-DD HH:MM (:0)
Additional info:
Used gnome-terminal just for consistency with the LightDM report; lxterminal also doesn’t seem to update login records so if you use it instead, observed result is actually ”no entries at all” (and issue for another report). Also, bug #1027805 about wtmp records is similarly applicable to LXDM, but that remains to be fixed even in LightDM…
The ”Filing bugs when off-line” section of the bug reporting community help can be applied here:
First, on the target system, gather the information in a file:
- For a bug report about a system crash:
apport-cli -p <package name> --save bug.crash
- For a bug report about any other issue:
apport-cli -f -p <package name> --save bug.apport
You will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the .apport or .crashextension.
When the file is ready, copy it to the system you intend to use for filing the report. There you can then file the report:
ubuntu-bug -c <apport_file.extension>
I know I can file a bug report on the local machine by running `ubuntu-bug`. But what about when I have a bug on another computer elsewhere so that it’s not convenient to get to it physically to file a report there? Can I use Ubuntu’s bug reporting tools to gather data about the bug remotely, transfer that data to my local machine and submit a bug report here with the data from the other system?
This was awesome! I don’t know if it’s the different editing or just that the topic is so fascinating and the professor so good at explaining, or a superposition of all three. And I still have prof. Moriarty’s version to watch, happy times!
Also reproducible with chromium-browser 28.0.1500.52-0ubuntu1.12.04.2 (in 12.04).
As the original reporter, I’m confirming that 5.20.0-0ubuntu2 from -proposed does contain the fix for this bug, i.e. the issue I reported above is no longer reproducible. I’m only hesitant about tagging this ’verification-done’ because PerformingSRUVerification is pretty adamant about having a solid test case and I’m not sure my sloppy initial report qualifies.
jani@saegusa:~$ LC_ALL=C apt-cache policy unity
unity:
Installed: 5.20.0-0ubuntu2
Candidate: 5.20.0-0ubuntu2
Version table:
*** 5.20.0-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ precise-proposed/main amd64 Packages
100 /var/lib/dpkg/status
5.18.0-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
5.10.0-0ubuntu6 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
Songtapperia olen joskus kokeillut kappaleiden tunnistukseen, muttei se kovin hyvä ollut. Shazam taas tarvii pätkän autenttista materiaalia, mutta näköjään nykyisin on sellaisiakin joihin voi hyräillä tai soittaa virtuaalikoskettimin.
I already knew the Beeb’s predator dinosaurs have serious eyesight problems, but this one takes the cake. Getting surprised by the largest dinosaur ever, over a landscape of virtually nothing blocking the view! Come on!