January 2008 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 352187] New: The KDE 4 shipped with the final version does not work at all.
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=352187 Summary: The KDE 4 shipped with the final version does not work at all. Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: publio.escipion.el.africano(a)gmail.com QAContact: qa(a)suse.de Found By: --- I tested openSuSE 10.3 under vmware workstation 6 before install it into a PC. Under vmware, I installed 10.3 and ask for install the preview version of KDE 4. It doesn't work at all: KDE 4 loaded fine, but no menu opened by mouse pointer: nor main, neither that of the secondary button mouse. Alt+F1 and Alt+F2 did work, but no program was executed ever. But KDE 3.5 did work fine. So, when I set up a physical PC I did not install KDE 4. ________ VMware Workstation 6.0.0 Build 45731 running under openSuSE 10.2 on AMD64. I submit the hwinfo of the virtual PC. -- 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 307488] New: eclipse does not pass parameters to eclipse.bin
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=307488 Summary: eclipse does not pass parameters to eclipse.bin Product: openSUSE 10.3 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Java AssignedTo: bnc-team-java(a)forge.provo.novell.com ReportedBy: felix(a)derklecks.de QAContact: qa(a)suse.de CC: dbornkessel(a)novell.com Found By: --- Eclipse does not work at the moment but trying to debug this a little I found a bug in the wrapper. When starting eclipse /usr/bin/eclipse get called which looks at the options and calls "/usr/share/eclipse/eclipse $ECLIPSE_OPTS $@ $VM_OPTS" so the user can pass his parameters. But "/usr/share/eclipse/eclipse just calls "/usr/share/eclipse/eclipse.bin -startup $STARTUP_JAR". That means all parameters are ignored. The last line of /usr/share/eclipse/eclipse should be: /usr/share/eclipse/eclipse.bin -startup $STARTUP_JAR $@ -- 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 20

[Bug 349577] New: TCSH 6.15.00-20.2 history saving is broken
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=349577 Summary: TCSH 6.15.00-20.2 history saving is broken Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: f+novell(a)congenio.de QAContact: qa(a)suse.de Found By: --- With tcsh-6.15.00-20.2, the history file does not get saved if the connection is broken. If you simply close a Windows SSH Terminal (SSH.com) instead of logging out gracefully via Ctrl-D or logout, the history file is truncated to 0 bytes afterwards. Partly, this can be circumvented by creating /etc/csh.logout with "history -S" in it, but the has the ill side-effect of also storing the last prompt output (!) into the histfile. My settings are: history 999 savehist = (1000 merge) I am not quite sure but I think that this was O.K. with openSUSE 10.0. Also, I know that something regarding a broken history was patched from tcsh-6.15.00-20 to tcsh-6.15.00-20.2 (have not tried the older one). Maybe this patch was counter-productive? -- 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 13

[Bug 331627] New: tcsh: losing savehistory
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=331627 Summary: tcsh: losing savehistory Product: openSUSE 10.3 Version: Final Platform: 64bit OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: kssingvo(a)novell.com QAContact: qa(a)suse.de Found By: Development Installed openSUSE 10.3 on my 64bit machine at home. When I logout (with shutdown) from KDE, my history is lost and no longer saved. I'm running 4 xterms simultaneously with tcsh in it. I notice that the $HOME/.history has size of 0 bytes afterwards. I'm having my $HOME on my local hd, and not via NFS. When I terminate the xterms sequently (= manually typing "exit"), then the history gets saved as expected. But not, if the system (KDE logout with shutdown) is doing this for me. Everything works well, when I did this in any previous SUSE versions, like 10.2, 10.1, ... Maybe the cause of the problem is a new shutdown process? Maybe a new logout algorithm of KDE? I don't know how to dig deeper into this help. Any hints? -- 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 10

[Bug 331021] New: Publishing a calendar crashes evolution
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=331021 Summary: Publishing a calendar crashes evolution Product: openSUSE 10.3 Version: Final Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: georg.wieser(a)gmail.com QAContact: lakhil(a)novell.com Found By: Other Fresh install of 10.3-GM, nothing done in Evolution but entering mail account information. Edit -> Preferences -> Calendar and Tasks -> Calendar Publishing -> Add -> CRASH Also happens after a second calendar and appointments were added. Bug Buddy says it collected information but can´t display it (yet). -- 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 12

[Bug 351991] New: Huge thread usage
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=351991 Summary: Huge thread usage Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: lakhil(a)novell.com QAContact: lakhil(a)novell.com Found By: --- Upstream bug http://bugzilla.gnome.org/show_bug.cgi?id=503574 For me, often e-d-s appears to grow wrt. memory use over time, though very intermittently, until it turns into some vast giant of a process :-) Recently I had the beasty deadlock on me, and I was surprised to see: "Thread 195" in the gdb trace (attached). Is it possible that our memory usage problems, could be caused by a runaway / unrestrained thread-pool problem ? Almost all of the threads were at: Thread 190 (Thread 0xad3ffb90 (LWP 14900)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb729d13e in __lll_mutex_lock_wait () from /lib/libpthread.so.0 #2 0xb7298c0d in _L_mutex_lock_81 () from /lib/libpthread.so.0 #3 0xb7298553 in pthread_mutex_lock () from /lib/libpthread.so.0 #4 0xb6e65622 in get_deltas (handle=0x87e9fc8) at e-cal-backend-groupwise.c:348 #5 0xb733f91f in g_thread_create_proxy (data=0xa6d2d00) at gthread.c:635 #6 0xb72970a5 in start_thread () from /lib/libpthread.so.0 #7 0xb721edfe in clone () from /lib/libc.so.6 Thread 189 (Thread 0xaaff7b90 (LWP 14927)): #0 0xffffe410 in __kernel_vsyscall () #1 0xb729d13e in __lll_mutex_lock_wait () from /lib/libpthread.so.0 #2 0xb7298c0d in _L_mutex_lock_81 () from /lib/libpthread.so.0 #3 0xb7298553 in pthread_mutex_lock () from /lib/libpthread.so.0 #4 0xb6e65622 in get_deltas (handle=0x806c338) at e-cal-backend-groupwise.c:348 #5 0xb733f91f in g_thread_create_proxy (data=0xae9a2a8) at gthread.c:635 #6 0xb72970a5 in start_thread () from /lib/libpthread.so.0 #7 0xb721edfe in clone () from /lib/libc.so.6 which looks odd: reading the code - there is apparently a *lot* of spawning of this thread going on - sometimes it's spawned after a 60second timeout too (why?). The logic here is unclear to me, but it seems that if get_deltas doesn't return inside a minute (the default) then we go on endlessly spawning these threads :-) - which is not cool: all of them blocking on the static 'connecting' mutex: ie. what we see. It seems clear that we shouldn't be launching duplicate threads to do the same work on a timeout here. The quick fix is to have a [ mutex protected ] list of threads already doing work here, and not dispatch duplicate threads. Of course - it's possible we also want some cancellation for very-long-running (failed) get_deltas threads too - not sure. -- 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 335546] New: Selecting the contact category crashes evolution data server
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=335546 Summary: Selecting the contact category crashes evolution data server Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution(a)forge.provo.novell.com ReportedBy: alberto.passalacqua(a)tin.it QAContact: lakhil(a)novell.com Found By: --- Selecting the contact category crashes evolution data server and makes evolution hang. The bug was already reported upstream, but considering its severity, I think it's a good idea to report it again here just as a reminder. The link to upstream bug report is: http://bugzilla.gnome.org/show_bug.cgi?id=486873 With kind regard, Alberto -- 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 10

[Bug 281277] New: Add support for Intel Bearlake chipsets
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=281277 Summary: Add support for Intel Bearlake chipsets Product: openSUSE 10.3 Version: Alpha 4plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: sndirsch(a)novell.com ReportedBy: sndirsch(a)novell.com QAContact: qa(a)suse.de Support for onboard graphics in Bearlake chipsets has been added to intel gfx driver, but agpgart support for them is still missing in intel_agp module. Wang Zhenyu (Intel) sent a patch to lkml for G33/Q33/Q35 agpgart. http://marc.info/?l=linux-kernel&m=118109985632636&w=2 -- 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 30

[Bug 287769] New: Screen doesn't lock after resume (from suspend to disk)
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=287769 Summary: Screen doesn't lock after resume (from suspend to disk) Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: qa(a)suse.de Found By: --- Usually when I resume from suspend to disk, the GNOME desktop is restored and the screen locks (I have an automatic screen saver enabled after a few minutes of being idle). However occasionally the screen does not lock, and any user who turns on the computer could resume work. Maybe it's related to moving the mouse during restore, but I really don't know. As a security feature, a password should be verified after resume (like in Windows/XP). -- 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 19

[Bug 270846] New: Add support for new RANDR 1.2 driver configuration theme
by bugzilla_noreply＠novell.com 09 Jan '08

09 Jan '08

https://bugzilla.novell.com/show_bug.cgi?id=270846 Summary: Add support for new RANDR 1.2 driver configuration theme Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: SaX2 AssignedTo: ms(a)novell.com ReportedBy: sndirsch(a)novell.com QAContact: qa(a)suse.de CC: mhopf(a)novell.com As already discussed together with Matthias for RANDR 1.2 we'll need support for the new driver configuration theme in SaX2. :-( "intel" driver can already be used for testing. I thought it would be a good place to track the status in Bugzilla and to discuss issues and details. -- 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 45