August 2013 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 792469] New: KDE:Release:49/kdebase4-session: update needed
by bugzilla_noreply＠novell.com 11 Oct '16

11 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=792469 https://bugzilla.novell.com/show_bug.cgi?id=792469#c0 Summary: KDE:Release:49/kdebase4-session: update needed Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: toddrme2178(a)gmail.com ReportedBy: Mathias.Homann(a)opensuse.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- kdebase4-session is still version 4.9.1, but KDE itself is 4.9.3, soon 4.9.4. please update. -- 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 1

[Bug 788509] New: KDE:Release:49/kdebase4-workspace: Bug - no ssh agent, no gpg agent
by bugzilla_noreply＠novell.com 11 Oct '16

11 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=788509 https://bugzilla.novell.com/show_bug.cgi?id=788509#c0 Summary: KDE:Release:49/kdebase4-workspace: Bug - no ssh agent, no gpg agent Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: 3rd party software AssignedTo: toddrme2178(a)gmail.com ReportedBy: Mathias.Homann(a)opensuse.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- Mathias Homann <Mathias.Homann(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flag| |SHIP_STOPPER? since KDE 4.9.3, kdm does not execute /etc/X11/xdm/sys.xsession anymore, which leads to the following problems: - no ssh agent running - no gpg agent running - http_proxy variables and others from /etc/profile.d not properly set as a workaround, /usr/share/kde4/config/kdm/Xsession can be a symlink to /etc/X11/xdm/Xsession but of yourse that has to be done manually on every system involved every time the packages happen to get rebuilt. -- 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 788062] New: KDE:Release:49/mirall: Bug
by bugzilla_noreply＠novell.com 11 Oct '16

11 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=788062 https://bugzilla.novell.com/show_bug.cgi?id=788062#c0 Summary: KDE:Release:49/mirall: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Minor Priority: P5 - None Component: 3rd party software AssignedTo: toddrme2178(a)gmail.com ReportedBy: Mathias.Homann(a)opensuse.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- your link target openSUSE:Factory/mirall has ceased to exist... -- 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 1

[Bug 783857] New: KDE:Release:49/python-kde4: Bug
by bugzilla_noreply＠novell.com 11 Oct '16

11 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=783857 https://bugzilla.novell.com/show_bug.cgi?id=783857#c0 Summary: KDE:Release:49/python-kde4: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software AssignedTo: toddrme2178(a)gmail.com ReportedBy: Mathias.Homann(a)opensuse.org QAContact: opensuse-communityscreening(a)forge.provo.novell.com Found By: Community User Blocker: --- since a few days, plasmoids written in python fail to load, and in ~/.xsession-errors the following message shows: plasma-desktop(9102)/python (plugin): Failed to import module Traceback (most recent call last): File "/usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py", line 22, in <module> from PyKDE4.plasma import Plasma RuntimeError: the sip module implements API v9.0 but the PyKDE4.plasma module requires API v8.1 package info: lemmy@sai:~> rpm -qf /usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py python-kdebase4-4.9.2-782.1.x86_64 lemmy@sai:~> rpm -qf /usr/share/kde4/apps/plasma_scriptengine_python/pyappletscript.py --requires python(abi) = 2.7 python-kde4 = 4.9.2 rpmlib(CompressedFileNames) <= 3.0.4-1 rpmlib(PayloadFilesHavePrefix) <= 4.0-1 rpmlib(PayloadIsLzma) <= 4.4.6-1 lemmy@sai:~> rpm -q python python-2.7.2-7.17.1.x86_64 lemmy@sai:~> rpm -q python3 python3-3.2.1-5.9.1.x86_64 -- 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 780621] New: YaST Installer continues to ignore low-vision accessibility
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=780621 https://bugzilla.novell.com/show_bug.cgi?id=780621#c0 Summary: YaST Installer continues to ignore low-vision accessibility Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: suseROCKS(a)bryen.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20100101 Firefox/15.0 YaST uses a bright white background for the dialogue windows during installation. This is a big no-no for low-vision users as well as for people with aging eyes. Typically, many low-vision users are extremely sensitive to white on screen. We tend to set our desktops to have a black background with white font. As my vision continues to deteriorate, I am having more difficulty with each openSUSE release to be able to see the screen and select my options. While I know there is a text-based install, even the default for YaST-ncurses is not a low-vision friendly color and requires you to edit a file to change the default color options. (I've never tried this during actual install, only during normal installed usage of openSUSE.) That is simply not an optimal solution for low-vision users, especially new users who may not have experience in how to configure in the background. Please devise a plan to provide alternative visual options for users. Perhaps a toggle-button that automatically inverts the colors of the install dialogues or alternative graphics screen that provides a darker background. This is not a protest statement, but a factual one... with my continued declining vision, if this is not fixed by 12.3, it is quite possible that I will no longer be able to install and use openSUSE. Reproducible: Always Steps to Reproduce: 1. 2. 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 11

[Bug 768112] New: yast2-qt high contrast mode broken
by bugzilla_noreply＠novell.com 04 Oct '16

04 Oct '16

https://bugzilla.novell.com/show_bug.cgi?id=768112 https://bugzilla.novell.com/show_bug.cgi?id=768112#c0 Summary: yast2-qt high contrast mode broken Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: tgoettlicher(a)suse.com ReportedBy: tgoettlicher(a)suse.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- Shift+F4 switched to high contrast mode doesn't work anymore. -- 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 642456] New: Permission issue for the "nut" UPS software
by bugzilla_noreply＠novell.com 06 Sep '16

06 Sep '16

https://bugzilla.novell.com/show_bug.cgi?id=642456 https://bugzilla.novell.com/show_bug.cgi?id=642456#c0 Summary: Permission issue for the "nut" UPS software Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Minor Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: reg(a)capiogroup.com QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.10) Gecko/20100914 SUSE/3.6.10-30.1 Firefox/3.6.10 On a standard install of nut (Network UPS Tools), classic version (not HAL) the driver did not have permission to run until I added the the group "root" to the user "upsd". my nut.conf is: [myups] driver = usbhid-ups port = /dev/usb/hiddev0 desc = "Tripp Lite UPS SU1500XL" Once that change was made it worked just fine. I don't think this is a big issue but they documentation goes out of it's way to make a point of keeping permissions on the nut daemon restricted so I thought it should be noted. Perhaps just a documentation change to let people know that it might be necessary would be enough. Reproducible: Always Steps to Reproduce: 1.Install 2.Set the nut.conf file 3.Try to run the driver: /usr/lib/ups/driver/upsdrvctl start Actual Results: Permission denied error. -- 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 811408] New: parted mklabel gpt_sync_mbr does not boot
by bugzilla_noreply＠novell.com 19 Aug '16

19 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=811408 https://bugzilla.novell.com/show_bug.cgi?id=811408#c0 Summary: parted mklabel gpt_sync_mbr does not boot Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: puzel(a)suse.com ReportedBy: ms(a)suse.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- I tested the suse extension in parted to create a sync MBR inside the GPT I also tested gptsync (the version with patches from Debian) to double check that it's not something I broke. In short the table gptsync wrote worked the result parted wrote doesn't I tested this inside the kiwi codebase: EXEC [/usr/sbin/parted -s /dev/loop0 mklabel gpt_sync_mbr 2>&1] EXEC [/usr/sbin/parted -s /dev/loop0 unit s mkpart primary 2048 12295 2>&1] ==> vfat EFI jump partition EXEC [/usr/sbin/parted -s /dev/loop0 unit s mkpart primary 12296 421903 2>&1] ==> Linux boot partition EXEC [/usr/sbin/parted -s /dev/loop0 unit s mkpart primary 421904 2498432 2>&1] ==> Linux root partition EXEC [/usr/sbin/parted -s /dev/loop0 unit s set 2 type 0x83 2>&1] EXEC [/usr/sbin/parted -s /dev/loop0 unit s set 3 type 0x83 2>&1] EXEC [/usr/sbin/parted -s /dev/loop0 unit s set 1 boot on 2>&1] EXEC [mkfs.ext3 -i 16384 -F -O resize_inode -N 64960 /dev/mapper/loop0p3 2>&1] ==> rootfs EXEC [mkfs.ext3 -i 16384 -F -O resize_inode -N 64960 -L 'BOOT' /dev/mapper/loop0p2 2>&1] ==> bootfs EXEC [mkdosfs -F 16 -n 'EFI' /dev/mapper/loop0p1 2>&1] ==> efi The partition table written in the MBR looks like this: fdisk -l /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw WARNING: GPT (GUID Partition Table) detected on '/tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw: 1279 MB, 1279262720 bytes 255 heads, 63 sectors/track, 155 cylinders, total 2498560 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xc15921c7 Device Boot Start End Blocks Id System /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw1 * 2048 12295 5124 83 Linux /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw2 12296 421903 204804 83 Linux /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw3 421904 2498432 1038264+ 83 Linux /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw4 1 1 0+ ee GPT Partition table entries are not in disk order changing the boot flag to another partition did not help to make it boot in legacy BIOS mode. When I write a new table via gptsync into the same raw disk I can boot it. I have tested legacy and EFI boot via qemu legacy: qemu-kvm /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw efi qemu-kvm -L /usr/share/qemu-ovmf/bios /tmp/mytest/LimeJeOS-openSUSE-12.3.x86_64-1.12.3.raw Thanks -- 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 26

[Bug 635303] New: dump version incompatible with ext4
by bugzilla_noreply＠novell.com 19 Aug '16

19 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=635303 https://bugzilla.novell.com/show_bug.cgi?id=635303#c0 Summary: dump version incompatible with ext4 Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Blocker Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: cilantro05(a)comcast.net QAContact: qa(a)suse.de Found By: --- Blocker: --- How can you possibly provide dump-0.4b41 on the OpenSuSE 11.3 download page, when that version does not support the filesystem of your default installation, ext4? I am a longtime SuSE (and dump) user, and it never would have occurred to me to check this. OK, my mistake -- but I just lost a whole day's work because my careully made backup was trash. Dump 0.4b42 does claim ext4 support... At the very lease, a prominent warning should be added to the result of a search for dump on software.opensuse.org. -- 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 3

[Bug 571841] New: dump/restore version from oss fails when ext4 filesystem is used
by bugzilla_noreply＠novell.com 19 Aug '16

19 Aug '16

http://bugzilla.novell.com/show_bug.cgi?id=571841 http://bugzilla.novell.com/show_bug.cgi?id=571841#c0 Summary: dump/restore version from oss fails when ext4 filesystem is used Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Maintenance AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: deligeo(a)physics.uoc.gr QAContact: qa(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.6) Gecko/20091201 SUSE/3.5.6-1.1.1 Firefox/3.5.6 Attempting to use the dump/restore backup tool (Version 0.4b41-161.1 x86_64) from oss repository to backup and restore /home the resulting files where corrupted. This is a known issue upstream and is corrected in version 0.4b42. See bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=511651 for more details. Reproducible: Always Steps to Reproduce: 1.use dump to backup an ext4 filesystem 2.move into a different computer 3.attempt to restore in an ext3 filesystem Actual Results: Files produced are not identical to original files. Several text files are now reported as binary. Expected Results: Should produce a correct image of initial files in the new filesystem. Or at the very least dump should NOT allow ext4 filesystems to be used until it is properly working on them. The main issue is that dump will not complain about ext4 partitions being dumped. Thus the problem is encountered later (too late) on when one attempts to restore the filesystem. Version 0.4b42 should resolve this issue by dealing with ext4 filesystems correctly thus restoring dump/restore functionality. -- 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 12