http://bugzilla.suse.com/show_bug.cgi?id=895447
Frederic Crozat <fcrozat(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fcrozat(a)suse.com
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=890115
Frederic Crozat <fcrozat(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |systemd-maintainers(a)suse.de
--- Comment #13 from Frederic Crozat <fcrozat(a)suse.com> ---
(In reply to Bjørn Lie from comment #11)
> I was thinking about
>
> systemd-vconsole-setup[135]: cannot open file no-latin1
>
> even when it's there.
This is related to dracut (reported as bnc#897972, sorry a SLES12 bug not
publicly visible) and a fix is being worked on.
(In reply to Terje J. Hanssen from comment #12)
> (In reply to Bjørn Lie from comment #9)
>
> > @ Terje: thats odd that it did not work as it does here.
> >
> > When you are in tty - could you try doing a
> >
> > systemctl restart systemd-vconsole-setup.service
> >
> > and see if you get norwegian keyboardlayout then.
> >
>
> Yes, that command works for root, fail with no access for normal user.
This is normal, loadkeys (used by systemd-vconsole-setup.service) is only
possible for root.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=898984
Ladislav Slezak <lslezak(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Unable to change settings |Unable to change settings
|for softwarerepositorys |for software repositories -
| |Qt UI ignores check button
| |state change
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=898984
Ladislav Slezak <lslezak(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P2 - High
Assignee|lslezak(a)suse.com |mvidner(a)suse.com
--- Comment #7 from Ladislav Slezak <lslezak(a)suse.com> ---
I can reproduce the problem in 13.1 with Yast from YaST:Head OBS project, the
y2log contains this:
2014-10-01 09:10:08 <2> muffin(23211) [qt-ui] YQUI.cc(qMessageHandler):716
<libqt-warning> QObject::connect: signal not found in YQCheckBox
2014-10-01 09:10:08 <2> muffin(23211) [qt-ui] YQUI.cc(qMessageHandler):716
<libqt-warning> QObject::connect: signal not found in YQCheckBox
2014-10-01 09:10:08 <2> muffin(23211) [qt-ui] YQUI.cc(qMessageHandler):716
<libqt-warning> QObject::connect: signal not found in YQCheckBox
# rpm -qa | grep libyui
libyui-qt-pkg6-2.44.7-3.4.x86_64
libyui-ncurses-pkg6-2.46.1-6.4.x86_64
libyui-qt6-2.46.0-2.1.x86_64
libyui-gtk6-2.44.5-7.1.x86_64
libyui-qt-graph6-2.44.2-12.1.x86_64
libyui-ncurses6-2.46.6-7.1.x86_64
libyui-devel-3.1.4-2.1.x86_64
libyui-gtk-pkg6-2.43.2-6.4.x86_64
libyui6-3.1.4-2.1.x86_64
IIRC there was the same bug in the past...
Martin, please check.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=838688
Thorsten Kukuk <kukuk(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|SHIP_STOPPER? |
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=899257
Thorsten Kukuk <kukuk(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Group|SUSE Enterprise Partner |
Component|Installer |Installation
Version|RC2 |Final
Product|SUSE Linux Enterprise |openSUSE 13.1
|Server 12 (SLES 12) |
QA Contact|qa-bugs(a)suse.de |jsrain(a)suse.com
--- Comment #2 from Thorsten Kukuk <kukuk(a)suse.com> ---
The behavior is correct for SLE12, moving to openSUSE 13.1
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=899263
Olav Reinert <seroton10(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(seroton10(a)gmail.c |
|om) |
--- Comment #2 from Olav Reinert <seroton10(a)gmail.com> ---
Created attachment 608624
--> http://bugzilla.suse.com/attachment.cgi?id=608624&action=edit
YaST2 logs
The error I saw can be found in y2log-1.gz within the attached archive.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=895447
Michal Filka <mfilka(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bnc-team-gnome(a)forge.provo.
| |novell.com
Flags| |needinfo?(bnc-team-gnome@fo
| |rge.provo.novell.com)
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657591https://bugzilla.novell.com/show_bug.cgi?id=657591#c0
Summary: Build Service is an internal product
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Platform: PC
OS/Version: openSUSE 11.3
Status: NEW
Severity: Enhancement
Priority: P5 - None
Component: Bugzilla
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: giecrilj(a)stegny.2a.pl
QAContact: novbugzilla-bugs(a)forge.provo.novell.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; pl-PL; rv:1.9.2.12)
Gecko/20101026 SUSE/3.6.12-0.7.1 Ant.com Toolbar 2.0.1 Firefox/3.6.12
The wording used in the description for openSUSE BuildService makes the product
Build Service hard to find in the product selection screen because it is
classified as Internal.
Reproducible: Always
Steps to Reproduce:
1. Create a new bug in openSUSE.org
2. Select the "BuildService".
Actual Results:
2. Component description:
build.opensuse.org instance itself -- Build Service is an own product in
bugzilla otherwise
Expected Results:
2. Component description:
build.opensuse.org instance itself -- Build Service is an internal product in
bugzilla otherwise
--
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.suse.com/show_bug.cgi?id=895447
Marius Tomaschewski <mt(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |behlert(a)suse.com
--- Comment #10 from Marius Tomaschewski <mt(a)suse.com> ---
The only possibility to workaround it in yast2-network I currently see,
would be to implement the "switch away from NM" like this -- and also
to document in the release notes (for users doing it manually):
# bnc#895447: NetworkManager does not cleanup on stop
# Ensure it is gone along with conflicting dhclients,
# ... before we switch over to another network.service.
systemctl --kill-who=all kill NetworkManager.service
systemctl stop NetworkManager.service
systemctl disable NetworkManager.service
Is this the way preferred by the NetworkManager?
--
You are receiving this mail because:
You are on the CC list for the bug.