https://bugzilla.suse.com/show_bug.cgi?id=1125564https://bugzilla.suse.com/show_bug.cgi?id=1125564#c2
Peter Varkoly <varkoly(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #2 from Peter Varkoly <varkoly(a)suse.com> ---
(In reply to Rainer Klute from comment #1)
> I found the problem: The self-signed certificate I used was rejected by the
> newer Cyrus imapd version.
>
> I am still keeping this bug open, though, because imapd should issue more
> specific error messages to help the user better to identify the problem. It
> should at least differentiate between "could not read the cert file" and
> "cert file contains invalid certificate". Even better would be to tell the
> user why exactly the cert file is invalid.
1. This should be fixed by cyrus devel team
2. We do not support cyrus-imap anymore.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1119629https://bugzilla.suse.com/show_bug.cgi?id=1119629#c4
Peter Varkoly <varkoly(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
OS|openSUSE Factory |All
--- Comment #4 from Peter Varkoly <varkoly(a)suse.com> ---
fixed
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1119651https://bugzilla.suse.com/show_bug.cgi?id=1119651#c1
Peter Varkoly <varkoly(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
OS|openSUSE Factory |All
--- Comment #1 from Peter Varkoly <varkoly(a)suse.com> ---
Fixed in libsasl version 2.1.27
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1111454
Bug ID: 1111454
Summary: Unable to tell if amavis is operating correctly or
not.
Classification: openSUSE
Product: openSUSE Distribution
Version: Leap 15.0
Hardware: x86-64
OS: SUSE Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Other
Assignee: bnc-team-screening(a)forge.provo.novell.com
Reporter: dgolden(a)golden-consulting.com
QA Contact: qa-bugs(a)suse.de
CC: opensuse(a)mike.franken.de
Depends on: 1106832
Found By: ---
Blocker: ---
Created attachment 785700
--> http://bugzilla.suse.com/attachment.cgi?id=785700&action=edit
Leap 42.3 startup log
+++ This bug was initially created as a clone of Bug #1106832 +++
After updating from openSUSE Leap 42.3 to 15.0 the error message from the
summary occurs on every start of amavisd:
Amavis::Util: can't obtain a tainted string at /usr/sbin/amavisd line 2921.
In addition, the modules and external programs are no longer listed as the were
previous to Leap 15.0.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1098832https://bugzilla.suse.com/show_bug.cgi?id=1098832#c2
Peter Varkoly <varkoly(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #2 from Peter Varkoly <varkoly(a)suse.com> ---
In later versions it works.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1098497https://bugzilla.suse.com/show_bug.cgi?id=1098497#c3
Peter Varkoly <varkoly(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|varkoly(a)suse.com |screening-team-bugs(a)suse.de
--- Comment #3 from Peter Varkoly <varkoly(a)suse.com> ---
I'm not maintainer of ldap-stuff
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1092819https://bugzilla.suse.com/show_bug.cgi?id=1092819#c1
Peter Varkoly <varkoly(a)suse.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Peter Varkoly <varkoly(a)suse.com> ---
DUP 1086807
*** This bug has been marked as a duplicate of bug 1086807 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
Bug ID: 1185994
Summary: GDM password screen blanks shortly after
suspend/resume
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: x86-64
OS: openSUSE Tumbleweed
Status: NEW
Severity: Normal
Priority: P5 - None
Component: GNOME
Assignee: gnome-bugs(a)suse.de
Reporter: David(a)WalkerStreet.info
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
After opening the lid to resume a suspended laptop, the password prompt
displayed by GDM shows for less than a second, and then the screen goes black.
Typing a character restores the screen, and things work normally after that. I
believe this started with Gnome 40.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1190196
Bug ID: 1190196
Summary: xfce4-power-manager segmentation fault then try to
operate with a icon in system tray
Classification: openSUSE
Product: openSUSE Tumbleweed
Version: Current
Hardware: Other
OS: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xfce
Assignee: bnc-team-xfce(a)forge.provo.novell.com
Reporter: virex(a)mail.ru
QA Contact: qa-bugs(a)suse.de
Found By: ---
Blocker: ---
Then try to operate with a icon in system tray xfce4-power-manager closes with
a error: segmentation fault
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1120256https://bugzilla.suse.com/show_bug.cgi?id=1120256#c66
--- Comment #66 from openQA Review <openqa-review(a)suse.de> ---
This is an autogenerated message for openQA integration by the openqa_review
script:
This bug is still referenced in a failing openQA test:
yast2_firstboot_custom_textmode
https://openqa.suse.de/tests/6999418
To prevent further reminder comments one of the following options should be
followed:
1. The test scenario is fixed by applying the bug fix to the tested product or
the test is adjusted
2. The openQA job group is moved to "Released" or "EOL" (End-of-Life)
3. The label in the openQA scenario is removed
--
You are receiving this mail because:
You are on the CC list for the bug.