February 2017 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1017610] During Initialize software manager - YAST not able to create repository from external USB diskdrive
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1017610 http://bugzilla.suse.com/show_bug.cgi?id=1017610#c14 Richard Bos <richard.bos(a)xs4all.nl> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(richard.bos@xs4al | |l.nl) | --- Comment #14 from Richard Bos <richard.bos(a)xs4all.nl> --- (In reply to Ladislav Slezák from comment #13) Ladislav, thanks for looking into this. > The repository is either empty or libzypp could not read the data. Could you > double check the disk content? If add the disk repository in an installed > system, can you see the packages from it? # LANG=C sha256sum -c openSUSE-Leap-42.2-DVD-x86_64.iso.sha256 openSUSE-Leap-42.2-DVD-x86_64.iso: OK Selected a random package: openSUSE-Leap-42.2-DVD-x86_64028/suse/x86_64> rpm -qip $( ls | head -431 | tail -1 ) Name : g3utils Version : 1.1.36 .... The g3utils are included in the mgetty source package. Distribution: openSUSE Leap 42.2 Medium seems OK to me. Besides that the problem is reported by more people. https://bugzilla.suse.com/show_bug.cgi?id=1017610#c10 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 904015] outlined fonts didn't get their antialias enabled by fontconfig in openSUSE 13.2 and above
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=904015 http://bugzilla.suse.com/show_bug.cgi?id=904015#c53 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(vkrevs(a)yahoo.com) --- Comment #53 from Petr Gajdos <pgajdos(a)suse.com> --- (In reply to Marguerite Su from comment #52) > He told us "He had been used Tahoma size=8 with enabled antialias"...but his > exclude range settings would definitely disable antialias for size=8 on both I would oppose that by quoting comment 0: "KDE font settings had been set up to use Tahoma 8 as the main font, with enabled anti-aliasing and excluding range 0.0-8.0." > There's no bug existed unless he means "both without antialias, openSUSE 13.1 > displayed clear and sharp while openSUSE 13.2 was not". That'll be an > embededbitmap issue. there'll be little things the rendering engine can do I had not get the point why embedded bitmaps should be a problem. > antialias and autohint disabled, hinting is enabled, BCI rendering will be > used. But even with closed-source sub-pixel rendering, it still needs > antialias to make the font look sharp because sub-pixel rendering actually > adds something grey, it'll be certainly blurred without antialias I would never mix rendering withoug antialias with subpixel rendering, yes. > But does Tahoma have embededbitmap? Apparently not: > > $ fc-match -v Tahoma:size=8 > embeddedbitmap: False(w) I am not sure fontconfig do some detection trough freetype that font contains embedded bitmaps; the above most likely means 'do not use embedded bitmaps even if rendered font contains them', as our default already for some time. -- I would stick on 42.2 as 13.2 is out of support. Vadim, what says $ fc-match -v sans:size=8 | grep 'family\|hint\|alias' on the 42.2? Assuming you have not touched any other fontconfig settings, but you have just run kde system settings, what says ~/.config/fontconfig/fonts.conf? Is there ~/.fonts.conf? What is there? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1021291] New: Deadlock during Upgrade from 42.1 to 42.2 due network hickups
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.opensuse.org/show_bug.cgi?id=1021291 Bug ID: 1021291 Summary: Deadlock during Upgrade from 42.1 to 42.2 due network hickups Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.2 Hardware: x86-64 OS: openSUSE 42.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers(a)suse.de Reporter: werner(a)suse.com QA Contact: jsrain(a)suse.com Found By: --- Blocker: --- I have seen a deadlock of the YaST2 installation screen during download of some packages caused by a temporary network hickup ... I had run strace -f -p <pid of y2base> on virtual console 2 to see that the process does not return from polling. Further invertigation had shown that a pipe had been stuck but the pipe from fd 19 to fd 20 was still there. As this was in the ram installation disk I've no log about that. After terminationg and redoing upgrade from within linuxrc I had h'finished the installation. IMHO there a timeout handler for such pollings is missed here! -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1021040] New: vim: Description improvement
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1021040 Bug ID: 1021040 Summary: vim: Description improvement Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: behlert(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- the current description for vim has this line at the end: "For SUSE Linux, Vim is used as /usr/bin/vi." This is rather bad wording, as vim is available as both vim and vi, and this can be understood as it's only available as vi. I wonder if we cannot drop the line completely. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1019575] New: Factory source checker is declining requests that should have a second review
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1019575 Bug ID: 1019575 Summary: Factory source checker is declining requests that should have a second review Classification: openSUSE Product: openSUSE Backports Version: SLE-12 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Factory Source Check Assignee: packagehub-bugs(a)suse.com Reporter: sbahling(a)suse.com QA Contact: packagehub-bugs(a)suse.com Found By: --- Blocker: --- By default the factory source checker will set an SR to openSUSE:Backorts to "Declined" if the factory source check fails. In some cases the failure is because of a bug in the check scripts or in some cases it's because of a minor difference like a security patch which should actually be acceptable based on human review. Auto-declining causes frustration for the contributors. Instead of auto-declining, the bot should fall back to human review and only declined if upon human review it is determined that the submission really does not meet policies. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1017610] During Initialize software manager - YAST not able to create repository from external USB diskdrive
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1017610 http://bugzilla.suse.com/show_bug.cgi?id=1017610#c13 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(richard.bos@xs4al | |l.nl) --- Comment #13 from Ladislav Slezák <lslezak(a)suse.com> --- Moreover the log contains these errors: 2017-01-15 04:53:58 <1> install(9911) [zypp++] ExternalProgram.cc(start_program):249 Executing 'repo2solv.sh' '-o' '/var/cache/zypp/solv/cd-bb576bd9/solv' '-X' '/var/cache/zypp/raw/cd-bb576bd 9/' 2017-01-15 04:53:58 <1> install(9911) [zypp++] ExternalProgram.cc(start_program):412 pid 10357 launched 2017-01-15 04:53:58 <2> install(9911) [zypp] RepoManager.cc(buildCache):1357 find: '*': No such file or directory 2017-01-15 04:53:58 <1> install(9911) [Pkg] Source_Resolvables.cc(LoadResolvablesFrom):152 Pool size at end: 0 (loaded 0 resolvables) 2017-01-15 04:54:00 <1> install(9911) [zypp] SATResolver.cc(problems):1121 nothing provides requested glibc The repository is either empty or libzypp could not read the data. Could you double check the disk content? If add the disk repository in an installed system, can you see the packages from it? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1017610] During Initialize software manager - YAST not able to create repository from external USB diskdrive
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=1017610 http://bugzilla.suse.com/show_bug.cgi?id=1017610#c12 Ladislav Slezák <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ma(a)suse.com Flags| |needinfo?(ma(a)suse.com) --- Comment #12 from Ladislav Slezák <lslezak(a)suse.com> --- (In reply to Richard Bos from comment #8) > Something between A6.1 and A6.2 is clearly adding the zero's...., this is: > if (!path_r.asString().empty()) > { > y2milestone("DEBUG A6"); > zypp::Pathname pth(probe_url.getPathName()); > ????? pth /= path_r; > > y2milestone("DEBUG A6.1: %s", probe_url.asString().c_str() ); Michael, any idea why this correct URL: 2017-01-15 04:46:53 <1> install(7713) [Pkg] Source_Create.cc(createManagedSource):204 DEBUG A6.1: cd:///?devices=/dev/disk/by-id/usb-TSSTcorp_CDDVDW_SE-208AB_RL6X853-0:0 > >>>>> probe_url.setPathName(pth.asString()); > y2milestone("DEBUG A6.2: %s", probe_url.asString().c_str() ); Is tuned into invalid one here??? 2017-01-15 04:46:53 <1> install(7713) [Pkg] Source_Create.cc(createManagedSource):206 DEBUG A6.2: cd:///%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00?devices=/dev/ disk/by-id/usb-TSSTcorp_CDDVDW_SE-208AB_RL6X853-0:0 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 979718] Memory leak on play.spotify.com
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=979718 http://bugzilla.suse.com/show_bug.cgi?id=979718#c5 Foulques du Peloux <floux.dp(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution|--- |INVALID --- Comment #5 from Foulques du Peloux <floux.dp(a)gmail.com> --- The problem was from Spotify, not Firefox. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 996203] Failed at step NAMESPACE spawning /usr/sbin/start_apache2: Operation not permitted
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=996203 http://bugzilla.suse.com/show_bug.cgi?id=996203#c12 Petr Gajdos <pgajdos(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(per(a)computer.org) --- Comment #12 from Petr Gajdos <pgajdos(a)suse.com> --- Per, 13.2 is out of support. As there is not proven bug in *.service file, I am so far clueless what could be a problem. Do you experience the same on Leap? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 824171] prepared kernel update openSUSE_Maintenance_1695 is not installable
by bugzilla_noreply＠novell.com 03 Feb '17

03 Feb '17

http://bugzilla.suse.com/show_bug.cgi?id=824171 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|ibs:running:4070:important |ibs:running:4070:important |ibs:running:4098:important |ibs:running:4098:important | |ibs:running:4139:important -- You are receiving this mail because: You are on the CC list for the bug.

1 0