For the record, this just happened to me on a *fresh* install of Ubuntu
18.04.
The first thing I did after system installed months ago was to install
Unity from repositories (and set lightdm as the default greeter). Unity
may not be the default anymore in 18.04 but it runs and looks great.
Today
For the record, this just happened to me on a *fresh* install of Ubuntu
18.04.
The first thing I did after system installed months ago was to install
Unity from repositories (and set lightdm as the default greeter). Unity
may not be the default anymore in 18.04 but it runs and looks great.
Today
This is not a bug, as the standard specification linked in the
description clearly defines what defaults values should be used if the
environment vars are empty or not set. So there is no need to set the
values unless you want to change the default ones, and it would be
redundant to set them to
@Tom #7: gnome-open was deprecated a long time ago, xdg-open now uses
gvfs-open. Upstream bug report is
https://bugzilla.gnome.org/show_bug.cgi?id=343896
** Bug watch added: GNOME Bug Tracker #343896
https://bugzilla.gnome.org/show_bug.cgi?id=343896
** Package changed: xdg-utils (Ubuntu) =
Shouldn't this import be the other way around? AFAIK, Gnome 3 uses
/usr/share/thumbnailers/*.thumbnailer files to implement external
handlers, NOT gsettings. The gconf2 was the Gnome 2 (ie, Natty and
before) way of registering external thumbnailers.
--
You received this bug notification because
@Thibault: xdg-open, for sure, and for 2 main reasons:
- xdg-open is more portable: it chooses the most appropriate open
command for your system, be it Gnome, KDE, LXDE, XFCE, etc, while gnome-
open works only in gnome. In fact, in Gnome systems xdg-open used to end
up calling gnome-open. So let
** This bug is no longer a duplicate of bug 367037
Error while burning - some files may be corrupted on the disc
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in Ubuntu.
https://bugs.launchpad.net/bugs/385540
Title:
My 2 cents for this issue:
- It also happens with tmpfs mounts. I have tmpfs /tmp tmpfs
defaults,nodev,nosuid,mode=1777 0 0 in my /etc/fstab and nautilus
also trash files there just fine (creating and moving to
/tmp/.Trash-1000), but fails to add that particular trash to the
global list of
@Sebastien: IMHO disabling trash for those mounts (and also for *all*
devices outside $HOME and /media) is overkill. Ok, it is better than
current behavior, but the best approach would be to support those
(already created and populated) per-device trashcans and list them when
the user clicks on
How viable is for Ubuntu to create a package available in Software
Center that patches gnome's GUI and/or polkit (whatever is required) to
re-enable hibernation?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in
I have this bug too (on Maverick)
My 2 cents:
- gedit clears the primary *only* if the selection was made on gedit itself!
(yes, this seems absurd, i know)
Steps to reproduce:
- Select something in Firefox (double or triple click this very line). Alt+Tab
to gedit. Middle-click. Pastes fine
-
Florian Sievers (#31) is right: in a clean Maverick install, 'cat
/proc/sys/kernel/sysrq' (or 'sudo sysctl -a | grep kernel.sysrq') shows
kernel.sysrq=0 , but in fact sysrq's are enabled (and eating up
Alt+PrtScn). If i set it as 'sudo sysctl -w kernel.sysrq=0', supposedly
it wouldn't change
@lopthopman (#26):
I just said that you are experiencing a different issue than what is
reported here. This bug here is for false alarms, when copy is OK but
Brasero calculares checksum incorrectly and thus reports burning errors.
If you are actually getting coasters, this should be reported in
Any chance this can be cherry-picked to maverick backports or updates?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/816804
Title:
gvfs-open exit code is 0 when file is not found
@Aleck: this is NOT the same bug. That bug happened when nautilus
migrated from GnomeVFS to gvfs/GIO. And this one is about something
else:
@Nikolaus: this happened because gnome migrated (again) the settings for
opening URIs (http:// , ftp:// , magnet:, mailto:, etc). Back in
Maverick, gnome
** Patch added: Patch gvfs-open so exit code = 1 when it fails to open any
file
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/816804/+attachment/2237738/+files/0001-gvfs-open-655470.patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Question: if this patch gets approved and merged upstream, what should i
do to make it cherry-picked all the way to Maverick ?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/816804
Updated patch, with cosmetic changes (spacing, line breaks, commit
message)
** Patch added: Patch gvfs-open so exit code = 1 when it fails to open any
file
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/816804/+attachment/2237872/+files/0001-gvfs-open-655470.patch
--
You received this
** Patch removed: Patch gvfs-open so exit code = 1 when it fails to open any
file
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/816804/+attachment/2237738/+files/0001-gvfs-open-655470.patch
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Public bug reported:
gvfs-open exits with error code 0 (success) even when there is error.
The following conditions should exit with error code 0:
- File is not found
- File is found, but default application for opening it is not registred
Examples:
$ gvfs-open nofile.txt || echo NOT FOUND!
** Bug watch added: GNOME Bug Tracker #655470
https://bugzilla.gnome.org/show_bug.cgi?id=655470
** Also affects: gvfs via
https://bugzilla.gnome.org/show_bug.cgi?id=655470
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
@lopthman: this bug is about a false alarm, not actual burning problem.
Also, for developers, my comment on a duplicate bug may help find the answer:
https://bugs.launchpad.net/ubuntu/+source/brasero/+bug/385540/comments/2
--
You received this bug notification because you are a member of Ubuntu
Very annoying bug, and its there for at least 9.04
One could still purge the files by manually deleting the contents or
/root/.local/share/.Trash
But restoring the files requires one to manually read the
info/xxx.trashinfo contents to know the original location of the trashed
file. Why cant the
8 months since bug was confirmed. Any news on it?
By the way, where ccan i find the rationale / specification on this
expunged folder? Is it for big files, other-users files, both, none,
something else?
Last but not least: shouldnt these files be deleted on reboot?
--
You received this bug
It is still present on 10.10 Maverick. If upstream was fixed almost 1
year ago, shouldnt Update Manager have already download the fix /
updated package?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in ubuntu.
Public bug reported:
Binary package hint: brasero
After burning a CD from an ISO file, Brasero reports an error saying
checksum from ISO file and burned CD do not match. (Some files may be
corrupted on the disc).
However, CD is fine and all files were burned correctly. I did a manual
** Attachment added: brasero-session.log
http://launchpadlibrarian.net/27726485/brasero-session.log
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/27726486/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/27726487/ProcMaps.txt
**
After studying the log and doing some tests, i think ive spotted the
error: Brasero is passing the wrong number of sectors to the readom
command (that looks like its the one brasero uses to read the burned cd
to calculate the checksum).
These log lines should says it all (some lines were omitted
** Branch linked: lp:~ubuntu-desktop/brasero/ubuntu
--
Brasero calculates wrong checksum after burn ISO to CD
https://bugs.launchpad.net/bugs/385540
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
desktop-bugs
** Branch unlinked: lp:~ubuntu-desktop/brasero/ubuntu
--
Brasero calculates wrong checksum after burn ISO to CD
https://bugs.launchpad.net/bugs/385540
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to brasero in ubuntu.
--
desktop-bugs
*** This bug is a duplicate of bug 205362 ***
https://bugs.launchpad.net/bugs/205362
** This bug has been marked a duplicate of bug 205362
system monitor update interval is not in seconds
--
system monitor crazy speed update
https://bugs.launchpad.net/bugs/371065
You received this bug
Some hints that might help debugging:
The FIRST and SECOND refreshes happens at the correct interval. Steps to
reproduce:
- Open up System Monitor and switch to Resource tab
- Set the interval to 10,00 (using the buttons, not keyboard - theres another
bug associated with keyboard input)
- Click
Question: as this problem was already forwarded / upstreamed, should i
double-post my comments at bugzilla too ? Im not sure how the process
works...
I dont have a bugzilla account, and even if i had, im not sure if
double-posting would be the correct procedure... but i also dont like to
post
Last but not least, this bug seems to be closely related to #93847 and
its various duplicates...
https://bugs.launchpad.net/ubuntu/+source/gnome-system-
monitor/+bug/93847
Excessive CPU usage by Gnome System Monitor
In fact, all those bugs may be just a symptom of this one: a refresh 10
times
*** This bug is a duplicate of bug 205362 ***
https://bugs.launchpad.net/bugs/205362
** This bug is no longer a duplicate of bug 93847
Excessive CPU usage by Gnome System Monitor
** This bug has been marked a duplicate of bug 205362
system monitor update interval is not in seconds
--
*** This bug is a duplicate of bug 205362 ***
https://bugs.launchpad.net/bugs/205362
** This bug is no longer a duplicate of bug 93847
Excessive CPU usage by Gnome System Monitor
** This bug has been marked a duplicate of bug 205362
system monitor update interval is not in seconds
--
*** This bug is a duplicate of bug 205362 ***
https://bugs.launchpad.net/bugs/205362
** This bug has been marked a duplicate of bug 205362
system monitor update interval is not in seconds
--
Excessive CPU usage by Gnome System Monitor
https://bugs.launchpad.net/bugs/93847
You received
37 matches
Mail list logo
