November 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 841337] New: mariadb-5.5.32-3.1.x86_64 Fatal error in defaults handling. Program aborted
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=841337 https://bugzilla.novell.com/show_bug.cgi?id=841337#c0 Summary: mariadb-5.5.32-3.1.x86_64 Fatal error in defaults handling. Program aborted Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: doiggl(a)velocitynet.com.au QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 SeaMonkey/2.20 Hello. Got this on a fresh install of 13.1-Beta1 openSUSE-Factory-KDE-Live-Build0725-x86_64.iso # rpm -qa |grep -i mariadb |sort mariadb-5.5.32-3.1.x86_64 mariadb-client-5.5.32-3.1.x86_64 mariadb-errormessages-5.5.32-3.1.x86_64 # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: failed (Result: exit-code) since Fri 2013-09-20 02:14:58 EST; 5min ago Sep 20 02:14:57 test.site mysql[23525]: Fatal error in defaults handling. Program aborted Sep 20 02:14:58 test.site mysql[23525]: Installing MariaDB/MySQL system tables in '/var/lib/mysql' ... Sep 20 02:14:58 test.site mysql[23525]: [62B blob data] Sep 20 02:14:58 test.site mysql[23525]: Fatal error in defaults handling. Program aborted Sep 20 02:14:58 test.site mysql[23525]: Installation of system tables failed! Examine the logs in Sep 20 02:14:58 test.site mysql[23525]: /var/lib/mysql for more information. Sep 20 02:14:58 test.site mysql[23525]: The problem could be conflicting information in an external Sep 20 02:14:58 test.site systemd[1]: mysql.service: control process exited, code=exited status=1 Sep 20 02:14:58 test.site systemd[1]: Failed to start LSB: Start the MySQL database server. Sep 20 02:14:58 test.site systemd[1]: Unit mysql.service entered failed state. # journalctl -xn -- Logs begin at Thu 2013-09-19 20:59:00 EST, end at Fri 2013-09-20 02:20:01 EST. -- Sep 20 02:15:01 test.site systemd[23691]: Reached target Default. -- Subject: Unit UNIT has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished starting up. -- -- The start-up result is done. Sep 20 02:15:01 test.site systemd[23691]: Startup finished in 38ms. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- All system services necessary queued for starting at boot have been -- successfully started. Note that this does not mean that the machine is -- now idle as services might still be busy with completing start-up. -- -- Kernel start-up required KERNEL_USEC microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 38997 microseconds. Sep 20 02:15:01 test.site systemd[1]: Started User Manager for 30. -- Subject: Unit user(a)30.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user(a)30.service has finished starting up. -- -- The start-up result is done. Sep 20 02:15:01 test.site /USR/SBIN/CRON[23689]: pam_unix(crond:session): session closed for user root Sep 20 02:15:02 test.site /USR/SBIN/CRON[23690]: pam_unix(crond:session): session closed for user wwwrun Sep 20 02:20:01 test.site /usr/sbin/cron[23819]: pam_unix(crond:session): session opened for user wwwrun by (uid=0) Sep 20 02:20:01 test.site systemd[1]: Starting Session 35 of user wwwrun. -- Subject: Unit session-35.scope has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-35.scope has begun starting up. Sep 20 02:20:01 test.site systemd[1]: Started Session 35 of user wwwrun. -- Subject: Unit session-35.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-35.scope has finished starting up. -- -- The start-up result is done. Reproducible: Always Steps to Reproduce: 1.Install 13.1-Beta1 openSUSE-Factory-KDE-Live-Build0725-x86_64.iso 2.# rpm -qa |grep -i mariadb |sort mariadb-5.5.32-3.1.x86_64 mariadb-client-5.5.32-3.1.x86_64 mariadb-errormessages-5.5.32-3.1.x86_64 Actual Results: # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: failed (Result: exit-code) since Fri 2013-09-20 02:14:58 EST; 5min ago Sep 20 02:14:57 test.site mysql[23525]: Fatal error in defaults handling. Program aborted Sep 20 02:14:58 test.site mysql[23525]: Installing MariaDB/MySQL system tables in '/var/lib/mysql' ... Sep 20 02:14:58 test.site mysql[23525]: [62B blob data] Sep 20 02:14:58 test.site mysql[23525]: Fatal error in defaults handling. Program aborted Sep 20 02:14:58 test.site mysql[23525]: Installation of system tables failed! Examine the logs in Sep 20 02:14:58 test.site mysql[23525]: /var/lib/mysql for more information. Sep 20 02:14:58 test.site mysql[23525]: The problem could be conflicting information in an external Sep 20 02:14:58 test.site systemd[1]: mysql.service: control process exited, code=exited status=1 Sep 20 02:14:58 test.site systemd[1]: Failed to start LSB: Start the MySQL database server. Sep 20 02:14:58 test.site systemd[1]: Unit mysql.service entered failed state. # journalctl -xn -- Logs begin at Thu 2013-09-19 20:59:00 EST, end at Fri 2013-09-20 02:20:01 EST. -- Sep 20 02:15:01 test.site systemd[23691]: Reached target Default. -- Subject: Unit UNIT has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit UNIT has finished starting up. -- -- The start-up result is done. Sep 20 02:15:01 test.site systemd[23691]: Startup finished in 38ms. -- Subject: System start-up is now complete -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- All system services necessary queued for starting at boot have been -- successfully started. Note that this does not mean that the machine is -- now idle as services might still be busy with completing start-up. -- -- Kernel start-up required KERNEL_USEC microseconds. -- -- Initial RAM disk start-up required INITRD_USEC microseconds. -- -- Userspace start-up required 38997 microseconds. Sep 20 02:15:01 test.site systemd[1]: Started User Manager for 30. -- Subject: Unit user(a)30.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit user(a)30.service has finished starting up. -- -- The start-up result is done. Sep 20 02:15:01 test.site /USR/SBIN/CRON[23689]: pam_unix(crond:session): session closed for user root Sep 20 02:15:02 test.site /USR/SBIN/CRON[23690]: pam_unix(crond:session): session closed for user wwwrun Sep 20 02:20:01 test.site /usr/sbin/cron[23819]: pam_unix(crond:session): session opened for user wwwrun by (uid=0) Sep 20 02:20:01 test.site systemd[1]: Starting Session 35 of user wwwrun. -- Subject: Unit session-35.scope has begun with start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-35.scope has begun starting up. Sep 20 02:20:01 test.site systemd[1]: Started Session 35 of user wwwrun. -- Subject: Unit session-35.scope has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit session-35.scope has finished starting up. -- -- The start-up result is done. Expected Results: mariadb-5.5.32-3.1.x86_64 starts ok -- 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 813914] New: MySQL / MariaDB don't start at system startup
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=813914 https://bugzilla.novell.com/show_bug.cgi?id=813914#c0 Summary: MySQL / MariaDB don't start at system startup Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: dev(a)lachner-net.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 I use the default installation for MySQL on openSUSE 12.3. So this error happens with MariaDB. I didn't try it with the original MySQL. I can start MySQL with the Yast2 runlevel editor an I can start it with rcmysql start. But at reboot, MySQL don't start automatically. Reproducible: Always Steps to Reproduce: 1. Activate MySQL in Yast2 runlevel editor. 2. MySQL works. 3. Restart computer. 4. MySQL don't start at boot. -- 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 844113] New: MySQL (MariaDB) fails to start
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=844113 https://bugzilla.novell.com/show_bug.cgi?id=844113#c0 Summary: MySQL (MariaDB) fails to start Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86 OS/Version: SUSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: lpwevers(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 On a clean installation, MySQL fails to start. Error details are below: # systemctl status mysql.service mysql.service - LSB: Start the MySQL database server Loaded: loaded (/etc/init.d/mysql) Active: failed (Result: exit-code) since Fri 2013-10-04 18:37:05 CEST; 3min 52s ago Process: 26621 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE) Oct 04 18:36:35 mail mysql[26621]: Will update MySQL now, if you encounter any problems, please read following file: Oct 04 18:36:35 mail mysql[26621]: /usr/share/doc/packages/mariadb/README.SuSE Oct 04 18:36:35 mail mysql[26621]: Log files inconsistency, please merge following files manually: Oct 04 18:36:35 mail mysql[26621]: Running protected MySQL... Oct 04 18:37:05 mail mysql[26621]: error: /var/tmp/mysql-protected.rIJZeJ/mysql.sock file didn't appeared... Oct 04 18:37:05 mail mysql[26621]: Try checking "/var/log/mysql/mysqld-upgrade-run.log"... Oct 04 18:37:05 mail systemd[1]: mysql.service: control process exited, code=exited status=1 Oct 04 18:37:05 mail systemd[1]: Failed to start LSB: Start the MySQL database server. Oct 04 18:37:05 mail systemd[1]: Unit mysql.service entered failed state. So, checking /var/log/mysql/mysqld-upgrade-run.log I get: 131004 18:36:36 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql 131004 18:36:36 InnoDB: The InnoDB memory heap is disabled 131004 18:36:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins 131004 18:36:36 InnoDB: Compressed tables use zlib 1.2.8 131004 18:36:36 InnoDB: Using Linux native AIO 131004 18:36:36 InnoDB: Initializing buffer pool, size = 128.0M 131004 18:36:36 InnoDB: Completed initialization of buffer pool InnoDB: Error: log file ./ib_logfile0 is of different size 0 50331648 bytes InnoDB: than specified in the .cnf file 0 5242880 bytes! 131004 18:36:36 [ERROR] Plugin 'InnoDB' init function returned error. 131004 18:36:36 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 131004 18:36:36 [ERROR] Unknown/unsupported storage engine: InnoDB 131004 18:36:36 [ERROR] Aborting 131004 18:36:36 [Note] /usr/sbin/mysqld: Shutdown complete 131004 18:36:36 mysqld_safe mysqld from pid file /var/tmp/mysql-protected.rIJZeJ/mysqld.pid ended Reproducible: Always Steps to Reproduce: 1. Install MySQL 2. Start it 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 2

[Bug 849017] New: fix online update dialog during installation
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=849017 https://bugzilla.novell.com/show_bug.cgi?id=849017#c0 Summary: fix online update dialog during installation Classification: openSUSE Product: openSUSE 13.1 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: jsuchome(a)suse.com ReportedBy: jdsn(a)suse.com QAContact: jsrain(a)suse.com Found By: Development Blocker: --- The dialog that asks during the installation if an online update should be run is left aligned and thus ugly. Having it centered is much nicer. A possible fix is in this pull request: https://github.com/yast/yast-installation/pull/92 This pull request is for the master branch. Anyhow, if possible it should be cherry-picked also to the openSUSE-13_1 branch (at least if there will be a new package for yast2-installation anyway). -- 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 842264] New: Starting mysql kills all permissions in /usr
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=842264 https://bugzilla.novell.com/show_bug.cgi?id=842264#c0 Summary: Starting mysql kills all permissions in /usr Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: All OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mhrusecky(a)suse.com ReportedBy: jengelh(a)inai.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- If you have /etc/my.cnf: log-bin=mysql-bin.log log-bin-index=mysql.log.index log-error=log.error.log that is, non-absolute paths, /etc/init.d/mysql will foolishly chown all of /usr to mysql:mysql because /usr happens to be the script's CWD. /etc/init.d/mysql tries to be overly smart (it should not) and does: 1. parse the mysql command line which it probably should not 68: --log-error=*) log_error="`echo "$arg" | sed -e 's/^[^=]*=//'`" 2. attempt to determine the directory of the particular file 329: log_dir="`dirname "$i"`" Because "$i" equals "log.error.log", `dirname "$i"` will be ".". That is BAD BAD BAD. 3. chowns everything. chmod 770 "$log_dir" chown -R --no-dereference mysql:mysql "$log_dir" 4. Almost everything in the system fails. Now, whether my.cnf should have relative paths is another question, but putting them there causes severe havoc. -- 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 668173] New: [SMBTA] WebYast module to control smbtad
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=668173 https://bugzilla.novell.com/show_bug.cgi?id=668173#c0 Summary: [SMBTA] WebYast module to control smbtad Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: Samba AssignedTo: bgeuken(a)novell.com ReportedBy: hhetter(a)novell.com QAContact: samba-maintainers(a)SuSE.de CC: hhetter(a)novell.com, mhaefner(a)novell.com, bbrunner(a)novell.com Found By: --- Blocker: --- During hackweek Björn took a look at SMBTA and made first steps to create a webyast module to control smbtad, which would be a killer feature for sure. Lots of IRC communication has passed. This stuff is totally in development, and no timeline or anything similar can be given at the moment. I created this bug for us to track the status of that idea, and of course this bug will not be blocking any release tracker bug. Stored as "Enhancement". I would be happy if Björn would update the status of this development in this bug from time to 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.

1 9

[Bug 843718] kiwi: missing patch: use kpartx sync mode to make sure devices are created
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843718 https://bugzilla.novell.com/show_bug.cgi?id=843718#c15 --- Comment #15 from Adrian Schröter <adrian(a)suse.com> 2013-11-06 10:48:26 UTC --- Just for reference, these are the kernel modules which we already preload on our standard workers, so they should be available: loop dm-mod dm-snapshot binfmt_misc fuse squashfs ext3 ext4 reiserfs btrfs virtio_pci virtio_blk fat vfat nf_conntrack_ipv6 fat vfat I dunno if LVM may need more, but there is also no proof yet that it is a missing kernel module. So some test case is with debug tracing is really needed here. (At some point in time I really want to switch to use the distro kernel, which can load modules also, but in the past they were way to broken to work within VMs). -- 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 843718] kiwi: missing patch: use kpartx sync mode to make sure devices are created
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=843718 https://bugzilla.novell.com/show_bug.cgi?id=843718#c14 --- Comment #14 from Ruediger Oertel <ro(a)suse.com> 2013-11-06 10:33:15 UTC --- relying on udev is just a really bad idea. in this case the udev rules simply do not trigger as the kernel modules are not available, next time is something else and you can at best get this working in a VM and not in any other solution like lxc or chroot. Any device nodes needed have to be created by the tools creating the action and not by some external daemon that may or may not work. -- 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 834967] New: after update to mysql-community-server 5.5.32 chown mysql:mysql run over /usr/bin and make system unusable
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=834967 https://bugzilla.novell.com/show_bug.cgi?id=834967#c0 Summary: after update to mysql-community-server 5.5.32 chown mysql:mysql run over /usr/bin and make system unusable Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 32bit OS/Version: openSUSE 12.3 Status: NEW Severity: Critical Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ctype(a)mail.ru QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:22.0) Gecko/20100101 Firefox/22.0 AlexaToolbar/alxf-2.18 after update to mysql-community-server 5.5.32 system become unstable and after reboot can be accessed only via console by root Reproducible: Always Steps to Reproduce: 1.automatic update has installed update of mysql Actual Results: files in /usr/bin become owned by mysql:mysql -- 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 18

[Bug 842346] New: ivtv-firmware package is missing in 13.1beta - causing ivtv driver to fail (easy solution)
by bugzilla_noreply＠novell.com 06 Nov '13

06 Nov '13

https://bugzilla.novell.com/show_bug.cgi?id=842346 https://bugzilla.novell.com/show_bug.cgi?id=842346#c0 Summary: ivtv-firmware package is missing in 13.1beta - causing ivtv driver to fail (easy solution) Classification: openSUSE Product: openSUSE Factory Version: 13.1 Beta 1 Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: johanp(a)aditus.nu QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 When installing the standard ivtv driver package the most common firmware (v4l-cx2341x) which is needed for Hauppauge analogue TV-cards (e.g. 150 and 350) is missing. The firmware that does exist (e.g. 4l-cx23418-apu.fw, etc.) seems to be contained in a separate RPM "kernel-firmware-20130714git-1.2.noarch" The firmware that is missing was previously (in OpenSuSE 12.3) included in package "ivtv-firmware" but this package seems to be missing in 13.1beta So the solution is simple, either re-introduce package "ivtv-firmare" or add the missing files to package "kernel-firmware-20130714git-1.2.noarch" Note: The latest firmware can be found at http://dl.ivtvdriver.org/ivtv/firmware/ivtv-firmware.tar.gz Reproducible: Always Steps to Reproduce: 1. Try to load the ivtv module with modprobe ivtv 2. Look at dmesg where error message about missing firmware is seen 3. Actual Results: Error messages: [ 8339.635660] ivtv-alsa: module loading... [ 8339.964127] ivtv0: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes) [ 8339.964132] ivtv0: Did you put the firmware in the hotplug firmware directory? [ 8339.964134] ivtv0: Retry loading firmware [ 8340.251937] ivtv1: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes) [ 8340.251941] ivtv1: Did you put the firmware in the hotplug firmware directory? [ 8340.251944] ivtv1: Retry loading firmware [ 8340.583802] ivtv0: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes) [ 8340.583808] ivtv0: Did you put the firmware in the hotplug firmware directory? [ 8340.583812] ivtv0: Failed to initialize on device video0 [ 8340.584281] ivtv0: Failed to initialize on device video32 [ 8340.584341] ivtv0: Failed to initialize on device vbi0 [ 8340.584361] ivtv0: Failed to initialize on device video24 [ 8340.584477] ivtv0: Failed to initialize on device radio0 [ 8340.871569] ivtv1: Unable to open firmware v4l-cx2341x-enc.fw (must be 376836 bytes) [ 8340.871575] ivtv1: Did you put the firmware in the hotplug firmware directory? [ 8340.871579] ivtv1: Failed to initialize on device video1 [ 8340.872227] ivtv1: Failed to initialize on device video33 [ 8340.872286] ivtv1: Failed to initialize on device video25 [ 8340.872307] ivtv1: Failed to initialize on device video17 [ 8340.872419] ivtv1: Failed to initialize on device radio1 [ 8340.874569] ivtv1: Failed to initialize on device vbi1 Expected Results: That the video device works as expected. Add the missing package from 12.3 repo since this firmware is architecture independent. Since this fault completely breaks the handling of video cards this could be considered a major 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