June 2015 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 909359] snapper delete command does not completely delete snapshot folders
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.novell.com/show_bug.cgi?id=909359 --- Comment #11 from Roman Bysh <rb03884(a)gmail.com> --- I guess this has already been added to Tumbleweed? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 907584] New: zeromq: Can't update due to file conflict
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.opensuse.org/show_bug.cgi?id=907584 Bug ID: 907584 Summary: zeromq: Can't update due to file conflict Classification: openSUSE Product: openSUSE Factory Version: 201411* Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem Assignee: tchvatal(a)suse.com Reporter: coolo(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- It's impossible to update because zeromq does not comply with shared library policy. the library packages are supposed to be coinstallable (and do not conflict): File /usr/bin/curve_keygen from install of libzmq4-4.0.5-2.1.x86_64(openSUSE-Oss) conflicts with file from package libzmq3-4.0.4-4.2.x86_64(@System) -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 924804] Snapper crashes when trying to delete single snapshot
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.suse.com/show_bug.cgi?id=924804 --- Comment #2 from Harvey Nimmo <harvey(a)nimmo.de> --- When trying to delete the snapshot in question, Snapper terminated immediately without performing the delete operation. (This is what I termed a 'crash'). On restarting snapper the snapshot in question (1154) was still listed. The effect of this situation was sufficiently inconvenient, that my disk usage quickly grew continually close the the maximum available on the partition (with corresponding warnings). This led me finally to reinstall Opensuse 13.2 from scratch. The log files from ca. 2015-03-28 are no longer available, I believe. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 930091] Crash during DVD installation (KVM, encrypted RAID disk with Fedora 21 installation)
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.suse.com/show_bug.cgi?id=930091 Björn Voigt <bjoernv(a)arcor.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(bjoernv(a)arcor.de) | --- Comment #3 from Björn Voigt <bjoernv(a)arcor.de> --- My KVM setup was only for testing/planning purposes. I have done full disk encryption tests both with openSUSE and with Fedora. Personally I do not like LVM so much. But YaST insists on LVM for full disk encryption. Fedora (tested with Fedora 21) can be installed on LVM or on Non-LVM partitions (e.g. normal partitions or raid devices) for full disk encryption. I reported the bug, because Fedora users with full disk encryption may wish to migrate to openSUSE. Of course they need to repartition and/or format their hard disks. But YaST should not crash before partitioning. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 932950] w truncates usernames and lies about available commands
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

1 0

[Bug 932950] w truncates usernames and lies about available commands
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.suse.com/show_bug.cgi?id=932950 --- Comment #3 from Dank Maymays <eimacdude(a)aol.com> --- inarguments -> invalid arguments (autocorrect) -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 932950] w truncates usernames and lies about available commands
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.suse.com/show_bug.cgi?id=932950 Dank Maymays <eimacdude(a)aol.com> changed: What |Removed |Added ---------------------------------------------------------------------------- OS|openSUSE 12.3 |openSUSE 13.2 --- Comment #2 from Dank Maymays <eimacdude(a)aol.com> --- PROCPS_USERLEN is great, but that only invalidates the first half of this bug report. It still remains the case that the argument definitions w itself prints when called with inarguments are erroneous: it claims there is an -n/--no-truncat option, which is false. Why did you then mark this as resolved? Did you not read in full the description I posted? It's even in the title. Re: 12.3 — that was a typo; I meant 13.2 and I've corrected this. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 931543] New: Thinkpad R60/T60 Hotkeys hotkey mask mismatch
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.opensuse.org/show_bug.cgi?id=931543 Bug ID: 931543 Summary: Thinkpad R60/T60 Hotkeys hotkey mask mismatch 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: ernestopheles(a)googlemail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- * Reproducible: openSUSE 13.1 x86_64, KDE 4, clean standard set-up, always * Symptom: On R60 and T60 series Thinkpads, volume and brightness changes through hotkeys are not acknowledged by the operating system * Fix: One-line command * Last known to work without a flaw: openSUSE 12.3 On R60 and T60 Thinkpads, volume and brightness hotkeys are not correctly interpreted. The brightness hotkeys work, but the system does not acknowledge the change with its usual pop-up/overlay notifications (KDE4). The volume keys work, too, however there are also no pop-up/overlay notifications and the volume is changed using the acpi subsystem (which can be observed by monitoring /proc/acpi/ibm/volume) while the volume of pulseaudio remains untouched. The following command reveals a mismatch of hotkey masks: # cat /sys/devices/platform/thinkpad_acpi/hotkey_all_mask /sys/devices/platform/thinkpad_acpi/hotkey_mask 0x00ffffff 0x008dffff It can be fixed by executing the following command with root privileges: # cat /sys/devices/platform/thinkpad_acpi/hotkey_all_mask > /sys/devices/platform/thinkpad_acpi/hotkey_mask This single change causes the hotkeys/buttons to work again as expected. A more detailed description of the identical problem and fix in Debian 7 can be found here: http://ebb.org/bkuhn/blog/2014/06/08/volume-hotkeys-thinkpad-t60.html -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 930091] Crash during DVD installation (KVM, encrypted RAID disk with Fedora 21 installation)
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.suse.com/show_bug.cgi?id=930091 Josef Reidinger <jreidinger(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bjoernv(a)arcor.de Flags| |needinfo?(bjoernv(a)arcor.de) --- Comment #2 from Josef Reidinger <jreidinger(a)suse.com> --- Hi Björn, I check logs and problem is that code do not expect unpartitioned md raid. Just to ensure to fix it correctly, what is your intention with this md raid? -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 927776] System failed to start
by bugzilla_noreply＠novell.com 01 Jun '15

01 Jun '15

http://bugzilla.suse.com/show_bug.cgi?id=927776 --- Comment #25 from Cristian Rodríguez <crrodriguez(a)opensuse.org> --- (In reply to Cristian Rodríguez from comment #24) > (In reply to Cristian Rodríguez from comment #23) > > (In reply to Richard Weinberger from comment #22) > > > (In reply to Cristian Rodríguez from comment #21) > > > > Ok Richard.. so you are running a self-built kernel right ? ensure > > > > http://cgit.freedesktop.org/systemd/systemd/tree/README section REQUIREMENTS > > > > is met by your build. In particular it looks like your kernel does not have > > > > CONFIG_FHANDLE set. > > > > > > Yeah, the kernel is self-built (it's my day job)... > > > But CONFIG_FHANDLE *is* set. > > > In fact this config option is default because of me: > > > https://git.kernel.org/linus/15bae280e412e79d74912c7ae6b6a002444edb1f > > > > ok.. let's try something different then: > > > > follow http://freedesktop.org/wiki/Software/systemd/Debugging/ > > section Early Debug Shell. > > > > when pid 1 is looping too fast... > > > > follow this instructions > > > > http://git.infradead.org/~rw/os132_boot_fail.txt > > > > also your boot log shows that the virtualbox kernel drivers are being > > loaded..which are known to be ..let say.. "buggy".. try disabling the > > vboxdrv service before continuing debugging.. > > oops, wrong instruction link.. here it is > http://lists.freedesktop.org/archives/systemd-devel/2015-February/028541.ht… It could be a coincidence that Apr 16 13:51:01 sandpuppy kernel: vboxdrv: Found 4 processor cores. Apr 16 13:51:01 sandpuppy kernel: vboxdrv: fAsync=0 offMin=0x2ac offMax=0x7a7e Apr 16 13:51:01 sandpuppy kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. Apr 16 13:51:01 sandpuppy kernel: vboxdrv: Successfully loaded version 4.3.20 (interface 0x001a0008). Apr 16 13:51:01 sandpuppy kernel: vboxpci: IOMMU not found (not registered) --> Things go bersek right after the virtual box drivers are loaded..>>>> Apr 16 13:51:01 sandpuppy systemd[1]: Failed to get initial list of names: Connection timed out Apr 16 13:51:01 sandpuppy systemd[1]: Looping too fast. Throttling execution a little. Apr 16 13:51:01 sandpuppy systemd[1]: Looping too fast. Throttling execution a little. That could be misleading so let's rule that out first... -- You are receiving this mail because: You are on the CC list for the bug.

1 0