Many thanks for the help, I removed the two // at the start and tried to run software manager. I had some unmet dependencies, but a quick install - f fixed that — pootpoot12 hours ago
Since the edit, it has enough information to be answered... but also, the OP is no longer looking for an answer.
@EliahKagan I feel the title ought to be changed... is OP trying to generalise their question although they really just want to install that thing? I would think so... but it reads like they are just giving that thing as an example
If they're truly asking the fully general question, then it could be closed as a duplicate of the general question about installing software from source that almost nothing should be closed as a dupe of.
not off-topic - that a root password has been set and su works to become root does not by itself mean a non-Ubuntu OS is being used
That question might be unclear, but I really don't think it should be closed as off-topic, which is what would happen if I were to vote to close it as unclear.
@pomsky ^^ If you mean because su was successfully used to get a root shell, it's not that rare for people to set a password for the root account on Ubuntu. People don't talk about it all that much, because they tend to get shouted down with poor, often factually inaccurate arguments (even when not attempting to run graphical applications), more in some other parts of the Ubuntu community than here. But I believe a substantial minority of Ubuntu users do it.
I have upgraded 14.04 to 16.04 . Now I am trying to open the gedit from terminal by passing the command:
sudo gedit /some/where/file.txt
but it is throwing an error stating that:
(gedit:2090): Gtk-WARNING : Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
T...
On the one hand, there actually is some truth in what was said--some of the messages, regarding d-bus, likely are due to how Nautilus is running as a user who isn't logged in. My comment sort of covered that, but not very well (it talked about whether Nautilus is already running as the user, but that's not the key issue), and I don't want to add additional wrong information.
On the other hand, it really seems to me that people are spinning this to scare the OP away from running Nautilus as root, and deliberately avoiding mentioning that the messages are most likely not indications of any actual problem. If that is true, then any response that doesn't point that out and object to it is questionable.
But I'd rather step away from it for a while and possibly come back--even at the (high) risk of never getting to it--than accuse people of something they're not doing or write something that, due to its own flaws, is likely to be interpreted as such.
I'm not flagging any comments or advocating removing them at this time, but it might be good to check back in a day or so to see if there are further developments. Fundamentally, I think a dupe closure or an answer can provide the needed clarity, and I'm skeptical that I could help the situation by commenting.
I tried to open Software Center using the command line
software-center
and it did work. I mean, Software Center opened and works fine, BUT, at the same time, in the Terminal window I see a lot of strange errors. How can that be? I'm puzzled.
Is there any explanation for this (and a fix for ...
@pomsky Thanks. I'm not sure why I missed that. My apologies. I've voted to close and commented about the related question.
@karel That question is not about a typo and it is not about Python programming. The OP wants to receive standard error from scripts run from a crontab. They deliberately created the erroneous code shown in the question as an example of the error message they want to see.
I think this edit is good. Tag wikis should probably follow official capitalization conventions except where they're actually unreasonable or would hinder readability, and the Ubuntu wiki page being linked to follows that capitalization as well.
@Natty Arguably already a partial answer... but it should be expanded. Or maybe converted to a comment. I'm not sure what feedback to give, but probably tp in its current state.
@Natty tp Could be read as an answer advising to use an earlier kernel than the version mentioned, but I think it's both intended as a comment and makes better sense as one.