June 2014 - openSUSE Bugs - openSUSE Mailing Lists

[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 874606] New: Pidgin (2.9.10) does not connect to Yahoo anymore
by bugzilla_noreply＠novell.com 23 Sep '16

23 Sep '16

https://bugzilla.novell.com/show_bug.cgi?id=874606 https://bugzilla.novell.com/show_bug.cgi?id=874606#c0 Summary: Pidgin (2.9.10) does not connect to Yahoo anymore Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: lenrocd(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created an attachment (id=587239) --> (http://bugzilla.novell.com/attachment.cgi?id=587239) debug messages from pidgin session User-Agent: Mozilla/5.0 (X11; Linux i686; rv:28.0) Gecko/20100101 Firefox/28.0 My instant messenger pidgin (version 2.10.9-4.12.1) refuses to connect to yahoo servers anymore, since a few weeks already. I would bet this is not related to the recent heartbleed bug(s) in the SSL layer, since I have this problem before the spread of that problem. After setting pidgin to report debug messages into a file I get this exact error messages: (09:04:19) yahoo: Login Failed, unable to retrieve login url: Error reading from login.yahoo.com: Input/output error (09:04:19) connection: Connection error on 0xb8b5ce90 (reason: 0 description: Error reading from login.yahoo.com: Input/output error) Reproducible: Always Steps to Reproduce: 1. start pidgin 2. try to login to the (yahoo) messenger account Actual Results: pidgin reports error about "Error reading from login.yahoo.com: Input/output error" Expected Results: login to the desired account gnutls packages are all up to date (versions 3.2.4-2.18.1). Openssl is up to date, as well (version 1.0.1e-11.32.1) So I think the issue is not related to the current SSL bug (heartbleed). Curious thing: at the same time, kopete succeeds in connecting to the same user account (yahoo messenger user). So there isn't any issues with the account (like being blocked somehow). Some user at this thread on the forums: https://forums.opensuse.org/showthread.php/497190-Pidgin-%282-10-9%29-still… states he does NOT have this issue with the same pidgin version but on Ubuntu. -- 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 12

[Bug 853038] New: pidgin xmpp video support missing
by bugzilla_noreply＠novell.com 23 Sep '16

23 Sep '16

https://bugzilla.novell.com/show_bug.cgi?id=853038 https://bugzilla.novell.com/show_bug.cgi?id=853038#c0 Summary: pidgin xmpp video support missing Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME AssignedTo: bnc-team-gnome(a)forge.provo.novell.com ReportedBy: wolfgang(a)rosenauer.org QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- According to different references on the pidgin site and other descriptions out there pidgin is supposed to have jingle based xmpp video/voice support. (e.g. http://michael.stapelberg.de/Artikel/video_chat_with_pidgin) I cannot find any way to enable this in our pidgin though. Unless I missed any additional plugin packages there is something missing to make this work. -- 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 19

[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 873342] New: squirrelmail broken if upload_tmp_dir is set to an unexpected value
by bugzilla_noreply＠novell.com 22 Aug '16

22 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=873342 https://bugzilla.novell.com/show_bug.cgi?id=873342#c0 Summary: squirrelmail broken if upload_tmp_dir is set to an unexpected value Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: Other OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: jengelh(a)inai.de ReportedBy: suse-beta(a)cboltz.de QAContact: qa-bugs(a)suse.de Found By: Beta-Customer Blocker: --- The squirrelmail-beta package comes with /etc/apache2/conf.d/squirrelmail.conf which contains php_admin_value open_basedir "/srv/www/htdocs/squirrelmail:/var/lib/squirrelmail:/usr/share/php5/PEAR:/tmp" This works with the default config, but breaks when squirrelmail is Alias'ed into a VirtualHost that has a completely different upload_tmp_dir outside the paths in open_basedir (/home/www/example.com/tmp/ in my case). Please add php_admin_value upload_tmp_dir /var/lib/squirrelmail/attach/ (or somewhere else inside open_basedir) to the apache squirrelmail.conf -- 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 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 864991] New: bsd-games : rot13 is unusable because of faulty reference in shell script
by bugzilla_noreply＠novell.com 19 Aug '16

19 Aug '16

https://bugzilla.novell.com/show_bug.cgi?id=864991 https://bugzilla.novell.com/show_bug.cgi?id=864991#c0 Summary: bsd-games : rot13 is unusable because of faulty reference in shell script 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: schaiba(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Firefox/27.0 /usr/bin/rot13 refers to /usr/games/caesar, which is not there, instead of /usr/bin/caesar. Reproducible: Always Steps to Reproduce: 1.try to use rot13 2. 3. Actual Results: One receives an error about /usr/games/caesar not being found -- 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