Public bug reported:
Affects: gnome-pilot (Ubuntu)
Severity: Normal
Priority: (none set)
Status: Unconfirmed
Description:
Syncing more-or-less worked in the previous version of gnome-pilot, but
broke completely with dist-upgrade I did around April 12 (gnome-pilot
2.0.13-0u
*** This bug is a duplicate of bug 33285 ***
I confirmed that mounting usbfs on /proc/bus/usb fixes the problem, so this is
a duplicate of 33285.
** This bug has been marked a duplicate of bug 33285
Can´t sync Evolution with T5
--
[dapper] gpilotd does not recognize USB sync attempt (regress
** Bug 39587 has been marked a duplicate of this bug
--
Can´t sync Evolution with T5
https://launchpad.net/malone/bugs/33285
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
For me, the screen blanks, then the monitor goes into low-power mode
when it's supposed to. But then, at some point later (I haven't
pinpointed exactly when), the monitor comes out of powersave mode, and
stays on. The screen stays blanked, but the monitor is on full-power
mode.
--
You received
** Also affects: nautilus (Ubuntu)
Importance: Undecided
Status: New
--
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/1045899
Title:
Maximum number of clients reached
To
Another clue may be that this is a laptop, and I only see the problem
when I'm docked with an external monitor setup (so I have two screens).
I never see this problem without the external/dual screen. I have a
desktop machine with only a single screen, but identical software setup,
which stays up
Sorry it took so long, but I can confirm that the problem is gone with
the new gnome-settings-daemon package. Thanks Sebastien!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.ne
This bug seems to have regressed back into gnome-settings-daemon
3.3.5-0ubuntu3 in Precise. I now see a duplicate gnome battery applet
icon in addition to the indicator one.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settin
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/833397
Title:
indicator power displayed twice on panel
To manage notifications about this bug g
Public bug reported:
Bug #833397, fixed in Oneiric, seems to be back in version
3.3.5-0ubuntu3. I now see both the gnome power status applet icon and
the indicator one (although only the indicator icon is functional).
** Affects: gnome-settings-daemon (Ubuntu)
Importance: Undecided
I'm not sure what the appropriate way to report a regression is, but I
created a new bug, and provided this bug number in it:
https://bugs.launchpad.net/bugs/934582
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon
Same here, unity session, always happens. Note that as in the previous
bug report, this happens when the dconf "/desktop/unity/panel/systray-
whitelist" key is set to "all" (which is really the only sane value for
it, given that lots of software only supports the gnome systray, and
does not suppor
Heh, I'm also seeing the duplicate nm-applet icons now as well. Both
nm-applet icons are functional as well, which is a bit different than
the power/battery icons.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon
> btw you guys should really drop the 'all' whitelist, that's what is
creating those bugs for you...
Sebastien, are you joking or trolling? You aren't seriously suggesting
that we should simply stop using any software that doesn't support the
indicator system, simply because the Ubuntu switch to
I agree with Chris that a proper fix ought to be committed, rather than
just another workaround. If nobody cares about the "show_desktop"
option enough to fix it, maybe it should just be disabled (i.e. remove
the gconf key, and just always show the desktop). Personally, losing
this option would a
@Sebastien: Ooh, excellent idea. Here's my story ;)
I don't want nautilus to draw the desktop because it doesn't give me a
useful desktop context menu, or even any way to create a useful desktop
context menu. And if it's drawing the desktop, it won't allow any other
software to give me a desktop
I'll also confirm this same bug with a Tungsten T5. Adding a due date
to all todos sucks, but seems to work around the problem.
Sadly, I'm guessing this won't get fixed in time for the feisty release
:o(
--
[feisty] etodo conduit times out when syncing with a palm device
https://bugs.launchpad.
Public bug reported:
Binary package hint: nautilus
Latest Gutsy update as of today. When I log in, Nautilus will either
eat up 100% of CPU, or it will segfault. I can subsequently run
Nautilus via the "Places" menu, and browse around w/out problem.
Possibly relevant out-of-ordinary details: I
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/9850414/CoreDump.gz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/9850415/Dependencies.txt
** Attachment added: "Disassembly.txt"
http://launchpadlibrarian.net/9850416/Disassembly.txt
** Attachment
Public bug reported:
Binary package hint: gnome-keyring
gnome-keyring-daemon is running before suspend, but is no longer running
upon resume. Doesn't survive suspend to disk or ram.
** Affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
--
gnome-keyring-daemon does
Well, the keyring stores all kinds of useful information, like WPA/WEP
keys, ssh key passphrases, etc.. The way I first noticed that the
daemon wasn't running is that Network Manager couldn't just resume my
wireless connection, but would always ask for the WAP's WPA passphrase
(since it couldn't g
Hmm. I don't even know how nautilus is being run on login, much less
how to start it up under valgrind. AFAICT, I don't see any reason that
nautilus should even be trying to start up. It's not in my session
script, I'm not using it to manage my desktop, etc...
Anyway, I'd be happy to try runnin
Unfortunately, no. I've never been able to get it to crash, nor consume
100% CPU when running it from a command line after login. I've only
ever seen it happen when logging in (and since it's not in my session, I
can't even figure out why it's running).
--
nautilus crashed on login with SIGSEGV
Umm. Nevermind.
Turns out PIBKAC...
A while back, I changed /etc/defaults/acpi-support to restart dbus on
resume, 'cause that was the only way I could get network-manager to
resume itself. That was killing gnome-keyring-daemon as well as gnome-
power-manager :o(
Sorry for the false alarm. My
I can confirm that my T5 syncs reliably on edgy.
--
Can´t sync Evolution with T5
https://launchpad.net/bugs/33285
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
25 matches
Mail list logo
