September 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 838804] New: mariadb-5.5.32-3.1 fails to start
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=838804 https://bugzilla.novell.com/show_bug.cgi?id=838804#c0 Summary: mariadb-5.5.32-3.1 fails to start Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Other 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 # 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 # /bin/systemctl start mysql.service returned 1 (unspecified error): # /bin/systemctl start mysql.service Job for mysql.service failed. See 'systemctl status mysql.service' and 'journalctl -xn' for details. # # 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-06 11:09:21 EST; 2min 13s ago Process: 3730 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE) Sep 06 11:08:51 test.site mysql[3730]: [72B blob data] Sep 06 11:08:51 test.site mysql[3730]: Fatal error in defaults handling. Program aborted Sep 06 11:08:51 test.site mysql[3730]: [52B blob data] Sep 06 11:08:51 test.site mysql[3730]: Fatal error in defaults handling. Program aborted Sep 06 11:09:21 test.site mysql[3730]: Starting service MySQL warning: /var/run/mysql/mysql.sock didn't appear within 30 seconds Sep 06 11:09:21 test.site mysql[3730]: chmod: cannot access '/var/run/mysql/mysqld.pid': No such file or directory Sep 06 11:09:21 test.site mysql[3730]: ..failed Sep 06 11:09:21 test.site systemd[1]: mysql.service: control process exited, code=exited status=1 Sep 06 11:09:21 test.site systemd[1]: Failed to start LSB: Start the MySQL database server. Sep 06 11:09:21 test.site systemd[1]: Unit mysql.service entered failed state. # Reproducible: Always Steps to Reproduce: 1.systemctl status mysql.service 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-06 11:09:21 EST; 2min 13s ago Process: 3730 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE) Sep 06 11:08:51 test.site mysql[3730]: [72B blob data] Sep 06 11:08:51 test.site mysql[3730]: Fatal error in defaults handling. Program aborted Sep 06 11:08:51 test.site mysql[3730]: [52B blob data] Sep 06 11:08:51 test.site mysql[3730]: Fatal error in defaults handling. Program aborted Sep 06 11:09:21 test.site mysql[3730]: Starting service MySQL warning: /var/run/mysql/mysql.sock didn't appear within 30 seconds Sep 06 11:09:21 test.site mysql[3730]: chmod: cannot access '/var/run/mysql/mysqld.pid': No such file or directory Sep 06 11:09:21 test.site mysql[3730]: ..failed Sep 06 11:09:21 test.site systemd[1]: mysql.service: control process exited, code=exited status=1 Sep 06 11:09:21 test.site systemd[1]: Failed to start LSB: Start the MySQL database server. Sep 06 11:09:21 test.site systemd[1]: Unit mysql.service entered failed state. Expected Results: mariadb sql prompt # 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 # -- 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 838180] New: error during balancing: <filesystem>: - No space left on device
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=838180 https://bugzilla.novell.com/show_bug.cgi?id=838180#c0 Summary: error during balancing: <filesystem>: - No space left on device Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: roeland(a)linux-it.nl 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 my nonprod laptop runs lvm/btrfs. learned from the past I do maintenance on the filesystems regularly; like deleting old snapshots, rebalance filesystems and so. Sometimes, when btrfs filesystem rebalance start <filesystem> is done, it errors out with the following error: ERROR: error during balancing '/usr' - No space left on device There may be more info in syslog - try dmesg | tail /usr also may be any other filesystem that uses btrfs. So far, all the times. resdoing the operation will end OK. Ergo, a second run would produce something like: Done, had to relocate 15 out of 15 chunks Reproducible: Sometimes Steps to Reproduce: 1. run btrfs filesystem rebalance start /usr 2. command dies 3. redo step 1 all OK grepping on "error" results in [206252.301386] btrfs: 16 enospc errors during balance. No other weird messages that gives me a clue -- 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 838688] New: perl-Bootloader does not work with btrfs as root filesystem
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=838688 https://bugzilla.novell.com/show_bug.cgi?id=838688#c0 Summary: perl-Bootloader does not work with btrfs as root filesystem Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader AssignedTo: jsrain(a)suse.com ReportedBy: kukuk(a)suse.com QAContact: jsrain(a)suse.com CC: stefan.fent(a)suse.com, snwint(a)suse.com, mchang(a)suse.com Found By: Development Blocker: Yes If I install todays build of openSUSE:Factory on btrfs as root filesystem, perl-Bootloader is not able to write the bootloader and the installer crashes. Cannot say since when this is broken, because since Milestone4 (including) today is the first day where you can create btrfs on root for installation again ... -- 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 838515] New: dkimproxy package has broken init script and is incorrectly packaged
by bugzilla_noreply＠novell.com 06 Sep '13

06 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=838515 https://bugzilla.novell.com/show_bug.cgi?id=838515#c0 Summary: dkimproxy package has broken init script and is incorrectly packaged Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: sum.notify(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 There are multiple problems with thee dkimproxy package that's in the stock openSUSE repository: 1) /etc/init.d/dkimproxy (line 87/88) test -f $DKIMPROXY_IN_CFG && $0 start-in || exit 0 test -f $DKIMPROXY_OUT_CFG && $0 start-out || exit 0 The idea behind this is to only start the in and out proxies if the configuration files exist. The "|| exit 0" is wrong an unnecessary. This means if there is no in-proxy configuration file, it won't even check to see if the out-proxy should start. It should be the following: test -f $DKIMPROXY_IN_CFG && $0 start-in test -f $DKIMPROXY_OUT_CFG && $0 start-out 2) The configuration file locations at the top need to be moved to /etc and should look (more) like the following: DKIMPROXY_IN_CFG="/etc/dkim/dkimproxy_in.conf" DKIMPROXY_OUT_CFG="/etc/dkim/proxy_out.conf" 3) And this gets us to the big problem. The entire layout for the package is bad. There is a /usr/share/dkimproxy/{etc,share,var}. The share directory shouldn't be replicated/nested, the init script should point to the real /var for the PID location and the init script should also reference /etc over the one in share. 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 1

[Bug 827097] New: Kaffeine 1.2.2 does not detect DVB USB hardware
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=827097 https://bugzilla.novell.com/show_bug.cgi?id=827097#c0 Summary: Kaffeine 1.2.2 does not detect DVB USB hardware Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Applications AssignedTo: kde-maintainers(a)suse.de ReportedBy: malte.gell(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 When you have a DVB-C USB stick like the Sundtek DVB-C stick it might happen Kaffeine 1.2.2 does not detect the stick and says "device not found". This error cannot be cured by restarting Kaffeine or reinstalling DVB drivers. It can only be cured by a patch for Kaffeine that was made available by Sundtek. Reproducible: Always Steps to Reproduce: 1. Connect DVB-C USB device to your computer 2. Start Kaffeine 1.2.2 Actual Results: Kaffeine will not see the DVB-C stick and will give an error "device not found" or "no device found". Expected Results: Kaffeine should detect the DVB-C device and start showing TV channels or radio stations over DVB. This bug is triggered every time you use a Sundtek DVB USB device with Kaffeine. Other DVB USB devices _may_ be affected as well. Sundtek DVB devices are fairly popular among Linux users due to its good Linux support. There is a patch available that cures the problem, the patch can be obtained from http://paste.opensuse.org/11289078 The attempt to include this patch directly into the kaffeine project has not been succesful, thus it may be the best way to include this patch on a distribution basis. This way Kaffeine in openSUSE will be able again to handle Sundtek DVB USB devices again and maybe other DVB hardware as well. -- 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 812528] New: Slovak localization date and numbers wrong
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=812528 https://bugzilla.novell.com/show_bug.cgi?id=812528#c0 Summary: Slovak localization date and numbers wrong Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hrach2(a)post.sk QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=532690) --> (http://bugzilla.novell.com/attachment.cgi?id=532690) Yast2 sound volume control dialog User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 Is State: Locale set to sk_SK.UTF-8 (/etc/sysconfig/language) When trying to set sound volume (YaST -> Sound -> Volume), dialog is opened with bad number type (not 0,1,2 etc. but some another type - see attachment) Problem is visible also in Dolphin (see Devices, HDD) and in Skype (there are used bad number types in dates) When in YaST is set en_US localization, numbers are shown correctly (in all mentioned cases) Using KDE.410 Reproducible: Always Steps to Reproduce: 1. Set locale in YaST to sk_SK See numbers and dates in YaST sound volume, Dolphin, skype (see details) Actual Results: Numbers and dates are shown with bad number type Expected Results: Numbers and dates are shown with digits 0,1,2 etc. Described behaviour is also commited in openSUSE 12.3 In both cases is used KDE 4.10 -- 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 34

[Bug 821064] New: locale setting LC_NUMERIC=sk_SK.UTF-8 cause wrong display of number in some QT4 widget
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=821064 https://bugzilla.novell.com/show_bug.cgi?id=821064#c0 Summary: locale setting LC_NUMERIC=sk_SK.UTF-8 cause wrong display of number in some QT4 widget Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: zdenop(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=540498) --> (http://bugzilla.novell.com/attachment.cgi?id=540498) example of wrong display for Slovak locale in QT4 app User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.32 (KHTML, like Gecko) Chrome/27.0.1425.0 Safari/537.32 SUSE/27.0.1425.0 My locale setting is LC_NUMERIC=sk_SK.UTF-8 and I found out it cause wrong display of numbers in some QT4 (and KDE4) widget e.g. QSpinBox. When I change it to LC_NUMERIC=cs_CZ.UTF-8 it is fixed Reproducible: Always Steps to Reproduce: 1. run 'LC_NUMERIC=sk_SK.UTF-8 qtconfig' 2. Check spinboxes in tab "Interface" (result in attachment QSpinbox-opensuse12.3-qt4.png) - there are some symbols instead of number 3. run 'LC_NUMERIC=cs_CZ.UTF-8 qtconfig' and numbers are displayed correctly -- 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 821016] New: kde does not remember video settings
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=821016 https://bugzilla.novell.com/show_bug.cgi?id=821016#c0 Summary: kde does not remember video settings Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: ohering(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Outsourced Testing Blocker: --- KDE does not seem to remember the display resolutions across reboots, something selects always the highest display resoltion. My CRT "LG 702BE" does 85Hz or 75Hz only at lower resolutions, the highest resoltion flickers at 60Hz. Its possible to adjust the resolution in the control center. But it does not stick, after a reboot the large resoltuion is active again. I think the system should remember the selected resoltion. -- 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 267903] KDM kcm module conflicts with /etc/sysconfig/displaymanager settings
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=267903 https://bugzilla.novell.com/show_bug.cgi?id=267903#c60 Hrvoje Senjan <hrvoje.senjan(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ianseeks(a)dsl.pipex.com --- Comment #60 from Hrvoje Senjan <hrvoje.senjan(a)gmail.com> 2013-09-05 23:21:42 UTC --- *** Bug 813459 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=813459 -- 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 813459] New: Invalid errors generated by kdm_config in /var/log/messages
by bugzilla_noreply＠novell.com 05 Sep '13

05 Sep '13

https://bugzilla.novell.com/show_bug.cgi?id=813459 https://bugzilla.novell.com/show_bug.cgi?id=813459#c0 Summary: Invalid errors generated by kdm_config in /var/log/messages Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: 64bit OS/Version: openSUSE 12.3 Status: NEW Severity: Minor Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: ianseeks(a)dsl.pipex.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=533511) --> (http://bugzilla.novell.com/attachment.cgi?id=533511) Grep of one days messages from /var/log/messages User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/534.34 (KHTML, like Gecko) konqueror/4.10.0 Safari/534.34 I've just been through my "/var/log/messages" file looking for some errors displayed (too fast to read) when booting up between grub and "kdm" login. I saw these comments in the "messages" so i checked the "/usr/share/kde4/config/kdm/kdmrc" file and there are no "multiple occurrences" of either sections or keys. 2013-04-04T09:10:40.555729+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of section [General] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. 2013-04-04T09:10:40.557071+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of section [X-*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. 2013-04-04T09:10:40.557251+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of section [X-*-Greeter] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. 2013-04-04T09:10:40.557452+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of key 'Language' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc 2013-04-04T09:10:40.557666+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of key 'ShowUsers' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc 2013-04-04T09:10:40.557870+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of key 'Theme' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc 2013-04-04T09:10:40.558049+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of key 'UseBackground' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc 2013-04-04T09:10:40.558223+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of key 'UseTheme' in section [X-*-Greeter] of /usr/share/kde4/config/kdm/kdmrc 2013-04-04T09:10:40.558399+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of section [X-:*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. 2013-04-04T09:10:40.558591+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of key 'AllowShutdown' in section [X-:*-Core] of /usr/share/kde4/config/kdm/kdmrc 2013-04-04T09:10:40.558775+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of section [X-:0-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. 2013-04-04T09:10:40.559581+01:00 linux-1b0m kdm_config[2160]: Multiple occurrences of key 'AutoLoginEnable' in section [X-:0-Core] of /usr/share/kde4/config/kdm/kdmrc I reported it on bugs.kde (https://bugs.kde.org/show_bug.cgi?id=317822) and its been suggested its reported to Opensuse as kdm_config has not been changed upstream for 10 years. Reproducible: Always Steps to Reproduce: 1. Reboot PC 2. 3. Actual Results: False error messages in /var/log/messages Expected Results: False error messages in /var/log/messages -- 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