Fix committed in ubuntu-defaults-baltix package source revision 14
** Changed in: baltix-default-settings
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397
** Branch linked: lp:~baltix-members/baltix-default-settings/ubuntu-
defaults-baltix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397
Title:
Executable files do not launch
To manage notificati
** Summary changed:
- Executable files do not launch in 13.04
+ Executable files do not launch
** Description changed:
If I make a text file executable - I can launch it in 12.10, or 12.04 .
- But in 13.04 it is just opening in gedit . I need to use terminal to
- launch it.
+ But in 13.04, 13.
I just had this problem. Coming from 12.04 to 14.04 my executable that
was launching WebStorm just started opening in GEdit.
It felt like a bug, not a "Feature".
This is why I went back to Windows. Someone decided to make an arbitrary
decision and now I have to find why it happened. These develop
It is not an unuseful comment, is UX feedback, which should be valued
the most. When I initially reacted to this bug, I was reporting my
experience helping users update and observing their struggle with layers
of fixes on their desktop, often scripts made by friends to help execute
tasks.
A LEAN U
** Changed in: nautilus (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397
Title:
Executable files do not launch in 13.04
To manage notifications abo
Hi,
For me this is a bug, the fix should be applied to the original package,
so 13.04 and future ubuntu installations will not suffer from this.
There is no sense with behavior 'View executable text files' selected by
default for a regular user.
Shellscripts are commonly used to launch other ex
It is still actual in 13.10 x64. Any attention to this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397
Title:
Executable files do not launch in 13.04
To manage notifications about this b
This was an intentional change done by upstream Nautilus developers.
Showing a dialog by default makes problems for users that have external
drives with FAT32-like filesystem, where all files are executable. See:
https://git.gnome.org/browse/nautilus/commit/?id=72d6c7ce7febd573
https://bugzilla.gn
Thanks for the references to the upstream process.
Not just the executable bit, but also the file magic (shell script or
ELF) could be parsed to sort out problems.
However, I guess this is not the place for discussing this.
--
You received this bug notification because you are a member of Ubunt
In Ubuntu 14.04 and 14.10 the problem is still there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397
Title:
Executable files do not launch in 13.04
To manage notifications about this bug go t
We should pay attention to this indeed.
This is a radical change for many users acquainted to execute shell scripts or
having them written by friends to fix things.
Believe me, this happens *all the time*.
Changing this behavior without any notice is irresponsible, a very
conservative step that
Just in Nautus File/Preferences/Behaviour Under Executable Files check
Ask me always.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397
Title:
Executable files do not launch in 13.04
To manage
It's simple to return back old behavior - set dconf setting value:
org.gnome.nautilus.preferences executable-text-activation
to 'ask'
** Also affects: baltix-default-settings
Importance: Undecided
Status: New
** Changed in: baltix-default-settings
Assignee: (unassigned) => Mantas
It's a completely incorrect behavior always to open executable text
files with Text Editor - lots of executable installers are very big
(200-500Mb) and opening very big files with Text Editor causes freeze of
operating system for several minutes on older computers, try for example
to open Unigine_V
** Changed in: nautilus (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/397
Title:
Executable files do not launch in 13.04
To manage notifications about thi
On Wed, 29 Jan 2014, Mantas Kriaučiūnas wrote:
> It's simple to return back old behavior - set dconf setting value:
> org.gnome.nautilus.preferences executable-text-activation
> to 'ask'
"simple"? most ubuntu users are afraid to open a Terminal.
however, thanks for the info, but this discussio
17 matches
Mail list logo
