March 2009 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 476298] New: Creating an NTP Server in Yast and Selecting Open Firewall Does Not Add NTP Services to Allowed Services List in the Firewall
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=476298 Summary: Creating an NTP Server in Yast and Selecting Open Firewall Does Not Add NTP Services to Allowed Services List in the Firewall Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: openSUSE 11.0 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: alpha096(a)virginbroadband.com.au QAContact: jsrain(a)novell.com Found By: --- Created an attachment (id=273130) --> (https://bugzilla.novell.com/attachment.cgi?id=273130) 1 of 2 images User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6 If we create a Public NTP Server via Yast ans we select Open Firewall in the Securities Options the NTP Service Permissions is not added to the list of Allowed Services Reproducible: Always Steps to Reproduce: 1.Yast 2.Network Services 3.NTP Server 4.Creat Public NTP Server and open Firewall option. Actual Results: NTP Services are not automatically added to allowed services so the NTP Server will never test or function at all Expected Results: When the Open Firewall Box is checked the NTP Server should be auto added to the Firewall's Allowed Services -- 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 479005] New: bluetooth-applet shouldn't specify pairing code
by bugzilla_noreply＠novell.com 01 Apr '09

01 Apr '09

https://bugzilla.novell.com/show_bug.cgi?id=479005 Summary: bluetooth-applet shouldn't specify pairing code Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: i686 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: riggwelter(a)opensuse.org QAContact: qa(a)suse.de Found By: --- When pairing with a device that requires a code, bluetooth-applet tells you the code to use rather than the old behaviour of asking the user to specify it. This is fine when pairing with a device such as a phone which asks the user for the code. The problem comes when pairing with a device with no input facility - such as speakers. These have their own hard-coded codes which makes it impossible to pair with them. -- 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 8

[Bug 479622] New: Display becomes corrupt after whiching to battery, if booting up on battery X hangs.
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=479622 Summary: Display becomes corrupt after whiching to battery, if booting up on battery X hangs. Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Critical Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jefowler(a)hughes.net QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1.2 Firefox/3.0.6 I have the following hardware: Compaq 6910p with ATI X2300 video display. I am currently using the ATI Catalyst 9.2 driver, problem was manifest in 9.1 driver, problem can be seen in the opensource drivers radeon, OSS radeonhd, and vesa drivers. Did not have issue prior to upgrading to 11.1, worked okay with 11.0 and 10.2. Basically, if I am on ac power everything is working okay. Once I unplug the AC power, the screen starts to become corrupt, until it is an unusable grabage screen. If I try to boot up on AC power, once X server starts the system will hang, and lock up. Can not do anything but a hard power off to get back control of the system. Also during the lock the fans will kick on full speed. Which would give the impress of something hung in a loop and using up all the cpu. Tested the power up issue, had the system boot to runlevel 3, and then modified xorg.conf to use the radeon, radeonhd, and vesa drivers saw same issue, when startx was issued. Reproducible: Always Steps to Reproduce: 1.If on ac power unplug ac and screen will start to corrupt. 2.Power up without AC power, and X will hang as soon as it starts. 3.Tested the power up issue, with radeon, radeonhd, and vesa drivers Actual Results: Nothing special here simple unplug the ac power and screen corruption will begin immediately. Same for booting without AC power. Expected Results: This should function as it did before, with the 11.0, and 10.2 versions of opensuse. do not have a serial port on the laptop, and so far have not been able to login remotely either. System appears to be hung solid. Have performed a reinstall from scratch did not resolve issue. Unforunately, since it is present in the open source drivers switching to them did does not help. Also using the open source ones for some reason X becomes unstable, and can hang during normal use. -- 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 490866] New: kernel: devel suggestion improvement
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490866 Summary: kernel: devel suggestion improvement Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: All OS/Version: Linux Status: NEW Severity: Enhancement Priority: P5 - None Component: Kernel AssignedTo: jblunck(a)novell.com ReportedBy: jengelh(a)medozas.de QAContact: qa(a)suse.de CC: dgollub(a)novell.com Found By: Beta-Customer I did the following change because it makes searching for faulty patches much easier. Just wanted to bring it to your attention. *** and somewhere add BuildRequires: quilt --- a/rpm/kernel-binary.spec.in +++ b/rpm/kernel-binary.spec.in @@ -253,10 +253,8 @@ cd linux-@SRCVERSION@ # Apply the patches needed for this architecture. %if ! %build_vanilla for patch in $(%_sourcedir/guards %symbols < %_sourcedir/series.conf); do - if ! patch -s -F0 -E -p1 --no-backup-if-mismatch -i ../$patch; then - echo "*** Patch $patch failed ***" - exit 1 - fi + quilt import "../$patch"; + quilt push || exit 1; done %else for patch in $(%_sourcedir/guards %symbols < %_sourcedir/series.conf | egrep ke On a related note, I could have also used git because it has true bisect (with quilt you have to calculate the steps yourself), but making a git tree out of it... takes its time sometimes. -- 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 457046] New: documentation for apparmor included twice and confusingly packaged ...
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=457046 Summary: documentation for apparmor included twice and confusingly packaged ... Product: openSUSE 11.1 Version: RC 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Documentation AssignedTo: ke(a)novell.com ReportedBy: felix(a)derklecks.de QAContact: ke(a)novell.com Found By: --- I was just looking for apparmor documentation and found two packages: # zypper se -s apparmor-admin_en-pdf Daten des Repositorys laden... Installierte Pakete lesen... S | Name | Typ | Version | Arch | Repository --+--------------------------------+-------+-----------+--------+----------- i | apparmor-admin_en-pdf | Paket | 10.3-8.86 | noarch | oss i | opensuse-apparmor-admin_en-pdf | Paket | 11.1-28.2 | noarch | oss # rpm -ql apparmor-admin_en-pdf opensuse-apparmor-admin_en-pdf /usr/share/doc/manual /usr/share/doc/manual/apparmor-admin_en-pdf /usr/share/doc/manual/apparmor-admin_en-pdf/APPARMOR-admin_en.pdf /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/LICENSE.txt /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/opensuse-apparmor-admin_en.pdf The supposingly SLES documentation has the following pdf metadata: fm@macbook:~> pdfinfo /usr/share/doc/manual/apparmor-admin_en-pdf/APPARMOR-admin_en.pdf | head -n 3 Title: openSUSE Documentation Author: Unknown Creator: Unknown The openSUSE one has: fm@macbook:~> pdfinfo /usr/share/doc/manual/opensuse-apparmor-admin_en-pdf/opensuse-apparmor-admin_en.pdf | head -n 3 Title: Documentation Author: SUSE Creator: DocBook V1.74.0 So are really two packages needed? And at least the title of APPARMOR-admin_en.pdf is wrong ... -- 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 488928] New: Konqueror 4.2 forgets cookies after reboot. Also, Google account cannot be accessed.
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=488928 Summary: Konqueror 4.2 forgets cookies after reboot. Also, Google account cannot be accessed. Classification: openSUSE Product: openSUSE 11.2 Version: Factory Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Major Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: adrian.ioan.cozma(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (compatible; Konqueror/4.2; Linux 2.6.27.19-3.2-default; X11; x86_64; en-US, en) KHTML/4.2.1 (like Gecko) SUSE I'm using KDE 4.2 and I usually manually update every 1 or 2 days from factory. There is over a month now cookies have started to live (and mostly die) after their own rule. It started with me not being able to access my Google Account (and subsequently the Gmail web interface) from Konqueror (FF works flawlessly). I can log in to Google (i.e. at google.com, and the search history is recorded), but the log in to account page (google.com/accounts/ManageAccount) keeps redirecting to itself. The weirdest thing had yet to be observed: all (or almost all) cookies disappear after rebooting, with no respect to the diff settings I've tried. The remembered cookies (if any then they are very few) are from random sites, and it seems there is no pattern related to the domain name. Konqueror's site policies are remembered, but in Konqueror>Settings>Cookies>Management the list is (almost) virgin after each reboot. As a consequence, I have to relog in to any site I need to after reboot (including those hosted on localhost). Gmail web interface and Google account pages cannot be accessed with Konqueror whatsoever. Reproducible: Always Steps to Reproduce: 1. Just reboot. Actual Results: Konqueror's cookie list is empty or, at best, it contains only a very small number of the cookies existing prior to the reboot. Expected Results: Not to forget the cookies after reboot. I wasn't sure if to fill a report or not. But after a month, someone replied to my post at openSUSE forums saying he faces the same problem. -- 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 490055] New: every boot: NetworkManager crashes
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490055 Summary: every boot: NetworkManager crashes Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jnelson-suse(a)jamponi.net QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7 Starting today (29 March 2009) NetworkManager crashes at boot requiring me to 'rcnetwork restart' every time. Crash backtrace included: Mar 29 22:23:37 worklaptop NetworkManager: <info> starting... Mar 29 22:23:37 worklaptop NetworkManager: <info> Trying to start the modem-manager... Mar 29 22:23:37 worklaptop NetworkManager: <info> Waiting for HAL to start... Mar 29 22:23:37 worklaptop NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess Mar 29 22:23:37 worklaptop NetworkManager: <info> Trying to start the supplicant... Mar 29 22:23:37 worklaptop NetworkManager: <info> Trying to start the system settings daemon... Mar 29 22:23:37 worklaptop NetworkManager: <info> modem manager appeared Mar 29 22:23:37 worklaptop NetworkManager: <info> modem manager disappeared Mar 29 22:23:37 worklaptop NetworkManager: <info> Trying to start the modem-manager... Mar 29 22:23:37 worklaptop NetworkManager: <info> modem manager appeared Mar 29 22:23:37 worklaptop NetworkManager: <info> modem manager disappeared Mar 29 22:23:37 worklaptop NetworkManager: <info> Trying to start the modem-manager... Mar 29 22:23:37 worklaptop NetworkManager: <info> modem manager appeared Mar 29 22:23:37 worklaptop NetworkManager: <info> modem manager disappeared Mar 29 22:23:37 worklaptop NetworkManager: <info> Trying to start the modem-manager... Mar 29 22:23:38 worklaptop NetworkManager: <info> modem manager appeared Mar 29 22:23:38 worklaptop NetworkManager: <info> modem manager disappeared Mar 29 22:23:38 worklaptop NetworkManager: <info> Trying to start the modem-manager... Mar 29 22:23:38 worklaptop NetworkManager: <info> modem manager appeared Mar 29 22:23:38 worklaptop NetworkManager: <info> modem manager disappeared Mar 29 22:23:38 worklaptop NetworkManager: <info> Trying to start the modem-manager... Mar 29 22:23:38 worklaptop NetworkManager: <info> modem manager appeared Mar 29 22:23:38 worklaptop NetworkManager: <WARN> nm_signal_handler(): Caught signal 6. Generating backtrace... Mar 29 22:23:38 worklaptop NetworkManager: ******************* START ********************************** Mar 29 22:23:41 worklaptop NetworkManager: (no debugging symbols found) Mar 29 22:23:41 worklaptop NetworkManager: [Thread debugging using libthread_db enabled] Mar 29 22:23:42 worklaptop NetworkManager: 0x00007f354271e575 in waitpid () from /lib64/libpthread.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #0 0x00007f354271e575 in waitpid () from /lib64/libpthread.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #1 0x000000000042ed43 in nm_logging_backtrace () Mar 29 22:23:42 worklaptop NetworkManager: #2 0x0000000000429d20 in ?? () Mar 29 22:23:42 worklaptop NetworkManager: #3 <signal handler called> Mar 29 22:23:42 worklaptop NetworkManager: #4 0x00007f35421e5645 in raise () from /lib64/libc.so.6 Mar 29 22:23:42 worklaptop NetworkManager: #5 0x00007f35421e6c33 in abort () from /lib64/libc.so.6 Mar 29 22:23:42 worklaptop NetworkManager: #6 0x00007f3543ba6203 in g_assertion_message () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #7 0x00007f3543ba66a2 in g_assertion_message_expr () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #8 0x00007f35444b8b31 in unassociate_proxies (key=<value optimized out>, Mar 29 22:23:42 worklaptop NetworkManager: val=<value optimized out>, user_data=<value optimized out>) Mar 29 22:23:42 worklaptop NetworkManager: at dbus-gproxy.c:661 Mar 29 22:23:42 worklaptop NetworkManager: #9 0x00007f3543b71e3d in g_hash_table_foreach () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #10 0x00007f35444b9556 in dbus_g_proxy_manager_filter ( Mar 29 22:23:42 worklaptop NetworkManager: connection=<value optimized out>, message=0x67bb00, user_data=0x67d0f0) Mar 29 22:23:42 worklaptop NetworkManager: at dbus-gproxy.c:748 Mar 29 22:23:42 worklaptop NetworkManager: #11 0x00007f354405f86b in dbus_connection_dispatch () Mar 29 22:23:42 worklaptop NetworkManager: from /lib64/libdbus-1.so.3 Mar 29 22:23:42 worklaptop NetworkManager: #12 0x00007f35444b01c5 in message_queue_dispatch ( Mar 29 22:23:42 worklaptop NetworkManager: source=<value optimized out>, callback=<value optimized out>, Mar 29 22:23:42 worklaptop NetworkManager: user_data=<value optimized out>) at dbus-gmain.c:101 Mar 29 22:23:42 worklaptop NetworkManager: #13 0x00007f3543b800db in g_main_context_dispatch () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #14 0x00007f3543b838ad in ?? () from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #15 0x00007f3543b83ddd in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: #16 0x000000000042a49e in main () Mar 29 22:23:42 worklaptop NetworkManager: Mar 29 22:23:42 worklaptop NetworkManager: Thread 1 (Thread 0x7f3545358740 (LWP 3305)): Mar 29 22:23:42 worklaptop NetworkManager: #0 0x00007f354271e575 in waitpid () from /lib64/libpthread.so.0 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #1 0x000000000042ed43 in nm_logging_backtrace () Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #2 0x0000000000429d20 in ?? () Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #3 <signal handler called> Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #4 0x00007f35421e5645 in raise () from /lib64/libc.so.6 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #5 0x00007f35421e6c33 in abort () from /lib64/libc.so.6 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #6 0x00007f3543ba6203 in g_assertion_message () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #7 0x00007f3543ba66a2 in g_assertion_message_expr () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #8 0x00007f35444b8b31 in unassociate_proxies (key=<value optimized out>, Mar 29 22:23:42 worklaptop NetworkManager: val=<value optimized out>, user_data=<value optimized out>) Mar 29 22:23:42 worklaptop NetworkManager: at dbus-gproxy.c:661 Mar 29 22:23:42 worklaptop NetworkManager: manager = (DBusGProxyManager *) 0x67d0f0 Mar 29 22:23:42 worklaptop NetworkManager: Mar 29 22:23:42 worklaptop NetworkManager: tmp = (GSList *) 0x673790 Mar 29 22:23:42 worklaptop NetworkManager: data = (DBusGProxyUnassociateData *) 0x7fff4d389850 Mar 29 22:23:42 worklaptop NetworkManager: Mar 29 22:23:42 worklaptop NetworkManager: #9 0x00007f3543b71e3d in g_hash_table_foreach () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #10 0x00007f35444b9556 in dbus_g_proxy_manager_filter ( Mar 29 22:23:42 worklaptop NetworkManager: connection=<value optimized out>, message=0x67bb00, user_data=0x67d0f0) Mar 29 22:23:42 worklaptop NetworkManager: at dbus-gproxy.c:748 Mar 29 22:23:42 worklaptop NetworkManager: Mar 29 22:23:42 worklaptop NetworkManager: Mar 29 22:23:42 worklaptop NetworkManager: Mar 29 22:23:42 worklaptop NetworkManager: dummy3 = 0, Mar 29 22:23:42 worklaptop NetworkManager: padding1 = 0x7f354428d878} Mar 29 22:23:42 worklaptop NetworkManager: tri = <value optimized out> Mar 29 22:23:42 worklaptop NetworkManager: full_list = <value optimized out> Mar 29 22:23:42 worklaptop NetworkManager: tmp = <value optimized out> Mar 29 22:23:42 worklaptop NetworkManager: sender = <value optimized out> Mar 29 22:23:42 worklaptop NetworkManager: Mar 29 22:23:42 worklaptop NetworkManager: #11 0x00007f354405f86b in dbus_connection_dispatch () Mar 29 22:23:42 worklaptop NetworkManager: from /lib64/libdbus-1.so.3 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #12 0x00007f35444b01c5 in message_queue_dispatch ( Mar 29 22:23:42 worklaptop NetworkManager: source=<value optimized out>, callback=<value optimized out>, Mar 29 22:23:42 worklaptop NetworkManager: user_data=<value optimized out>) at dbus-gmain.c:101 Mar 29 22:23:42 worklaptop NetworkManager: connection = (DBusConnection *) 0x679f30 Mar 29 22:23:42 worklaptop NetworkManager: #13 0x00007f3543b800db in g_main_context_dispatch () Mar 29 22:23:42 worklaptop NetworkManager: from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #14 0x00007f3543b838ad in ?? () from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #15 0x00007f3543b83ddd in g_main_loop_run () from /usr/lib64/libglib-2.0.so.0 Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: #16 0x000000000042a49e in main () Mar 29 22:23:42 worklaptop NetworkManager: No symbol table info available. Mar 29 22:23:42 worklaptop NetworkManager: The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] Mar 29 22:23:42 worklaptop NetworkManager: ******************* END ********************************** Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 4

[Bug 486762] New: There is no way to eject an (empty) CD on MacPro
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=486762 Summary: There is no way to eject an (empty) CD on MacPro Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: BastisEmail(a)yahoo.de QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.0.6) Gecko/2009012700 SUSE/3.0.6-0.1 Firefox/3.0.6 There is no chance to eject an empty CD jack in a MacintoshPro. The drive does not have any button - it must be controlled by the operating system. openSuse does have trouble in finding the correct keyboard layout. There is not chance to use the "eject" key on the keyboard! Btw: On Ubuntu 8.10, the correct keyboard layout is chosen and the "eject" key is AUTOMATICALLY linked with an app that ejects/closes the CD ROM drive! Reproducible: Always Steps to Reproduce: 1. 2. 3. -- 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 486554] New: Kernel 2.6.27.19-3.2 Unable to access machine after a day or so, but all VMs continue to function normally
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=486554 Summary: Kernel 2.6.27.19-3.2 Unable to access machine after a day or so, but all VMs continue to function normally Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: x86-64 OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: bdarlt(a)gmail.com QAContact: qa(a)suse.de Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.6) Gecko/2009020414 CentOS/3.0.6-1.el5.centos Firefox/3.0.6 I recently installed OpenSuSe 11.1 to run a few VMs we had running on an OpenSuSe 10.2 machine. I started all the VMs on the 11.1 one machine, and all seemed well. A few days later I tried to access the machine (Dom0) and ssh just hung. So I tried the serial console, and logged in and got a shell. The first thing I ran hung the serial console, and nothing would unhang it. I attempted sysrq, but I am not sure if that was enabled, or if my iLO2 was passing it along. I found Bug 463372 - Kernel 2.6.27.7 SuSE file monitoring serious bug (inotify) , which sounds very similar what I am experiencing. Except I am not running Samba or Dovecot. But I am running the xen kernel. All VMs on the machine behaved the way they should during the week that I couldn't access their Dom0 (I had to wait for a scheduled time to move VMs and reboot the Dom0). I am happy to debug and try things, but am unsure how to recreate the hang. All system logs just stopped, so I couldn't see anything out of the ordinary. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Expected Results: The machine should have remained accessible. We have 2 Dual-Core AMD Opteron(tm) Processor 2216 HE The machine (Dom0) in question is a blade, HP ProLiant BL465c G1 -- 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 490792] New: k3b cannot open /dev/sr0 if blank media is inserted
by bugzilla_noreply＠novell.com 31 Mar '09

31 Mar '09

https://bugzilla.novell.com/show_bug.cgi?id=490792 User steffen.sobiech(a)gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=490792#c408252 Summary: k3b cannot open /dev/sr0 if blank media is inserted Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: All OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: steffen.sobiech(a)gmx.de QAContact: qa(a)suse.de Found By: --- Created an attachment (id=283244) --> (https://bugzilla.novell.com/attachment.cgi?id=283244) output of lshal User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.7) Gecko/2009022800 SUSE/3.0.7-1.1.6 Firefox/3.0.7 K3b cannot open /dev/sr0 if a blank medium (CD-R, DVD-R) is inserted prior to starting k3b. This one _could_ be a duplicate of bug #408252, but I'm using the updated hal and the problem seems to persist. hal-0.5.12-10.13.1 k3b-1.0.5-48.22 (KDE 3.5.10) Reproducible: Always Steps to Reproduce: 1. Insert blank CD-R or DVD-R into writer drive 2. start k3b Actual Results: k3b complains about not being able to access the writer device anymore Expected Results: k3b should be able to burn cds and dvds :) -- 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