https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c1 Vladimir Moravec changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mse00000@gmail.com --- Comment #1 from Vladimir Moravec 2013-12-05 12:19:18 UTC --- Hi, would you please provide the yast logs? See here: http://en.opensuse.org/openSUSE:Bugreport_YaST -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c Martin Schreiber changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mse00000@gmail.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c3 --- Comment #3 from Vladimir Moravec 2013-12-17 16:04:46 UTC --- *** Bug 853341 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=853341 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c5 --- Comment #5 from Martin Schreiber 2013-12-18 08:33:51 UTC --- Created an attachment (id=572306) --> (http://bugzilla.novell.com/attachment.cgi?id=572306) /proc/cmdline -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c6 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@suse.com AssignedTo|snwint@suse.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #6 from Steffen Winterfeldt 2013-12-18 09:50:58 CET --- Thanks! As Xorg works, I'd suspect this is KMS having mode setting/monitor detection trouble. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c8 --- Comment #8 from Martin Schreiber 2014-02-18 07:18:02 UTC --- After adding " video=VGA-1:1024x768 drm_kms_helper.edid_firmware=edid/1024x768.bin " to kernel boot parameters it works as expected. " video=VGA-1:1024x768 " is not sufficient. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c10 --- Comment #10 from Martin Schreiber 2014-03-13 15:39:28 UTC --- I don't think it is so simple. Xorg chooses the correct screen resolution with this monitor. The problem is that boot parameter video=1024x768 does not switch to 1024x768 but to some higher resolution. It is especially a problem while booting with the install DVD and selecting 1024x768 at the boot menu. This doesn't work too, so the boot process is not visible on screen because of 'CANNOT DISPLAY THIS VIDEO MODE'. IIRC the install-GUI later switches to correct 1024x768. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c12 --- Comment #12 from Martin Schreiber 2014-03-13 16:46:15 UTC --- video=1024x768 nomodeset -> 'CANNOT DISPLAY THIS VIDEO MODE' video=VGA-1:1024x768 nomodeset -> 'CANNOT DISPLAY THIS VIDEO MODE' -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c14 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel-maintainers@forge.pr |yast2-maintainers@suse.de |ovo.novell.com | --- Comment #14 from Takashi Iwai 2014-03-17 13:41:27 UTC --- OK, so the screen resolution selection in the bootloader setup is rather confusing, thus it should be dropped or rewritten. As this is no kernel bug, I reassign it back to YaST guys. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c15 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |tiwai@suse.com --- Comment #15 from Steffen Winterfeldt 2014-03-17 16:04:43 CET --- What do you mean, confusing? video=1024x768 should set the resolution, or not? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c17 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |tiwai@suse.com --- Comment #17 from Steffen Winterfeldt 2014-03-18 08:13:04 CET --- Well, 'video' was an option introduced _by_ KMS. This is all about setting the video mode for KMS; we're not talking about vesa here. So, how exactly should the mode be set, then? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c19 --- Comment #19 from Martin Schreiber 2014-03-18 08:15:08 UTC --- Please remember that "video=VGA-1:1024x768" does not work in the test case, "video=VGA-1:1024x768 drm_kms_helper.edid_firmware=edid/1024x768.bin" is necessary. I attached another monitor which can display the KMS selected resolution. Same result, "video=VGA-1:1024x768" does not switch the console resolution. Has anybody managed to switch console resolution by boot parameter? How can we switch console resolution if the "video=" option will be removed? "drm_kms_helper.edid_firmware=xxx" is not very convenient, especially if it is not possible to google the correct syntax because the monitor shows 'CANNOT DISPLAY THIS VIDEO MODE'. ;-) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c21 --- Comment #21 from Takashi Iwai 2014-03-18 08:28:53 UTC --- (In reply to comment #19)

Please remember that "video=VGA-1:1024x768" does not work in the test case, "video=VGA-1:1024x768 drm_kms_helper.edid_firmware=edid/1024x768.bin" is necessary. I attached another monitor which can display the KMS selected resolution. Same result, "video=VGA-1:1024x768" does not switch the console resolution.

It's because your monitor gives the bogus EDID :) It's rather a hardware problem specific to your monitor, and the EDID override is merely a workaround. So, it's not required normally. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c23 --- Comment #23 from Martin Schreiber 2014-03-18 08:37:32 UTC --- Why do you think it is not required that KMS accepts that I want to work with a specific console resolution? Are you sure that KMS always knows better than the user what the user needs? Sometimes a specific console resolution is necessary. I am not sure with the "bogus EDID". Xorg selects a useful resolution for the "bogus" monitor and console resolution switching does not work with another not bogus monitor. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c25 --- Comment #25 from Steffen Winterfeldt 2014-03-18 10:21:07 CET --- We will never know unless we look at the actual edid from the monitor. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c27 --- Comment #27 from Martin Schreiber 2014-03-18 11:15:46 UTC --- KMS does not select 1024x768. If I unplug the 1024x768 monitor after booting and connect a CRT-monitor, a higher resolution is visible. The question remains: Should "video=VGA-1:1024x768" switch console resolution to 1024x768? Currently it will not, independent if the "bogus" LCD or the CTR-monitor is connected while booting. If it should switch to 1024x768, does it work for you? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c29 --- Comment #29 from Martin Schreiber 2014-03-18 11:26:07 UTC ---

The video option doesn't restrict the modes. It just sets the default mode to be set initially. So the answer of "Should "video=VGA-1:1024x768" switch console resolution to 1024x768?" is: "Yes, providing "video=VGA-1:1024x768" as kernel parameter should switch console resolution to 1024x768, it does work for me."?

-- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c31 --- Comment #31 from Martin Schreiber 2014-03-18 11:56:33 UTC --- How do you set the console resolution (the console which will be showed by pressing Ctrl+Alt+F1 for example) to 1024x768? What does "It merely picks up the very first mode to be used for VGA-1 output (if used as framebuffer)" mean? Does it mean "The mode which will be picked up for VGA-1 output (if used as framebuffer) is independent of the "video=VGA-1:1024x768" kernel parameter."? What is the purpose of the "video=" parameter then? I am very confused, sorry. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c33 --- Comment #33 from Martin Schreiber 2014-03-18 16:07:54 UTC ---

You should check what outputs are really available on your system at the boot *without* any video and EDID override options. Check /sys/class/drm/card0-*/modes.

Boot with LCD-monitor connected: /sys/class/drm/card0/card0-VGA-1/modes: " 1024x768i 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 " /sys/class/drm/card0/card0-DVI-D-1/modes: " " /sys/class/drm/card0/card0-SVIDEO-1/modes: " " Boot with CRT-monitor connected: /sys/class/drm/card0/card0-VGA-1/modes: " 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 640x480 640x480 640x480 720x400 " /sys/class/drm/card0/card0-DVI-D-1/modes: " " /sys/class/drm/card0/card0-SVIDEO-1/modes: " " -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c35 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mse00000@gmail.com --- Comment #35 from Takashi Iwai 2014-03-18 16:24:42 UTC --- Unless specified with "i" suffix, no interlace mode should be enabled, AFAIK. OK, let's start from the beginning. Suppose the outputs above are the result without any extra boot option. Now, plug the LCD monitor and boot with video=1024x768 option only. This results in "CANNOT DISPLAY THIS VIDEO MODE", right? If so, boot with drm.debug=0x0e option together with video=1024x768 option, and attach the whole kernel log. As you can see, there are multiple definitions for the same resolution, and some of them might be broken. Either EDID is broken or the VESA compatible mode isn't supported by the monitor (unlikely). But it's hard to tell without any real logs... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c37 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mse00000@gmail.com --- Comment #37 from Takashi Iwai 2014-03-18 16:39:24 UTC --- Confusing... I didn't ask about CRT monitor. Does LCD monitor work as is? If so, forget about LCD monitor. Instead, connect only CRT monitor from the beginning and boot up only with "video=1024x768 drm.debug=0x0e 3" options. This will boot in runlevel 3. Does it result in "CANNOT DISPLAY THIS VIDEO MODE", right? If so, login from another machine (or via typing blindly) to get the kernel boot message at this moment (the output of "dmesg" command), and attach the output to bugzilla (don't paste). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c39 --- Comment #39 from Martin Schreiber 2014-03-18 17:05:15 UTC --- Comment #36 is answer for #34. Answer for #35:

Now, plug the LCD monitor and boot with video=1024x768 option only. This results in "CANNOT DISPLAY THIS VIDEO MODE", right?

Correct.

If so, boot with drm.debug=0x0e option together with video=1024x768 option, and attach the whole kernel log.

See uploaded messages.gz. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c41 --- Comment #41 from Martin Schreiber 2014-03-18 17:15:31 UTC ---

If so, login from another machine (or via typing blindly) to get the kernel boot message at this moment (the output of "dmesg" command), and attach the output to bugzilla (don't paste).

See uploaded dmesg.gz. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c43 --- Comment #43 from Martin Schreiber 2014-03-18 17:21:28 UTC ---

The driver seems trying to connect with 1024x768i.

And why shows the CRT-Monitor an image with resolution > 1024x768 in this state and no 1024x768i? And why does booting with the CRT-monitor and "video=VGA-1:1024x768" not show a 1024x768 image but something higher (possibly 1280x1024)? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c45 --- Comment #45 from Takashi Iwai 2014-03-18 17:26:28 UTC --- That being said, attach the dmesg output before and after re-connecting from LCD to CRT. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c47 --- Comment #47 from Martin Schreiber 2014-03-18 17:42:24 UTC --- dmesg_lcd1: booted with LCD, LCD connected. dmesg_crt: LCD disconnected, CRT connected. dmesg lcd2: CRT disconnected, LCD connected. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c49 --- Comment #49 from Martin Schreiber 2014-03-18 19:06:44 UTC ---

It means that the VGA hotplug isn't detected properly

Yup, I thought the same. ;-)

thus the interlace mode is kept for CRT, which may result in strange size.

The CRT shows a clear image with more text rows than in 1024x768 mode. I would not expect this in a interlaced 1024x768 mode... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c51 Martin Schreiber changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mse00000@gmail.com | --- Comment #51 from Martin Schreiber 2014-03-19 08:19:50 UTC --- Created an attachment (id=582748) --> (http://bugzilla.novell.com/attachment.cgi?id=582748) boot with CRT - attach CRT - boot with "video=1024x768 drm.debug=0x0e 3" - CRT shows 48 text rows -> probably 1024x768 - dmesg >crt1.txt - disconnect CRT - connect LCD - LCD shows 'CAN NOT DISPLAY THIS VIDEO MODE' - blindly dmesg >lcd.txt - disconnect LCD - connect CRT - CRT shows 48 text rows -> probably 1024x768 - dmesg >crt2.txt I'll repeat the procedure booting with LCD. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c53 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mse00000@gmail.com --- Comment #53 from Takashi Iwai 2014-03-19 08:47:42 UTC --- So, CRT works as expected without extra setup? That's a good start. There are two things behind your problem: 1. LCD monitor doesn't work as it advertises with the interlace mode 2. Replugging the monitor doesn't trigger the mode reset 1 can be worked around by the edid override. It's rather the hardware issue. 2 is because the driver doesn't detect the VGA hotplug always, and it doesn't react intentionally. This is again no bug of the driver. Usually user-space daemon like gnome-settings-daemon listens to the event and reconfigures the display. Or, manually, running xrandr on X would trigger the mode probing. If you can still see the issue with edid override and the manual mode reconfiguring, get the log again with drm.debug=0x0e from the beginning of the procedure. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c55 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mse00000@gmail.com --- Comment #55 from Takashi Iwai 2014-03-19 09:34:44 UTC --- Yes, the kernel parser behavior could be improved. But, the current behavior is no bug, per se. And, yes, interlace mode was tested in the past. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c57 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |mse00000@gmail.com --- Comment #57 from Takashi Iwai 2014-03-19 10:23:14 UTC --- (In reply to comment #53)

If you can still see the issue with edid override and the manual mode reconfiguring, get the log again with drm.debug=0x0e from the beginning of the procedure.

-- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c59 Martin Schreiber changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mse00000@gmail.com | --- Comment #59 from Martin Schreiber 2014-03-19 10:41:05 UTC --- With "video=VGA-1:1024x768 drm_kms_helper.edid_firmware=edid/1024x768.bin" the LCD-monitor shows a correct 1024x768 console. With "video=1024x768 drm_kms_helper.edid_firmware=edid/1024x768.bin" the LCD-monitor shows a correct 1024x768 console too. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c61 Martin Schreiber changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|mse00000@gmail.com | --- Comment #61 from Martin Schreiber 2014-03-19 11:15:39 UTC ---

OK, regarding about video option (about the original bug issue), the problem is only about switching between CRT and LCD?

For me switching between CRT and LCD is no problem because I usually do not replace the monitor in a running system. The problem is that there is no simple possibility to force KMS to use the not interlaced mode, especially while booting with the OpenSUSE 13.1 install DVD. Anyway, googling the problem most likely will show the "drm_kms_helper.edid_firmware=edid/1024x768.bin" trick to other users now. ;-)

The EDID thing is very like WONTFIX for openSUSE 13.1. This is the designed behavior although it's suboptimal. We can improve the behavior but it's for the future upstream kernel.

OK. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c63 --- Comment #63 from Takashi Iwai 2014-03-19 13:50:37 UTC --- Created an attachment (id=582808) --> (http://bugzilla.novell.com/attachment.cgi?id=582808) Patch to improve the cmdline mode parser -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c65 --- Comment #65 from Takashi Iwai 2014-04-07 10:06:40 UTC --- FWIW, I also backported the patch to opensUSE 13.1 and SLE12 branches. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=853350 https://bugzilla.novell.com/show_bug.cgi?id=853350#c66 --- Comment #66 from Swamp Workflow Management 2014-05-19 12:14:01 UTC --- openSUSE-SU-2014:0678-1: An update that solves 17 vulnerabilities and has 23 fixes is now available. Category: security (important) Bug References: 639379,812592,81660,821619,833968,842553,849334,851244,851426,852656,852967,853350,856760,857643,858638,858872,859342,860502,860835,861750,862746,863235,863335,864025,864867,865075,866075,866102,867718,868653,869414,871148,871160,871252,871325,875440,875690,875798,876531,876699 CVE References: CVE-2013-4579,CVE-2013-6885,CVE-2013-7263,CVE-2013-7264,CVE-2013-7265,CVE-2013-7281,CVE-2014-0069,CVE-2014-0101,CVE-2014-0196,CVE-2014-1438,CVE-2014-1446,CVE-2014-1690,CVE-2014-1737,CVE-2014-1738,CVE-2014-1874,CVE-2014-2523,CVE-2014-2672 Sources used: openSUSE 13.1 (src): cloop-2.639-11.7.1, crash-7.0.2-2.7.1, hdjmod-1.28-16.7.1, ipset-6.19-2.7.1, iscsitarget-1.4.20.3-13.7.1, kernel-docs-3.11.10-11.3, kernel-source-3.11.10-11.1, kernel-syms-3.11.10-11.1, ndiswrapper-1.58-7.1, openvswitch-1.11.0-0.25.1, pcfclock-0.44-258.7.1, virtualbox-4.2.18-2.12.1, xen-4.3.2_01-15.1, xtables-addons-2.3-2.7.1 -- 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.

http://bugzilla.novell.com/show_bug.cgi?id=853350 Swamp Workflow Management changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:2807:important | -- You are receiving this mail because: You are on the CC list for the bug.