Public bug reported:
/usr/libexec/tracker-extract-3 and /usr/libexec/tracker-miner-fs-3 are
constantly taking 100% CPU, causing the machine to overheat and the fans
to work overtime.
This should not happen.
What doesn't help:
• Ubuntu Settings > Search > turn off search.
• Restart the machine.
Public bug reported:
When you right-click on a "Favourite" in the dock, it shows a small menu
relating to that app. For example, right-click on Nautilus to show the
options "All Windows", "New Window", and the various Nautilus shortcuts.
However, when the menu is long (I have many Nautilus
This appears to have been fixed, because it works for me.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1693480
Title:
Nautilus contextual menu in dockbar doesn't show common
An easy way to check if the bug is still present in Ubuntu is to enter a
flatpak-search command, e.g.
flatpak search meld
At the time of writing, this produces 3,010 spurious identical error
messages. This bug is relevant:
https://github.com/flatpak/flatpak/issues/5323
Note: flatpak version
** Description changed:
The snap version of gedit prevents viewing and editing files outside a
strictly limited set of folders. For example, it cannot change files in
standard folders ~/bin, ~/.local, ~/.config, ~/.ssh, or standard files
such as ~/.bashrc or ~/.profile. Even "sudo -H
Re comment #27
It's NOT only snap. This also happens to me with:
• The flatpak version of Firefox
• The Appimage version of Firefox
• Chrome installed from the official Chrome PPA
I have seen confirmation of this from others.
Thus Snap, Flatpak, Appimage and PPA are all affected.
--
You
** Description changed:
The snap version of gedit prevents viewing and editing files outside a
strictly limited set of folders. For example, it cannot change files in
- standard folders ~/bin or ~/.local or ~/.config, or standard files such
- as ~/.bashrc or ~/.profile. Even "sudo -H gedit
** Description changed:
The snap version of gedit prevents viewing and editing files outside a
strictly limited set of folders. For example, it cannot change files in
standard folders ~/bin or ~/.local or ~/.config, or standard files such
as ~/.bashrc or ~/.profile. Even "sudo -H gedit
The status is "Fix Released" October 2020, but it's still happening.
Ubuntu 20.04
Nautilus 3.36.3-stable
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1839380
Title:
Nautilus
@seb128 — Hmm, maybe I'm wrong about it being maintained. It's just that
it shows a lower level of compatibility in its Extensions listing. Sorry
if I was wrong.
I don't recall where specifically I have came across the recommendation
for NG, but I found it referenced in several places when I was
I have created Bug #1906420 which, if implemented, will solve this and
other bugs.
Please visit and "star" it (the green writing at the top) if you agree
with it.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1906420
--
You received this bug notification
I have created Bug #1906420 which, if implemented, will solve this and
other bugs.
Please visit and "star" it (the green writing at the top) if you agree
with it.
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-
icons/+bug/1906420
--
You received this bug notification
Public bug reported:
By default, Ubuntu installs the Gnome extension "Desktop Icons" [1] (by
rastersoft).
Unfortunately, this extension is now unmaintained, is problematic, and
leads to several bugs, including but not limited to Bug #1901150 and Bug
#1813441.
The same author has created, and
** Summary changed:
- gedit snap fails to open fails in user dot directories
+ gedit snap fails to save or open files in miscellaneous directories including
dot-folders, ~/bin, and system folders.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Please don't expire this request.
The problem still exists in full.
** Changed in: gedit (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1897562
I'm using Ubuntu 20.04.
On my desktop, Delete (which moves the item to the Recycling bin) just deletes
it.
Shift+Delete (which deletes the item permanently) does ask.
To me, this is correct behaviour and shouldn't change.
But...
I don't know if this has anything to do with the extension that
The updated Desktop Icons, "Desktop Icons NG (DING)" (by the same
author), fixes these problems.
Canonical could make its life easier by simply replacing the old Desktop
Icons with the new Desktop Icons NG (DING).
Desktop Icons:
https://extensions.gnome.org/extension/1465/desktop-icons/
Desktop
@seb128 — Correction to my previous post: For system folders, I cannot
even load files.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/1897562
Title:
gedit needs classic confinement
@seb128 — I can load files from ~/bin, but when I try to save, I get
this error (screenshot attached):
Could not save the file "/home/paddy/bin/myscript".
You do not have the permissions necessary to save the file. Please check that
you typed the location correctly and try again.
The same is
** Description changed:
The snap version of gedit prevents viewing and editing files outside a
strictly limited set of folders. For example, it cannot change files in
- standard folder ~/bin, or standard files such as ~/.bashrc. Even "sudo
- -H gedit /etc/fstab" doesn't work.
+ standard
Public bug reported:
The snap version of gedit prevents viewing and editing files outside a
strictly limited set of folders. For example, it cannot change files in
standard folder ~/bin, or standard files such as ~/.bashrc. Even "sudo
-H gedit /etc/fstab" doesn't work.
As there is a bug in the
Thank you for the links, Sebastian and Daniel.
I've resubmitted a bug report, because the one that was turned down was
specifically about max-recents in dconf, rather than about the
functionality.
https://gitlab.gnome.org/GNOME/gedit/-/issues/357
** Bug watch added:
Public bug reported:
• Ubuntu 20.04.1 LTS 64-bit
• gedit 3.36.2-0ubuntu1
gedit used to have an option to change the number of recently-opened
files in the Open dropdown button.
Later, that option was removed (I don't know why), but we could still set it as
follows (in this case, I've set it to
I have since discovered that sh.lang has been corrected for the problem
that I reported in comment #9 and so this can probably be re-closed.
Source:
https://gitlab.gnome.org/GNOME/gtksourceview/tree/master/data/language-specs
--
You received this bug notification because you are a member of
Could we reopen this, please?
gedit has highlighting for sh, but not for bash.
Most of the time, this works fine for bash, but sometimes it goes wrong.
For example, use a command substitution that contains a quote within
case-esac as follows.
#!/bin/bash
case ${SOMETHING} in
( 'a' )
Ubuntu 14.04 64-bit: I find that the Nexus 5 connects intermittently,
whereas the Samsung (two different models) won't connect at all.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
@brian-murray: For 12.04, unless this bug causes failures for people, I
wonder if the fix is worth the potential risk in an LTS, especially as
the next LTS, 14.04, is only 6-7 months away.
However, if you do release the code for testing, I shall be happy to
test it.
--
You received this bug
… it also makes things easier to chown the file to my username so I
don't need to type in sudo ggedit just ggedit
You don't have to use sudo, regardless of who owns the script.
Additionally, you should use gksudo, not sudo — which is already in the
one-line script, to save you the trouble of
@cavsfan: This has been happening since 11.10. If this has only recently
started with you, and was working beforehand, it would be interesting
and useful to find out what happened!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit
@samuel - Thanks for the function. Unfortunately, that only works from
the terminal; it doesn't work from Alt+F2.
For that reason, the simplest method is to create a new file (I call it
ggedit), place it in your path, and make it executable. The file
contains just one line:
gksudo gksudo gedit
@Doung McMahon: Fantastic.
Will the new version of gedit be released with 13.04?
Is there any possibility to back-port it to LTS?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
@cousteaulecommandant — Shouldn't temporary files be created in /tmp
rather than $HOME?
That depends on whether the contents are potentially private. As this is
related to .Xauthority, according to nicolas-m-le-zer0, these files
should go to the user's home folder.
--
You received this bug
@rpr-nospam — thanks for the clarification. I am aware of the
permissions ability, but it is further improved if the user uses
encryption on his home folder. Anyway, that is probably suitable for a
separate discussion.
Regarding comment #105 by @nicolas-m-le-zer0, I have been automatically
@Nicolay Doytchev: This is not a support forum. Please ask your question
on either the Ubuntu Forums [1] or an Ask Ubuntu [2]. In fact, you may
find a thread where someone else has already found the answer.
[1] http://ubuntuforums.org/
[2] http://askubuntu.com/
--
You received this bug
I believe that you are correct about LightDM being introduced in 11.10.
Thank you for your extra information. It should be helpful to the
developers in finding out where this bug is happening.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Further comments in bug #728700 led me to searching Google.
It appears that LightDM may be a red herring for this problem.
It seems to be (as far as I can tell — I may be wrong) that this is
caused by glib when cancelling a file being copied, as per comment #60
and others.
--
You received this
That's the sort of thing other people and I are getting.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/728700
Title:
Nautilus doesn't clean up temporary files from cancelled file
Please have a look at bug #984785.
We believe that the .goutput files are to do with lightdm, so your
experience is interesting. Can you remember if, when you cancelled your
copies, you logged out, restarted or crashed?
--
You received this bug notification because you are a member of Ubuntu
I searched my computer and found that these files are also present in
/var/lib/lightdm, created by user lightdm.
Look at bug #728700. The submitter of that bug thinks that this is
caused by failed copies, but I have been unable to duplicate this.
--
You received this bug notification because
@Isamu Arai: As stated in comment #29, an alias is no good if you are
using Alt-F2 to run the command. That is why I use an executable file
within a path.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
@NoOp: An alias is fine, unless you are using Alt-F2 to run the command.
But don't set gksudo to 'gksudo gksudo', because only gedit has this
problem. Rather set another name. I have created an executable file
called ggedit in my path (~/bin), and it contains just one line:
gksudo gksudo gedit
I don't think that the response is appropriate. We specifically have
reasons to sometimes run certain GUI programs as root, such as Nautilus
and gedit.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
What happens if you use gksudo instead of gksu? (Officially, there is no
difference between gksu and gksudo, but in fact there is a subtle
difference.)
Also, if you use sudo, you should use -H, as:
sudo -H nautilus
--
You received this bug notification because you are a member of Ubuntu
Desktop
@Freecore: Thank you for your comments.
For whatever reason (probably the post is too old), I cannot edit my
original post; but your gksudo gksudo is so much easier than my
solution. And weird!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Clark, thank you for your update. I was wondering whether or not
anything would happen to this problem. I know we're not the only people
with it, as I have seen complaints elsewhere on the 'net.
I have tested on the Alpha 12.10 Quantal (fully updated), and
unfortunately it is still there. Still
I've just realised that this is probably a duplicate of bug #629153,
which was raised almost two years ago!
Would you agree that #629153 is a duplicate? If so, I'll mark it thus.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp
This bug is still present in 12.10 Quantal Quetzal. :(
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/796076
Title:
When run as root [gksudo gedit whatever] gedit tries to open a
Public bug reported:
For a software Autorun Prompt, all that happens is an icon in the
Launcher. Clicking on the icon does nothing. After a few seconds, the
icon disappears.
Sample screen-shot attached.
What should have happened:
The Autorun Prompt should display, allowing the user to run the
** Attachment added: Showing the Launcher icon before it disappears. No
Autorun Prompt appears even when clicking on it.
https://bugs.launchpad.net/bugs/1027627/+attachment/3231871/+files/Autorun%20Prompt%20failure%2012.10.png
--
You received this bug notification because you are a member
If you are interested, I have created a simple workaround for this
problem. The how-to is described in the following forum post.
http://ubuntuforums.org/showpost.php?p=12071894postcount=81
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed
I can confirm that this is still happening.
It's been over a year already -- this simple error does not reflect well
on Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/796076
*** This bug is a duplicate of bug 950160 ***
https://bugs.launchpad.net/bugs/950160
This bug is not exactly a duplicate of bug #950160, as I can still
create keyboard shortcuts with the Alt key (e.g. Alt-Y).
As I do not know the technical underpinnings, would the resolution of
bug #950160
On 2012-05-30 the status was changed to Incomplete.
However, that question was answered; so shouldn't the status be reset to
Confirmed?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
Sebastien, that is an interesting question!
sudo userdel --remove -- newuser
- This gives the same problem.
However, the manual for userdel says:
On Debian, administrators should usually use deluser(8) instead.
So I tried:
sudo deluser --remove-home -- newuser
- That command worked correctly.
Public bug reported:
System Settings User Accounts delete a user:
If the user has an encrypted home folder, this action does not delete his
(encrypted) files.
This is a potential (though highly unlikely) security vulnerability, as
recreating the user can reveal the previous files (as
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1009607
Title:
User Accounts does not delete all files when deleting a user with an
encrypted folder
To manage
I have tried this in Unity, Unity 2d and even Gnome Classic (No
Effects).
They are all the same.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/995885
Title:
Custom
Public bug reported:
When I log out and then log in again, the sound (both input and output)
is disabled.
Work-around: When I restart the machine, the sound is re-enabled.
I have attached four screen-shots (in ScreenShots.tar.bz2) to
demonstrate the problem. They are:
1 Applet working.png --
** Attachment added: Four screen-shots as explained in the description to
illustrate before logging out and after logging in again
https://bugs.launchpad.net/bugs/1003310/+attachment/3159093/+files/ScreenShots.tar.bz2
--
You received this bug notification because you are a member of Ubuntu
Clark Everetts:
Thank you for posting your work-around. I have just tested it with my
WMF files. Unfortunately, as Libre Office crops larger WMF files, the
saved-as pictures are also cropped, and I have no way around that. For
me, the only work-around remains either running 10.04 in a virtual
Public bug reported:
I have put the package on this bug as GIMP, but seeing the range of
problems (described below), it is probably something else.
SUMMARY:
1. In Lucid 10.04, GIMP would flawlessly import WMF files.
2. Starting Maverick 10.10, it would not work.
3. There was, at least, a
** Attachment added: The GIMP import dialogue for WMF files. The negative
ratio cannot be changed.
https://bugs.launchpad.net/bugs/1001570/+attachment/3153305/+files/GIMP%20import%20dialogue.png
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
More information...
It seems to be related to the category of the shortcuts.
For example:
If I set (say) Super-D as a shortcut in one of the main categories (e.g.
Launchers Launch Terminal), then the Super key works.
But if set in the Custom Shortcuts, then the Super key will not work.
See
Public bug reported:
Prior to Precise 12.04, you could use the Super key in shortcuts, for
example Ctrl-Super-M.
However, with 12.04, if you set a shortcut with Super, it simply does
not work. There is no error message; it just doesn't do anything.
To duplicate:
First, ensure that zenity is
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/995885
Title:
Custom keyboard shortcuts do not work if they use the Super key
To manage notifications about this bug go
This happened to me while trying to install Virtual Box Guest Additions.
Running a clean installation of 12.04 Beta 64-bit in Virtual Box.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
Not everyone likes this dimming effect. If it is implemented, please
make it optional!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/883138
Title:
Dim file extensions
To manage
I think we should indeed add a Lucid component to the bug, because Lucid
is LTS.
I don't know dmesg. I logged into another user and then back into my own
(having been logged out, of course), and I have attached the results of dmesg.
I used the command:
dmesg dmesg-2011-03-11.lst
Let me know if
I'm amazed... the second time I did the process, it did not log me out.
That's the first time that's happened since I installed 10.04 (I used to
have 8.04). However, after I restarted my computer, it went back to
normal (crashing me when logging into another user).
I have attached Xorg.0.log
And here is Xorg.0.log.old.
** Attachment added: Xorg.0.log.old after logging into another user, having
the first user crash, and logging back in to the first user
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/693446/+attachment/1901028/+files/Xorg.0.log.old
--
You received this bug
I repeated the exercise with 10.10 and I could not duplicate the issue.
So, I suspect that the problem has been resolved in 10.10.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/693446
I have reinstalled 10.04.1 from scratch (in a fresh partition on an
external hard drive, so there is no customisation); run Update Manager
to install all updates; rebooted; and created a new user.
I still get the same error.
I have attached the logs from /var/log/gdm.
** Attachment added: Logs
Public bug reported:
Binary package hint: gdm
When using switch user, the original user gets logged out.
More detail:
- First user logs in.
- Switch user -- login screen shows first user still logged in.
- Second user logs in.
- Second user logs out.
- Login screen shows first user logged out.
** Attachment added: Logs from /var/log/gdm
https://bugs.launchpad.net/bugs/693446/+attachment/1773675/+files/gdmlogs.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm in ubuntu.
https://bugs.launchpad.net/bugs/693446
Public bug reported:
Binary package hint: nautilus
Ubuntu 8.04.1
GNOME nautilus 2.22.3
REPRODUCING THE PROBLEM
1. Start nautilus.
2. Right-click any subfolder and select Create Archive...
3. Press Create.
Normally, this correctly creates an archive containing the folder and
all its files and
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16895815/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/16895816/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/16895817/ProcStatus.txt
--
Create
76 matches
Mail list logo
