February 2016 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 867499] Cannot enable second radeon card, although it is recognized.
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=867499 http://bugzilla.suse.com/show_bug.cgi?id=867499#c9 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WONTFIX |UPSTREAM --- Comment #9 from Egbert Eich <eich(a)suse.com> --- Actually, let's mark it UPSTREAM. This is used when a ticket gets transferred to upstream. This is however independent if a fix was provided or not. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 867499] Cannot enable second radeon card, although it is recognized.
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=867499 http://bugzilla.suse.com/show_bug.cgi?id=867499#c8 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |WONTFIX Flags|needinfo?(strzol(a)gmail.com) | --- Comment #8 from Egbert Eich <eich(a)suse.com> --- Ok, thanks for confirming! I will close it as WONTFIX as the issue went away by updating with no explicit fix provided. I don't know any better resolution state. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 940294] New: [TRACKER] Issues of X.Org Xserver accessing systemd-logind
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=940294 Bug ID: 940294 Summary: [TRACKER] Issues of X.Org Xserver accessing systemd-logind Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Milestone 1 Hardware: All OS: Other Status: CONFIRMED Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: eich(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com CC: sndirsch(a)suse.com Blocks: 934901, 939432, 939571, 939594, 939838 Found By: Development Blocker: --- This is meant as a tracker for the various issues that arise from the X.Org Xserver accessing systemd-logind. boo#934901 - Do not restart systemd-logind during package update boo#939432 - Does not boot after installing in virtualbox No fallback to fbdev. boo#939571 - gdm can't show up after logout boo#939594 - X11 fails to start after second boot boo#939838 - Starting X manually from VT results in a blank screen -- You are receiving this mail because: You are on the CC list for the bug.

1 9

[Bug 934901] Do not restart systemd-logind during package update
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=934901 http://bugzilla.suse.com/show_bug.cgi?id=934901#c28 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |xorg-maintainer-bugs@forge. | |provo.novell.com Resolution|--- |FIXED Assignee|xorg-maintainer-bugs@forge. |systemd-maintainers(a)suse.de |provo.novell.com | Flags|needinfo?(systemd-maintaine | |rs(a)suse.de) | --- Comment #28 from Egbert Eich <eich(a)suse.com> --- On a VT switch the Xserver gives up DRM master so that another Xserver can obtain it. When switching back, it cannot become DRM master any more without the help of systemd-logind if it is not running as root. I've discussed this with Hans de Goede over dinner at FOSDEM: He had discussed this issue extensively with Lennard: 1. systemd-logind should have at least the lifetime of the Xserver if not of the system. Its restart should be delayed during an update unless it is clear no Xserver is running. (Maybe by checking the pids in /tmp/.X*-lock for mapping /usr/bin/Xorg: ls -l /proc/$xpid/map_files/ | grep -q "/usr/bin/Xorg"). There is in fact no reason to restart it unless there is a security issue somewhere. 2. systemd-logind should not crash: it is a simple enough application (much simpler than the Xserver), if it crashes it is tantamount to the Xserver crashing. 3. Anything we can do on the side of the Xserver will be kludgey. I would therefore like to close this ticket now with the fix we currently have. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 867499] Cannot enable second radeon card, although it is recognized.
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=867499 http://bugzilla.suse.com/show_bug.cgi?id=867499#c7 --- Comment #7 from Stratos Zolotas <strzol(a)gmail.com> --- I think this was resolved...I had forgotten it and I am on 42.1 now (was on 13.2 when I reported it. I think you can close it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 965028] [nvidia prop] system breaks when upgrading
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965028 http://bugzilla.suse.com/show_bug.cgi?id=965028#c7 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|system breaks when |[nvidia prop] system breaks |upgrading |when upgrading --- Comment #7 from Egbert Eich <eich(a)suse.com> --- Furthermore, the issues with the driver in the nvidia repo may be resolved already - there has been a mixup with repo names. Please test these. Before you do, please follow the de-installation steps for the driver from the web site carefully to make sure all traces have been removed. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 867499] Cannot enable second radeon card, although it is recognized.
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=867499 http://bugzilla.suse.com/show_bug.cgi?id=867499#c6 Egbert Eich <eich(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |strzol(a)gmail.com Flags| |needinfo?(strzol(a)gmail.com) --- Comment #6 from Egbert Eich <eich(a)suse.com> --- Stratos, is this the same machine & GPU setup you tested boo#962295 for? If so, we should be past the detection issue. Being that this issue is for TW there is no released version to fix. Can this ticket be closed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 835975] GUI install fails on iMac with Radeon, text install does not start X11
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=835975 http://bugzilla.suse.com/show_bug.cgi?id=835975#c38 --- Comment #38 from Egbert Eich <eich(a)suse.com> --- Gary, it looks like this issue is more complicated than I thought. In comment #27 you offered ssh access to me. If you can set this up for me, we may be able to speed up this. Please, email me in private. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 962295] New: X server crashs when user rotate monitor 90 degrees .
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=962295 Bug ID: 962295 Summary: X server crashs when user rotate monitor 90 degrees . Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs(a)forge.provo.novell.com Reporter: mcaj(a)suse.com QA Contact: xorg-maintainer-bugs(a)forge.provo.novell.com Found By: --- Blocker: --- Created attachment 662038 --> http://bugzilla.suse.com/attachment.cgi?id=662038&action=edit Xorg setting HI reasonably I replace my Nvidia VGA cards with ATI/AMD cards. The binary driver worked there very strange and I was able to use it any more. So lets run the open-source driver for ATI radeon. In my case I have two separate VGA cards, each of them is connect to one monitor. and one monitor is rotate 90 degrees clockwise. My cards are: 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] Subsystem: ASUSTeK Computer Inc. Device [1043:0471] Kernel driver in use: radeon Kernel modules: radeon -- 04:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series] [1002:68f9] Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e164] Kernel driver in use: radeon Kernel modules: radeon the Xorg setting looks ( /home/$USERNAME/.local/share/kscreen/* ) like the attachment file 9d5da4196763fd85520f8065dfeb4453 There the option "rotation" id its set to 2 rotate the monitor as I need. Steps to reproduce: 1. take machine with two VGA ATI//AMD cards with up to date Leap standard installation with KDE/Plasma. 2. start it with two monitor - no rotation set yet. 3. stop X and setup rotate in the file /home/$USERNAME/.local/share/kscreen/* to 2 for one monitor there. 4. start the X server. You will get errors like this example (EE) BUG: triggered 'if (axnum >= dev->valuator->numAxes)' (EE) BUG: exevents.c:2087 in InitValuatorAxisStruct() (EE) (EE) Backtrace: (EE) 0: X (xorg_backtrace+0x48) [0x58b0c8] (EE) 1: X (InitValuatorAxisStruct+0x68) [0x51f748] (EE) 2: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fa56569d000+0x5479) [0x7fa5656a2479] (EE) 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fa56569d000+0x590f) [0x7fa5656a290f] (EE) 4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fa56569d000+0x763b) [0x7fa5656a463b] (EE) 5: X (ActivateDevice+0x37) [0x432d97] (EE) 6: X (0x400000+0x88fa6) [0x488fa6] (EE) 7: X (0x400000+0x9e9db) [0x49e9db] (EE) 8: X (0x400000+0x9efa3) [0x49efa3] (EE) 9: X (config_init+0x9) [0x49d9f9] (EE) 10: X (InitInput+0xab) [0x47cc0b] (EE) 11: X (0x400000+0x40f79) [0x440f79] (EE) 12: /lib64/libc.so.6 (__libc_start_main+0xf5) [0x7fa5721c6b05] (EE) 13: X (0x400000+0x2c5de) [0x42c5de] (EE) -- You are receiving this mail because: You are on the CC list for the bug.

1 16

[Bug 965513] New: dleyna-renderer crashes sometimes with file not foudn error
by bugzilla_noreply＠novell.com 07 Feb '16

07 Feb '16

http://bugzilla.suse.com/show_bug.cgi?id=965513 Bug ID: 965513 Summary: dleyna-renderer crashes sometimes with file not foudn error Classification: openSUSE Product: openSUSE Tumbleweed Version: 2015* Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome(a)forge.provo.novell.com Reporter: tchvatal(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 664685 --> http://bugzilla.suse.com/attachment.cgi?id=664685&action=edit dleyna.core scarabeus@arcarius: ~ $ LC_ALL=C coredumpctl gdb /usr/lib/dleyna-renderer-service PID: 23147 (dleyna-renderer) UID: 1000 (scarabeus) GID: 100 (users) Signal: 11 (SEGV) Timestamp: Sat 2016-02-06 21:50:57 CET (13h ago) Command Line: /usr/lib/dleyna-renderer-service Executable: /usr/lib/dleyna-renderer-service Control Group: /user.slice/user-1000.slice/session-1.scope Unit: session-1.scope Slice: user-1000.slice Session: 1 Owner UID: 1000 (scarabeus) Boot ID: a8ce4c026ff3481ca857e1e84b9a89bd Machine ID: b4ea4eb15ab7c29b6cc20a47544e5eb7 Hostname: arcarius.suse.cz Coredump: /var/lib/systemd/coredump/core.dleyna-renderer.1000.a8ce4c026ff3481ca857e1e84b9a89bd.23147.1454791857000000.xz Message: Process 23147 (dleyna-renderer) of user 1000 dumped core. GNU gdb (GDB; openSUSE Factory) 7.10.1 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/dleyna-renderer-service...Reading symbols from /usr/lib/debug/usr/lib/dleyna-renderer-service.debug...done. done. warning: core file may not match specified executable file. [New LWP 23147] [New LWP 23148] [New LWP 23149] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `/usr/lib/dleyna-renderer-service'. Program terminated with signal SIGSEGV, Segmentation fault. #0 dlr_device_unsubscribe (device=0x70ed40) at device.c:434 434 device.c: No such file or directory. [Current thread is 1 (Thread 0x7f431fb34840 (LWP 23147))] (gdb) bt #0 0x00007f431f230848 in dlr_device_unsubscribe (device=0x70ed40) at device.c:434 #1 0x00007f431f236e4a in dlr_upnp_unsubscribe (upnp=<optimized out>) at upnp.c:840 #2 0x00007f431f2342e7 in prv_control_point_stop_service () at server.c:722 #3 0x00007f431f751e08 in prv_context_quit_cb (user_data=<optimized out>) at libdleyna/core/main-loop.c:61 #4 0x00007f431f489f4a in g_main_context_dispatch (context=0x710140) at gmain.c:3154 #5 0x00007f431f489f4a in g_main_context_dispatch (context=context@entry=0x710140) at gmain.c:3769 #6 0x00007f431f48a2c8 in g_main_context_iterate (context=0x710140, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3840 #7 0x00007f431f48a5e2 in g_main_loop_run (loop=0x744700) at gmain.c:4034 #8 0x00007f431f751fec in dleyna_main_loop_start (server=<optimized out>, control_point=<optimized out>, user_data=0x0) at libdleyna/core/main-loop.c:155 #9 0x00007f431ec84610 in __libc_start_main (main=0x4008e0 <main>, argc=1, argv=0x7fff3f729c08, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3f729bf8) at libc-start.c:289 #10 0x0000000000400949 in _start () at ../sysdeps/x86_64/start.S:118 (gdb) bt full #0 0x00007f431f230848 in dlr_device_unsubscribe (device=0x70ed40) at device.c:434 i = 0 dev = 0x70ed40 Python Exception <class 'gdb.MemoryError'> Cannot access memory at address 0x4d53fd8948555441: context = #1 0x00007f431f236e4a in dlr_upnp_unsubscribe (upnp=<optimized out>) at upnp.c:840 iter = {dummy1 = 0x744de0, dummy2 = 0x7f430c001320, dummy3 = 0x0, dummy4 = 0, dummy5 = 0, dummy6 = 0x0} device = 0x70ed40 #2 0x00007f431f2342e7 in prv_control_point_stop_service () at server.c:722 #3 0x00007f431f751e08 in prv_context_quit_cb (user_data=<optimized out>) at libdleyna/core/main-loop.c:61 #4 0x00007f431f489f4a in g_main_context_dispatch (context=0x710140) at gmain.c:3154 dispatch = 0x7f431f486bb0 <g_idle_dispatch> prev_source = 0x0 was_in_call = 0 user_data = 0x0 callback = 0x7f431f751df0 <prv_context_quit_cb> cb_funcs = <optimized out> cb_data = 0x70efd0 need_destroy = <optimized out> source = 0x70ee00 current = 0x725700 i = 1 #5 0x00007f431f489f4a in g_main_context_dispatch (context=context@entry=0x710140) at gmain.c:3769 #6 0x00007f431f48a2c8 in g_main_context_iterate (context=0x710140, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3840 max_priority = 200 timeout = 0 some_ready = 1 nfds = <optimized out> allocated_nfds = 7 fds = 0x746f00 #7 0x00007f431f48a5e2 in g_main_loop_run (loop=0x744700) at gmain.c:4034 __func__ = "g_main_loop_run" #8 0x00007f431f751fec in dleyna_main_loop_start (server=<optimized out>, control_point=<optimized out>, user_data=0x0) at libdleyna/core/main-loop.c:155 retval = 1 #9 0x00007f431ec84610 in __libc_start_main (main=0x4008e0 <main>, argc=1, argv=0x7fff3f729c08, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff3f729bf8) at libc-start.c:289 result = <optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -8154818167302845658, 4196640, 140734257863680, 0, 0, 8154394328421305126, 8093664545504168742}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x400a30 <__libc_csu_init>, 0x7fff3f729c08}, data = {prev = 0x0, cleanup = 0x0, canceltype = 4196912}}} not_first_call = <optimized out> #10 0x0000000000400949 in _start () at ../sysdeps/x86_64/start.S:118 -- You are receiving this mail because: You are on the CC list for the bug.

1 0