http://bugzilla.opensuse.org/show_bug.cgi?id=936206
Bug ID: 936206
Summary: accounts-daemon segfault when inccorrect passwd
provided
Classification: openSUSE
Product: openSUSE Factory
Version: 201505*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: bnc-team-gnome(a)forge.provo.novell.com
Reporter: mpluskal(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 639342
--> http://bugzilla.opensuse.org/attachment.cgi?id=639342&action=edit
backtrace
I have noticed segfault when logging in on current factory (over ssh, when
entering wrong passwd):
#0 magazine_chain_pop_head (magazine_chunks=0x1f547c0) at gslice.c:539
#1 thread_memory_magazine1_alloc (tmem=<optimized out>, ix=1) at gslice.c:842
#2 g_slice_alloc (mem_size=mem_size@entry=24) at gslice.c:998
#3 0x00007fded1db6b76 in g_list_prepend (list=0x7fdec4001500,
data=data@entry=0x1fd6a00) at glist.c:311
#4 0x000000000040f3f8 in wtmp_helper_entry_generator (users=0x1f726a0,
state=0x7fff4e948258) at wtmp-helper.c:165
#5 0x0000000000408f6b in load_entries (daemon=daemon@entry=0x1f688c0,
users=users@entry=0x1f726a0, entry_generator=0x40f300
<wtmp_helper_entry_generator>) at daemon.c:247
#6 0x000000000040913f in reload_users (daemon=daemon@entry=0x1f688c0) at
daemon.c:317
#7 0x00000000004092d9 in reload_users_timeout (daemon=0x1f688c0,
daemon@entry=<error reading variable: value has been optimized out>) at
daemon.c:358
#8 0x00007fded1dbb583 in g_timeout_dispatch (source=0x1fb4600,
callback=<optimized out>, user_data=<optimized out>) at gmain.c:4545
#9 0x00007fded1dbab55 in g_main_dispatch (context=0x1f5c8d0) at gmain.c:3122
#10 g_main_context_dispatch (context=context@entry=0x1f5c8d0) at gmain.c:3737
#11 0x00007fded1dbaec8 in g_main_context_iterate (context=0x1f5c8d0,
block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at
gmain.c:3808
#12 0x00007fded1dbb18a in g_main_loop_run (loop=0x1f64640) at gmain.c:4002
#13 0x0000000000408020 in main (argc=1, argv=0x7fff4e948558) at main.c:219
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=931523
Bug ID: 931523
Summary: gnome-shell: center_pointer (backend=0xcab0b0) at
backends/meta-backend.c:106 segfault
Classification: openSUSE
Product: openSUSE Factory
Version: 201505*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: bnc-team-gnome(a)forge.provo.novell.com
Reporter: mpluskal(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Created attachment 634746
--> http://bugzilla.opensuse.org/attachment.cgi?id=634746&action=edit
backtrace
Same conditions as boo#931513
(gdb) bt
#0 center_pointer (backend=0xcab0b0) at backends/meta-backend.c:106
#1 0x00007fd71a341a31 in meta_backend_x11_post_init (backend=0xcab0b0) at
backends/x11/meta-backend-x11.c:449
#2 0x00007fd71a3664e5 in meta_init () at core/main.c:358
#3 0x0000000000401f8e in main (argc=1, argv=0x7ffdb849f158) at main.c:429
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=975831
Bug ID: 975831
Summary: [Trackerbug] Wayland as default session for GNOME
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: All
OS: SUSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: bnc-team-gnome(a)forge.provo.novell.com
Reporter: zaitor(a)opensuse.org
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
This is a tracker bug for what we have set up to track what needs to be fix
before this is a route we can take.
Please add bugs to this one.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=980329
Bug ID: 980329
Summary: gettext tools do not support Ruby
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: YaST2
Assignee: yast2-maintainers(a)suse.de
Reporter: ke(a)suse.com
QA Contact: jsrain(a)suse.com
Blocks: 979781
Found By: ---
Blocker: ---
+++ This bug was initially created as a clone of Bug #979781 +++
The German translation of module yast2-journal contains an error:
msgid "Between %{since} and %{until}"
msgstr "Zwischen %{seit} und %{bis}"
"since" and "until" should not be translated. See this code:
...
===================================================================
We see this kind of bugs again and again.
In the past, YCC was properly supported in gettext. We need this for Ruby as
well. Please, take the time to report appropriate info to the gettext
maintainers (or better, provide a patch).
In the meantime, which tools can I use as a workaround?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=904210
Bug ID: 904210
Summary: package link not shown in web UI
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: BuildService
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: nico.kruber(a)gmail.com
QA Contact: adrian(a)suse.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:33.0) Gecko/20100101
Firefox/33.0
Build Identifier:
if repo B is based on repo A which contains package C, then linking to B:C
(without C being directly available in B) produces no UI elements to show
(un)expanded sources in the web UI, neither is the link shown as such ("links
to ...")
example:
https://build.opensuse.org/package/show/KDE:Extra/PackageKithttps://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=0https://build.opensuse.org/package/show/KDE:Extra/PackageKit?expand=1
Reproducible: Always
Steps to Reproduce:
1. create link to a package in openSUSE:13.2:Update which is only available in
openSUSE:13.2
2. browse to that link
Actual Results:
the link exists but is not shown as such
Expected Results:
same UI as if the package was linked to openSUSE:13.2 directly
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=920134
Bug ID: 920134
Summary: windows:mingw:win{32,64}/mingw{32,64}-binutils: windmc
memory bug
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: All
OS: Windows
Status: NEW
Severity: Major
Priority: P5 - None
Component: 3rd party software
Assignee: fstrba(a)suse.com
Reporter: gitne(a)gmx.de
QA Contact: opensuse-communityscreening(a)forge.provo.novell.com
CC: fridrich.strba(a)bluewin.ch, gitne(a)gmx.de,
hib(a)hiberis.nl, mkbosmans(a)gmail.com,
tlillqvist(a)suse.com
Found By: Community User
Blocker: No
Created attachment 624972
--> http://bugzilla.opensuse.org/attachment.cgi?id=624972&action=edit
Sample source message file for windmc without a trailing line feed (U+000A)
character
If the input file does not end with a line feed character (U+000A) the windmc
tool eats up all the memory and then terminates with an out of memory error. To
reproduce, try the atteched sample.mc file. Append a line feed character at the
end of the file and windmc works (mostly) as intended.
Warning: Be careful when reproducing on 64 bit systems with lots of RAM and/or
swap space. This operation may cause the system to seemingly block for an
extended amount of time. It is probably best to use the mingw32 version of
windmc or to specifically limit the available amount of memory to the process
to a reasounable amount.
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=948280
Bug ID: 948280
Summary: windows:mingw:win{32,64}/mingw{32,64}-filesystem: Add
hardening options?
Classification: openSUSE
Product: openSUSE.org
Version: unspecified
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: 3rd party software
Assignee: fstrba(a)suse.com
Reporter: gerald(a)wireshark.org
QA Contact: opensuse-communityscreening(a)forge.provo.novell.com
CC: fridrich.strba(a)bluewin.ch, hib(a)hiberis.nl,
idonmez(a)suse.com, mkbosmans(a)gmail.com,
tlillqvist(a)suse.com
Found By: ---
Blocker: ---
It doesn't appear that any of the mingw:win32 or mingw:win64 packages are built
with hardening options enabled, e.g. --dynamicbase, --nxcompat, and
--highentropyva. Would it be possible to do so?
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=974835
Bug ID: 974835
Summary: bluetooth conflict between 2 users
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 42.1
Hardware: x86-64
OS: openSUSE 42.1
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: epistemepromeneur(a)free.fr
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
i open a kde session for user1
i enable bluetooth with bluedevil. i need this permanently for user1.
then
i open a kde session for users2
i disable bluetooth with bluedevil. i don't need this for user2.
i close the session for user2
then
i return to user1 kde session.
i tried to connect my bluetooth headset to see a video. this fails.
i search in the systray. no more bluetooth icon.
bluetooth is disabled !
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=911001
Bug ID: 911001
Summary: dnsmasq apparmor profile prevents libvirt default
network to start
Classification: openSUSE
Product: openSUSE Factory
Version: 201412*
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: AppArmor
Assignee: suse-beta(a)cboltz.de
Reporter: cbosdonnat(a)suse.com
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
This commit in libvirt forces dnsmasq to actually use the leaseshelper program:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=421406808abaf7eb66abd27d71…
The problem is that the dnsmasq apparmor profile prevents the libvirt default
network to start due to:
* Not allowing /bin/bash to be run
* Not allowing leaseshealper contained in /usr/lib64 folder to be run.
Note that this bug may hit 13.2 if an updated libvirt is shipped there.
--
You are receiving this mail because:
You are on the CC list for the bug.