« first day (2385 days earlier)      last day (139 days later) » 

1:50 AM
Some Error Occurred on this post
 
 
1 hour later…
3:26 AM
@Natty tp
 
 
3 hours later…
 
1 hour later…
 
3 hours later…
10:47 AM
@Natty tp
@Natty tp
OT 17.04
 
 
2 hours later…
1:06 PM
I tried the solution offered by @pomsky in this thread. It worked fine: duplicate applications icons in ubuntu dockMarco Castro 1 min ago
^^ Nevermind, OP accepted
 
 
2 hours later…
2:46 PM
@Kulfy sorry it took so long to get back to you about this. I was participating in a charity dance event yesterday and I was tired after that. Until after lunch today I didn't feel energetic again haha
So, bug reports are considered to be off topic here
this was a controversial decision and I personally disagree with it to some extent, but it is established policy so we need to follow it
this policy is supposed to be applied with nuance
we don't want people to report bugs here because bugs should be reported on Launchpad so they can get fixed
I do agree with that, and with the policy that questions about bugs in beta versions should be off-topic
however, asking for a workaround for a bug should be on topic
many bugs are long lived. I have to hack around various bugs just to use Ubuntu. If I hadn't been able to find out how to do that on the internet, I wouldn't have been able to do it
So I think we should only close questions that are really intended as bug reports or are about problems with beta versions
or, questions that are unanswered for a while and are about things caused by a bug that was fixed can be closed with that reason, though arguably they can also be no-repro
in practice if a question is about some problem and it's a bug, then we just close it, because it's hard to apply this policy in a nuanced way
If you can explicitly say in the question you are looking for a workaround for the bug, the question might not get closed. This question somewhat divided opinions
You can always advise OP to ask on Unix & Linux. Questions about bugs are fine there.
So, the question is closed according to policy. I'll note that is has two deleted answers, which are both completely useless NAA answers. Bug report type questions do tend to attract those, which is a good reason for closing them
 
3:39 PM
@Zanna That's indeed a very detailed explanation. Thank you for doing that. But I still have some doubts. Like all questions I've mentioned here revolve around a same bug but then why only 1 was closed as OT?
 
because only on that one someone found the bug
otherwise it might be some user config issue
this one is asking how to disable a dialog - can't be off-topic
this one asking "how can I stop it?" is also asking a how type question that can be interpreted as not-a-bug-report
I'd much rather avoid interpreting a question as a bug report if possible :)
 
Honestly saying this sounds confusing to me. May be interpreting a question would take some more time on my side.
Zanna as you are good with comand line can you please explain what is significance of UBUNTU_MENUPROXY in env UBUNTU_MENUPROXY=/path/to/some/executable/file?
 
seems like a user-defined variable... haven't seen before
 
3:55 PM
Actually I saw that in a screenshot in a question. And I have no idea what is that doing in a Desktop Entry
 
actually I see this variable is defined for me haha
if I run printenv | grep UBUNTU I see it
its value is 1
so I wonder what this variable does
and why it would be set to a path
 
I believe that's completely useless. Since when I execute that in terminal I get output when env is executed as a command and then value of UBUNTU_MENUPROXY which is being defined there.
 
the env command is used to run a command with a particular environment. So the command there sets UBUNTU_MENUPROXY only for this command. Often you don't need env because you can just define variables in the same line as the command you run with the syntax VAR=val command
 
I can't check that on my system right now since I am taking a backup and currently on live system. I got no output at least on live system.
@Zanna Yeah that's why I was confused that why OP set that path.
 
ah so maybe the Exec line in the .desktop file is the problem, because it doesn't make sense
I don't see how that command could run NetBeans :)
 
4:02 PM
Yeah indeed. That command looks odd.
I asked to to replace content of that .desktop'
 
Looks in the screenshot like it's starting when they call it in the terminal. The warnings are not important
 
Yeah but I believe his main concern is that shortcut
 
that's what I mean. There's no evidence that the problem is not limited to the .desktop file
 
Indeed.
 
 
2 hours later…
 
2 hours later…
 
2 hours later…

« first day (2385 days earlier)      last day (139 days later) »