On 10/24/2016 06:34 PM, Michael Catanzaro wrote:
> On Mon, 2016-10-24 at 18:07 +0200, Jakub Filak wrote:
>> I use ABRT to report crashes, I deal with ABRT reports and I'm happy
>> with
>> the current default.
>>
>> I am sorry. I understand your problem, but I
On 10/25/2016 03:54 AM, Kevin Kofler wrote:
>
> Even without this written down anywhere, it used to be common understanding
> that Fedora bugs are public by design. But then came the ABRT team. Now we
> get tons of "private" bug reports. Mostly because ABRT lets users attach
> tons of crazy thi
On 10/21/2016 09:16 PM, Michael Catanzaro wrote:
> On Fri, 2016-10-21 at 20:56 +0200, Florian Weimer wrote:
>> Bugzilla is specifically not designed for keeping sensitive stuff
>
> Now, ABRT's heuristic for whether to make the bug private is really
> terrible; you can imagine that any application
On 10/21/2016 11:29 PM, Chris Murphy wrote:
> On Fri, Oct 21, 2016 at 1:16 PM, Michael Catanzaro
> wrote:
>> On Fri, 2016-10-21 at 20:56 +0200, Florian Weimer wrote:
>>> Bugzilla is specifically not designed for keeping sensitive stuff
>>
>> Really? Every Bugzilla that I regularly work with (GNOM
On 09/13/2016 05:00 PM, Michael Catanzaro wrote:
> Hi,
>
> To be clear, the problem is that a small handful of package maintainers
> (including Bastien) are collectively "responsible" for all of the GNOME
> and freedesktop components in Fedora (including fprintd), and it's
> simply not reasonable
On 09/13/2016 06:32 PM, Bastien Nocera wrote:
>
>
> - Original Message -
>
>
> A couple of things could be done to help with that:
> - Bring back the x-bugzilla .desktop metadata, and have ABRT file upstream
> bugs
Does GNOME Bugzilla support XMLRPC? Is there any testing instance AB
Jan,
I was thinking about this issue some more and I started working on a patch
for ABRT. But I suddenly realized that even users that want ABRT to generate
backtrace from coredump on their machines might not want gdb to pull gcc.
Taking this into account I believe gdb should ask users whether th
Hi Kaleb,
I believe glusterfs processes match the conditions where a core dump
file is not produced (see man 5 core). Especially the set-user-ID &
set-group-ID rule.
I proposed to change the default value of suid_dumpable in February this
year [1]. However, I am not sure if the outcome of th
Hello,
I want to clarify the situation around "no coredumps in CWD".
If configured ABRT can create a core dump file in the current working directory
(more precisely, ABRT can write a core dump to a file according to the old
value
of /proc/sys/kernel/core_pattern) if the process' RLIMIT_CORE (u
On 02/12/2016 07:57 PM, Andrew Lutomirski wrote:
On Fri, Feb 12, 2016 at 10:32 AM, Richard W.M. Jones wrote:
On Fri, Feb 12, 2016 at 07:24:06AM -0500, Jakub Filak wrote:
The default value 0 is there for good security reason, but I would
like to propose changing the default value to 2 for
On 02/25/2016 08:11 PM, Adam Jackson wrote:
On Thu, 2016-02-25 at 18:58 +0100, Jan Kratochvil wrote:
On Thu, 25 Feb 2016 18:03:52 +0100, David Malcolm wrote:
I think I'm only semi-serious here [1], but have you considered
Rust?
[1] e.g. it's not yet in Fedora.
or proven C++11(/14/17)?
(it is
On 02/16/2016 03:23 PM, Andrew Lutomirski wrote:
On Feb 15, 2016 10:36 PM, "Jakub Filak" <mailto:jfi...@redhat.com>> wrote:
>
> It looks like that there are no opponents of this change but several
supporters
> and few of them even want to have suid_dumpable=
then he/she is skilled enough to spot kernel warning in the logs.
What do you think about it?
I would especially like to hear thoughts on this from security experts.
Do I need to get any permission to do so?
Regards,
Jakub
On 02/12/2016 01:24 PM, Jakub Filak wrote:
- Forwarded Message -
I'm not a security expert but I would rather start with something
less ambitious and more secure. Just for sure.
Regards,
Jakub
On 02/15/2016 11:22 AM, Miroslav Vadkerti wrote:
The issue described in the article was fixed by requiring an absolute
path in core_pattern (If I understand it corre
On 02/12/2016 07:57 PM, Andrew Lutomirski wrote:
On Fri, Feb 12, 2016 at 10:32 AM, Richard W.M. Jones wrote:
On Fri, Feb 12, 2016 at 07:24:06AM -0500, Jakub Filak wrote:
The default value 0 is there for good security reason, but I would
like to propose changing the default value to 2 for
notice.
Regards,
Jakub
On 02/12/2016 07:32 PM, Richard W.M. Jones wrote:
On Fri, Feb 12, 2016 at 07:24:06AM -0500, Jakub Filak wrote:
The default value 0 is there for good security reason, but I would
like to propose changing the default value to 2 for development
Fedora releases (Alpha, Beta
- Forwarded Message -
From: "Jakub Filak"
To: secur...@lists.fedoraproject.org
Sent: Thursday, February 11, 2016 9:51:04 AM
Subject: Use suid_dumpable=2 for development releases
Hello,
As a maintainer of ABRT, I have been asked several times why ABRT does not catch
crash
()
Trace/breakpoint trap (core dumped)
$ abrt
d41eb2e 1x firefox 2016-02-09 08:23:26
Looks like it works.
Regards,
Jakub
On 02/08/2016 06:02 PM, Jakub Filak wrote:
abrt should write the reason why it ignores crashes of Firefox to
system logs.
Jakub
On 02/03/2016 02:48 PM, Martin Stransky wro
abrt should write the reason why it ignores crashes of Firefox to system
logs.
Jakub
On 02/03/2016 02:48 PM, Martin Stransky wrote:
On 02/03/2016 02:45 PM, Jakub Jelen wrote:
On 02/03/2016 10:53 AM, Martin Stransky wrote:
Also please remove Firefox from ABRT blacklist at:
/etc/abrt/abrt-a
On 01/19/2016 11:55 AM, Jonathan Wakely wrote:
On 19/01/16 11:00 +0100, Jakub Filak wrote:
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.servic
On 01/14/2016 07:37 AM, Roman Tsisyk wrote:
Hi,
Fedora enables hardened builds [1] by default.
This implies -fomit-frame-pointer -fstack-protector and -fPIE.
[1]: https://fedoraproject.org/wiki/Packaging:Guidelines#PIE
How it is supposed to be debugged by upstream developers?
It would be n
You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and enable abrt-journal-core.service:
http://abrt.readthedocs.org/en/latest/examples.html#getting-core
On 01/08/2016 04:02 PM, Matthew Miller wrote:
On Fri, Jan 08, 2016 at 12:49:39PM +0100, Jakub Filak wrote:
A few months after Fedora 23 was released we have:
- 1149 bug reports for Workstation
- 14 bug reports for Server
- 5 bug reports for Cloud
Do we have stats for non-edition reports
On 10/13/2015 08:50 AM, Jakub Filak wrote:
Hello,
some time ago, Stephen Gallagher approached ABRT team with a request to include
/etc/os-release and especially VARIANT_ID in the Bugzilla bugs opened by ABRT.
We have decided to put this information into Whiteboard in this form:
"VARI
Hello,
some time ago, Stephen Gallagher approached ABRT team with a request to include
/etc/os-release and especially VARIANT_ID in the Bugzilla bugs opened by ABRT.
We have decided to put this information into Whiteboard in this form:
"VARIANT_ID=$id;"
Here is the list of Fedora 23 bugs for Wor
Hello,
GDB has switched from Python 2 to Python 3 (bug #1014549), so the
packages shipping gdb plugins have to switch to Python 3 too. Here is
the list of components providing "*-gdb.py" files in Fedora 22:
efl
gcc
gdb-heap
glib2
golang
insight
isl
kcbench-data
kernel
libreoffice
mingw-gcc
mono
/wiki/Test_Day:2015-04-14_ABRT
and follow the instructions.
If you don't have much time, don't be discouraged by the huge number of test
cases and go through only the new and important features.
Thanks!
Regards,
Jakub Filak
The ABRT Team
__
On Tuesday 07 of April 2015 07:25:32 Michael Catanzaro wrote:
> On Tue, 2015-04-07 at 14:15 +0200, Vít Ondruch wrote:
> > Dne 7.4.2015 v 14:09 Michael Catanzaro napsal(a):
> > > Hi,
> > >
> > > I want 'dnf debug-info-install' to be available by default on
> > > Workstation.
> >
> > Sorry for my i
On Wednesday 21 of January 2015 09:33:31 Vít Ondruch wrote:
> Dne 20.1.2015 v 14:22 Bohuslav Kabrda napsal(a):
> > 1) DNF will be the default package manager for F22 [2], so everything is
> > ok here.
> I really wonder what is the state here. This is on my rawhide:
...
> It is surprising to see so
On Tue, 2014-12-02 at 10:32 +, Richard W.M. Jones wrote:
> On Tue, Dec 02, 2014 at 03:36:11AM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > On Sun, Nov 30, 2014 at 08:29:27PM -0500, Rahul Sundaram wrote:
> > > Hi
> > >
> > > On Sun, Nov 30, 2014 at 1:36 PM, Lars Seipel wrote:
> > > >
> > > >
On Mon, 2014-12-01 at 16:01 +, Richard W.M. Jones wrote:
> On Mon, Dec 01, 2014 at 03:18:36PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> > On Sun, Nov 30, 2014 at 01:43:39PM +, Richard W.M. Jones wrote:
> > > On Fri, Nov 28, 2014 at 07:39:47AM +0100, Jakub Filak
On Fri, 2014-11-28 at 00:28 +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Nov 27, 2014 at 07:02:00PM +0100, Jan Kratochvil wrote:
> > On Thu, 27 Nov 2014 16:23:57 +0100, Jakub Filak wrote:
> > > Do you find 'environ' attachment valuable or is ABRT jus
On Thu, 2014-11-27 at 19:02 +0100, Jan Kratochvil wrote:
> On Thu, 27 Nov 2014 16:23:57 +0100, Jakub Filak wrote:
> > Do you find 'environ' attachment valuable or is ABRT just publishing
> > personal
> > information?
>
> No but I can imagine in some cases it
Hello,
As you might know ABRT attaches 'environ' file to its Bugzilla bugs. The file
contains a full copy of /proc/[pid]/environ. Even though ABRT highlights
black-listed words and encourages users to review the data before submitting
them, it may happen that the reporter misses something and publ
On Mon, 2014-10-27 at 14:01 +1000, Peter Hutterer wrote:
> On Thu, Oct 23, 2014 at 02:54:38AM -0400, Jakub Filak wrote:
> > Hi folks,
> >
> > I ported the ABRT kernel oops detector to journald some time ago, because of
> > NoDefaultSyslog change.
> >
> >
Hi folks,
I ported the ABRT kernel oops detector to journald some time ago, because of
NoDefaultSyslog change.
I wanted to do the same with the ABRT Xorg stack trace detector (just because I
do not like the current implementation and it is possible now [2]), but
I am not able to trigger the Xorg'
On Wed, 2014-10-15 at 16:55 -0600, Orion Poplawski wrote:
>
> We used to have the ability to get statistics grouped by packager,
> right, or am I mis-remembering?
We still have it, but you can filter by packager only on 'Problems'
page:
https://retrace.fedoraproject.org/faf/problems/hot/*/265/*
On Fri, 2014-10-10 at 11:12 +0100, Richard W.M. Jones wrote:
> On Thu, Oct 09, 2014 at 05:39:34PM -0400, Przemek Klosowski wrote:
> > I was curious about the rate of bug reporting in Fedora, and did
> > this quick experiment. I thought it might be interesting to folks
> > here who either work on th
Error: Package: libreport-plugin-kerneloops-2.1.11-1.fc19.x86_64
(updates-testing)
Requires: libs
On Thu, Jan 09, 2014 at 03:00:30AM -0500, Jakub Filak wrote:
> I am sorry for the inconvenience.
>
> We usually rebuild entire ABRT stack (satyr/libreport/abrt) at once
> ,
I am sorry for the inconvenience.
We usually rebuild entire ABRT stack (satyr/libreport/abrt) at once
, however, I'm not able to build abrt for Rawhide because of
some strange auto* error.
The build works on my Rawhide VM but the koji build fails.
I will be more careful next time.
Regards,
Ja
On Fri, 2013-12-06 at 20:06 +0100, Miloslav Trmač wrote:
> On Fri, Dec 6, 2013 at 10:56 AM, Jakub Filak wrote:
> > I'd like to add abrt-cli package to the comps group 'standard'.
> >
> > The package pulls core ABRT functionality for catching C/C++ crashes,
&g
Hello,
I'd like to add abrt-cli package to the comps group 'standard'.
The package pulls core ABRT functionality for catching C/C++ crashes,
uncaught Python exceptions, Kernel oopses and VMCore processing.
There is a bugzilla bug requesting this change:
https://bugzilla.redhat.com/show_bug.cgi?
Thank you for all your ideas!
I am going to change the default template to:
[abrt] : (): killed by SIG
Conclusion:
- do not drop because some email clients cannot display
custom headers in "index"
- drop VR from because Ales Kozumplik is the only one who
wants it (VR is always availa
> > ABRT provides per component customization.
> >
> > https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-formatting
>
> Excellent. Given that almost no packages are shipping these, is there
> any guideline or guidance how to do so? Just add them to our packages?
> Anything we
> I wonder if someday it would make sense to customize this per user?
> Possibly too much complexity...
>
> kevin
ABRT provides per component customization.
https://github.com/abrt/abrt/wiki/FAQ#component-specific-bugzilla-bug-formatting
--
devel mailing list
devel@lists.fedoraproject.org
htt
Hello,
a bugzilla ticket [1] requiring a better Bugzilla summary field text
produced by abrt has been filed. Before I start changing the bug summary
format I'd like to do a little survey:
What would you like see in the bug summaries produced by abrt?
Regards
Jakub
1: https://bugzilla.redhat.co
On Tue, 2013-07-02 at 16:19 -0500, Richard Shaw wrote:
> I saw this during the update:
>
>
> Updating : abrt-libs-2.1.5-1.fc18.x86_64
>10/76
> cp: cannot create regular file
> â/var/tmp/abrt/ccpp-2013-03-27-09:24:26-2877/environâ: No such file or
> directory
> cp: cannot create regular file
ABRT changes since version 2.1.0
In an effort to simplify ABRT's reporting workflow we have decided to move the
default dump location from /var/spool/abrt to /var/tmp/abrt.
Users didn't have write access to dump directories located in /var/spool/abrt
and in order to provide writable directory fo
48 matches
Mail list logo
