May 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 911517] Midnight Commander - error messages in case of SFTP file transfers
by bugzilla_noreply＠novell.com 03 May '15

03 May '15

http://bugzilla.novell.com/show_bug.cgi?id=911517 David Haller <dnh(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|dnh(a)opensuse.org |bnc-team-screening(a)forge.pr | |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 836558] New: MidnightCommander: long file-names in tar archives truncated
by bugzilla_noreply＠novell.com 03 May '15

03 May '15

https://bugzilla.novell.com/show_bug.cgi?id=836558 https://bugzilla.novell.com/show_bug.cgi?id=836558#c0 Summary: MidnightCommander: long file-names in tar archives truncated Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 4 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: d_werner(a)gmx.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=554071) --> (http://bugzilla.novell.com/attachment.cgi?id=554071) a sample extfs for mc which correctly lists and copies out long file names User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:23.0) Gecko/20100101 Firefox/23.0 tar archives support in MidnightCommander: tar archives containing long file-names or long path-name + file-name, e.g. resulting from nested sub-directories: file names are truncated. It seems the length of the path-name + file-name is limited to 100 characters, longer names are truncated. They are displayed truncated in the mc panel, and when the file (or its parent directory in the archive) is copied out of the archive with F5 it will have a truncated name. Therefore deeply nested tar archives can not safely be un-tarred with mc. There exist different formats of tar archives, "newer" formats (e.g. posix which is now the default) allow long file names (unlimited length). The problem happens in openSUSE 12.3 and also 13.1M4. Reproducible: Always Steps to Reproduce: mkdir testdir echo test > "testdir/testname_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789.txt" tar cJf testdir.tar.xz testdir start mc, enter testdir.tar.xz Actual Results: the displayed file name is limited to testname_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123456789_123 copy out (F5) will create the file with the truncated name. The tar archive itself is correct and tar xJf correctly restores the full file-names. Expected Results: the displayed file names or the file names created during copy out (F5) should be the correct file names recorded in the tar archive The attached VFS "untar" uses the installed tar (or star or gtar) to browse tar archives with mc and to copy out files, therefore avoiding the limitation of the mc internal tar list and copyout working rm, mkdir, rmdir partly working (only uncompressed tar archives) copyin works partly (only uncompressed tar archives, archive rootdir) -- 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 929338] openSUSE 13.2 LibreOffice does not open documents
by bugzilla_noreply＠novell.com 03 May '15

03 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=929338 --- Comment #3 from Jim Hill <jimmylhill(a)Q.com> --- Thru yesterday I reloaded openSUSE 13.2, deleted both Libre Office Repositories, de-selected all Libre Office apps, and rebooted the system. Then I went to opensuse.org/program/libreoffice and did a reload, first with one repository, then with both repositories. Both attempts yielded the same results. I was able to access libreoffice writer, create new documents, save those documents, and reopen only those newly saved documents. I still was not able to open calc or any of the other apps, and I cannot open any of the documents, including write documents, I have previously saved. As my saved and archived documents consist mainly of write and calc docements, this is frustrating me. I have reduced my repositories down quite low. I have seen no error codes or caution flags so far, but I may not have JAVA repository installed. What is the best one to assure proper workings with LibreOffice? Your suggestion makes sense. After I read it I tried to find /libreoffice/ with the System folder /etc/system config tool by using the search function. Nothing came up. The only code editor I have showing in my tools is Linux 32 bit Terminal. It has been at least 15 years since I was consistently working in code, so... is there a quick point to this code line or can you walk me thru the steps to tackle this name change? Thanks... very respectfully (v/r) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929338] New: openSUSE 13.2 LibreOffice does not open documents
by bugzilla_noreply＠novell.com 02 May '15

02 May '15

http://bugzilla.novell.com/show_bug.cgi?id=929338 Bug ID: 929338 Summary: openSUSE 13.2 LibreOffice does not open documents Classification: Internal Novell Products Product: openSUSE Build Service Version: master Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: General Assignee: adrian(a)suse.com Reporter: jimmylhill(a)Q.com QA Contact: adrian(a)suse.com Found By: --- Blocker: --- OpenSuse v. 13.2 Gnome Libre Office does not open documents. It displays on spp bar and will not open new documents. Id does open help page. Reloaded software from Yast 2 Software Management without a change. Loaded LibreOffice: Factory repository and reloaded software. Still no pages display, either new or document. Have not loaded v. 13.2 from scratch yet because that is a 6.5-8 hour evolution. Noticed also that data entry in Yast 2 must be extremely slow, or the characters jumble. Have almost 8 years worth of docs I cannot access at this time. Need help. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 908730] after eula-acception packagekitd just hangs
by bugzilla_noreply＠novell.com 02 May '15

02 May '15

http://bugzilla.suse.com/show_bug.cgi?id=908730 --- Comment #19 from kevin vandeventer <pilotgi(a)gmail.com> --- Today I see there's an update for AdobeICCProfiles, v2.0-154.1 from the Tumbleweed repo. This update requires a license agreement and packagekit hangs on this agreement also. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929444] New: /etc/apcupsd/apcupsd.conf places lock file in wrong location
by bugzilla_noreply＠novell.com 02 May '15

02 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=929444 Bug ID: 929444 Summary: /etc/apcupsd/apcupsd.conf places lock file in wrong location Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: patrick.shanahan(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- in apcupsd-3.14.13-95.5.x86_64.rpm the provided /etc/apcupsd/apcupsd.conf places the lock file: LOCKFILE /etc/apcupsd where it cannot be written. changing that to: LOCKFILE /var/lock provides intended function -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929434] New: rpmconf has issues with unicode.
by bugzilla_noreply＠novell.com 02 May '15

02 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=929434 Bug ID: 929434 Summary: rpmconf has issues with unicode. Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: zaitor(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I suspect there is a missing Requires here, but no clue which one :-) drude:~ # zypper in rpmconf Loading repository data... Reading installed packages... Resolving package dependencies... The following 3 NEW packages are going to be installed: python3-rpm python3-rpmconf rpmconf 3 new packages to install. Overall download size: 98.7 KiB. Already cached: 0 B After the operation, additional 274.2 KiB will be used. Continue? [y/n/? shows all options] (y): Retrieving package python3-rpmconf-1.0.7-1.6.noarch (1/3), 29.1 KiB ( 65.1 KiB unpacked) Retrieving: python3-rpmconf-1.0.7-1.6.noarch.rpm ..............................................................................................................................................[done] Retrieving package python3-rpm-4.12.0.1-5.1.x86_64 (2/3), 46.9 KiB (167.1 KiB unpacked) Retrieving: python3-rpm-4.12.0.1-5.1.x86_64.rpm ...............................................................................................................................................[done] Retrieving package rpmconf-1.0.7-1.6.noarch (3/3), 22.7 KiB ( 42.0 KiB unpacked) Retrieving: rpmconf-1.0.7-1.6.noarch.rpm ......................................................................................................................................................[done] Checking for file conflicts: ..................................................................................................................................................................[done] (1/3) Installing: python3-rpmconf-1.0.7-1.6 ...................................................................................................................................................[done] (2/3) Installing: python3-rpm-4.12.0.1-5.1 ....................................................................................................................................................[done] (3/3) Installing: rpmconf-1.0.7-1.6 ...........................................................................................................................................................[done] drude:~ # rpmconf usage: rpmconf [-h] [-a] [-c] [-d] [-D] [-f EDITOR] [-Z] [-o [PACKAGE [PACKAGE ...]]] [-v] optional arguments: -h, --help show this help message and exit -a, --all Check configuration files of all packages. -c, --clean Find and delete orphaned .rpmnew and .rpmsave files. -d, --debug Dry run. Just show which file will be deleted. -D, --diff Non-interactive diff mode. Useful to audit configs. Use with -a or -o options. -f EDITOR, --frontend EDITOR Define which frontend should be used for merging. For list of valid types see man page. -Z Display SELinux context of old and new file. -o [PACKAGE [PACKAGE ...]], --owner [PACKAGE [PACKAGE ...]] Check only configuration files of given package. -v, --version Display rpmconf version. drude:~ # rpmconf -d -a Traceback (most recent call last): File "/usr/sbin/rpmconf", line 63, in <module> main() File "/usr/sbin/rpmconf", line 60, in main rconf.run() File "/usr/lib/python3.4/site-packages/rpmconf/rpmconf.py", line 88, in run self._handle_package(pkg_hdr) File "/usr/lib/python3.4/site-packages/rpmconf/rpmconf.py", line 241, in _handle_package for conf_file in self.get_list_of_config(package): File "/usr/lib/python3.4/site-packages/rpmconf/rpmconf.py", line 117, in get_list_of_config for rpm_file in files: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe5 in position 27: invalid continuation byte -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 920024] bash-completion for scp removes hostname
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=920024 Robert Munteanu <robert.munteanu(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED CC| |robert.munteanu(a)gmail.com Resolution|--- |DUPLICATE --- Comment #5 from Robert Munteanu <robert.munteanu(a)gmail.com> --- Dupe of #915037 *** This bug has been marked as a duplicate of bug 915037 *** -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929224] system can't start/top services anymore, can't reboot, can't be shutdown
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=929224 Bugzilla Account Maintenance <autobugz> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|tsaupe(a)suse.de |bnc-team-screening(a)forge.pr | |ovo.novell.com Bernhard Wiedemann <bwiedemann(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwiedemann(a)suse.com, | |jfehlig(a)suse.com Assignee|bnc-team-screening(a)forge.pr |systemd-maintainers(a)suse.de |ovo.novell.com | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 929415] New: libtool: illegal use of install-info in post script
by bugzilla_noreply＠novell.com 01 May '15

01 May '15

http://bugzilla.opensuse.org/show_bug.cgi?id=929415 Bug ID: 929415 Summary: libtool: illegal use of install-info in post script Classification: openSUSE Product: openSUSE Factory Version: 201503* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- As this is now in Tumbleweed, I was informed that there is an error happening on install/upgrade of libtool: The change causing the issue must be: -%installinfo --info-dir=%{infodir} %{infodir}/libtool.info.gz +%installinfo --info-dir=%{infodir} %{infodir}/libtool.info*.gz And the issue itself is: (139/247) Installing: libtool-2.4.6-1.1 ............................................................................................................................[done] Additional rpm output: install-info: excess command line argument /usr/share/info/libtool.info-2.gz' install-info: excess command line argument/usr/share/info/libtool.info.gz' Point being: install-info only wants ONE .info file per call. -- You are receiving this mail because: You are on the CC list for the bug.

1 1