http://bugzilla.suse.com/show_bug.cgi?id=893678
--- Comment #20 from Marius Tomaschewski <mt(a)suse.com> ---
A "systemctl stop NetworkManager" is not sufficient -- there is a NM setting
causing to stop NM only, but not the dhclient processes started by NM...
See also bug#895447 => "systemctl --kill-who=all kill NetworkManager".
We're working on a documentation how to do it manually -- here the a paste
from current draft:
"[...]
Procedure to enable NetworkManager manually:
1) First, stop the running network (wicked) service to get a clean state
(configuration may differ):
systemctl is-active network.service && \
systemctl stop network.service
2) Then, stop the wicked-daemon services as well:
systemctl is-active wickedd.service && \
systemctl stop wickedd.service
3) Disable wicked, enable NetworkManager.service (creates alias link):
systemctl disable wicked.service
systemctl --force enable NetworkManager.service
4) Start the NetworkManager service via the alias link:
systemctl start network.service
or directly:
systemctl start NetworkManager.service
Procedure to disable NetworkManager and switch to wicked.service manually:
1) Stop the running NetworkManager.service:
systemctl is-active NetworkManager.service && \
systemctl --kill-who=all kill NetworkManager.service
Note: The normal NetworkManager.service stop action stops NetworkManager, but
leaves processes such as dhcp clients running to not break network connectivity
when it is restarted on update or there is a remote fs mounted while shutdown.
The --kill-who=all kill action ensures to stop them too as they conflict with
the wicked service using a different implementation.
2) Disable NetworkManager, enable wicked.service (creates alias link):
systemctl disable NetworkManager.service
systemctl --force enable wicked.service
3) Start the new network.service, which now is wicked.service:
systemctl start wicked.service
or via the alias link:
systemctl start network.service
The wickedd daemon service are started automatically via dependencies.[...]"
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=898723
Michael Schröder <mls(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #3 from Michael Schröder <mls(a)suse.com> ---
The code in question already contains the following:
#FIXME - in theory some sort of try/except here
# TypeError appears to be raised, sometimes :(
rp.getPrimary(complete_path, csum)
Anyway, the sqlite database generation code is kind of obsolete and the
generation is disabled by default in the createrepo version used in SLE12 and
Factory.
I thus don't think it is worth fixing (the second createrepo probably truncated
the primary file, so that the first createrepo crashed when it re-read the data
to generate the sqlite version).
Closing with WONTFIX. Thanks anyway for reporting!
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=899365
Bug ID: 899365
Summary: Hotplug does not work after Suspend to RAM
Classification: openSUSE
Product: openSUSE 13.1
Version: Final
Hardware: x86-64
OS: openSUSE 13.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: s91066(a)yahoo.gr
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
After a resume from Suspend to RAM I cannot hotplug any USB device. Devices
that are already plugged are available anymore and no new devices are
discovered.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=874621
--- Comment #24 from Michal Marek <mmarek(a)suse.com> ---
As a wrote in comment 4, the proper fix is to call depmod during package
installation. The format of modules.dep changed, but that's not a bug in either
of the versions.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=898541
--- Comment #2 from F. S. <frederic.santos(a)u-bordeaux1.fr> ---
Good news if LLVM 3.5 has hit factory, thank you.
It would be great if LLVM 3.5 could be included in 13.2 final. On the website
winehq.org, we can see than numerous bugs (including this one!) happening on
AMD platforms can be solved using the latest version of LLVM.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=894370
Swamp Workflow Management <swamp(a)suse.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Whiteboard|maint:released:sle11-sp3:58 |maint:released:sle11-sp3:58
|825 |825
|maint:released:sle11-sp2:58 |maint:released:sle11-sp2:58
|829 |829
|maint:released:sle10-sp3:58 |maint:released:sle10-sp3:58
|832 |832
|maint:released:sle10-sp3:58 |maint:released:sle10-sp3:58
|824 |824
|maint:released:sle10-sp4:58 |maint:released:sle10-sp4:58
|833 |833
|maint:released:sle11-sp1:58 |maint:released:sle11-sp1:58
|823 |823
|maint:released:sle11-sp1:58 |maint:released:sle11-sp1:58
|828 |828
|maint:running:59193:importa |maint:running:59193:importa
|nt |nt
| |maint:running:59192:importa
| |nt
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=890115
--- Comment #17 from Dr. Werner Fink <werner(a)suse.com> ---
Btw: What is wrong with UTF-8? Does this not work with Norwegian keyboard?
Please configure the stuff with YaST2, that is Norwegian keyboard and Norwegian
language together a second language US English and avoid GNOME. Then run
mkinitrd to see which font is then enabled in the initrd.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=897929
Karl Eichwalder <ke(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |IN_PROGRESS
--- Comment #7 from Karl Eichwalder <ke(a)suse.com> ---
Thanks, I merged it.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=782909https://bugzilla.novell.com/show_bug.cgi?id=782909#c0
Summary: dbus-daemon eats 100% CPU
Classification: openSUSE
Product: openSUSE 12.1
Version: Final
Platform: x86-64
OS/Version: openSUSE 12.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening(a)forge.provo.novell.com
ReportedBy: jdelvare(a)suse.com
QAContact: qa-bugs(a)suse.de
CC: dmueller(a)suse.com, vuntz(a)suse.com
Found By: Community User
Blocker: ---
>From times to times I notice that dbus-daemon eats 100% CPU. I have not yet
been able to figure out the action causing this to happen, if any.
I installed the debuginfo package for dbus-1, and gdb prints the following
backtrace when the bug happens:
#0 0x0000000000404778 in __errno_location@plt ()
#1 0x000000000043c7e1 in _dbus_babysitter_unref (sitter=0x66ee80) at
dbus-spawn.c:317
#2 _dbus_babysitter_unref (sitter=0x66ee80) at dbus-spawn.c:275
#3 0x00000000004067fb in bus_pending_activation_unref
(pending_activation=0x667090) at activation.c:187
#4 bus_pending_activation_unref (pending_activation=0x667090) at
activation.c:156
#5 0x000000000042f3be in free_entry_data (table=<optimized out>,
entry=<optimized out>) at dbus-hash.c:461
#6 _dbus_hash_table_unref (table=0x6734f0) at dbus-hash.c:411
#7 0x0000000000406b0d in bus_activation_unref (activation=0x665840) at
activation.c:962
#8 0x00000000004085df in bus_context_unref (context=0x6630c0) at bus.c:1044
#9 0x00000000004052ab in main (argc=<optimized out>, argv=0x7fff63a73f58) at
main.c:611
The dbus-daemon process is owned by gdm. I tried restarting it with:
# systemctl restart dbus.service
but other than killing my Gnome session, it did not do anything.
Any suggestion on how to debug this further?
Note that I have a non-standard X stack on this machine, so it is possible that
the problem happens only on this machine and wouldn't possibly happen on a
standard openSUSE 12.1 installation. Still I'd be happy to get it fixed.
--
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=893665
--- Comment #9 from Pawel Wieczorkiewicz <pwieczorkiewicz(a)suse.com> ---
(In reply to Frans Leerink from comment #8)
> Hello Pawel,
Hi Frank,
>
> I am just back from vacation, so sorry for late reaction.
>
No worries :-).
> Just a few questions to clarify what you need and how to get the logs.
>
> 1 Should I do these steps with "Wicked" reconfigured, since I currently run
> networkmanager successfully?
>
First of all disable and kill NetworkManager properly. Description how to do
that can be found here:
https://bugzilla.suse.com/show_bug.cgi?id=893678#c17
> 2 How should I get the logs? Should I run on the command line just the
> various
> commands in the given sequence. Should I run the commands as user or as
> root?
>
Here's more detailed description:
‒ set DEBUG=all in /etc/sysconfig/network/config
edit /etc/sysconfig/network/config file and tweak the requested DEBUG variable.
- enable wpa_supplicant in the debugging mode
Easiest is to edit the wpa_supplicant.service file and restart it by:
* Apply the following diff (note it is just an additional -d option on the
wpa_supplicant parm list)
diff --git a/usr/lib/systemd/system/wpa_supplicant.service
b/usr/lib/systemd/system/wpa_supplicant.service.old
index c764a53..7f475cf 100644
--- a/usr/lib/systemd/system/wpa_supplicant.service
+++ b/usr/lib/systemd/system/wpa_supplicant.service.old
@@ -5,7 +5,7 @@ Before=network.target
[Service]
Type=dbus
BusName=fi.w1.wpa_supplicant1
-ExecStart=/usr/sbin/wpa_supplicant -d -c
/etc/wpa_supplicant/wpa_supplicant.conf -u -f /var/log/wpa_supplicant.log
+ExecStart=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf
-u -f /var/log/wpa_supplicant.log
[Install]
WantedBy=multi-user.target
* execute as root on terminal: systemctl daemon-reload
* execute as root on terminal: systemctl restart wpa_supplicant
All the following commands should be manually executed as root on the terminal:
‒ systemctl restart wickedd
‒ wicked --debug all ifup all # systemctl restart wicked
‒ wicked ifstatus all > status.log
‒ wicked show-config > configs.log
‒ journalctl -b -o short-iso > wicked.log
‒ ip addr show > ip_addr.log
‒ ip route show > routes.log
‒ ip -6 route show >> routes.log
Provide also log file from wpa_supplicant: /var/log/wpa_supplicant.log
> Regards, Frans
--
You are receiving this mail because:
You are on the CC list for the bug.