Public bug reported:
Affects: gnome-screensaver (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
When running two sessions (with gdmflexiserver, for example), gnome-
screensaver will start a non-blank screen screensaver on the session not
bei
** Bug watch added: GNOME Bug Tracker #339330
http://bugzilla.gnome.org/show_bug.cgi?id=339330
** Also affects: gnome-screensaver (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=339330
Severity: Unknown
Priority: Unknown
Status: Unknown
--
Screensaver starts when
This menu item no longer actually exists, so this can probably be
closed.
--
System/Lock Screen doesn't work with xscreensaver.
https://launchpad.net/bugs/39964
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
rejecting - this is a hal bug. oops.
** Also affects: hal (Ubuntu)
Importance: Untriaged
Status: Unconfirmed
** Summary changed:
- NetworkManager detects wireless interface as wired interface after coming out
of suspend.
+ HAL changes wireless interface (net.80211) to wired (net.80203
I'm attaching a log of hald's verbose output when this happens, but it
doesn't appear to have any obviously useful information on the problem.
Search for "event is 'button/sleep" to get to what I believe is the
relevant portion.
--
HAL changes wireless interface (net.80211) to wired (net.80203)
This is a rather obscure bug, but more info is not needed. I've
confirmed it with nautilus on edgy.
This is entirely in nautilus. To reproduce it, do the following:
1) Remove ~/.thumbnails
2) Create a directory with one thumbnailable file in it, that has a space in
the name.
3) Go to that directo
This occurs with my test, on edgy as well.
** Changed in: nautilus (Ubuntu)
Status: Needs Info => Confirmed
--
Nautilus duplicates thumbnails for files with special characters when searching
https://launchpad.net/bugs/55814
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
http
Public bug reported:
The IMAP4rev1 option for receiving mail is broken, unsupported,
unnecessary, outdated and confusing. Evolution developers seem to agree
at http://bugzilla.gnome.org/show_bug.cgi?id=324118 that it should never
have been included in a stable release. We really shouldn't have it
Just to clarify here, I'm listing this as a bug because I believe this
is something that could be done without significant discussion. We could
just patch evolution to remove the IMAP4rev1 option when creating new
accounts, without causing the compatibility issues entailed with
removing the code en
I can't confirm this in a mostly clean 6.06.1 installation. Evolution
does appear to be using the gconf setting instead of x-www-browser or
$BROWSER, so I can't see where the problem would be unless the gconf key
is set incorrectly.
--
evolution ignoring preferred browser setting
https://launchpa
Hmm... that seems reasonable, but we also don't seem to say that this
option shouldn't be used. In fact, the help file for Evolution says the
exact same thing for IMAP and IMAP4rev1. Is there some documentation
that I am missing that says this, and if so, why is it so obscure?
--
IMAP4rev1 should
I think the problem here could be solved if gaim were to improve IRC support.
As it is now, gaim performs very poorly in large chatrooms, which is precisely
the type of chatroom that Live Support will be using. There is a significant
lag, it seems to use more resources, and there is no highligh
Public bug reported:
Affects: gnome-session (Ubuntu)
Severity: Minor
Priority: Low
Assignee: shane arsenault
Status: Needs Info
Description:
System/Lock Screen no longer causes xscreensaver to lock the screen.
This is probably related to the use of gnome-screensaver b
This is using System > Lock Screen. It was reported when I was running a
relatively clean Flight 6, but with xscreensaver instead of gnome-
screensaver. I will test this on a recently updated system this weekend.
--
System/Lock Screen doesn't work with xscreensaver.
https://launchpad.net/bugs/399
A patch to simply stop the automatic timezone selection would be quite
easy. I can do this if it is needed.
Alternatively, I can improve my original patch to allow for timezones to
be specified for entire countries/states. This would probably also be
rather easy, though it would require that someo
The obvious way to fix this would be to add a entry to each
city in Locations.xml. Unfortunately, that would be a very tedious task.
It may be better to add timezone information to locations where the
distance code gives the incorrect result, and use the distance code as a
default.
--
Clock app
** Attachment added: "Patch for libgweather"
http://launchpadlibrarian.net/12714304/libgweather-tzfix.diff
--
Clock applet chooses wrong timezone for many cities (eg Pittsburgh, Beijing)
https://bugs.launchpad.net/bugs/185190
You received this bug notification because you are a member of Ubun
These two patches (for gnome-panel and libgweather trunks) may or may
not lay the groundwork for solving this problem. As I proposed in my
recent comment, the code allows for tags in Locations.xml;
I've added an example for San Diego.
Unfortunately, I can't figure out how to test this, due to the
Of course, it is almost impossible to write code that works perfectly
without any testing. The patches here should now work.
I'm not happy with this solution, however. It seems as though it
requires a huge amount of work in updating Locations.xml, in a rather
unfortunate way. It could certainly be
I agree that the solution is rather wanting, and believe that the
timezone-guessing code is something that does not belong in any release.
The idea of it not selecting a timezone at all is interesting: it would
be very easy to do - I can make the patch if necessary - and wouldn't
require any extra
It seems that the backup-writing code has been rewritten (to begin with,
it's now in gedit-local-...). This error no longer occurs in hardy, with
2.22, and was probably fixed in even earlier versions.
** Changed in: gedit (Ubuntu)
Status: Triaged => Fix Released
--
gedit error "Could not
I'm confirming this after reproducing it with a clean loop mounted image
- vim works without an error, but gedit gives this error.
** Changed in: gedit (Ubuntu)
Status: Unconfirmed => Confirmed
--
gedit error "Could not create a backup file" when trying to save a file in a
VFAT partition
** Bug watch added: GNOME Bug Tracker #343559
http://bugzilla.gnome.org/show_bug.cgi?id=343559
** Also affects: gedit (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=343559
Importance: Unknown
Status: Unknown
--
gedit error "Could not create a backup file" when trying to
I've figured out the problem, and added a description of it to the
upstream bug. For now, you can get around the issue by mounting with the
option umask=(YOUR_USER_NUMBER) instead of umask=000 (probably
umask=1000).
--
gedit error "Could not create a backup file" when trying to save a file in a
My apologies - I meant uid, not umask.
Ari wrote:
> Hi Constantine, first thanks a lot for your quick response!
>
> On umask: It doesn't look like that option will accept a user number...
> it seems to be a permission mask for filesystems that don't support
> builtin unix permissions
>
>
> umask:
Thank you for your comments. I believe that you do make good points, but
bug reports are not the proper venue for discussing such changes. Your
ideas would be better received as a specification
(https://features.launchpad.net/distros/ubuntu/+specs, and
https://wiki.ubuntu.com/FeatureSpecifications)
Thanks for your comment. The changes you are requesting require more
discussion and should rather be done on an appropriate mailing list or
forum.
http://www.ubuntu.com/community/forums/ might be a good start.
** Changed in: gedit (Ubuntu)
Status: Unconfirmed => Rejected
--
Using F5 as H
*** This bug is a duplicate of bug 59981 ***
Rejecting hal part as well.
** Changed in: hal (Ubuntu)
Status: Unconfirmed => Rejected
--
HAL changes wireless interface (net.80211) to wired (net.80203) in
info.category after suspend
https://launchpad.net/bugs/55809
--
desktop-bugs maili
Public bug reported:
Baobab displays directory content sizes in binary prefix based units,
but uses SI prefixes. We need to either display sizes with the correct
units (KiB, MiB, etc), or have the calculation scheme changed so that
the numbers are in SI units. I will report this upstream and write
** Bug watch added: GNOME Bug Tracker #382093
http://bugzilla.gnome.org/show_bug.cgi?id=382093
** Also affects: gnome-utils (upstream) via
http://bugzilla.gnome.org/show_bug.cgi?id=382093
Importance: Unknown
Status: Unknown
--
Baobab uses incorrect units
https://launchpad.net/bug
Public bug reported:
Binary package hint: abiword
Akin to bug #44672 in Evince, Abiword also ignores the system's and
user's DPI settings (Xft.dpi and xorg.conf) for purposes of zooming.
This was also discussed in bug #62347 in abiword, but was beyond the
scope of that bug.
It appears that Abiwo
.
** Changed in: abiword (Ubuntu)
Assignee: (unassigned) => Constantine Evans
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desk
** Changed in: abiword (Ubuntu)
Status: Unconfirmed => In Progress
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
en an instance of GR_UnixGraphics is created (destroyed),
instead of being done in the function as it is now, which causes a
significant performance problem.
** Changed in: abiword (Ubuntu)
Assignee: Constantine Evans => (unassigned)
Status: In Progress => Confirmed
--
Abiword
A fix for this was committed upstream.
** Changed in: abiword (Ubuntu)
Status: Confirmed => Fix Committed
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.
Messed up subtle aspects of this, due on distinction of upstream/package
status.
** Changed in: abiword (Ubuntu)
Status: Fix Committed => Confirmed
--
Abiword ignores DPI setting for zooming, assumes 72 dpi (1440 dpi / 20)
https://launchpad.net/bugs/76396
--
desktop-bugs mailing list
de
36 matches
Mail list logo
