October 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 908669] Virtualbox Guest additions: Automount of shared folders does not work
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.novell.com/show_bug.cgi?id=908669 http://bugzilla.novell.com/show_bug.cgi?id=908669#c8 --- Comment #8 from Swamp Workflow Management <swamp(a)suse.de> --- openSUSE-RU-2015:1665-1: An update that has three recommended fixes can now be installed. Category: recommended (low) Bug References: 811221,908669,936254 CVE References: Sources used: openSUSE 13.2 (src): virtualbox-4.3.30-24.1 -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 811221] New: I met a wrong message in virtualbox when I create a new VM
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

https://bugzilla.novell.com/show_bug.cgi?id=811221 https://bugzilla.novell.com/show_bug.cgi?id=811221#c0 Summary: I met a wrong message in virtualbox when I create a new VM Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening(a)forge.provo.novell.com ReportedBy: ogpugr(a)gmail.com QAContact: qa-bugs(a)suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (iPad; CPU OS 6_1_3 like Mac OS X) AppleWebKit/536.26 (KHTML, like Gecko) Version/6.0 Mobile/10B329 Safari/8536.25 Actually my operating system version is openSUSE 12.3, but it isn't listed above. I installed the virtualbox at http://software.opensuse.org/package/virtualbox . I installed the virtualbox successfully. But in the create new VM page, I chose the Windows XP, then I click the add button, it told me "Could not create the VM: this parameter must be a string or Unicode object. Reproducible: Always Steps to Reproduce: 1.Create new VM 2.Choose Windows XP 3.Click add Actual Results: The machine said " Could not create the VM: this parameter must be a string or Unicode object. Expected Results: Create the Virtual machine successful. -- 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 908669] Virtualbox Guest additions: Automount of shared folders does not work
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.novell.com/show_bug.cgi?id=908669 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:4041:low | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 936254] VirtualBox guest time skew - virtualbox-guest-tools fails to enable VBoxService
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.novell.com/show_bug.cgi?id=936254 Swamp Workflow Management <swamp(a)suse.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Whiteboard|obs:running:4041:low |obs:running:4063:moderate |obs:running:4063:moderate |obs:running:4062:moderate |obs:running:4062:moderate | -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 933565] updating the kernel causes grub2 to select fedora
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=933565 http://bugzilla.suse.com/show_bug.cgi?id=933565#c11 --- Comment #11 from Josef Reidinger <jreidinger(a)suse.com> --- I check logs and default is properly set there, but it is EFI system, so it is possible, that EFI default entry changed, which is out of yast2-bootloader control. As it happen only after kernel upgrade, maybe it is related with adding/removing new respective old entry, that flag different kernel to boot it. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 865132] Postfix main.cnf had mailbox_command stripped
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=865132 http://bugzilla.suse.com/show_bug.cgi?id=865132#c4 Michal Filka <mfilka(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(varkoly(a)suse.com) --- Comment #4 from Michal Filka <mfilka(a)suse.com> --- ok. There are three reports for the same bug already. @Peter: Should I drop call to config.postfix from yast2-network completely? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 947686] LEAP 42.1 Beta - Online repositories cannot be added
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=947686 http://bugzilla.suse.com/show_bug.cgi?id=947686#c1 Ladislav Slezak <lslezak(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tonysu(a)su-networking.com Flags| |needinfo?(tonysu@su-network | |ing.com) --- Comment #1 from Ladislav Slezak <lslezak(a)suse.com> --- Please, attach the YaST log (see https://en.opensuse.org/Bugs/YaST) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 948389] User login fail on gnome
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.opensuse.org/show_bug.cgi?id=948389 http://bugzilla.opensuse.org/show_bug.cgi?id=948389#c3 Dominique Leuenberger <dimstar(a)opensuse.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |asemen(a)suse.com Flags| |needinfo?(asemen(a)suse.com) --- Comment #3 from Dominique Leuenberger <dimstar(a)opensuse.org> --- (In reply to Stefan Dirsch from comment #2) > No, since reporter claims that other WMs like icewm and twm do work. Back to > GNOME. How is GNOME supposed to cmoe up, if X bails out with no screen detected? Anyway, Andrej: can you please extract a full journal log instead of only an excerpt? * Reboot the system * Try to login to GNOME (X session, not wayland) (you use GDM as display manager, as far as I can tell) * once login failed, switch to tty1 (ctrl-alt-f1) * login as root, then journalctl -b > journal Attach the 'journal' file here. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 948389] User login fail on gnome
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.opensuse.org/show_bug.cgi?id=948389 http://bugzilla.opensuse.org/show_bug.cgi?id=948389#c2 Stefan Dirsch <sndirsch(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|X.Org |GNOME Assignee|xorg-maintainer-bugs@forge. |bnc-team-gnome(a)forge.provo. |provo.novell.com |novell.com QA Contact|xorg-maintainer-bugs@forge. |qa-bugs(a)suse.de |provo.novell.com | --- Comment #2 from Stefan Dirsch <sndirsch(a)suse.com> --- No, since reporter claims that other WMs like icewm and twm do work. Back to GNOME. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 947825] yast2 kdump asks for highmem and suggests wrong values
by bugzilla_noreply＠novell.com 01 Oct '15

01 Oct '15

http://bugzilla.suse.com/show_bug.cgi?id=947825 http://bugzilla.suse.com/show_bug.cgi?id=947825#c7 --- Comment #7 from Petr Tesařík <ptesarik(a)suse.com> --- Another data point: SLAB usage has increased considerably. My research shows that: - additional ~2.5M is used by debugfs inodes and dentry objects as a result of having more trace events. Note that this memory is allocated even if debugfs is not mounted. - additional ~1M is used as a result of growing struct task_struct - additional ~0.5M is used by various smaller allocations In my test VM, I saw additional 6M used by kmalloc caches. I managed to track it down to the qxl framebuffer driver, which may allocate delayed work if called in atomic context. In my case the length of the queue was 20k+ operations. Since bitblt operations also include the bitmap data, it adds up... Note that it's difficult to estimate such allocations. For example the qxl backlog depends on video output resolution, color depth and the amount of data sent to the console by printk() in atomic context (which in turn may depend on other drivers). It would be great if I could extract such information from the kernel at run-time. I'm afraid it's not possible. I'm going to adjust kdumptool to reflect the above observations for a "typical" case (what is "typical", anyway?). However, note that it may fail. For example, I had a bug report that kdump failed after connecting the computer to a 8K monitor; that was because the framebuffer suddenly took up 7680*4320*4 = ~127 MiB instead of just 4 MiB, which was calculated when kdump was first configured with a Full-HD monitor. It's possible to add some reserve, but I'm not sure that everyone wants to waste additional 100+M just in case the system gets connected to a large monitor, another 100+M just in case it gets connected to a large SAN, etc. -- You are receiving this mail because: You are on the CC list for the bug.

1 0