[Bug 1753460] [NEW] package gnome-session-bin 3.27.91-0ubuntu1 failed to install/upgrade: Unterprozess installed gnome-session-bin package post-installation script gab den Fehler-Ausgangsstatus 2 zurü
Public bug reported: By dist-upgrade: sudo apt update && sudo apt dist-upgrade OK:1 http://archive.canonical.com/ubuntu bionic InRelease Holen:2 http://archive.ubuntu.com/ubuntu bionic InRelease [235 kB] OK:3 http://archive.ubuntu.com/ubuntu bionic-updates InRelease OK:4 http://archive.ubuntu.com/ubuntu bionic-backports InRelease OK:5 http://archive.ubuntu.com/ubuntu bionic-security InRelease Holen:6 http://archive.ubuntu.com/ubuntu bionic-proposed InRelease [235 kB] Holen:7 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8.531 kB] Holen:8 http://archive.ubuntu.com/ubuntu bionic/universe i386 Packages [8.495 kB] Holen:9 http://archive.ubuntu.com/ubuntu bionic-proposed/universe amd64 Packages [286 kB] Holen:10 http://archive.ubuntu.com/ubuntu bionic-proposed/universe i386 Packages [314 kB] Holen:11 http://archive.ubuntu.com/ubuntu bionic-proposed/universe Translation-en [154 kB] Es wurden 18,3 MB in 14 s geholt (1.292 kB/s). Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Alle Pakete sind aktuell. Paketlisten werden gelesen... Fertig Abhängigkeitsbaum wird aufgebaut. Statusinformationen werden eingelesen Fertig Paketaktualisierung (Upgrade) wird berechnet... Fertig Die folgenden Pakete wurden automatisch installiert und werden nicht mehr benötigt: gir1.2-mutter-1 gnome-characters gnome-logs gnome-tweak-tool libmutter-1-0 Verwenden Sie »sudo apt autoremove«, um sie zu entfernen. 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert. 6 nicht vollständig installiert oder entfernt. Nach dieser Operation werden 0 B Plattenplatz zusätzlich benutzt. Möchten Sie fortfahren? [J/n] j gnome-session-bin (3.27.91-0ubuntu1) wird eingerichtet ... update-alternatives: Fehler: Alternativen-Pfad /usr/bin/gnome-session existiert nicht dpkg: Fehler beim Bearbeiten des Paketes gnome-session-bin (--configure): Unterprozess installed gnome-session-bin package post-installation script gab den Fehler-Ausgangsstatus 2 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von gnome-session: gnome-session hängt ab von gnome-session-bin (>= 3.27.91-0ubuntu1); aber: Paket gnome-session-bin ist noch nicht konfiguriert. gnome-session hängt ab von gnome-session-bin (<< 3.28); aber: Paket gnome-session-bin ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes gnome-session (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von gnome-shell-extensions: gnome-shell-extensions hängt ab von gnome-session-bin (>= 3.8); aber: Paket gnome-session-bin ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes gnome-shell-extensions (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ubuntu-session: ubuntu-session hängt ab von gnome-session-bin (>= 3.27.91-0ubuntu1); aber: Paket gnome-session-bin ist noEs wurde kein Apport-Bericht verfasst, da die Fehlermeldung darauf hindeutet, dass dies lediglich ein Folgefehler eines vorherigen Problems ist. Es wurde kein Apport-Bericht verfasst, da die Fehlermeldung darauf hindeutet, dass dies lediglich ein Folgefehler eines vorherigen Problems ist. Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits erreicht ist. Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits erreicht ist. Es wurde kein Apport-Bericht verfasst, da das Limit MaxReports bereits erreicht ist. ch nicht konfiguriert. ubuntu-session hängt ab von gnome-session-bin (<< 3.28); aber: Paket gnome-session-bin ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ubuntu-session (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von gnome-session-wayland: gnome-session-wayland hängt ab von gnome-session (>= 3.22.1); aber: Paket gnome-session ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes gnome-session-wayland (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert dpkg: Abhängigkeitsprobleme verhindern Konfiguration von ubuntu-desktop: ubuntu-desktop hängt ab von ubuntu-session; aber: Paket ubuntu-session ist noch nicht konfiguriert. dpkg: Fehler beim Bearbeiten des Paketes ubuntu-desktop (--configure): Abhängigkeitsprobleme - verbleibt unkonfiguriert Fehler traten auf beim Bearbeiten von: gnome-session-bin gnome-session gnome-shell-extensions ubuntu-session gnome-session-wayland ubuntu-desktop E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gnome-session-bin 3.27.91-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux
Re: [Bug 1750558] Re: gnome-software crashed with SIGSEGV in __strlen_avx2()
Am 20.02.2018 um 14:41 schrieb Jean-Baptiste Lallement: > Thanks for your report. > > Are you able to reproduce this crash and could you provide the steps to > do it? > > Thanks. > > ** Changed in: gnome-software (Ubuntu) > Status: New => Incomplete > I think the crash are in the Future by the Displaymanger. ( lightdm i have the best Experience, gdm2 no way to choice another Displaysystem ). 1. Displaymanger 2. choice Ubuntu or gnome Wayland no way to end or work with. ( Mouse no function but move ) 3. change to tty2 and reboot. 4. start new and choise no wayland and the bug Report came. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1750558 Title: gnome-software crashed with SIGSEGV in __strlen_avx2() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750558/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1748450] Re: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from
gdm3 no mouse function but move. gnome Displaysystems not boot and then boot no mouse function but move. lightdm goes into Automatic login. why? Have changed this manually. gdm3 is Ubuntu adjusted, why. But no mouse function to change this, no click possible. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1748450 Title: gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748450/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1714330] Re: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent()
Am 15.09.2017 um 18:08 schrieb Nicolás Abel Carbone: > Is there a missing piece in the bug It's a missing piece. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1714330 Title: gnome-shell crashed with SIGSEGV in on_crtc_flipped() from g_closure_invoke() from invoke_flip_closure() from page_flip_handler() from drmHandleEvent() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1714330/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1707406] Re: nautilus-desktop crashed with SIGSEGV in g_type_check_instance_cast()
*** This bug is a duplicate of bug 1707369 *** https://bugs.launchpad.net/bugs/1707369 The bug is not existens in new Update. Ubuntu 17.10 31.07.2017. Thank you. -- 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/1707406 Title: nautilus-desktop crashed with SIGSEGV in g_type_check_instance_cast() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1707406/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12040] Re: GNOME Main Menu panel applet slow to open on first click (NOT compiz related)
@BavarianPH: it seems that there are people in the project who interpret any negative statement about Ubuntu, or any positive statement against one of its 'avowed enemies' as 'heresy' and use that to 'punish' the 'heretic' who dared to utter it. This happens in the forums - which I no longer use since the forum moderators are part of the problem - and seems to happen here as well. This is counterproductive and sad. Free software in general, and Ubuntu in particular should be approached with an open mind. If something does not work as it should it needs to be changed. If some other program - whether it be open or proprietarty, free or fee does not matter - does it better it should be possible to state this without being accused of heresy, punished by forum gods or demoted by some arbitrary measure. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. https://bugs.launchpad.net/bugs/12040 Title: GNOME Main Menu panel applet slow to open on first click (NOT compiz related) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 690244] [NEW] All gtk2.0 apps crash in gtkicontheme due to use of uninitialized parameter 'theme_name'
Public bug reported:
Running up to date natty (11.04, last update Tue Dec 14 17:30)
All gtk2.0 and many Qt apps crash in gtkicontheme due to an
uninitialized parameter (theme_name). This currently makes it impossible
to log in through X since the gdm greeter also crashes. When logging in
using startx and a non-gtk based session - a plain xterm or a non-gtk
dependent window manager like Xmonad - any application which directly or
indirectly uses the gtk theme engine crashes. This includes Qt apps
which use the gtk theme engine.
A sample trace looks like this, created using gcalctool but it could
have been made using any application which uses gtk or the gtk theme
engine:
---8
fr...@ostrogoth:~$ gdb gcalctool
GNU gdb (GDB) 7.2-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as i686-linux-gnu.
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /usr/bin/gcalctool...(no debugging symbols found)...done.
(gdb) r
Starting program: /usr/bin/gcalctool
[Thread debugging using libthread_db enabled]
[New Thread 0xb6ef6b70 (LWP 5351)]
(process:5347): Gtk-CRITICAL **: set_table: assertion `buffer-tag_table
== NULL' failed
Program received signal SIGSEGV, Segmentation fault.
__strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:39
39 ../sysdeps/i386/i686/multiarch/../strcmp.S: No such file or directory.
in ../sysdeps/i386/i686/multiarch/../strcmp.S
(gdb) thread apply all bt full
Thread 2 (Thread 0xb6ef6b70 (LWP 5351)):
#0 0xb7fe1416 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb7671df6 in __poll (fds=0xb7709ff4, nfds=3, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:87
resultvar = value optimized out
oldtype = 0
result = value optimized out
#2 0xb777a88b in g_poll () from /lib/libglib-2.0.so.0
No symbol table info available.
#3 0xb776a21f in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#4 0xb776a9a3 in g_main_loop_run () from /lib/libglib-2.0.so.0
No symbol table info available.
#5 0xb7967dc4 in ?? () from /usr/lib/libgio-2.0.so.0
No symbol table info available.
#6 0xb779339f in ?? () from /lib/libglib-2.0.so.0
No symbol table info available.
#7 0xb7713cc9 in start_thread (arg=0xb6ef6b70) at pthread_create.c:304
__res = value optimized out
__ignore1 = value optimized out
__ignore2 = value optimized out
pd = 0xb6ef6b70
now = value optimized out
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {-1217245196, 0, 4001536,
-1225825480, 1954574631, 1212015396}, mask_was_saved = 0}},
---Type return to continue, or q return to quit---
priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup =
0x0,
canceltype = 0}}}
not_first_call = value optimized out
robust = value optimized out
freesize = value optimized out
__PRETTY_FUNCTION__ = start_thread
#8 0xb76806be in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
No locals.
Thread 1 (Thread 0xb7130820 (LWP 5347)):
#0 __strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:39
No locals.
#1 0xb7b7ec50 in get_directory_index (directory=0x810e280 8x8/emblems,
cache=value optimized out)
at /build/buildd/gtk+2.0-2.23.2/gtk/gtkiconcache.c:190
name = value optimized out
name_offset = value optimized out
dir_list_offset = value optimized out
n_dirs = 65536
i = value optimized out
#2 0xb7b85c3a in theme_subdir_load (icon_theme=0x80bc848,
theme_name=0x810e138
\260\242\020\bpF\017\b\210F\017\b\310\350\020\b\330\350\020\b\360\350\020\b\b\351\020\b
\351\020\b8\351\020\bP\351\020\bh\351\020\b)
at /build/buildd/gtk+2.0-2.23.2/gtk/gtkicontheme.c:2575
d = 0x80f3f60
type_string = value optimized out
context_string = value optimized out
---Type return to continue, or q return to quit---
size = 8
min_size = 8
max_size = 8
threshold = 2
dir_mtime = value optimized out
type = ICON_THEME_DIR_FIXED
full_dir = 0x810e358 /usr/share/icons/gnome/8x8/emblems
dir = 0x810e2d0
context = 938
error = 0x0
#3 insert_theme (icon_theme=0x80bc848,
theme_name=0x810e138
\260\242\020\bpF\017\b\210F\017\b\310\350\020\b\330\350\020\b\360\350\020\b\b\351\020\b
\351\020\b8\351\020\bP\351\020\bh\351\020\b)
at /build/buildd/gtk+2.0-2.23.2/gtk/gtkicontheme.c:992
i = value optimized out
l = value optimized out
dirs = 0x810e138
themes = value optimized out
priv = 0x810a2b0
theme = 0x810cc00
[Bug 690244] Re: All gtk2.0 apps crash in gtkicontheme due to use of uninitialized parameter 'theme_name'
valgrind log ** Attachment added: valgrind.log https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/690244/+attachment/1765871/+files/valgrind.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. https://bugs.launchpad.net/bugs/690244 Title: All gtk2.0 apps crash in gtkicontheme due to use of uninitialized parameter 'theme_name' -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 690244] Re: All gtk2.0 apps crash in gtkicontheme due to use of uninitialized parameter 'theme_name'
Deleting the /usr/share/icons/gnome/icon-theme.cache file brought gtk back to life. I use a theme called 'wild-shine' but tried with many other themes. The gnome icon-theme seems to be used by all of those. As to what caused that cache file to become corrupt is a question I have no answer to. These problems started when it became impossible to log in using gdm - the greeter worked but as soon as the session was started it was killed. Were there recent updates to the cache handling code which could have caused this mishap? If so it might be a good idea to have package updates delete stale cache files. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+2.0 in ubuntu. https://bugs.launchpad.net/bugs/690244 Title: All gtk2.0 apps crash in gtkicontheme due to use of uninitialized parameter 'theme_name' -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 196688] Re: GPM in Hardy seems to have a memory leak
I just got bitten by this bug on Lucid. Currently gnome-power-manager uses ~120 MB resident memory after running for about two weeks: $ ps auxw|grep gnome-power-manager|grep -v grep frank 2735 0.0 16.1 186140 123588 ? SApr03 8:09 gnome-power-manager Most of that memory is used on the heap as can be seen in /proc/[pid]/smaps: 08ea5000-11d9e000 rw-p 00:00 0 [heap] Size: 146404 kB Rss: 116416 kB Pss: 116416 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 82896 kB Private_Dirty: 33520 kB Referenced:47516 kB Swap: 29968 kB KernelPageSize:4 kB MMUPageSize: 4 kB A 146 MB heap seems a bit overdone for a trivial program like gnome-power-manager. This machine has gone through some updates without being rebooted. That should not be a problem - this is not Windows after all - but maybe gnome-power-manager should have been restarted after one of those updates? -- GPM in Hardy seems to have a memory leak https://bugs.launchpad.net/bugs/196688 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 204566] Re: Rhythmbox keeps trying to install codecs
Instead of fiddling with filenames you can just purge the gnome-codec- install package: sudo dpkg -P gnome-codec-install or sudo apt-get autoremove --purge gnome-codec-install -- Rhythmbox keeps trying to install codecs https://bugs.launchpad.net/bugs/204566 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 285682] Re: can't mount digital camera showing a window popup message: -60 could not lock the device message
Do you happen to have a media player like rhythmbox running in the background? Some of those also try to mount MTP devices and will happily mount your camera making it inaccessible to other programs. For rhythmbox the solution is simple: disable the MTP plugin. -- can't mount digital camera showing a window popup message: -60 could not lock the device message https://bugs.launchpad.net/bugs/285682 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 475811] Re: crashes when a filename uses :
There is a notice in Mono's Uri.cs that there is a difference between Mono 1.2 and Mono 2.0 in how scheme name characters are checked: // Check scheme name characters as specified in RFC2396. // Note: different checks in 1.x and 2.0 (mcs/class/System/System/Uri.cs:1380) Maybe that is what triggered this bug? -- crashes when a filename uses : https://bugs.launchpad.net/bugs/475811 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488752] Re: pdftopdf crashes
mode profile=AOLMe Too!/mode Demangled the missing function is GfxColorSpace::parse(Object*, Gfx*) This seems to have been introduced by this patch: http://lists.freedesktop.org/archives/poppler/2009-October/005198.html -- pdftopdf crashes https://bugs.launchpad.net/bugs/488752 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488752] Re: pdftopdf crashes
This is not a bug in poppler. It is a bug in pdftopdf as bundled with cups. Currently cups can not be compiled with the latest libpoppler because the interface to iccColorSpaceCache (in libpoppler) has changed as can be seen in the patch linked to above. -- pdftopdf crashes https://bugs.launchpad.net/bugs/488752 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 488752] Re: pdftopdf crashes
New bug opened in cups: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/489791 -- pdftopdf crashes https://bugs.launchpad.net/bugs/488752 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to poppler in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 475811] Re: crashes when a filename uses :
Sebastien: the easiest way to import a 'buggy' image (?) is to remove the colon from the name... or is that not what you meant? To get f-spot to run as it is (without any patches) I'd suggest changing the name of the picture on the filesystem and in the database. Even though you could %-encode colons in the database this currently does not seem to work well as they get written back as ordinary colons by f-spot. To change the name in the database I'd suggest dumping it, editing the dump and importing it again: sqlite3 .config/f-spot/photos.db .dump photos.dump edit the resulting dump (change the offending colons into periods or underscores or whatnot) change the filenames on the filesystem in a similar way import the database: cat photos.dump|sqlite3 photos.db If sqlite3 does not give any errors and the database has a sane size (slightly smaller than the original photos.db) you can try to start f-spot with it: mv .config/f-spot/photos.db .config/f-spot/photos.db.org mv photos.db config/f-spot/photos.db f-spot --debug If it starts and the offending pictures are visible you're good to go. If it crashes you might have forgotten a colon or two or messed up the database in another way. If the offending pictures are missing you might have forgotten to rename them in the filesystem. -- crashes when a filename uses : https://bugs.launchpad.net/bugs/475811 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 475811] Re: F-spot crashes when i start It.
I notice there is a colon in that filename. Unix has no problems with that but Windows does. Maybe mono does as well? That would be a bug by the way... -- F-spot crashes when i start It. https://bugs.launchpad.net/bugs/475811 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to f-spot in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 475811] Re: F-spot crashes when i start It.
It does seem to be the colon in the filename which causes the crash. I
ran a photos.db through an instrumentd f-spot with the following result:
...
...
AppendValues ( Gtk.TreeIter, 2003%20Kitchen%20Before)
AppendValues ( Gtk.TreeIter, Michigan)
AppendValues ( Gtk.TreeIter, Volume%202)
AppendValues ( Gtk.TreeIter, Volume%203)
AppendValues ( Gtk.TreeIter, 2005-02-12--14:13:46)
[Warn 00:53:34.914] Caught an exception - URI scheme must start with a letter
and must consist of one of alphabet, digits, '+', '-' or '.' character. (in
`System')
Notice that as soon as a name with a colon in it shows up f-spot børks.
A look at mcs/class/System/System/Uri.cs (part of Mono) shows what
happens: as soon as there is a colon in a string and that colon is not
at position 0 (which is always an error) or position 1 (which is
interpreted as following an MS-DOS/Windows drive letter) the part of the
string before the colon is interpreted as an URI scheme (eg http, file,
ftp, etc.). This will naturally lead to an error as (in the above
example) ' 2005-02-12--14' is not a valid scheme.
The solution is for f-spot to %-encode colons in the string before it
gets handled by any of Mono's URI-handling functions. It does this for
spaces (-%20) but not for colons (-%3A). This should be changed...
This are the salient bits from Uri.cs:
pos = uriString.IndexOf (':');
if (pos == 0) {
return Invalid URI: The format of the URI
could not be determined.;
} else if (pos 0) {
// It must be Unix file path or Windows UNC
if (uriString [0] == '/'
Path.DirectorySeparatorChar == '/'){
ParseAsUnixAbsoluteFilePath (uriString);
if (kind == UriKind.Relative)
isAbsoluteUri = false;
} else if (uriString.Length = 2 uriString
[0] == '\\' uriString [1] == '\\')
ParseAsWindowsUNC (uriString);
else {
/* Relative path */
isAbsoluteUri = false;
path = uriString;
}
return null;
} else if (pos == 1) {
if (!IsAlpha (uriString [0]))
return URI scheme must start with a
letter.;
// This means 'a:' == windows full path.
string msg = ParseAsWindowsAbsoluteFilePath
(uriString);
if (msg != null)
return msg;
return null;
}
// scheme
scheme = uriString.Substring (0, pos).ToLower
(CultureInfo.InvariantCulture);
// Check scheme name characters as specified in RFC2396.
// Note: different checks in 1.x and 2.0
if (!CheckSchemeName (scheme))
return Locale.GetText (URI scheme must start
with a letter and must consist of one of alphabet, digits, '+', '-' or '.'
character.);
--
F-spot crashes when i start It.
https://bugs.launchpad.net/bugs/475811
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to f-spot in ubuntu.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12040] Re: GNOME Main Menu panel applet slow to open on first click (NOT compiz related)
As I already stated in #28 this bug has *nothing* to do with compiz, compositors, window managers or anything else of that sort. If turning off compiz changes something you should file another bug for *compiz*. -- GNOME Main Menu panel applet slow to open on first click (NOT compiz related) https://bugs.launchpad.net/bugs/12040 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12040] Re: Gnome menu is slow when clicking for the first time
Yep, the problem is still alive and kicking. Just opened the menu, it took 25 seconds to appear... -- Gnome menu is slow when clicking for the first time https://bugs.launchpad.net/bugs/12040 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 395324] Re: 'These windows do not support save current setup....' metacity warning when logging in with gdm 2.26
This bug also occurs on my T23 (PIII-m - x86) with current Karmic. -- 'These windows do not support save current setup' metacity warning when logging in with gdm 2.26 https://bugs.launchpad.net/bugs/395324 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 347653] Re: should not ship mini-commander files when it's not built
Good to hear, then I'll be able to ditch the 'reinstall_minicommander' script (sudo dpkg -r mini-commander; sudo apt-get -f install; sudo dpkg -i --force-all $minicommander) -- should not ship mini-commander files when it's not built https://bugs.launchpad.net/bugs/347653 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 347653] Re: package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/
Original bug report: https://bugs.launchpad.net/ubuntu/+source/gnome- applets/+bug/34732 Link to patch: http://launchpadlibrarian.net/22037527/20_mini- commander_include_server_file_only_when_built.patch (patch should still apply to current version) -- package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server', which is also in package mini-commander https://bugs.launchpad.net/bugs/347653 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 347653] Re: package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/
Here's a new version of the patch which corrects a problem for those who actually want to build the gnome-applets package WITH mini-commander, instead of using an external mini-commander. The bug was that I used the wrong directory name in the Makefile.in (but not in Makefile.am) ** Attachment added: Only include mini-commander files when the applet is actually built http://launchpadlibrarian.net/24304886/20_mini-commander_include_server_file_only_when_built.patch -- package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server', which is also in package mini-commander https://bugs.launchpad.net/bugs/347653 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 347653] Re: should not ship mini-commander files when it's not built
Sure, I can try to get their attention again... it has been a while... -- should not ship mini-commander files when it's not built https://bugs.launchpad.net/bugs/347653 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 347653] Re: should not ship mini-commander files when it's not built
related Gnome bug: http://bugzilla.gnome.org/show_bug.cgi?id=576613 -- should not ship mini-commander files when it's not built https://bugs.launchpad.net/bugs/347653 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 347653] [NEW] package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/server
Public bug reported: Binary package hint: gnome-applets gnome-applets still, after 3 years, contains the '/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server' file for the long-deprecated mini_commander applet. This makes it impossible to use a stand-alone version of mini_commander without resorting to ugly hacks. As the applet is not in the package the server file has no business being there either. I have submitted a patch to resolve this issue several months ago but did not get any reaction from the package maintainer. Please please please REMOVE that stale server file! Don't make things difficult which should be easy. If upstream insists on installing that file just remove it in debian/rules as is done with so many other unwanted files. I am sure that I am not the only one using mini_commander instead of the overweight, disfunctional and misnamed 'deskbar' replacement. Anyone who 'just' wants a command line applet in the panel is much better served by mini_commander as that a) actually sits in the panel and b) uses much less memory and c) is much faster and d) starts much faster and and and... so why throw up - or refuse to remove - a barrier to those who happen to dislike 'deskbar-applet'? I can resubmit the patch if needed, it is short and sweet and simple and non-invasive. ProblemType: Package Architecture: i386 DistroRelease: Ubuntu 9.04 ErrorMessage: trying to overwrite `/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server', which is also in package mini-commander NonfreeKernelModules: ath_hal Package: gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] PackageArchitecture: all SourcePackage: gnome-applets Title: package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server', which is also in package mini-commander Uname: Linux 2.6.29-rc7-t23-200903142109 i686 ** Affects: gnome-applets (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 -- package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server', which is also in package mini-commander https://bugs.launchpad.net/bugs/347653 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 347653] Re: package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/24294515/Dependencies.txt ** Attachment added: DpkgTerminalLog.gz http://launchpadlibrarian.net/24294516/DpkgTerminalLog.gz -- package gnome-applets-data 2.26.0-0ubuntu1 [modified: usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server] failed to install/upgrade: trying to overwrite `/usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server', which is also in package mini-commander https://bugs.launchpad.net/bugs/347653 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-applets in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 267371] Re: [gvfs] [smb] Damaged OpenOffice files from samba shares
I am seeing file corruption when copying from a Windows NT4 server to an up-to-date version of Jaunty with a 2.6.29-rc2 kernel (but also using the stock Jaunty kernel) using gvfs. The files in question have NOTHING to do with OOo, they are JPEG's from a digital camera. Files are reliably corrupted every time, the corruption also seems to be more or less identical judging by the way the images are mangled. The NT4 server share is mounted over a (vpnc -...- Cisco PIX) VPN which is also used (without problems) to run a VNC session to the Windows server. Copying the same files from the same server using scp works fine so the files themselves are OK. The main difference between the problem described in this bug report and my experience is that I get corruption which is unrelated to OpenOffice.org. This bug does not seem to be confined to OOo... -- [gvfs] [smb] Damaged OpenOffice files from samba shares https://bugs.launchpad.net/bugs/267371 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gvfs in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34732] Re: mini-commander missing in 2.14.0ubuntu1
Now, almost three years after the initial bug report this problem still remains... I made a small patch to get rid of all traces of mini-commander in the gnome-applets package when it is not built. If anyone knows of a valid reason to keep the server file for a non-existent applet around please speak up, otherwise please add this patch to the mix so those who choose not to have their memory eaten by a disfunctional deskbar-applet still can install an external mini-commander without having to --force-all the installation. ** Attachment added: Only include mini-commander files when the applet is actually built http://launchpadlibrarian.net/22037527/20_mini-commander_include_server_file_only_when_built.patch -- mini-commander missing in 2.14.0ubuntu1 https://bugs.launchpad.net/bugs/34732 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12040] Re: Gnome menu is slow when clicking for the first time
The root cause of this bug has nothing to do with Compiz, Metacity or any window- or compositing-manager so bringing those into the mix only serves to muddle the issue. The first time the menu button is clicked Gnome starts searching high and low for menu entries, accompanying icons and such. It is this search which takes time. A possible solution to this problem would be for Gnome to do this search in the background at a low priority (so as not to impede anything the user might want to do once the desktop has appeared) when the system is first started in the hope that it is ready once the user decides to click on the menu button. If said user immediately presses the menu button he'll still have to wait for the thing to load but that can not be helped - yet. As to who will ever implement something akin to what I mentioned, who knows? I don't really use the menu as the hacked version of good old mini_commander (no system-hogging deskbar nonsense for me...) is much faster but maybe I should look into it anyway. -- Gnome menu is slow when clicking for the first time https://bugs.launchpad.net/bugs/12040 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 185311] Re: hardy, locking assertion failure, xorg/libsdl
A good temporary solution to these problems is to copy Bryce's noxcb version of libx11 to a separate directory which you then prepend to LD_LIBRARY_PATH before starting problematic apps. A simple if somewhat hackish way to do that goes like this: # go to your home directory, get the package, create directory # and change ownership to normal user for now... makes it safer # for hamfisted types who might rm -rf /usr accidentally when given the chance... TMPDIR=$(mktemp -d) cd $TMPDIR wget -P $TMPDIR http://people.ubuntu.com/~bryce/Testing/libx11/libx11-6_1.1.3-1ubuntu2~noxcb_i386.deb sudo mkdir -p /opt/LIBx11-noxcb sudo chown $USER /opt/LIBx11-noxcb # this produces a data.tar.gz, control.tar.gz and debian-binary file. # The data.tar.gz contains the interesting bits, the rest is unimportant for this purpose cd /opt/LIBx11-noxcb ar x $TMPDIR/libx11-6_1.1.3-1ubuntu2~noxcb_i386.deb # unpack data.tar.gz, move usr/lib - /opt/LIBx11-noxcb/lib # remove everything else which is not needed tar zxf data.tar.gz mv usr/lib . rm -rf control.tar.gz data.tar.gz debian-binary usr #revert ownership of the directory back to root) cd sudo chown -R root:root /opt/LIBx11-noxcb rm -rf $TMPDIR # that's all folks! (this script is attached to this posting - as always check before you run to assure yourself that there are no nasty surprises hiding in there...) You now have a directory called /opt/LIBx11-noxcb which only contains a lib directory with libX11.so.6.2.0 (and libX11.so.6 symlinked to this file). This directory is outside of package management so it will not be messed up by any updates, nor will installing the library this way mess up your system. If you want to run an app which needs this library you just prepend it to LD_LIBRARY_PATH before running the app. Like so: LD_LIBRARY_PATH=/opt/LIBx11-noxcb/lib:$LD_LIBRARY_PATH name_of_app_to_run If you have to do this very often you might want to create or change a startup script for said app... Once the problems have been solved and xcb no longer gives locking problems you can just rm -rf /opt/LIBx11-noxcb... ** Attachment added: A script to install libx11-noxcb outside of package management's reach http://launchpadlibrarian.net/16474477/install_libx11-noxcb_in_opt.sh -- hardy, locking assertion failure, xorg/libsdl https://bugs.launchpad.net/bugs/185311 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to pygtk in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 27109] Re: nautilus uses 100% cpu after closing a ssh session
On my Gutsyfied (from Feisty to Gutsy beta) Thinkpad T23 Nautilus goes to 100% CPU when the Gnome session is terminated. Best way to see this is to switch user from A to B, terminate user B's session and go back to A. The CPU is pegged with user B's dying Nautilus. Possibly related: I quite often have to shoot down bonobo-activation- server to get Nautilus to start after having logged in and out once without a reboot. Terminating Nautilus (using nautilus -q) also leads to the dying nautilus hogging the CPU, all the while spewing dire '0x8177880 2007/09/30 23:26:54.2265 (USER): debug log dumped due to signal 11' warnings into nautilus-debug-log.txt at a rate of app. 7000 messages per second. After killing the morbid nautilus the CPU gets pegged by tracker which insists on indexing this logfile (easily remedied by deleting the offending log file but still...) -- nautilus uses 100% cpu after closing a ssh session https://bugs.launchpad.net/bugs/27109 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a direct subscriber. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 129029] Re: [Gutsy Tribe-5] No Sound on Login Screen or during Login
Hmmm, strangely enough I sometimes DO get the ready-to-login drumroll sound now. Sometimes, not always. Just like I sometimes have to kill bonobo-activation-server to get Nautilus to run (bug #90923: https://bugs.launchpad.net/ubuntu/+source/libbonobo/+bug/90923). Maybe these two are related? -- [Gutsy Tribe-5] No Sound on Login Screen or during Login https://bugs.launchpad.net/bugs/129029 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 129029] Re: [Gutsy Tribe-5] No Sound on Login Screen or during Login
Same but different here on Gutsy beta (updated from feisty using update- manager -c -d). No sounds during login, no sounds when trying to set them using System-Preferences-Sound-System Sounds (the test button does not produce any sound) but no problems with sounds in applications. Pulseaudio (which I had to manually install by the way...) works OK, applications use it, sound does not skip (had to add myself to the pulse-rt group first...) but no login/logout/ready sounds... -- [Gutsy Tribe-5] No Sound on Login Screen or during Login https://bugs.launchpad.net/bugs/129029 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 91012] Re: [apport] hal-device-manager crashed with ImportError in module() App crashed running Hardware Information
aolme too/aol dist-upgraded from edgy to feisty, first run of hardware information ended in this. -- [apport] hal-device-manager crashed with ImportError in module() App crashed running Hardware Information https://launchpad.net/bugs/91012 -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24383] GTK filechooser takes about 45 seconds to start
Public bug report changed: https://launchpad.net/malone/bugs/24383 Comment: Dapper Drake with whatever Gnome-bits it comes with. Daily update. Machine is a 2 Ghz P4 notebook with 768 MiB RAM and 5400 RPM harddrive. But those bookmarks, yeah... I have (had) some NFS-mounted bookmarks which might well be part of the problem. Removing them does speed up things quite a bit. I'll do some more experimenting. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34732] mini-commander missing in 2.14.0ubuntu1
Public bug report changed: https://launchpad.net/malone/bugs/34732 Comment: Since mini-commander is to be removed from gnome-applets it should also be removed from gnome-applets-data. The latter currently still contains the bonobo server: /usr/lib/bonobo/servers/GNOME_MiniCommanderApplet.server (found this out when I made a stand-alone package for mini-commander. Deskbar is just to heavy for my liking...) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34732] mini-commander missing in 2.14.0ubuntu1
Public bug report changed: https://launchpad.net/malone/bugs/34732 Task: ubuntu gnome-applets Sourcepackagename: gnome-applets = gnome-applets-data -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 34732] mini-commander missing in 2.14.0ubuntu1
Public bug reported: https://launchpad.net/malone/bugs/34732 Affects: gnome-applets (Ubuntu) Severity: Normal Priority: (none set) Status: Unconfirmed Description: The mini-commander applet is missing from gnome- applets_2.14.0-0ubuntu1_i386.deb (no idea about other architectures). The missing file is: /usr/lib/gnome-applets/mini_commander_applet (the man page is still in the package so I assume mini-commander is meant to be part of this package) -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 12040] Gnome menu is slow when clicking for the first time
Public bug report changed: https://launchpad.net/malone/bugs/12040 Comment: This problem is still alive and kicking in Dapper with the latest updates (gnome-panel_2.13.91-0ubuntu6_i386.deb). The first time the 'foot' menu is opened it takes several seconds to appear. Meanwhile the panel or the menu applet has grabbed the X server so I can not do anything else but wait for the menu to appear. Irritating to say the least. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 24383] GTK filechooser takes about 45 seconds to start
Public bug report changed: https://launchpad.net/malone/bugs/24383 Comment: It takes more than 8 seconds for the file chooser to appear in gedit... using Dapper with libgtk2.0-0_2.8.14-0ubuntu1_i386.deb. The directory contains about 200 files (.dotfiles included). Performance of the 'new' file chooser on anything but a clean directory is still abysmal IMnsHO. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
