September 2007 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 293433] New: hotplugged usb ntfs partitions are mounted as ntfs instead of ntfs-3g
by bugzilla_noreply＠novell.com 19 Oct '08

19 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=293433 Summary: hotplugged usb ntfs partitions are mounted as ntfs instead of ntfs-3g Product: openSUSE 10.3 Version: Alpha 6 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: peter.kerekfy(a)winsdom.com QAContact: qa(a)suse.de Found By: --- HAL (or whatever) mounts hotplugged ntfs partitions with ntfs instead of ntfs-3g. I know it is a terrible hack but I created a symlink from /sbin/mount.ntfs to /usr/bin/ntfsmount which happens to be the userspace ntfs-3g executeable. Regards, Peter. -- 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 27

[Bug 226686] New: Yast/German: "Installationsquelle wechseln"
by bugzilla_noreply＠novell.com 18 Oct '08

18 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=226686 Summary: Yast/German: "Installationsquelle wechseln" Product: SUSE Linux 10.1 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: Ulrich.Windl(a)rz.uni-regensburg.de QAContact: ke(a)novell.com In Yast's "Software" group the German text "Instalationsquelle wechseln" (change installation source) seems to imply that the user can exchange (in the meaning of replacing one for another) the installation source, while in fact the use can manage installation sources (that is: add, change, delete) to have multiple sources. Maybe "Installationsquellen verwalten" (manage installation sources) would be more precise. -- 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 269834] New: Configuration of Modem and ISDN through NM Applet only possible if at least 1 Modem already configured
by bugzilla_noreply＠novell.com 17 Oct '08

17 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=269834 Summary: Configuration of Modem and ISDN through NM Applet only possible if at least 1 Modem already configured Product: openSUSE 10.3 Version: Alpha 3 Platform: x86 OS/Version: openSUSE 10.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: casualprogrammer(a)yahoo.com QAContact: qa(a)suse.de I suggest making this feature available permanently, without having to go through YaST modem setup the first time. -- 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 13

[Bug 328116] New: Bluetooth DUND not working
by bugzilla_noreply＠novell.com 16 Oct '08

16 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=328116 Summary: Bluetooth DUND not working Product: openSUSE 10.3 Version: RC 1 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: funtasyspace(a)yahoo.com QAContact: qa(a)suse.de CC: seife(a)novell.com Found By: --- Created an attachment (id=174560) --> (https://bugzilla.novell.com/attachment.cgi?id=174560) output of hcidump for DUN connection attempt I can't manage to get the bluetooth dial-up network daemon to work on openSUSE 10.3. I just took my working peer configuration from openSUSE 10.2 and put it to '/etc/ppp/peers/bluetooth-dun' As before on openSUSE 10.2 I modified '/etc/sysconfig/bluetooth' to start the DUND automatically with the following parameters: DUND_DAEMON_ARGS="--listen --persist call bluetooth-dun" Next I verified, that dund is running: # ps ax | grep dund 1865 ? S<s 0:00 /usr/bin/dund --listen --persist call bluetooth-dun Now if I try to connect to the dund via my mobile phone or with a second pc and dund, nothing happens. It seems like dund doesn't react to incoming DUN requests at all!? Could it be, that a client tries to lookup the DUN-Service via SDP first? I recognized, that the SDP daemon (sdpd) is missing (or no longer shiped) with openSUSE 10.3. [ No SDP deamon -> SDP lookup of DUN-Service fails -> client doesn't even try to request a DUN connection ] I attached the output of 'hcidump hci0' on the machine providing the DUN service, when I try to connect from my mobile phone. -- 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 309646] New: Kopete crashes at Yahoo! login
by bugzilla_noreply＠novell.com 16 Oct '08

16 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=309646#c5 Summary: Kopete crashes at Yahoo! login Product: openSUSE 10.3 Version: Beta 3 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: schaiba(a)gmail.com QAContact: qa(a)suse.de Found By: Other When configuring kopete to use my y! account, everything goes ok. After restarting kopete and trying to login, it crashes. Here's the traceback: System configuration startup check disabled. (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b6b9f46b8b0 (LWP 12345)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #5 0x00002b6b99661b45 in raise () from /lib64/libc.so.6 #6 0x00002b6b996630e0 in abort () from /lib64/libc.so.6 #7 0x00002b6b9969f21f in ?? () from /lib64/libc.so.6 #8 0x00002b6ba08fb1e7 in YMSGProtocol::parse () from /opt/kde3/lib64/kde3/kopete_yahoo.so #9 0x00002b6ba0900692 in CoreProtocol::wireToTransfer () from /opt/kde3/lib64/kde3/kopete_yahoo.so #10 0x00002b6ba09007f8 in CoreProtocol::addIncomingData () from /opt/kde3/lib64/kde3/kopete_yahoo.so #11 0x00002b6ba08fe415 in ClientStream::bs_readyRead () from /opt/kde3/lib64/kde3/kopete_yahoo.so #12 0x00002b6ba08fe68b in ClientStream::qt_invoke () from /opt/kde3/lib64/kde3/kopete_yahoo.so #13 0x00002b6b98c39e6c in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x00002b6b98c3a604 in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #15 0x00002b6ba08fcd93 in KNetworkByteStream::slotReadyRead () from /opt/kde3/lib64/kde3/kopete_yahoo.so #16 0x00002b6ba08fce5d in KNetworkByteStream::qt_invoke () from /opt/kde3/lib64/kde3/kopete_yahoo.so #17 0x00002b6b98c39e6c in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #18 0x00002b6b98c3a604 in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #19 0x00002b6b981d6636 in KNetwork::KBufferedSocket::qt_invoke () from /opt/kde3/lib64/libkdecore.so.4 #20 0x00002b6b98c39e6c in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #21 0x00002b6b98c3a524 in QObject::activate_signal () from /usr/lib/qt3/lib64/libqt-mt.so.3 #22 0x00002b6b98c53f4b in QSocketNotifier::event () from /usr/lib/qt3/lib64/libqt-mt.so.3 #23 0x00002b6b98be36dd in QApplication::internalNotify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #24 0x00002b6b98be43f8 in QApplication::notify () from /usr/lib/qt3/lib64/libqt-mt.so.3 #25 0x00002b6b9819f1fd in KApplication::notify () from /opt/kde3/lib64/libkdecore.so.4 #26 0x00002b6b98bd94a3 in QEventLoop::activateSocketNotifiers () from /usr/lib/qt3/lib64/libqt-mt.so.3 #27 0x00002b6b98b99854 in QEventLoop::processEvents () from /usr/lib/qt3/lib64/libqt-mt.so.3 #28 0x00002b6b98bf7f53 in QEventLoop::enterLoop () from /usr/lib/qt3/lib64/libqt-mt.so.3 #29 0x00002b6b98bf7e02 in QEventLoop::exec () from /usr/lib/qt3/lib64/libqt-mt.so.3 #30 0x00000000004412ba in QWidget::setUpdatesEnabled () #31 0x00002b6b9964eb54 in __libc_start_main () from /lib64/libc.so.6 #32 0x0000000000431909 in QWidget::setUpdatesEnabled () #33 0x00007fff14333388 in ?? () #34 0x0000000000000000 in ?? () -- 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 270459] New: Installation - Bootloader [Buttons]
by bugzilla_noreply＠novell.com 16 Oct '08

16 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=270459 Summary: Installation - Bootloader [Buttons] Product: openSUSE 10.3 Version: Alpha 3 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: odabrunz(a)novell.com ReportedBy: locilka(a)novell.com QAContact: jsrain(a)novell.com Please, see this link http://en.opensuse.org/YaST/Style_Guide/Use_cases/Installation#Proposal_Wor… Installation Proposal: * [Back] button should be disabled in the first dialog (there is not any previous dialog) * [Finish] should be [Accept] (it doesn't finish installation, it just accepts changes) Screenshot will be attached. -- 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 11

[Bug 238572] New: SCSI Subsystem Locks-up Machine
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=238572 Summary: SCSI Subsystem Locks-up Machine Product: openSUSE 10.2 Version: Final Platform: x86 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers(a)forge.provo.novell.com ReportedBy: jim(a)edwardsj7.com QAContact: qa(a)suse.de My system has the root, "/", and "/home" directories on two different SCSI drives on the same chain of an Adaptec 29320 (U320) card and they are using the AIC79xx driver version 3.0. From time to time the system will cease to function and the SCSI activity indicator LED will stay on at 100% (usually it only flashes very briefly) and the machine becomes unresponsive. Maybe after a long time it will seem to return, but really the SCSI drives are off-line and even a restart fails back to what looks like an "init 3" screen with "login" displayed, but nothing is accepted. A system hard RESET, or power off and on, is required to restore functionality. The ensuing reboot displays a large number of transactions being replayed for the "/" RFS, 800+ is not unusual, but nothing for the ext3 (when it was RFS it had some transactions). It seems that this lock-up is triggered by things that try to move a lot of data over the SCSI bus, like "mkisofs" or some other large file transfers. Moving "/home" to an IDE drive did not help. "/" is on an RFS version 3.6 partition and "/home" is on an ext3 partition (it was RFS, and changed to ext3 with no effect). The same system hardware (AMD Athlon XP 2500+ etc.) has been running Suse 9.0 successfully with no such problems, and still can, so it seems to me to be likely to be related to the newer drivers (version 9.0's are much older, version 1.3.something, I think), possibly in association with RFS ??? For info ... jim@linux:~> cat /proc/scsi/aic79xx/4 Adaptec AIC79xx driver version: 3.0 Adaptec 29320 Ultra320 SCSI adapter aic7902: Ultra320 Wide Channel B, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs Allocated SCBs: 68, SG List Length: 128 Serial EEPROM: 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x17c8 0x09f4 0x01c7 0x2807 0x0010 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0410 0xb458 Target 0 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Goal: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Curr: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Channel A Target 0 Lun 0 Settings Commands Queued 47423 Commands Active 0 Command Openings 32 Max Tagged Openings 32 Device Queue Frozen Count 0 Target 1 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Goal: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Curr: 320.000MB/s transfers (160.000MHz DT|IU|QAS, 16bit) Channel A Target 1 Lun 0 Settings Commands Queued 105578 Commands Active 0 Command Openings 32 Max Tagged Openings 32 Device Queue Frozen Count 0 Target 2 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 3 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 4 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 5 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 6 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Goal: 80.000MB/s transfers (40.000MHz, 16bit) Curr: 80.000MB/s transfers (40.000MHz, 16bit) Channel A Target 6 Lun 0 Settings Commands Queued 32843 Commands Active 0 Command Openings 1 Max Tagged Openings 0 Device Queue Frozen Count 0 Target 7 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 8 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 9 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 10 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 11 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 12 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 13 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 14 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Target 15 Negotiation Settings User: 320.000MB/s transfers (160.000MHz RDSTRM|DT|IU|QAS, 16bit) Targets "0" and "1" are the two SCSI hard drives. Thanks for any help Jim -- 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 27

[Bug 304316] New: hal: use better libexecdir
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=304316 Summary: hal: use better libexecdir Product: openSUSE 10.3 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sbrabec(a)novell.com QAContact: qa(a)suse.de Found By: --- According to packaging conventions, libexecdir should be based on %{_prefix}/lib, not %{_libdir}. See also: bug 157894 This change will allow to use 32-bit addons on 64-bit systems, which is IMHO possible, because addons are binaries. Please note, that this change must be done in all addon providing packages. -- 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 16

[Bug 328385] New: KDE fails to resize properly with XRandR 1.2 rotation
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=328385 Summary: KDE fails to resize properly with XRandR 1.2 rotation Product: openSUSE 10.3 Version: RC 1 Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE AssignedTo: kde-maintainers(a)suse.de ReportedBy: loki1984(a)vfemail.net QAContact: qa(a)suse.de Found By: Beta-Customer I have a Thinkpad X41 Tablet with an Intel 915GM graphics card. I did a fresh install of OpenSuSE 10.3 RC1, and have done all available updates. The output of xrandr -q is as follows: Screen 0: minimum 320 x 200, current 1024 x 768, maximum 1024 x 1024 VGA disconnected 1024x768+0+0 (normal left inverted right) 0mm x 0mm 1024x768_60 60.0* LVDS connected 1024x768+0+0 (normal left inverted right) 0mm x 0mm 1024x768 57.6*+ 85.0 75.0 70.1 60.0 832x624 74.6 800x600 85.1 72.2 75.0 60.3 56.2 640x480 85.0 72.8 75.0 59.9 720x400 85.0 640x400 85.1 640x350 85.1 Running xrandr --output LVDS --rotate left in KDE gives me a properly rotated 1024x1024 desktop, however I have to move the main panel to the bottom of the screen manually the first time. The desktop size is 1024x1024 because the non-existant VGA monitor is at 1024x768, and the LCD is at 768x1024, so 1024x1024 is the smallest resolution which will fit both. This is part works more or less properly as far as I can tell. Running xrandr --output VGA --rotate left --output LVDS --rotate left is where I run into problems. This gives me a properly rotated 768x768 desktop. The bottom of the screen beyond 768 is just blank. xrandr -q lists the current size correctly as 768x1024, and I can move the cursor and windows down to there, but no desktop background shows up in that area, and I cannot move the panel down to the bottom. When I maximize a window it maximizes in the 768x768 desktop area. In GNOME the rotation works flawlessly, which leads me to believe that my Xorg configuration is correct. Also, when I run kwin --replace in KDE while it's rotated, windows maximize in the proper 768x1024 area, however the panel is still stuck and the background in the area below 768 is still black. When I run xrandr --output VGA --rotate left --output LVDS --rotate left --fb 1024x1024, then I get a properly rotated desktop. However, my mouse can still travel far off the screen on the one side, and my stylus requires a hack to work properly. Basically, with the --fb FOOxBAR option, I get a FOOxFOO desktop instead of a FOOxBAR desktop, provided that the specified FOOxBAR size is large enough to hold the proper desktop size, if not I get an error from xrandr. Hopefully the info I provided proves helpful, if you need any more please let me know. ~Loki -- 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 30

[Bug 230895] New: hotkey-setup & power button on compaq presario M2000 laptop
by bugzilla_noreply＠novell.com 15 Oct '08

15 Oct '08

https://bugzilla.novell.com/show_bug.cgi?id=230895 Summary: hotkey-setup & power button on compaq presario M2000 laptop Product: openSUSE 10.2 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Mobile Devices AssignedTo: behlert(a)novell.com ReportedBy: f.alabas(a)ttnet.net.tr QAContact: qa(a)suse.de Hotkeys on my laptop is all recognized well, except of Fn-F6 ($KEY_COFFEE) that is for simply locking the screen. It is not recognized when configuring as a input action or as a keyboard shortcut on KDE. In addition, power button is not responding although it has been configured as "wm_shutdown" in etc/sysconfig/poversave/events file. However this was already working at Suse Linux 10.1. -- 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