I can't reproduce it again since I don't have the splitter any more.
Sorry.
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
It's for this reason I'd like to keep the bug open and provide any maintainer
with more information about the request.
Agreed. It's not because I can't reproduce it any more that the bug is
invalid.
--
Unable to force screen resolution with vtswitch/splitter
happening to me too, karmic up-to-date. Getting from all sources
(multiverse).
--
rhythmbox is consuming a lot of CPU resources
https://bugs.launchpad.net/bugs/451171
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gstreamer0.10 in
I think a simple conversion from \\foo\bar to smb://foo/bar before
opening would suffice, although handling them internally would be
better.
--
UNC file share notation should also be usable, not just URIs
https://bugs.launchpad.net/bugs/119747
You received this bug notification because you are a
Public bug reported:
Binary package hint: seahorse-plugins
Upgraded to Koala yesterday, but this is not my first login to the
system since.
Today, I've just started the computer and there was a crash report on
the panel. Apart from that, everything is more than fine.
ProblemType: Crash
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/34318083/Dependencies.txt
** Attachment added: Disassembly.txt
http://launchpadlibrarian.net/34318084/Disassembly.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/34318085/ProcMaps.txt
** Attachment
Fixed here too, thanks! My new upgrades were not affected too. All fine.
--
seahorse-agent assert failure: ERROR:iop-profiles.c:606:IOP_generate_profiles:
assertion failed: (obj (obj-profile_list == NULL) obj-orb)
https://bugs.launchpad.net/bugs/429322
You received this bug notification
2009/11/4 Chris Coulson chrisccoul...@googlemail.com:
This bug is still present and nobody has fixed it. Your comments are
misleading. Like I said, users aren't seeing crash reports any more
because Apport is disabled, but the bug is still there.
You have hundreds of similar reports and the