April 2010 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 594482] New: grub config not using uuid
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=594482 http://bugzilla.novell.com/show_bug.cgi?id=594482#c0 Summary: grub config not using uuid Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: juhliarik(a)novell.com ReportedBy: aschnell(a)novell.com QAContact: jsrain(a)novell.com Found By: Development Blocker: --- I have changed /etc/sysconfig/storage to mount by uuid per default before YaST starts during installation. /etc/fstab used uuid but /boot/grub/menu.lst does not. Maybe bootloader config uses an old target-map. The uuid is only known after creating the filesystems. -- Configure bugmail: http://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 594393] New: need /usr/lib/news/bin/innbind in permissions
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=594393 http://bugzilla.novell.com/show_bug.cgi?id=594393#c0 Summary: need /usr/lib/news/bin/innbind in permissions Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: lnussel(a)novell.com ReportedBy: mls(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- In inn-2.5, inndstart and startinnfeed were removed, innd and nnrpd call a new setuid root binary called innbind. Thus, please add: /usr/lib/news/bin/innbind root:news 4554 I don't know if we should leave the startinnfeed/inndstart entries so that customers can use an old version as well. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 593946] New: HAL is deprecated: remove its usage for printing and scanning
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=593946 http://bugzilla.novell.com/show_bug.cgi?id=593946#c0 Summary: HAL is deprecated: remove its usage for printing and scanning Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: All OS/Version: openSUSE 11.3 Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: Other AssignedTo: jsmeix(a)novell.com ReportedBy: jsmeix(a)novell.com QAContact: qa(a)suse.de Found By: Development Blocker: --- HAL was used for printing and scanning to grant the currently logged in "desktop" user read/write device access permissions for scanners (also for scanners in all-in-one devices). HAL is deprecated and does no longer support this functionality. Therefore HAL related stuff in printing and scanning packages can be removed in particular: HAL related code in yast2-scanner. HAL related stuff in sane-backends. HAL related stuff in HPLIP. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 7

[Bug 593833] New: gmixer does not have OnlyShowIn line in /etc/xdg/autostart/gmixer-trayicon.desktop
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=593833 http://bugzilla.novell.com/show_bug.cgi?id=593833#c0 Summary: gmixer does not have OnlyShowIn line in /etc/xdg/autostart/gmixer-trayicon.desktop Classification: openSUSE Product: openSUSE 11.3 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE AssignedTo: andrea(a)opensuse.org ReportedBy: wstephenson(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- gmixer is not appropriate for all desktops; its autostart .desktop file should have an OnlyShowIn=LXDE;XFCE line. -- Configure bugmail: http://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 593699] New: rsyslog logs on console
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=593699 http://bugzilla.novell.com/show_bug.cgi?id=593699#c0 Summary: rsyslog logs on console Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: novell-web(a)zmi.at QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 I replaced syslog-ng with rsyslog, and now all logs from iptables are shown on the console. It's reproducible, re-starting syslog-ng stops console logging. I have the default config, which contains if ($syslogfacility-text == 'kern') and \ ($msg contains 'IN=' and $msg contains 'OUT=') then \ -/var/log/firewall;RSYSLOG_TraditionalFileFormat if ($syslogfacility-text == 'kern') and \ ($msg contains 'IN=' and $msg contains 'OUT=') then \ ~ I also tried with (the better) if ($syslogfacility-text == 'kern') and \ ($msg contains 'IN=' and $msg contains 'OUT=') then \ -/var/log/firewall;RSYSLOG_TraditionalFileFormat & ~ But anyway it's logged on the console. Googling showed me this page http://www.linux.org.za/Lists-Archives/glug-tech-1001/msg00009.html and really doing sysctl kernel.printk="4 4 1 7" stops console logging with rsyslog. But I don't want this, I want rsyslog to behave like syslog-ng. Any ideas how to disable iptables logs with rsyslog? BTW: the iptabes rule causing that log is $IPTABLES -A RULE_19 -j LOG --log-level info --log-prefix "lastdrop " --log-tcp-options --log-ip-options but as I said with syslog-ng it works correctly. Reproducible: Always Steps to Reproduce: 1. switch from syslog-ng to rsyslog 2. access PC so that an iptables log is generated 3. that entry shows up on the console Actual Results: iptables log appears on console Expected Results: shouldn't display iptables logs on console -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11

[Bug 593094] New: pcmanfm: select folder with mouse not posible 2nd time
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=593094 http://bugzilla.novell.com/show_bug.cgi?id=593094#c0 Summary: pcmanfm: select folder with mouse not posible 2nd time Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: LXDE AssignedTo: andrea(a)opensuse.org ReportedBy: mail(a)lutz-thuns.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.2) Gecko/20100317 SUSE/3.6.2-1.4 Firefox/3.6.2 After opening pcmanfm and switching folder with double click, any further files / folders can not be selected. Double clicking on further files /folders do work, though (but no correct right click, as nothing is selected). With that, if selecting a file or folder with uo/down arrow and pressing F2 for rename, pcmanfm crashes leaving pcmanfm[6656]: segfault at 10 ip b6d73668 sp bf8d086c error 6 in libglib-2.0.so.0.2305.0[b6d5d000+df000] Reproducible: Always Steps to Reproduce: 1. start pcmanfm 2. open folder with double click 3. go back and try selecting a single file / folder Actual Results: No files / folders can be selected. Expected Results: normal behaviour S | Name | Typ | Version | Arch | Repository --+---------------+-------+----------------------------+--------+------------- i | libglib-2_0-0 | Paket | 2.23.5-1.1 | i586 | factory-oss i | pcmanfm | Paket | 0.9.3beta+git20100331-46.1 | i586 | LXDE_factory i | pcmanfm-lang | Paket | 0.9.3beta+git20100331-46.1 | noarch | LXDE_factory -- Configure bugmail: http://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 592642] New: Mouse integration doesn't work in guet system
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=592642 http://bugzilla.novell.com/show_bug.cgi?id=592642#c0 Summary: Mouse integration doesn't work in guet system Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 3 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Usability AssignedTo: mseben(a)novell.com ReportedBy: mseben(a)novell.com QAContact: qa(a)suse.de Found By: --- Blocker: --- I tested openSUSE-KDE-LiveCD-x86_64-Build0539-Media.iso on virtualbox-ose 3.1.6 and I found mouse integration dosn't work, all other features like screen resizing,shared clipboard ,etc..., works correctly ------ in previous builds, mouse integration works fine, i suppose this issue was caused by new xorg-server which no longer use HAL see: http://lists.opensuse.org/opensuse-factory/2010-03/msg00127.html ----- in vbox guest were are using HAL to detect vbox mouse : /usr/share/hal/fdi/policy/20thirdparty/90-vboxguest.fdi -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 15

[Bug 592424] New: YaST doesn't load apache module mod_cache when I enable mod_mem_cache
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=592424 http://bugzilla.novell.com/show_bug.cgi?id=592424#c0 Summary: YaST doesn't load apache module mod_cache when I enable mod_mem_cache Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: szotsaki(a)gmail.com QAContact: jsrain(a)novell.com Found By: --- Blocker: --- User-Agent: Opera/9.80 (X11; Linux x86_64; U; hu) Presto/2.2.15 Version/10.10 YaST doesn't write Apache module name mod_cache when I enable mod_mem_cache or mod_disk_cache into the variable APACHE_MODULES. Reproducible: Always Steps to Reproduce: 1. Go to YaST 2 > HTTP Server > Server modules when using Apache 2. Turn on mem_cache (or possibly disk_cache) only. Don't turn on or off anything else. 2. Install memcached (zypper in memcached libmemcache0). 3. Start apache2: rcapache2 restart. Actual Results: Apache 2 won't start because the error below: /etc/init.d/apache2 configtest httpd2-prefork: Syntax error on line 116 of /etc/apache2/httpd.conf: Syntax error on line 27 of /etc/apache2/sysconfig.d/loadmodule.conf: Cannot load /usr/lib64/apache2-prefork/mod_mem_cache.so into server: /usr/lib64/apache2-prefork/mod_mem_cache.so: undefined symbol: ap_cache_cacheable_hdrs_out Expected Results: Apache starts normally. It took an hour to find this, so I share here: please, turn on mod_cache automatically when the user turns on either mod_mem_cache or mod_disk_cache. -- Configure bugmail: http://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 592349] New: atd jobs are executed delayed after wakeup from suspend-to-RAM
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=592349 http://bugzilla.novell.com/show_bug.cgi?id=592349#c0 Summary: atd jobs are executed delayed after wakeup from suspend-to-RAM Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: i686 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hendrikw(a)arcor.de QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.8) Gecko/20100204 SUSE/3.5.8-0.1.1 Firefox/3.5.8 (.NET CLR 3.5.30729) When I schedule a job with the atd daemon and set the computer in suspend-to-RAM mode, the job is executed delayed by the time, the computer was in suspend-to-RAM mode. Reproducible: Always Steps to Reproduce: 1. schedule an at-job (at -f ...) at 7pm 2. set a wakup time 5 minutes before the at-job is scheduled: SECS=`date -u --date "2010-03-30 18:55:00" +%s` echo 0 > /sys/class/rtc/rtc0/wakealarm echo $SECS > /sys/class/rtc/rtc0/wakealarm 3. pm-suspend Actual Results: If the job was scheduled to run at 7:00pm and the computer was 1 hour in suspend-to-RAM mode the job is executed at 8:00pm. Expected Results: The job should be executed at the scheduled time (7:00pm). workaround: wakeup atd with a script in /etc/pm/sleep.d see this email thread for more details (in german): http://lists.opensuse.org/opensuse-de/2010-03/msg01298.html -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 5

[Bug 592237] New: Romanian translation completed
by bugzilla_noreply＠novell.com 15 Apr '16

15 Apr '16

http://bugzilla.novell.com/show_bug.cgi?id=592237 http://bugzilla.novell.com/show_bug.cgi?id=592237#c0 Summary: Romanian translation completed Classification: openSUSE Product: openSUSE 11.3 Version: Milestone 4 Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Translations AssignedTo: ke(a)novell.com ReportedBy: oprea_luci(a)yahoo.com QAContact: ke(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ro; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2 (.NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729) Completed installation distribution in Romanian translation. Svn files will be climbed in April. Hope you can test translation openSUSE Milestone 5 or 6 Can get early warnings of installation as the installation steps which are not 100% Romanian. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

1 11