[Bug 2193021] New: [abrt] nemo: g_type_check_instance_is_fundamentally_a(): nemo-desktop killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2193021
Bug ID: 2193021
Summary: [abrt] nemo:
g_type_check_instance_is_fundamentally_a():
nemo-desktop killed by SIGSEGV
Product: Fedora
Version: rawhide
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:40484f82287c3ceb18507c67505aea3cd89dc9fa;VAR
IANT_ID=cinnamon;
Component: nemo
Assignee: leigh123linux(a)googlemail.com
Reporter: bradleyc.hackett(a)yahoo.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
leigh123linux(a)googlemail.com, riehecky(a)fnal.gov
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
nemo-5.6.4-1.fc39
Additional info:
reporter: libreport-2.17.9
type: CCpp
reason: nemo-desktop killed by SIGSEGV
journald_cursor:
s=775cfc3ae8894860b677b4c9e90f15a3;i=12e90;b=856be612c3d640c3bb398e236ffe83d4;m=3e41f3e3;t=5fabc63796eef;x=5fbedb6a1812558a
executable: /usr/bin/nemo-desktop
cmdline: nemo-desktop
cgroup: 0::/user.slice/user-1000.slice/session-2.scope
rootdir: /
uid: 1000
kernel: 6.4.0-0.rc0.20230428git33afd4b76393.7.fc39.x86_64
package: nemo-5.6.4-1.fc39
runlevel: N 5
backtrace_rating: 4
crash_function: g_type_check_instance_is_fundamentally_a
Truncated backtrace:
Thread no. 1 (11 frames)
#0 g_type_check_instance_is_fundamentally_a at ../gobject/gtype.c:4166
#2 desktop_location_changed_callback at ../src/nemo-pathbar.c:223
#4 signal_emit_unlocked_R.isra.0 at ../gobject/gsignal.c:3812
#7 g_settings_real_change_event at ../gio/gsettings.c:392
#8 _g_cclosure_marshal_BOOLEAN__POINTER_INTv at ../gio/gmarshal-internal.c:428
#9 _g_closure_invoke_va at ../gobject/gclosure.c:895
#12 settings_backend_path_changed at ../gio/gsettings.c:467
#14 g_settings_backend_invoke_closure at ../gio/gsettingsbackend.c:275
#18 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276
#19 g_main_context_iteration at ../glib/gmain.c:4343
#20 g_application_run at ../gio/gapplication.c:2573
Potential duplicate: bug 1933799
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2193021
7 months, 1 week
[Bug 2240297] New: dnscrypt-proxy package doesn't create /var/cache/dnscrypt-proxy directory
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2240297
Bug ID: 2240297
Summary: dnscrypt-proxy package doesn't create
/var/cache/dnscrypt-proxy directory
Product: Fedora
Version: 39
Status: NEW
Component: dnscrypt-proxy
Assignee: davide(a)cavalca.name
Reporter: morb(a)misentropic.com
QA Contact: extras-qa(a)fedoraproject.org
CC: davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
go-sig(a)lists.fedoraproject.org, zebob.m(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
The package fails to create /var/cache/dnscrypt-proxy, thusly preventing
downloading lists of resolvers and further bootstrapping
Version-Release number of selected component (if applicable):
dnscrypt-proxy-2.1.4-2.fc39
How reproducible:
quite
Steps to Reproduce:
1. Install the dnscrypt-proxy package from a mirror
2. Start the service
3. Check journalctl for error messages from the service, claiming its inability
to update cache file
Actual results:
ep 22 19:32:27 peppermill dnscrypt-proxy[19778]: dnscrypt-proxy 2.1.4
Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Network connectivity detected
Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Now listening to 127.0.0.1:53
[UDP]
Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Now listening to 127.0.0.1:53
[TCP]
Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Service is not usable yet
Sep 22 19:32:27 peppermill dnscrypt-proxy[19778]: Resolving server host
[download.dnscrypt.info] using bootstrap resolvers over udp
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [public-resolvers]
failed to update cache file [/var/cache/dnscrypt-proxy/public-resolvers.md]:
open /var/cache/dnscrypt-proxy/sf-jm64uh4swjstkxyl.tmp: no such file or
directory
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [public-resolvers]
loaded
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Service is not usable yet
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Resolving server host
[raw.githubusercontent.com] using bootstrap resolvers over udp
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [relays] failed to
update cache file [/var/cache/dnscrypt-proxy/relays.md]: open
/var/cache/dnscrypt-proxy/sf-uvkpifsx2fujtmrn.tmp: no such file or directory
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Source [relays] loaded
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Unable to use source
[public-resolvers]: [Invalid format for source at
[[https://download.dnscrypt.info/resolvers-list/v3/public-resolvers.md
https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/p...
https://ipv6.download.dnscrypt.info/resolvers-list/v3/public-resolvers.md]]]
Sep 22 19:32:28 peppermill dnscrypt-proxy[19778]: Invalid format for source at
[[https://download.dnscrypt.info/resolvers-list/v3/public-resolvers.md
https://raw.githubusercontent.com/DNSCrypt/dnscrypt-resolvers/master/v3/p...
.md https://ipv6.download.dnscrypt.info/resolvers-list/v3/public-resolvers.md]]
Sep 22 19:32:28 peppermill systemd[1]: dnscrypt-proxy.service: Main process
exited, code=exited, status=255/EXCEPTION
Sep 22 19:32:28 peppermill systemd[1]: dnscrypt-proxy.service: Failed with
result 'exit-code'.
Expected results:
After directory creation:
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: dnscrypt-proxy 2.1.4
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Network connectivity detected
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Now listening to 127.0.0.1:53
[UDP]
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Now listening to 127.0.0.1:53
[TCP]
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Service is not usable yet
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Resolving server host
[raw.githubusercontent.com] using bootstrap resolvers over udp
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Source [public-resolvers]
loaded
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Service is not usable yet
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Resolving server host
[download.dnscrypt.info] using bootstrap resolvers over udp
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Source [relays] loaded
Sep 22 19:33:27 peppermill dnscrypt-proxy[19827]: Firefox workaround
initialized
...
Additional info:
None
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2240297
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
7 months, 1 week
[Bug 2210222] New: Systemd unit file is not shipped in %_unitdir
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2210222
Bug ID: 2210222
Summary: Systemd unit file is not shipped in %_unitdir
Product: Fedora
Version: 38
OS: Linux
Status: NEW
Component: dnscrypt-proxy
Severity: low
Assignee: zebob.m(a)gmail.com
Reporter: pemensik(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
go-sig(a)lists.fedoraproject.org, zebob.m(a)gmail.com
Target Milestone: ---
Classification: Fedora
I have noticed after installing dnscrypt-proxy package, that its systemd unit
file is not in vendor path where unit files from packages are supposed to be.
That should be fixed.
Reproducible: Always
Steps to Reproduce:
1. systemctl cat dnscrypt-proxy | head -1
2.
3.
Actual Results:
# /etc/systemd/system/dnscrypt-proxy.service
Expected Results:
# /usr/lib/systemd/system/dnscrypt-proxy.service
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2210222
7 months, 1 week
[Bug 2241775] New: TRIAGE-CVE-2023-5341 ImageMagick: Heap use-after-free in coders/bmp.c [epel-all]
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2241775
Bug ID: 2241775
Summary: TRIAGE-CVE-2023-5341 ImageMagick: Heap use-after-free
in coders/bmp.c [epel-all]
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: ImageMagick
Keywords: Security, SecurityTracking
Severity: medium
Priority: medium
Assignee: luya_tfz(a)thefinalzone.net
Reporter: pdelbell(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: blaise(a)gmail.com, davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, luya_tfz(a)thefinalzone.net,
michel(a)michel-slm.name, ngompa13(a)gmail.com,
pampelmuse(a)gmx.at, sergio(a)serjux.com
Target Milestone: ---
Classification: Fedora
More information about this security flaw is available in the following bug:
http://bugzilla.redhat.com/show_bug.cgi?id=2241774
Disclaimer: Community trackers are created by Red Hat Product Security team on
a best effort basis. Package maintainers are required to ascertain if the flaw
indeed affects their package, before starting the update process.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2241775
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
7 months, 1 week