August 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 288211] New: Internal error, unknown error 'mail:async-error' requested
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=288211 Summary: Internal error, unknown error 'mail:async-error' requested Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: openSUSE 10.2 Status: NEW Severity: Major Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: fred.blaise(a)gmail.com QAContact: lakhil(a)novell.com Found By: --- Hello, All of a sudden today, evolution wouldn't work properly, actually not being usable anymore. I had to switch mailer :( I get this pop-up: Internal error, unknown error 'mail:async-error' requested Then, it goes nuts in the statsbar, "generating message list" with no end. In the console, I see these, non-stop: (evolution-2.8:6101): camel-WARNING **: Could not save object state file to '/home/fblaise/.evolution/mail/imap/frederic blaise(a)dominomp01/folders/INBOX/.#cmeta': Too many open files (evolution-2.8:6101): camel-WARNING **: Could not save object state file to '/home/fblaise/.evolution/mail/imap/frederic blaise(a)dominomp01/folders/INBOX/.#cmeta': Too many open files (evolution-2.8:6101): evolution-mail-WARNING **: Error occurred while existing dialogue active: Could not connect to dominomp01: Too many open files (evolution-2.8:6101): camel-WARNING **: Could not save object state file to '/home/fblaise/.evolution/mail/imap/frederic blaise(a)dominomp01/folders/INBOX/.#cmeta': Too many open files I am using these pkgs: `--> rpm -aq |grep evo evolution-sharp-0.12.0-14.1 evolution-data-server-1.8.2-9 evolution-2.8.2-5 libopensync-plugin-evolution2-0.20-9 beagle-evolution-0.2.12-28 Please help, thanks -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 294426] New: Evolution crashed for attachment reminder
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=294426#c1 Summary: Evolution crashed for attachment reminder Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: kaprasad(a)novell.com QAContact: lakhil(a)novell.com CC: jjohnny(a)novell.com Found By: --- Steps to Reproduce: 1. Open a new composer window. 2. Type a message with a key word for attachment. 3. Click on send. This pops an Evolution window saying: { Internal error, unknown error. 'org.gnome.evolution.plugins.attachment_reminder:attachment-reminder' requested' } Then Evolution crashed. Below are the traces. IMAP was the backend server. Distribution: openSUSE 10.3 (i586) Alpha6 Gnome Release: 2.19.4 2007-07-17 (SUSE) BugBuddy Version: 2.18.1 System: Linux 2.6.22-5-default #1 SMP 2007/07/16 06:54:15 UTC i686 X Vendor: The X.Org Foundation X Vendor Release: 60900000 Selinux: No Accessibility: Enabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 217776128 vsize: 217776128 resident: 50888704 share: 44453888 rss: 95342592 rss_rlim: 900254720 CPU usage: start_time: 1185344076 rtime: 9071 utime: 8577 stime: 494 cutime:32 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0xb657a6c0 (LWP 21792)] [New Thread 0xb086cb90 (LWP 21829)] [New Thread 0xb106db90 (LWP 21828)] [New Thread 0xb10dfb90 (LWP 21805)] [New Thread 0xb18e0b90 (LWP 21804)] [New Thread 0xb2106b90 (LWP 21803)] [New Thread 0xb3329b90 (LWP 21801)] [New Thread 0xb297fb90 (LWP 21800)] [New Thread 0xb432bb90 (LWP 21796)] 0xffffe410 in ?? () #0 0xffffe410 in ?? () #1 0xbfa5a448 in ?? () #2 0x00000000 in ?? () Thread 9 (Thread 0xb432bb90 (LWP 21796)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb432b368 in ?? () No symbol table info available. #2 0x00000f84 in ?? () No symbol table info available. #3 0x00000000 in ?? () No symbol table info available. Thread 8 (Thread 0xb297fb90 (LWP 21800)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb297f368 in ?? () No symbol table info available. #2 0x000000cf in ?? () No symbol table info available. #3 0x00000000 in ?? () No symbol table info available. Thread 7 (Thread 0xb3329b90 (LWP 21801)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb3329368 in ?? () No symbol table info available. #2 0x00000557 in ?? () No symbol table info available. #3 0x00000000 in ?? () No symbol table info available. Thread 6 (Thread 0xb2106b90 (LWP 21803)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb2106368 in ?? () No symbol table info available. #2 0x00000f82 in ?? () No symbol table info available. #3 0x00000000 in ?? () No symbol table info available. Thread 5 (Thread 0xb18e0b90 (LWP 21804)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb18e02e8 in ?? () No symbol table info available. #2 0xffffffff in ?? () No symbol table info available. #3 0x00000001 in ?? () No symbol table info available. #4 0xb66cb6d7 in poll () from /lib/libc.so.6 No symbol table info available. #5 0xb6776885 in g_main_context_iterate (context=0x854ad40, block=1, dispatch=1, self=0x8547be0) at gmain.c:2996 got_ownership = <value optimized out> max_priority = 2147483647 timeout = -1 some_ready = <value optimized out> nfds = 1 allocated_nfds = <value optimized out> fds = (GPollFD *) 0x85486e0 __PRETTY_FUNCTION__ = "g_main_context_iterate" #6 0xb6776c37 in IA__g_main_loop_run (loop=0x8096b68) at gmain.c:2898 got_ownership = -1222867936 self = (GThread *) 0x8547be0 __PRETTY_FUNCTION__ = "IA__g_main_loop_run" #7 0xb7d1b4d2 in startup_mainloop (arg=0x0) at e-book.c:3763 loop = (GMainLoop *) 0xfffffffc #8 0xb6796e4f in g_thread_create_proxy (data=0x8547be0) at gthread.c:634 __PRETTY_FUNCTION__ = "g_thread_create_proxy" #9 0xb71c6192 in start_thread () from /lib/libpthread.so.0 No symbol table info available. #10 0xb66d4d2e in clone () from /lib/libc.so.6 No symbol table info available. Thread 4 (Thread 0xb10dfb90 (LWP 21805)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb10df2f8 in ?? () No symbol table info available. #2 0xffffffff in ?? () No symbol table info available. #3 0x00000008 in ?? () No symbol table info available. #4 0xb66cb6d7 in poll () from /lib/libc.so.6 No symbol table info available. #5 0xb6776885 in g_main_context_iterate (context=0x854a120, block=1, dispatch=1, self=0x854caf0) at gmain.c:2996 got_ownership = <value optimized out> max_priority = 2147483647 timeout = -1 some_ready = <value optimized out> nfds = 8 allocated_nfds = <value optimized out> fds = (GPollFD *) 0x84af660 __PRETTY_FUNCTION__ = "g_main_context_iterate" #6 0xb6776c37 in IA__g_main_loop_run (loop=0x854c740) at gmain.c:2898 got_ownership = -1222867936 self = (GThread *) 0x854caf0 __PRETTY_FUNCTION__ = "IA__g_main_loop_run" #7 0xb72193b0 in ?? () from /usr/lib/libORBit-2.so.0 No symbol table info available. #8 0x0854c740 in ?? () No symbol table info available. #9 0xb67feff4 in ?? () from /usr/lib/libglib-2.0.so.0 No symbol table info available. #10 0xb10df3c8 in ?? () No symbol table info available. #11 0xb6796e4f in g_thread_create_proxy (data=0x854caf0) at gthread.c:634 __PRETTY_FUNCTION__ = "g_thread_create_proxy" Backtrace stopped: frame did not save the PC Thread 3 (Thread 0xb106db90 (LWP 21828)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb106d368 in ?? () No symbol table info available. #2 0x00000f86 in ?? () No symbol table info available. #3 0x00000000 in ?? () No symbol table info available. Thread 2 (Thread 0xb086cb90 (LWP 21829)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xb086c368 in ?? () No symbol table info available. #2 0x00000f80 in ?? () No symbol table info available. #3 0x00000000 in ?? () No symbol table info available. Thread 1 (Thread 0xb657a6c0 (LWP 21792)): #0 0xffffe410 in ?? () No symbol table info available. #1 0xbfa5a448 in ?? () No symbol table info available. #2 0x00000000 in ?? () No symbol table info available. #0 0xffffe410 in ?? () The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (10760 sec old) --------------------- /usr/share/themes/Synchronicity/gtk-2.0/gtkrc:48: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. GTK Accessibility Module initialized /usr/share/themes/Gilouche/gtk-2.0/gtkrc:42: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/Gilouche/gtk-2.0/gtkrc:43: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/Gilouche/gtk-2.0/gtkrc:44: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. GTK Accessibility Module initialized (gnome_segv:21765): Gnome-WARNING **: Accessibility: failed to find module 'libgail-gnome' which is needed to make this application accessible GTK Accessibility Module initialized (bug-buddy:21768): Gnome-WARNING **: Accessibility: failed to find module 'libgail-gnome' which is needed to make this application accessible /usr/share/themes/Gilouche/gtk-2.0/gtkrc:42: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored. /usr/share/themes/Gilouche/gtk-2.0/gtkrc:43: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored. /usr/share/themes/Gilouche/gtk-2.0/gtkrc:44: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored. Failed to read a valid object file image from memory. -------------------------------------------------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 3

[Bug 295875] New: Bogofilter option still availabe even when the plugin is disabled
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=295875 Summary: Bogofilter option still availabe even when the plugin is disabled Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: kaprasad(a)novell.com QAContact: lakhil(a)novell.com Found By: Integration Test 1. Disable the Bogofilter Junk Plugin in the Plugins. 2. Now in Mail Preferences under Junk tab the Bogofilter option is still availabe for Default Junk plugin selection. And the error statement is shown below saying "Bogofilter plugin is not available. Please check whether the package is installed." Note: But the Bogofilter options are not displayed anyways. Bogofilter option should not be availabe when the plugin is disabled. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 6

[Bug 295943] New: Using magic space bar messages cannot be read in the child folders when the tree is collapsed .
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=295943 Summary: Using magic space bar messages cannot be read in the child folders when the tree is collapsed. Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: kaprasad(a)novell.com QAContact: lakhil(a)novell.com Found By: Integration Test 1. Select the parent folder whose child folders have unread messages. 2. Collapse the tree from the folder tree view. 3. Use space bar to read the unread messages in the parent folder. Once this is done in parent folder it does not open the tree and read the unread messages of the child folders, instead the focus goes to the next visible folder in the tree. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 295938] New: Not able to wrap around to the next unread message within a folder with magic space bar .
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=295938 Summary: Not able to wrap around to the next unread message within a folder with magic space bar. Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: kaprasad(a)novell.com QAContact: lakhil(a)novell.com Found By: Integration Test 1. In a folder when the point of focus in the message list of a folder is in the middle where you have unread messages above as well as below. 2. Use magic space bar to read the unread messages in the folder. 3. After completion of reading the unread messages until end of the folder it does not wrap around to read the unread ones above. Similarly when all the folders below are read, it does not wrap around to the starting folder that contains unread messages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 1

[Bug 267440] New: [AI] LWE SF 2007 community booth
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=267440 Summary: [AI] LWE SF 2007 community booth Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Action Items AssignedTo: martin.lasarsch(a)novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: adrian(a)novell.com http://en.opensuse.org/Meetings/Status_Meeting_2007-04-11 Action item mlasars: - organize LWE SF community member booth -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 3

[Bug 296437] New: /dev/dsp has wrong permissions
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=296437 Summary: /dev/dsp has wrong permissions Product: openSUSE 10.3 Version: Alpha7 Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: nderkach(a)gmail.com QAContact: qa(a)suse.de Found By: --- /dev/dsp has adopted wrong permissions after latest factory update: # ls -l dsp crw-rw---- 1 root audio 14, 3 Авг 1 17:17 dsp Should be "crw-rw-rw-" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 2

[Bug 204006] php5 does not provide pecl
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=204006#c8 Cristian Rodriguez <crrodriguez(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|judas_iscariote@shorewall.ne|crrodriguez@novell.com |t | --- Comment #8 from Cristian Rodriguez <crrodriguez(a)novell.com> 2007-08-01 11:06:58 MST --- there is still a wrongness here, it is pear that should provide pecl not php5-devel stricly. php5-devel should provide only php-config and phpize. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 175593] I can not install the sources of packages
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=175593#c10 Michael Andres <ma(a)novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ma(a)novell.com |jkupec(a)novell.com Status|ASSIGNED |NEW --- Comment #10 from Michael Andres <ma(a)novell.com> 2007-08-01 10:55:06 MST --- Targeted via zypper in 10.3. (requires libzypp-3.13.5) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 0

[Bug 274934] New: integrating control-center into gnome main menu
by bugzilla_noreply＠novell.com 01 Aug '07

01 Aug '07

https://bugzilla.novell.com/show_bug.cgi?id=274934 Summary: integrating control-center into gnome main menu Product: openSUSE 10.3 Version: Alpha 4 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Usability AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: christian.jaeger(a)rub.de QAContact: qa(a)suse.de IMHO it would be a good idea to give quicker access to the functions found in the control center; the way toward that would be to integrate it into the main-menu's layout. As it is now, clicking on 'control center' from within the main-menu opens a new windows and thus disrupts the work flow, unlike going over the traditional, collapsing gnome-menu. The concept of the application-browser is good AFAIAC - not only novice users are regularly irritated when they move the mouse a bit too far in a sub-sub-sub-menu and the whole menu-tree collapses. But the abundance of applets is confusing and they need a large, new window. So it could be more user-friendly to break this down by presenting applets by sets; within the gnome main-menu. See the attached picture for a design-proposal. In this proposal, categories are present on the left side of the tab, sub-menus open in a tab (recognizable only by the use of a different background-colour) on the right side. I think this layout would make is easier than ever for novice users to execute common tasks. The categories scroll vertically, the applications are browseable by clicking the horizontally-pointing arrows. This is intended to keep the layout as calm as possible. Browsing through an applet-category goes step-by-step or better: set-by-set. Sets of tiles should appear by popularity; most-often-used applets should appear in the first set, second-most-often-used in the second set and so on. Within these sets, ordering should not change from usage to usage because that would be confusing. Also, the search-function of the main-menu should function as a filter here, like in the original SUSE-control-center. Note that 'install software' is prominent in the main- and applications-tabs in my design; not in the 'system'-tab. Here are some suggestions for layout-guidelines: • The mouse should have to move short ways --> no dead space wanted, the menu should stay small. • The hierarchy of buttons is top-down and left-right: Super buttons in the top-bar, main links above submenu-links and actions, submenu-links left of actions • There is three types of click-able objects in the menu: 'super'-objects in the top bar (those aren't tiles), links (those aren't tiles and don't have symbols) and action (are tiled, have symbols) • Clicking on links changes the layout of the main frame, by either changing the whole frame or portions of it (tabs) • Links appear only within the main frame, which they change, in order to make their being connected obvious • Activities are represented by tiles. --> installing software is only an activity, too! • Sub-menus appear as links on the left side of the main-window, their collected activities as tiles on the right side • Use of tabs, consisting of a coloured background, makes it obvious to the eye that they belong to one 'set' of a link. • Sets of activities don't scroll! Use left/right-arrows to 'browse' them instead. • Lists of links do scroll (up/down-arrows) if necessary because we don't want more than one part of the main windows to change • Information should not be clickable! (because it confuses) -->'harddrive' and 'network' are reduced to text-status and aren't tiles, anymore This bug depends on Bug 274817. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 3