May 2014 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 800701] New: X windows is corrupt after logging in on an AMD A10-5800K APU
by bugzilla_noreply＠novell.com 31 Jul '18

31 Jul '18

https://bugzilla.novell.com/show_bug.cgi?id=800701 https://bugzilla.novell.com/show_bug.cgi?id=800701#c0 Summary: X windows is corrupt after logging in on an AMD A10-5800K APU Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Xen AssignedTo: jdouglas(a)suse.com ReportedBy: ajbiii(a)comcast.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1 Installed 12.3. The regular kernel and X windows works fine. Reboot to the xen kernel. The login screen is displayed correctly. After logging in, the display is corrupt. The mouse pointer is ok and I can see that the menu is active by putting the cursor in the lower left corner and clicking but the display is unusable. Just an aside: The xen kernel wouldn't even boot on the APU with 12.1 or 12.2. Reproducible: Always Steps to Reproduce: 1. Install 12.3 on an AMD Trinity APU. 2. Boot regular kernel, log in and verify X is working. 3. Reboot with the xen kernel. 4. Log in and observe the corruption Actual Results: Screen is corrupt Expected Results: Normal X windows operation -- 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 23

[Bug 879402] New: date format of atq is unusable for sorting
by bugzilla_noreply＠novell.com 29 Jul '18

29 Jul '18

https://bugzilla.novell.com/show_bug.cgi?id=879402 https://bugzilla.novell.com/show_bug.cgi?id=879402#c0 Summary: date format of atq is unusable for sorting Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: martin(a)oneiros.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0 The atq in 13.1 uses a date/time format that is unsuitable for sorting by date/time and there is no way to set the date format used (e.g. to ISO8601). Reproducible: Always Steps to Reproduce: 1. Set up some jobs with at 2. Run atq Actual Results: > atq 1377 Thu May 29 15:04:00 2014 a ms 1387 Thu May 22 21:59:00 2014 a ms 1376 Thu May 29 18:39:00 2014 a ms 1372 Wed May 28 21:32:00 2014 a ms 1 Fri May 23 21:04:00 2014 a ms 1361 Sun May 25 08:04:00 2014 a ms 1373 Thu May 29 09:29:00 2014 a ms 1367 Tue May 27 20:02:00 2014 a ms 4 Fri May 23 22:03:00 2014 a ms 1369 Wed May 28 21:04:00 2014 a ms 7 Sat May 24 19:04:00 2014 a ms 10 Sat May 24 23:03:00 2014 a ms Expected Results: The date format should be ISO 8601 - or there should be a switch to set the date format used. The atq up to 12.3 used ISO 8601, so this is a regression. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612075 -- 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 13

[Bug 869116] New: Apper No Longer Requires escalation to root auth to make changes to installing O/S changes
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=869116 https://bugzilla.novell.com/show_bug.cgi?id=869116#c0 Summary: Apper No Longer Requires escalation to root auth to make changes to installing O/S changes Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Major Priority: P5 - None Component: Security AssignedTo: security-team(a)suse.de ReportedBy: secure(a)aphofis.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 Apper in its now current for will not call for escalation to root authority to modify and install changes to O/S. If we wanted to copy MS convention where updates and changes to the O/S....we would use it. This is one of the stand-out security features thats sets our O/S above the rest and to enable these changes without root authority sets a dangerous precedent Reproducible: Always Steps to Reproduce: 1. Every time apper wants to make changes to the O/S 100% reproducable 2. 3. Actual Results: No escalation to root authority is called by apper Expected Results: Changes to O/S should be the privilege of root and no user authority and escalation to root should be called for before we let any application change the O/S With so much log data files I don’t really no what to supply to support this...Please provide details of what audit log files you require to solve. Priority set as this is a direct threat to O/S security and its now broken as previously root auth was always required. Please do not close as DOWNSTREAM OR UPSTREAM..Apper is an integral and non optional inclusion to the packing list of 12.3 and as such the product opensuse is the arbiter and coordinator of Apper -- 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 848914] New: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS
by bugzilla_noreply＠novell.com 19 Jun '18

19 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=848914 https://bugzilla.novell.com/show_bug.cgi?id=848914#c0 Summary: Publish Information around Partitioning Requirements of Boot Requirements with UEFI BIOS Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Enhancement Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: secure(a)aphofis.com QAContact: jsrain(a)suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Firefox/24.0 If ever we are going to see changed in PC BIOS's it will be in this decade. Current UEFI BIOS's are standard with most all X_64 Motherboards. The UEFI BIOS is a temporary measure to permit backwardly compatible Processors and Motherboards and my enhancement would be to publish partitioning information on screen thats not an option before the partitioning phase of Installation. Current warnings generated by the Partitioner itself do warn of requirements for /boot/uefi with FAT. As there will be many changes to BIOS this decade I think we need a mandatory full screen explanation of partitioning changes that can be written for all coming versions as it will be needed and under that preface every installation from 13.x to anything can all make use of a text screen before the partitioner is displayed on screen as part of every Installation Reproducible: Always Steps to Reproduce: 1. Try to configure a boot partition with an X_64 UEFI BIOS and a warning is generated on the users final acceptance of the chosen partitioning. 2. The warning is too late and there is not sufficient space to provide detailed instructions and the reasoning and its going to get more problematic. Additionally as soon as M.S come out with a new file formation partitioning we will need to spell partitioning out in a clear concise way before the user does anything with the partitioner 3. Expected Results: Its a small and advantages addition to the Install Program to have a text screen available before the partitioning part of our current installation is reached. Currently we only knock back the partitioning with a warning after the partitioner has been used. It needs full explanation before not a single line after. It should be very easy to implement this text screen as the need far outweighs the man hour time factor it would take to implement above. I believe this should be assigned and completed as an urgent undertaking before we ship another version as its benefit now and future is so very important. -- 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 813340] New: Suspected memory corruption in standard capi20 lib
by bugzilla_noreply＠novell.com 17 Jun '18

17 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=813340 https://bugzilla.novell.com/show_bug.cgi?id=813340#c0 Summary: Suspected memory corruption in standard capi20 lib Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 0 Platform: x86-64 OS/Version: openSUSE 12.3 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: jan.fengler(a)adviqo.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 The capi20 lib from the i4l-base source-package from http://download.opensuse.org/repositories/home:/kkeil:/ISDN/openSUSE_Factor… (and also Version 3.23-100.1 which is newer) seems to create memory corruption during capi20_put_message sending data_b3_req, because no memory is assigned for the data that is put behind the original message in the function capi_processMessage (capi20.c row 962ff). Unfortunately this seems to be a private function and so i could not easily write a test against the entire lib. Reproducible: Always Steps to Reproduce: I provide an example program that uses a 1:1 copy of the original function. I use capi via JNI from Java and it crashes when freeing memory exactly as the test program does. Actual Results: Memory corruption when freeing the memory used for the data_b3_req-message. Expected Results: No memory corruption, the program should terminate without a problem. The last known working version (from openSuSE 10.3) assigned memory for SND_BUFSIZ bytes and copied the original message to this before copying the data bytes after the message and that worked. I will change the code of the function standardPutMessage to do this to avoid the problem and add a patch to this bug report if it works with the patch. I must admit that i could have overseen something, but unfortunately it seems not so far. -- 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 9

[Bug 872264] New: 'hostname -s' returns "hostname: Name or service not known" when content of /etc/HOSTNAME omits domain
by bugzilla_noreply＠novell.com 15 Jun '18

15 Jun '18

https://bugzilla.novell.com/show_bug.cgi?id=872264 https://bugzilla.novell.com/show_bug.cgi?id=872264#c0 Summary: 'hostname -s' returns "hostname: Name or service not known" when content of /etc/HOSTNAME omits domain Classification: openSUSE Product: openSUSE Factory Version: 13.2 Milestone 0 Platform: PC OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: mrmazda(a)earthlink.net QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- To reproduce: 1-configure /etc/HOSTNAME sans domain (no dots contained therein) 2-run any script containing 'hostname -s' Actual behavior: 1-script output disrupted by return of "hostname: Name or service not known" Expected behavior: 1-same output as if -s had been omitted from hostname call Comments: 1-Cauldron and Rawhide both sensibly produce same short hostname output from 'hostname' as from 'hostname -s' when /etc/hostname omits dot(s)/domain. 2-According to the man page, 'hostname -s' should "Display the short host name. This is the host name cut at the first dot.", as it does in current Cauldron and Rawhide, whose hostname man page contains the identical description of -s as Factory's. -- 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 700065] New: the wiki produces invalid XHTML
by bugzilla_noreply＠novell.com 27 May '18

27 May '18

https://bugzilla.novell.com/show_bug.cgi?id=700065 https://bugzilla.novell.com/show_bug.cgi?id=700065#c0 Summary: the wiki produces invalid XHTML Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: x86-64 OS/Version: openSUSE 11.4 Status: NEW Severity: Minor Priority: P5 - None Component: Wiki AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: giecrilj(a)stegny.2a.pl QAContact: adrian(a)novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 The wiki pages are declared to be XHTML 1.0 Transitional. A script inserted into every HEAD violates this declaration. Reproducible: Always Steps to Reproduce: 1. Validate <URL: http://en.opensuse.org/Main_Page >. 2. Inspect the document source. Actual Results: 1. Line 21, Column 16: required attribute "type" not specified 2. <script> Expected Results: 1. No errors 2. <script type="text/javascript" > -- 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 16

[Bug 682920] New: strange defaults in mailman
by bugzilla_noreply＠novell.com 15 May '18

15 May '18

https://bugzilla.novell.com/show_bug.cgi?id=682920 https://bugzilla.novell.com/show_bug.cgi?id=682920#c0 Summary: strange defaults in mailman Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: openSUSE 11.3 Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: jmatejek(a)novell.com ReportedBy: suse-beta(a)cboltz.de QAContact: qa(a)suse.de Found By: Beta-Customer Blocker: --- (partly copied from http://mail.python.org/pipermail/mailman-users/2007-November/058954.html after seeing the same problem on 11.3) I called "/usr/lib/mailman/bin/newlist mailman" to create the master mailing list. Doing so resulted in the error Bad owner email address: mailman@(unused) The openSUSE Mailman package sets DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST to '(unused)' in Defaults.py, which causes this problem. Please use a default without parenthesis - according to the mail I linked above, this should display the "correct" error message about an invalid list address. Of course it would be even better to have an error message that says DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST need to be set - but that's probably something for upstream. -- 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 829715] New: Translation for "Education" program group and program "Virtual globe"
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=829715 https://bugzilla.novell.com/show_bug.cgi?id=829715#c0 Summary: Translation for "Education" program group and program "Virtual globe" Classification: openSUSE Product: openSUSE Factory Version: 13.1 Milestone 3 Platform: x86-64 OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers(a)suse.de ReportedBy: asv(a)lumo.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: No Created an attachment (id=548179) --> (http://bugzilla.novell.com/attachment.cgi?id=548179) "Education" not translated "Education" program group as well as "Virtual globe" program name in k-menu is not translated. See screenshot (german version) -- 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 14

[Bug 878503] New: xlock: Error in `/usr/lib/xlock/xlock': free(): invalid pointer: 0x0000000002252630
by bugzilla_noreply＠novell.com 15 Mar '18

15 Mar '18

https://bugzilla.novell.com/show_bug.cgi?id=878503 https://bugzilla.novell.com/show_bug.cgi?id=878503#c0 Summary: xlock: Error in `/usr/lib/xlock/xlock': free(): invalid pointer: 0x0000000002252630 Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: X11 Applications AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: admin(a)ifyouwantblood.de QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.116 Safari/537.36 SUSE/34.0.1847.116 xlock crashed while running a screensaver. no user input, i came back to my pc and xlock was gone. the memory map doesn't look complete, but there is nothing more. Reproducible: Sometimes Steps to Reproduce: 1. xlock 2. 3. Actual Results: ==== Backtrace: ========= /lib64/libc.so.6(+0x7410f)[0x7f71dd82c10f] /lib64/libc.so.6(+0x7996e)[0x7f71dd83196e] /usr/lib/xlock/xlock[0x423191] /usr/lib/xlock/xlock[0x427e55] /usr/lib/xlock/xlock[0x41133f] /usr/lib/xlock/xlock[0x50ff4d] /usr/lib/xlock/xlock[0x411466] /usr/lib/xlock/xlock[0x40b9b7] /usr/lib/xlock/xlock[0x40bcdc] /usr/lib/xlock/xlock[0x40d6cb] /usr/lib/xlock/xlock[0x40a697] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f71dd7d9be5] /usr/lib/xlock/xlock[0x40af01] ======= Memory map: ======== 00400000-005ac000 r-xp 00000000 00:14 1309675 /usr/lib/xlock/xlock 007ab000-007ac000 r--p 001ab000 00:14 1309675 /usr/lib/xlock/xlock 007ac000-00878000 rw-p 001ac000 00:14 1309675 /usr/lib/xlock/xlock 00878000-008dc000 rw-p 00000000 00:00 0 01e0e000-0235a000 rw-p 00000000 00:00 0 [heap] 7f71d3edb000-7f71d3efb000 rw-s 1d9ddf000 00:04 1290 /dev/dri/card0 7f71d3efb000-7f71d3f1b000 rw-s 1d9dbf000 00:04 1290 /dev/dri/card0 7f71d3f1b000-7f71d3f3b000 rw-s 1d9d9f000 00:04 1290 /dev/dri/card0 7f71d3f3b000-7f71d3f5b000 rw-s 1d9d7f000 00:04 1290 /dev/dri/card0 7f71d3f5b000-7f71d3f7b000 rw-s 1d9d5f000 00:04 1290 /dev/dri/card0 7f71d3f7b000-7f71d3f9b000 rw-s 1d9d3f000 00:04 1290 /dev/dri/card0 7f71d3f9b000-7f71d3fbb000 rw-s 1d9d1f000 00:04 1290 /dev/dri/card0 7f71d3fbb000-7f71d3fdb000 rw-s 1d9cff000 00:04 1290 /dev/dri/card0 7f71d3fdb000-7f71d3ffb000 rw-s 1d9cdf000 00:04 1290 /dev/dri/card0 7f71d3ffb000-7f71d401b000 rw-s 1d9cbf000 00:04 1290 /dev/dri/card0 7f71d401b000-7f71d403b000 rw-s 1d9c9f000 00:04 1290 /dev/dri/card0 7f71d403b000-7f71d405b000 rw-s 1d9c7f000 00:04 1290 /dev/dri/card0 7f71d405b000-7f71d407b000 rw-s 1d9c5f000 00:04 1290 /dev/dri/card0 7f71d407b000-7f71d409b000 rw-s 1d9c3f000 00:04 1290 /dev/dri/card0 7f71d409b000-7f71d40bb000 rw-s 1d9c1f000 00:04 1290 /dev/dri/card0 7f71d40bb000-7f71d40db000 rw-s 1d9bff000 00:04 1290 /dev/dri/card0 7f71d40db000-7f71d40fb000 rw-s 1d9bdf000 00:04 1290 /dev/dri/card0 7f71d40fb000-7f71d411b000 rw-s 1d9bbf000 00:04 1290 /dev/dri/card0 7f71d411b000-7f71d413b000 rw-s 1d9b9f000 00:04 1290 /dev/dri/card0 7f71d439b000-7f71d43bb000 rw-s 1d991f000 00:04 1290 /dev/dri/card0 7f71d43bb000-7f71d43db000 rw-s 1d98ff000 00:04 1290 /dev/dri/card0 7f71d43db000-7f71d43fb000 rw-s 1d98df000 00:04 1290 /dev/dri/card0 7f71d43fb000-7f71d441b000 rw-s 1d98bf000 00:04 1290 /dev/dri/card0 7f71d441b000-7f71d443b000 rw-s 1d989f000 00:04 1290 /dev/dri/card0 7f71d443b000-7f71d445b000 rw-s 1d987f000 00:04 1290 /dev/dri/card0 7f71d445b000-7f71d447b000 rw-s 1d985f000 00:04 1290 /dev/dri/card0 7f71d447b000-7f71d449b000 rw-s 1d983f000 00:04 1290 /dev/dri/card0 7f71d449b000-7f71d44bb000 rw-s 1d981f000 00:04 1290 /dev/dri/card0 7f71d44bb000-7f71d44db000 rw-s 1d97ff000 00:04 1290 /dev/dri/card0 7f71d44db000-7f71d44fb000 rw-s 1d97df000 00:04 1290 /dev/dri/card0 7f71d44fb000-7f71d451b000 rw-s 1d97bf000 00:04 1290 /dev/dri/card0 7f71d451b000-7f71d453b000 rw-s 1d979f000 00:04 1290 /dev/dri/card0 7f71d453b000-7f71d455b000 rw-s 1d977f000 00:04 1290 /dev/dri/card0 7f71d455b000-7f71d457b000 rw-s 1d975f000 00:04 1290 /dev/dri/card0 7f71d457b000-7f71d459b000 rw-s 1d973f000 00:04 1290 /dev/dri/card0 7f71d459b000-7f71d45bb000 rw-s 1d971f000 00:04 1290 /dev/dri/card0 7f71d45bb000-7f71d45db000 rw-s 1d96ff000 00:04 1290 /dev/dri/card0 7f71d45db000-7f71d45fb000 rw-s 1d96df000 00:04 1290 /dev/dri/card0 7f71d45fb000-7f71d467b000 rw-s 1d783d000 00:04 1290 /dev/dri/card0 7f71d467b000-7f71d46fb000 rw-s 1d87ef000 00:04 1290 /dev/dri/card0 7f71d46fb000-7f71d471b000 rw-s 1ccf1a000 00:04 1290 /dev/dri/card0 7f71d471b000-7f71d473b000 rw-s 1ccefa000 00:04 1290 /dev/dri/card0 7f71d473b000-7f71d47bb000 rw-s 1748b7000 00:04 1290 /dev/dri/card0 7f71d47bb000-7f71d483b000 rw-s 174837000 00:04 1290 /dev/dri/card0 7f71d483b000-7f71d48bb000 rw-s 1747b7000 00:04 1290 /dev/dri/card0 7f71d48bb000-7f71d52bb000 rwxp 00000000 00:00 0 7f71d52bb000-7f71d533b000 rw-s 172276000 00:04 1290 /dev/dri/card0 7f71d5343000-7f71d5363000 rw-s 1d96bf000 00:04 1290 /dev/dri/card0 7f71d5363000-7f71d5383000 rw-s 1d969f000 00:04 1290 /dev/dri/card0 7f71d5383000-7f71d53a3000 rw-s 1d967f000 00:04 1290 /dev/dri/card0 7f71d53a3000-7f71d53c3000 rw-s 1cdec3000 00:04 1290 /dev/dri/card0 7f71d53c3000-7f71d53cc000 r-xp 00000000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d53cc000-7f71d55cb000 ---p 00009000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d55cb000-7f71d55cc000 r--p 00008000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d55cc000-7f71d55cd000 rw-p 00009000 00:14 555537 /usr/lib64/libXrender.so.1.3.0 7f71d55cd000-7f71d55d7000 r-xp 00000000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d55d7000-7f71d57d6000 ---p 0000a000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d57d6000-7f71d57d7000 r--p 00009000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d57d7000-7f71d57d8000 rw-p 0000a000 00:14 555877 /usr/lib64/libXcursor.so.1.0.2 7f71d57d8000-7f71d5858000 rw-s 174737000 00:04 1290 /dev/dri/card0 7f71d5858000-7f71d585c000 r-xp 00000000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d585c000-7f71d5a5b000 ---p 00004000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d5a5b000-7f71d5a5c000 r--p 00003000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d5a5c000-7f71d5a5d000 rw-p 00004000 00:14 1242554 /usr/lib64/libtxc_dxtn.so 7f71d5a5d000-7f71d5a97000 r-xp 00000000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5a97000-7f71d5c97000 ---p 0003a000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5c97000-7f71d5c99000 r--p 0003a000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5c99000-7f71d5c9a000 rw-p 0003c000 00:14 555606 /usr/lib64/libLLVMObject.so 7f71d5c9a000-7f71d5cbe000 r-xp 00000000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5cbe000-7f71d5ebe000 ---p 00024000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5ebe000-7f71d5ebf000 r--p 00024000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5ebf000-7f71d5ec0000 rw-p 00025000 00:14 555604 /usr/lib64/libLLVMMCParser.so 7f71d5ec0000-7f71d5edf000 r-xp 00000000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d5edf000-7f71d60df000 ---p 0001f000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d60df000-7f71d60e0000 r--p 0001f000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d60e0000-7f71d60e1000 rw-p 00020000 00:14 555632 /usr/lib64/libLLVMipa.so 7f71d60e1000-7f71d615c000 r-xp 00000000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d615c000-7f71d635c000 ---p 0007b000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d635c000-7f71d635e000 r--p 0007b000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d635e000-7f71d6360000 rw-p 0007d000 00:14 555623 /usr/lib64/libLLVMTransformUtils.so 7f71d6360000-7f71d63ce000 r-xp 00000000 00:14 555596 /usr/lib64/ this is a Tumbleweed install. -- 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