April 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 862343] New: Enable more features in terminal vim +xclipboard and +clientserver
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=862343 https://bugzilla.novell.com/show_bug.cgi?id=862343#c0 Summary: Enable more features in terminal vim +xclipboard and +clientserver Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Enhancement Priority: P5 - None Component: Development AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: andreash87(a)gmx.ch QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1700.107 Safari/537.36 I have the packages `vim`, `vim-data`, and `gvim` installed. The terminal version of Vim (`/usr/bin/vim`) is lacking the features `+xclipboard`, and `+clientserver`. The feature `+xclipboard` enables to access the clipboard of a running X-session. This is useful when you're running vim in a graphical terminal emulator such as Konsole and want to interact with the clipboard of the GUI session around. E.g. copy code from a page in your browser. The feature `+clientserver` enables opening a file in an already running vim session. This way you can browse files in one terminal window, and edit them in another one. Both features are available in `gvim`, however, some people prefer terminal vim over gvim. I personally, prefer terminal vim in certain cases. E.g. editing git commit-messages, or sudoedit sessions. One big advantage of terminal vim is that it can be used inside a tmux, or screen session. Please enable the above mentioned flags in terminal vim. Reproducible: Always -- 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 807288] New: 783172
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=807288 https://bugzilla.novell.com/show_bug.cgi?id=807288#c0 Summary: 783172 Classification: openSUSE Product: openSUSE 12.3 Version: RC 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: per(a)computer.org QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:11.0) Gecko/20100101 Firefox/11.0 When installing 12.3rc2 over ssh, I receive the following when I try to initiate phase2: # /usr/lib/YaST2/startup/YaST2.ssh File /var/lib/YaST2/runme_at_boot does not exist ... Not running YaST ... Bug#783172 is possibly related. Work-around: touch /var/lib/YaST2/runme_at_boot Reproducible: Always -- 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 45

[Bug 831057] New: Logrotate not running scripts with correct parameters in "nosharedscripts" mode
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=831057 https://bugzilla.novell.com/show_bug.cgi?id=831057#c0 Summary: Logrotate not running scripts with correct parameters in "nosharedscripts" mode Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: joschibrauchle(a)gmx.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36 There is a but in "logrotate" program of versions below 3.8.4: When specifying a pattern to match the rotated files, the pre-/postscripts are supposed to be called with the exact file name of the actual file that is being rotated, not the specified pattern. This is the behavior described in the man page. But actually, this is not the case and the pre-/postrotate scripts are given the pattern as parameter. Example: ------------------- log_files_with_pattern_* { weekly compress dateext rotate 1 notifempty create 644 root root prerotate prerotate_script.sh $1 endscript } ------------------- According to the manpage, logrotate defaults to noscriptmode. Thus, the prerotate script should be run multiple times like this: ------------------- prerotate_script.sh log_files_with_pattern_<CURRENT-FILE-TO-BE-ROTATED-MATCHING-THE-PATTERN> ------------------- but is actually called multiple times like this: ------------------- prerotate_script.sh log_files_with_pattern_<ALL-FILES-MATCHING-REGARDLESS-OF-BEING-ROTATED-OR-NOT> ------------------- This bug makes it impossible for the scripts to run on exactly the file that is being rotated. The BUG was fixed in version 3.8.4 of logrotate. Please see the changelog of version 3.8.4 here: http://svn.fedorahosted.org/svn/logrotate/tags/r3-8-4/CHANGES It states as included fixes: - Call prerotate/postrotate script only for really rotated files in nosharedscripts mode (as stated in man page). Please backport the corresponding changeset to openSUSE 12.x: https://fedorahosted.org/logrotate/changeset/403 This bug also affects all SLES11SPx releases and was reported to Novell as well. Reproducible: Always Steps to Reproduce: 1. Configure pre-/postscript in logrotate with a pattern 2. Run logrotate Actual Results: Pre-/postscripts are called with parameters of all files matching the pattern. Expected Results: Pre-/postscripts should be called with a single parameter of only the actual file that is being rotated. -- 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 858412] New: dvipdfm / dvipdfmx fail to find dvipdfmx.cfg
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=858412 https://bugzilla.novell.com/show_bug.cgi?id=858412#c0 Summary: dvipdfm / dvipdfmx fail to find dvipdfmx.cfg Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mjr19(a)cam.ac.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 dvipdfm / dvipdfmx fail to find their configuration file, as they search for dvipdfmx.cfg using a progname of dvipdfm-x, not dvipdfm or dvipdfmx. Reproducible: Always Steps to Reproduce: 1. cat test.tex \documentclass{article} \usepackage{times} \begin{document} Hello \end{document} 2. latex test.tex 3. dvipdfm test.dvi Actual Results: ** WARNING ** Could not open config file "dvipdfmx.cfg". $ test.dvi -> test.pdf $ [1 $ kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ptmr8r mktexpk: Running gsftopk ptmr8r 600 [and for some reason gs then dies on signal 11, and no output is produced, but that isn't the issue here] Expected Results: No warning about missing config files, and the use of the installed Type1 fonts. This can be fixed as follows: /etc/texmf # ln -s dvipdfmx dvipdfm-x /etc/texmf # mktexlsr . Then dvipdfmx runs fine, showing that the problem is the change in the progname it uses for searching for its configuration file. This is probably related to the line 2013-06-15 in texlive-20130620-source/texk/dvipdfm-x/ChangeLog "Merge dvipdfmx and xdvipdfmx into dvipdfm-x." It is not yet clear to me if/how upstream has fixed this (put configuration under dvipdfm-x, or change name used when searching for configuration). -- 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 856363] New: xdvi -sourceposition exits with Fatal error: currinf.set_char_p...
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=856363 https://bugzilla.novell.com/show_bug.cgi?id=856363#c0 Summary: xdvi -sourceposition exits with Fatal error: currinf.set_char_p... Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mjr19(a)cam.ac.uk QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:25.0) Gecko/20100101 Firefox/25.0 xdvi crashes under some circumstances when called with -sourceposition (e.g. from auctex). Reproducible: Always Steps to Reproduce: pc23:/tmp> cat t.tex \documentclass{article} \usepackage{times} \begin{document} Line 1 \section{test} \end{document} pc23:/tmp> latex -src-specials t.tex [...] pc23:/tmp> xdvi -sourceposition "1:1 t.tex" t.dvi Actual Results: xdvi: Fatal error: currinf.set_char_p is not a registered routine! Expected Results: xdvi showing a preview See also http://sourceforge.net/p/xdvi/bugs/388/ -- 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 847102] New: lualatex+fontspec is not functional
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=847102 https://bugzilla.novell.com/show_bug.cgi?id=847102#c0 Summary: lualatex+fontspec is not functional Classification: openSUSE Product: openSUSE 13.1 Version: RC 1 Platform: x86-64 OS/Version: All Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: d.pashov(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=564464) --> (http://bugzilla.novell.com/attachment.cgi?id=564464) run with lualatex luatest.tex User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 lualatex breaks when compiling a document using fontspec. There is a new upstream version which apparently fixes the issue. http://tug.org/pipermail/tex-live/2013-July/033909.html Reproducible: Always Steps to Reproduce: 1. Try to compile the following minimal example with lualatex \documentclass[]{article} \usepackage{fontspec}% \begin{document} Hello World!! \end{document} 2. Notice it ends prematurely with "quiting: fix your writable cache path". 3. Actual Results: Error produced, task not accomplished. Expected Results: A pdf file should have been produced. -- 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 20

[Bug 871258] New: server:mail/sendmail: Please update Sendmail
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=871258 https://bugzilla.novell.com/show_bug.cgi?id=871258#c0 Summary: server:mail/sendmail: Please update Sendmail Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: werner(a)suse.com ReportedBy: bjoernv(a)arcor.de QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: --- Blocker: --- Please update package "sendmail" to the newest version (currently this is 8.14.8). -- 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 859889] New: autoyast gets autoinst.xml twice per at the same time
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=859889 https://bugzilla.novell.com/show_bug.cgi?id=859889#c0 Summary: autoyast gets autoinst.xml twice per at the same time Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: All OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: AutoYaST AssignedTo: fehr(a)suse.com ReportedBy: achernikov(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- [22/Jan/2014:08:24:52 EST] "GET /autoinst.xml HTTP/1.1" 200 9736 - -> /autoinst.xml [22/Jan/2014:08:24:52 EST] "GET /autoinst.xml HTTP/1.1" 200 9736 - -> /autoinst.xml This a log from webserver serving autoinst.xml. Seems the same file served twice. Which is overhead. Full linuxrc input: ``` Typing:[1]: <Esc><Enter> Typing:[2]: linux netdevice=eth0 netsetup=dhcp install=cd:/ Typing:[3]: dud=http://192.168.122.130:8888/zypp_req_only.dud lang=en_US Typing:[4]: autoyast=http://192.168.122.130:8888/autoinst.xml Typing:[5]: insecure=1 Typing:[6]: <Enter> ``` -- 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 786041] New: Unable to access SD storage on ZTE Blade Android phones
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=786041 https://bugzilla.novell.com/show_bug.cgi?id=786041#c0 Summary: Unable to access SD storage on ZTE Blade Android phones Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: hare(a)suse.com QAContact: qa-bugs(a)suse.de Found By: Development Blocker: --- When I plug in the USB cable to my ZTE Blade phone (aka BASE Lutea in Germany), the usb storage device is detected, but no SCSI device is recognized. Removing this line in 40-usb_modeswitch.rules: ATTRS{idVendor}=="19d2", ATTRS{idProduct}=="0083", RUN+="usb_modeswitch '%b/%k'" makes everything work 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 5

[Bug 871272] New: install summary offers graphical/multi-user logins but only graphical is selectable
by bugzilla_noreply＠novell.com 02 Apr '14

02 Apr '14

https://bugzilla.novell.com/show_bug.cgi?id=871272 https://bugzilla.novell.com/show_bug.cgi?id=871272#c0 Summary: install summary offers graphical/multi-user logins but only graphical is selectable Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: yast2-maintainers(a)suse.de ReportedBy: pat(a)indy.rr.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Created an attachment (id=584426) --> (http://bugzilla.novell.com/attachment.cgi?id=584426) yast and zypper logs from install and first update User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 last page of install setup is summary where two boot options are offered, "Graphical" and "Multi-User". Selecting Multi-User returns to summary display and when install is finished, system boots to Graphical/runlevel5, not Multi-User/runlevel3 which is desired. Reproducible: Always Steps to Reproduce: 1.Select Multi-User on install summary screen 2.Complete install 3.system boots to Graphical/runlevel5 Actual Results: boots into Graphical mode, runlevel 5 rather than the selected Multi-User, runlevel3 Expected Results: should boot to runlevel 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