December 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 905844] New: lxde control center: no text visible under the program icons
by bugzilla_noreply＠novell.com 21 Feb '18

21 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=905844 Bug ID: 905844 Summary: lxde control center: no text visible under the program icons Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: PC OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: LXDE Assignee: andrea(a)opensuse.org Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- On a fresh 13.2 installation, usign LXDE, the window of LXDE control center only shows the program icons but there is no text under the icons. The only icon with text is the Install Software icon but the text under it is not "Install Software" but "Installed Size:". Clicking on the different icons starts the corresponding programs except for Install Software: the program that is supposed to run (package-manager) included in 13.1 in the package libzypp, does not exist in 13.2. -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 819514] New: After update pushed 5/10/2013, network unavailable after resuming from sleep
by bugzilla_noreply＠novell.com 20 Feb '18

20 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=819514 https://bugzilla.novell.com/show_bug.cgi?id=819514#c0 Summary: After update pushed 5/10/2013, network unavailable after resuming from sleep Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: tonysu(a)su-networking.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 First reported in this Forum thread http://forums.opensuse.org/english/get-technical-help-here/network-internet… For others in the thread, unknown whether recommendations were helpful. Note that others in the thread were not using Network Manager, whereas I am. For myself, my wireless networking was not functional (for that matter any networking) was functional resuming from sleep. Attempted to systemctl stop|start|restart network.service systemctl status network service returned Active with no errors after each above attempt. Service was verified stopped and restarted without errors. After rebooting, my network was still unavailable. Attampted again to stop|start|restart services. Then, I did a hardware NIC disable/re-enable which resulted in NM reporting networking enabled, but wireless "undetermined" (no check or unchecked box, a weird white box). Using NM, unchecked, re-checked "networking" and the wireless box was "normal, unchecked" Checked the box an wireless is working. After the wireless working was working again, I re-ran "systemctl status network.service" with the following results NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sat 2013-05-11 14:35:15 PDT; 56s ago Main PID: 26829 (NetworkManager) CGroup: name=systemd:/system/NetworkManager.service └─26829 /usr/sbin/NetworkManager --no-daemon May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr0): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> failed to allocate link cache: (-10) Operation not supported May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> (virbr2): ignoring bridge not created by NetworkManager May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <warn> /sys/devices/virtual/net/virbr2-nic: couldn't determine device driver; ignoring... May 11 14:35:15 LOCALMACHINE,LOCALNETWORK NetworkManager[26829]: <info> ModemManager available in the bus The above may not be helpful, I suspect that the errors only refer to a number of virtual device bridges I have configured on this machine, but of course NM does not support managing those. Reproducible: Always Steps to Reproduce: 1. zypper up 5/10/2013 2. Put machine to sleep 3. resume machine Actual Results: Networking unavailable. Expected Results: Network should re-connect to available networks automatically Assigning Major, but impact likely depends on whether the User is able to regain networking either by restarting the network service or re-booting. If there are critical programs which would be adversely affected by a re-boot, then the problem is very serious, maybe even critical. -- 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 640407] New: SDL: erroneously uses xrandr-style mode switching
by bugzilla_noreply＠novell.com 09 Feb '18

09 Feb '18

https://bugzilla.novell.com/show_bug.cgi?id=640407 https://bugzilla.novell.com/show_bug.cgi?id=640407#c0 Summary: SDL: erroneously uses xrandr-style mode switching Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: X.Org AssignedTo: bnc-team-xorg-bugs(a)forge.provo.novell.com ReportedBy: jengelh(a)medozas.de QAContact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: Beta-Customer Blocker: --- Starting with 11.3, I am seeing a new issue with my "oversize" desktop (2944x2208 VirtualSize on a 1280x1024 resolution). Problem: SDL-1.2.14. When SDL switches to fullscreen 640x480 - for example, because the game is configured to run in such resolution - or back, it changes the desktop size too by means of xrandr or something along the lines of that. Actual results: Windows on my desktop are reordered, which is usually a result of the WM being forced to do so because the desktop size (virtualsize) changed. Resolution switching also takes significantly longer than it did before — this is another sign that it switches desktop size (too), not just resolution. First the screen goes black-with-backlight and after roughly 500ms, the TFT screen finally gets the new 640x480 mode signal (I use VGA), which is evidenced by the backlight going briefly off. Expected results: Previous behavior. In other worsd, leave desktop size as-is (and subsequently keep my windows where they are) and _only_ change the resolution. The old switching style is also way faster in that there is no black-with-backlight delay. Additional information: Not all programs are affected. The entire group of Doom engines exhibits the behavior for example, though I found that UnrealTournament99 does not. Both Doom and UT use libSDL-1.2.so.0 (no static SDL as far as I can see). Overriding the system SDL 1.2.14 libraries and using LD_LIBRARY_PATH to point to SDL-1.2.13 libraries brings back the desired behavior. -- 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 909119] New: Evince is compiled without XPS support
by bugzilla_noreply＠novell.com 07 Feb '18

07 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=909119 Bug ID: 909119 Summary: Evince is compiled without XPS support Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: a7169932(a)drdrb.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I have libgxps2 installed (I think I got it OOTB), but I can't open OXPS file in Evince. I guess it's compiled without XPS support. Can you change it? -- You are receiving this mail because: You are on the CC list for the bug.

1 3

[Bug 904321] New: Evince can't render certain letter combinations
by bugzilla_noreply＠novell.com 06 Feb '18

06 Feb '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904321 Bug ID: 904321 Summary: Evince can't render certain letter combinations Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: hogg.bob.2(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 612734 --> http://bugzilla.opensuse.org/attachment.cgi?id=612734&action=edit Snippet of a PDF document showing the rendering issue (in PNG format) Evince cannot seem to render certain combinations of sequential letters - particularly the sequences "fi" and "fl". It just displays blank space in that area. But the letters "f", "i", and "l" all display correctly in different sequences. gv/GhostView can display them fine, so I doubt this is a font issue. (I did uninstall most of the non-English fonts that come installed with openSUSE by default to save space, but that should not cause English text to display incorrectly) The attachment is a snippet of a PDF document that shows the rendering issue - the words with the problem are "specified"/"unspecified". (I can't post the PDF itself because of copyright issues, but I can make a minimal example if needed). The bug has been fairly consistently reproducible across more than one PDF document. -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 904089] New: can not add openvpn connection with gnome-control-center
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=904089 Bug ID: 904089 Summary: can not add openvpn connection with gnome-control-center Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: mgoppold(a)web.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.94 Safari/537.36 Build Identifier: fresh install: try to add a openvpn connection but all entries are disabled Reproducible: Always Steps to Reproduce: 1. open gnome-control-center 2. open network 3. dismiss incompatible network service 4. click [+] to add a connection 5. select VPN 6. select OpenVPN 7. Dialog open but all disabled same result as user and root -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 901361] New: IMAP+ plugin forces SSL 3.0
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=901361 Bug ID: 901361 Summary: IMAP+ plugin forces SSL 3.0 Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Evolution Assignee: bnc-team-evolution(a)forge.provo.novell.com Reporter: sionescu(a)cddr.org QA Contact: lakhil(a)novell.com Found By: --- Blocker: --- Today(2014-10-15), FastMail disabled SSL 3.0 on all their servers because of a recently discovered vulnerability, and Evolution cannot connect to the imap server because it apparently forces SSL 3.0 on the outbound connection. I'm using Evolution 3.10.4-24.1 on x86_64 and the account is configured as follows: plugin IMAP+ on host "mail.messagingengine.com", port 993, encryption method "SSL on a dedicated port" The exact error message I get is "Could not connect to 'mail.messagingengine.com:993': Cannot communicate securely with peer: no common encryption algorithm(s)." -- You are receiving this mail because: You are on the CC list for the bug.

1 13

[Bug 907982] New: Segfault with g_type_check_instance_cast
by bugzilla_noreply＠novell.com 30 Jan '18

30 Jan '18

http://bugzilla.opensuse.org/show_bug.cgi?id=907982 Bug ID: 907982 Summary: Segfault with g_type_check_instance_cast Classification: openSUSE Product: openSUSE 13.1 Version: Final Hardware: x86-64 OS: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: toganm(a)dinamizm.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 615610 --> http://bugzilla.opensuse.org/attachment.cgi?id=615610&action=edit darktable gdb backtrace for the segfault When using Darktable from home:toganm:photography repo which is based on darktable git master branch, I had segfaults. Darktable development thinks this is an issue with either gobject or glib. Attached is the latest gdb trace. Let me know if more info is needed Thanks -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 897422] New: systemd ignores swap options in fstab
by bugzilla_noreply＠novell.com 08 Jan '18

08 Jan '18

https://bugzilla.novell.com/show_bug.cgi?id=897422 https://bugzilla.novell.com/show_bug.cgi?id=897422#c0 Summary: systemd ignores swap options in fstab Classification: openSUSE Product: openSUSE Factory Version: 201409* Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: seife(a)novell.slipkontur.de QAContact: qa-bugs(a)suse.de Found By: Third Party Developer/Partner Blocker: --- Because I'm running on a SSD, I added the following to my fstab: susi:~ # grep swap /etc/fstab /dev/sda5 swap swap discard=once 0 0 This works well, if I do "swapon -a"; Sep 19 08:19:31 susi kernel: [583832.054201] Adding 2093052k swap on /dev/sda5. Priority:-1 extents:1 across:2093052k SSDsFS But during boot, it is not honored: susi:~ # dmesg|grep swap [ 8.339693] Adding 2093052k swap on /dev/sda5. Priority:-1 extents:1 across:2093052k SSFS (the missing "Ds" flags) Searching for who activates swap during boot, I looked through /var/log/boot.log: /var/log/boot.log: Activating swap /dev/sda5... /var/log/boot.log:[ OK ] Activated swap /dev/sda5. so I looked in the usual suspect for that string: susi:~ # rpm -ql systemd | xargs grep "Activating swap" 2>/dev/null Binary file /bin/systemd matches Binary file /usr/lib/systemd/systemd matches => systemd bug? -- 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 903854] New: nameserver line missing from /etc/resolv.conf; interface is controlled by networkmanager
by bugzilla_noreply＠novell.com 25 Dec '17

25 Dec '17

http://bugzilla.opensuse.org/show_bug.cgi?id=903854 Bug ID: 903854 Summary: nameserver line missing from /etc/resolv.conf; interface is controlled by networkmanager Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Major Priority: P5 - None Component: Network Assignee: bnc-team-screening(a)forge.provo.novell.com Reporter: lmuelle(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- This system got upgraded from openSUSE 13.1 to 13.2. After resuming from suspend to memory DNS resolving doesn't work as /etc/esolv.conf hase no nameserver line. Beside the usual header with comments it has search example.org but no nameserver at all. On the other side dhcpcd-test reports a DNSSERVERS mug:~ # dhcpcd-test enp0s25 | grep ^DNSSERVERS= DNSSERVERS='192.168.178.1' Network cable reconnection fixes the issue and /etc/esolv.conf got: ### many lines of comments search example.org nameserver 192.168.178.1 nameserver fd00::2665:11ff:fef7:203b -- You are receiving this mail because: You are on the CC list for the bug.

1 9