February 2018 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1078552] Filesystems shown as TODO - prevents mounting existing filesystems
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1078552 http://bugzilla.suse.com/show_bug.cgi?id=1078552#c10 --- Comment #10 from Per Jessen <per(a)computer.org> --- (In reply to Ancor Gonzalez Sosa from comment #9) > (In reply to Anton Aylward from comment #8) > > > > Is that because support for JFS upstream has been dropped? > > Yes, I think so. > > > But ... Let me get this right. > > You're dropping support for JFS and for ReiserFS. > > Both has been discontinued by upstream, not (open)SUSE. That leaves very few > options for us. Which upstream is that? JFS is alive and well, afaict. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078811] New: Print kipi-plugins not working in gwenview
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1078811 Bug ID: 1078811 Summary: Print kipi-plugins not working in gwenview Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Factory Status: NEW Severity: Normal Priority: P5 - None Component: KDE Applications Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: petersenmde(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On my fully updated desktop and laptop Tumbleweed computers. In gwenview when I select Plugins > Images > both Print Images and Print assistant are greyed out. The File > Print function does work, but I cannot set the picture size. - It fills the page. Current versions of packages installed: gwenview5 17.12.1-1.1 kipi-plugins 5.8.0-3.1 libKF5Kipi32_0_0 17.12.1-1.1 libkipi-data 17.12.1-1.1 In Digikam: Tools > Print Creator... does bring up a "print assistant" dialog box, and I am able to select number of prints per page etc. Mark -- You are receiving this mail because: You are on the CC list for the bug.

1 12

[Bug 1078552] Filesystems shown as TODO - prevents mounting existing filesystems
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1078552 http://bugzilla.suse.com/show_bug.cgi?id=1078552#c9 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |aschnell(a)suse.com, | |jsrain(a)suse.com Resolution|--- |FIXED Flags|needinfo?(per(a)computer.org) | --- Comment #9 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- (In reply to Per Jessen from comment #7) > (In reply to Ancor Gonzalez Sosa from comment #6) > > (In reply to Per Jessen from comment #3) > > > > > > The option to mount can't be selected. This is a JFS volume - with e.g. > > > ext4, it works. Oh, I see, it isn't even recognised as a JFS volume. > > > > JFS support is being dropped. That's intentional. > > How do we mount existing filesystems then? I guess it's not important to > you, but for us that is a complete show-stopper. Would upgrades work? I don't think upgrades will work. And handling of existing filesystems will need to be done "by hand", the installer and the Expert Partitioner will not handle those filesystems, AFAIK. (In reply to Anton Aylward from comment #8) > > Is that because support for JFS upstream has been dropped? Yes, I think so. > But ... Let me get this right. > You're dropping support for JFS and for ReiserFS. Both has been discontinued by upstream, not (open)SUSE. That leaves very few options for us. > Will that last remaining "other" FS that uses dynamic allocation, XFS, be > depreciated as well I don't think XFS will fall in disgrace in the Linux kernel and/or upstream community anytime soon. But that's out of our control. So I'm closing the bug because the TODOs are gone and the drop of JFS support is intentional. Works as expected. On the other hand. If your are not satisfied with the answers I have added Jiri Srain and Arvin to CC. They can give you better insights about the reasons behind such decision. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078997] libstorage-ng fails to build on armv6 and armv7
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1078997 http://bugzilla.suse.com/show_bug.cgi?id=1078997#c2 --- Comment #2 from Guillaume GARDET <guillaume.gardet(a)opensuse.org> --- For the 1st error, I think the root problem comes from byte_to_humanstring function when you do the conversion 'long double f = size;'. See line in code here [1]. For the broken test, I get f = 18446744073709551616.000000 size = 18446744073709551615 So, we clearly loose the required precision for this test on arm 32 bits! Then, you probably want to rework the "omit_zero" management. [1]: https://github.com/openSUSE/libstorage-ng/blob/6d88d4152aa5aa20920c392bc5d2… -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1078480] New: Konsole does not persist cursor profile changes
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1078480 Bug ID: 1078480 Summary: Konsole does not persist cursor profile changes Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs(a)opensuse.org Reporter: comrad(a)posteo.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 758222 --> http://bugzilla.opensuse.org/attachment.cgi?id=758222&action=edit The noted settings are resetted every time I want to change a profile setting in KDE's Konsole. I choose "Settings" - "Edit current profile" - choose most right "extended" tab (Sorry, translated from German). The settings "blinking cursor" and custom cursor color are not persisted in the profile and not changed in the terminal session. After closing Konsole and reopening it the changes are there. -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1044727] screen resolution off-by-2 on Raspberry Pi 3: 1922x1200
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1044727 http://bugzilla.opensuse.org/show_bug.cgi?id=1044727#c15 Max Staudt <mstaudt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(sbrabec(a)suse.com) --- Comment #15 from Max Staudt <mstaudt(a)suse.com> --- Since Tumbleweed images are out of date right now (should be fixed soon), I downloaded the newest image straight from OBS, using the 'osc' tool (it needs an OBS account, your Bugzilla username/password should suffice): osc getbinaries openSUSE:Factory:ARM JeOS:XFCE-raspberrypi3.aarch64 images aarch64 With this latest Tumbleweed package, I could not reproduce the problem. Could you please confirm this? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1079014] New: sysctl does not apply values
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1079014 Bug ID: 1079014 Summary: sysctl does not apply values Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.0 Hardware: x86-64 OS: All Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: werner(a)suse.com Reporter: bwiedemann(a)suse.com QA Contact: qa-bugs(a)suse.de CC: schwab(a)suse.com Found By: Development Blocker: --- Steps To Reproduce: strace sysctl -w vm.swappiness=10 cat /proc/sys/vm/swappiness 60 # rpm -q procps procps-3.3.12-lp150.2.2.x86_64 openat(AT_FDCWD, "/proc/sys/vm/swappiness", O_WRONLY|O_TRUNC) = 3 lseek(3, 1, SEEK_CUR) = 1 write(3, "10\0", 3) = 3 close(3) Changing values works when using echo 10 > /proc/sys/vm/swappiness So probably the trailing \0 vs \n is causing trouble. sysctl on 42.3 created a trailing \n -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 1078849] Certain system view nodes in Yast partitioner only displaying node label in main window area.
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1078849 http://bugzilla.suse.com/show_bug.cgi?id=1078849#c2 Ancor Gonzalez Sosa <ancor(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ancor(a)suse.com Assignee|yast2-maintainers(a)suse.de |ancor(a)suse.com --- Comment #2 from Ancor Gonzalez Sosa <ancor(a)suse.com> --- Your system is perfectly sane. The Expert Partitioner is being rewritten and those sections are indeed being worked as we speak. It will be finished by the Leap15 final release. Meanwhile, you can follow the process at https://lizards.opensuse.org/author/yast-team/ We publish an status update there about the Partitioner rewrite (and other YaST stuff) every two weeks aprox. I will assign the bug to myself and will let you know when all the sections are there (I estimate 4 weeks). -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1067838] X server slows down
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=1067838 http://bugzilla.opensuse.org/show_bug.cgi?id=1067838#c7 Max Staudt <mstaudt(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |NORESPONSE --- Comment #7 from Max Staudt <mstaudt(a)suse.com> --- This should be RESOLVED NORESPONSE, really. Sorry! -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1079020] New: zypper up is missing '--from' option
by bugzilla_noreply＠novell.com 02 Feb '18

02 Feb '18

http://bugzilla.suse.com/show_bug.cgi?id=1079020 Bug ID: 1079020 Summary: zypper up is missing '--from' option Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp Assignee: zypp-maintainers(a)forge.provo.novell.com Reporter: mbrugger(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- When you want to update packages of a specific repository you have to use the depcreated 'zypper up -r <repo>' option. Instead zypper should accept 'zypper up --from <repo>' -- You are receiving this mail because: You are on the CC list for the bug.

1 2