May 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 221162] New: missing help text for "Boot Loader Location"
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=221162 Summary: missing help text for "Boot Loader Location" Product: openSUSE 10.2 Version: Beta 2 plus Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: odabrunz(a)novell.com ReportedBy: jsuchome(a)novell.com QAContact: jsrain(a)novell.com In yast2-bootloader, Expert tab has a frame with "Boot Loader Location" options. This widget is mentioned in help text only with the label ("Boot Loader Location" in bold), but without any information. -- 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 6

[Bug 208870] New: Bad grub location selected
by bugzilla_noreply＠novell.com 27 Jul '08

27 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=208870 Summary: Bad grub location selected Product: openSUSE 10.2 Version: Alpha 4 Platform: 64bit OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hugo.costelha(a)gmail.com QAContact: jsrain(a)novell.com I had SUSE Linux 10.1 installed, and I was trying openSUSE 10.2, to help improving it by bug reporting. I had just one SATA drive installed with SUSE 10.1, so I installed an IDE hard-drive and started openSUSE 10.2 installation from the CDs. Initially openSUSE 10.2 sugested to use the SATA drive, so I changed it to use the IDE drive, and proceeded with the install. When it made the first reboot, the old (SUSE 10.1) GRUB appeared (with no reference to openSUSE 10.2) and booted the 10.1. So, the grub install location was badly selected. -- 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 35

[Bug 267832] New: kopete can't respond to GWIM chats started by the Windows Java client
by bugzilla_noreply＠novell.com 26 Jul '08

26 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=267832 Summary: kopete can't respond to GWIM chats started by the Windows Java client Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: wstephenson(a)novell.com ReportedBy: wstephenson(a)novell.com QAContact: qa(a)suse.de CC: jbeulich(a)novell.com, adrian(a)novell.com Drei Fragen: Problembeschreibung " Du chattest Adrian an, und bekommst keine Antwort, obwohl er behauptet, er hätte Dich geantwortet. " Habe ich das richtig verstanden? Wenn du ein Chat startest, und gleich keine Antwort bekommst, machst Du üblicherweise das Chatfenster zu, oder lässt du es offen, bis jemand darauf antwortet? Kommen von Adrian eingeleiteten chats bei dir an? Ich teste zuerst lokal, falls ich das Problem nicht reproduzieren kann, melde ich mich bei Dir, Jan. -- 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 19

[Bug 228920] New: KOrganizer does not sync with palm device using kpilot
by bugzilla_noreply＠novell.com 26 Jul '08

26 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=228920 Summary: KOrganizer does not sync with palm device using kpilot Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: PSpee(a)gmx.de QAContact: qa(a)suse.de Syncing a palm device with openSUSE deletes all calendar information on the device. The datebook in KOrganizer keeps the information. Steps to Reproduce: Sync palm device with kpilot and KOrganizer Actual Results: Open datebook on palm device and the calendar is empty Expected Results: Datebook on palm device should have all KOrganizer entries Build Date & Platform: openSUSE 10.2 Final Palm Tungsten|T Additional Builds and Platforms: - Also Occurs On Ubuntu: https://bugs.launchpad.net/products/kdepim/+bug/66313 Additional Information: The bug seems to be fixed in KDE-SVN according to the ubuntu link above The Logfile of kpilot says: 21:17:51 Mit Datei "/home/pspee/.kde/share/apps/korganizer/pspee.ics" abgleiche n 21:17:51 Kalender-Datenbanken können nicht geöffnet werden. 21:17:51 Der Abgleich vcal-conduit kann nicht durchgeführt werden -- 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 10

[Bug 246650] New: Changing keyboard layout impossible in kickoff search input field
by bugzilla_noreply＠novell.com 25 Jul '08

25 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=246650 Summary: Changing keyboard layout impossible in kickoff search input field Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: auxsvr(a)yahoo.com QAContact: qa(a)suse.de Using the KDE keyboard configuration, I am unable to switch to other layouts when kickoff has the focus (this is necessary to search and in the future to navigate via keyboard in kickoff). What is weird is that if I switch to another layout from the default (US english) before focusing on kickoff, I can then switch layouts normally, even though the keyboard icon flag on the taskbar doesn't change accordingly. -- 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 10

[Bug 275039] New: KOrganizer module is started even though I disable and quit it on each session
by bugzilla_noreply＠novell.com 25 Jul '08

25 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=275039 Summary: KOrganizer module is started even though I disable and quit it on each session Product: openSUSE 10.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sven.burmeister(a)gmx.net QAContact: qa(a)suse.de There is a bug in Psi (unmapped windows) which seems to be related to KDE, so I updated KDE to the build-system packages. Since then the KOrganizer systray-module is started on every session although I right-click it, make sure that there is not X in fornt of the autostart-setting and tell it to "Not Start" when it asks on quit whether it should start on each start-up. I tis not in my ~.kde/Autostart, yet I found it in /opt/kde3/share/autostart with X-KDE-autostart-condition=korgacrc:General:Autostart:true which does not seem to work, i.e. not respect the user's settings regarding autostart. -- 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 8

[Bug 266893] New: krpmview does not close after RPM install from konqueror with YAST2
by bugzilla_noreply＠novell.com 24 Jul '08

24 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=266893 Summary: krpmview does not close after RPM install from konqueror with YAST2 Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: openSUSE 10.2 Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: floridafryes(a)yahoo.com QAContact: jsrain(a)novell.com Installing RPM from folder in konqueror using "Install Package with YaST" button works after reboot. Installing a second RPM the same way causes error message "Another process is accessing the package database. Package management cannot be used now." It is necessary to identify the process manually and kill it to allow further installs. I narrowed the problem program down to krpmview. Below is the terminal capture that remedies the problem. sandbox:/home/rfrye # ps -ef | grep /opt/kde3/share/apps/krpmview/setup_temp_source rfrye 4310 3980 0 09:40 pts/0 00:00:00 kdesu -n --nonewdcop -- /opt/kde3/share/apps/krpmview/setup_temp_source /home/rfrye/downloads/mplayer-codecs-20061022-1.i386.rpm root 4324 4318 0 09:40 ? 00:00:00 /bin/bash /opt/kde3/share/apps/krpmview/setup_temp_source /home/rfrye/downloads/mplayer-codecs-20061022-1.i386.rpm root 5220 5213 0 09:42 pts/5 00:00:00 grep /opt/kde3/share/apps/krpmview/setup_temp_source sandbox:/home/rfrye # kill 4310 sandbox:/home/rfrye # -- 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 12

[Bug 270229] New: make root prompt easy to restore to color used by normal users (not red)
by bugzilla_noreply＠novell.com 24 Jul '08

24 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=270229 Summary: make root prompt easy to restore to color used by normal users (not red) Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Keywords: Usability Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)ij.net QAContact: qa(a)suse.de Root prompt foreground color was recently changed to some kind of red. In my Konsole with white background the red color has insufficient contrast with the background for me to read the prompt content without eyestrain. Likewise on my VCs where I have the background set to blue and the foreground set to bright white via setterm in /root/.bashrc, my foreground color is ignored, leaving me with a red foreground that is hard to read on my blue background. It would seem that exporting PS1 in .bashrc with the preferred color scheme should work, but the one liners I tried either get it right on the VCs or on the Konsole but not both, as their background colors are nearly opposite, dictating entirely different foreground colors, like the system handled nicely by default before the change to red. The setterm colors should be honored in the VCs, and in Konsole the schema should also be obeyed, at least via some easy to find and use preference setting, if not by default. -- 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 9

[Bug 216044] New: NCC configuration error message truncated (ncurses)
by bugzilla_noreply＠novell.com 24 Jul '08

24 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=216044 Summary: NCC configuration error message truncated (ncurses) Product: openSUSE 10.2 Version: Beta 1 Platform: IA64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: gp(a)novell.com QAContact: jsrain(a)novell.com When installing in ncurses mode, on a console of 80x25, I got an error message. This bug report is _not_ about the error as such, but about the fact that the message was truncated such that the full name of the source which caused problems did not appear. -- 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 15

[Bug 230860] New: grub error: message too large
by bugzilla_noreply＠novell.com 24 Jul '08

24 Jul '08

https://bugzilla.novell.com/show_bug.cgi?id=230860 Summary: grub error: message too large Product: openSUSE 10.2 Version: Final Platform: i686 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: pgunreben(a)lucent.com QAContact: qa(a)suse.de At the first reboot after installing openSuSE, grub stopped on error: file "(HD0,1)/boot/message" too large, press any key to continue. After pressing a key the boot continues normally. >ls -l /boot/message -rw-r--r-- 1 root root 379904 Dec 27 14:10 /boot/message Hardware: AMD K7 1200 MHz on ASUS A7V -- 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 22