On 03/05/2018 12:28 PM, Stephen Morris wrote:
Firstly, am I doing something wrong when I issue the command in a shell
and get the segmentation fault but no error message or stack trace
messages?
No, the problem manifests in various ways. I only got a stack trace
because I used gdb on it.
___
On Tue, 2018-03-06 at 08:04 +1100, Eyal Lebedinsky wrote:
> > That works, but '*/Droid\ Sans*' (i.e. with a literal space) segfaults.
>
> A '\' inside single quotes is *not* an escape, use "*/Droid\ Sans*" for that.
Maybe so, but it still segfaults ...
poc
___
On 06/03/18 07:28, Stephen Morris wrote:
On 5/3/18 12:55 pm, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
This is consistent, and also happens on a second machine. Both run f27 fully
updated.
The following does work:
$ dnf provide
On 06/03/18 02:30, Patrick O'Callaghan wrote:
On Mon, 2018-03-05 at 22:21 +0800, Ed Greshko wrote:
On 03/05/18 20:46, Eyal Lebedinsky wrote:
On 05/03/18 23:35, Tim wrote:
On Mon, 2018-03-05 at 12:55 +1100, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provi
On 5/3/18 12:55 pm, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
This is consistent, and also happens on a second machine. Both run f27
fully updated.
The following does work:
$ dnf provides '*/Droid*'
But this one crashes:
$ dn
On Mon, 2018-03-05 at 22:21 +0800, Ed Greshko wrote:
> On 03/05/18 20:46, Eyal Lebedinsky wrote:
> > On 05/03/18 23:35, Tim wrote:
> > > On Mon, 2018-03-05 at 12:55 +1100, Eyal Lebedinsky wrote:
> > > > While it mostly works, this specific command fails:
> > > >
> > > > $ dnf provides '*/Droid San
On 03/05/18 20:46, Eyal Lebedinsky wrote:
> On 05/03/18 23:35, Tim wrote:
>> On Mon, 2018-03-05 at 12:55 +1100, Eyal Lebedinsky wrote:
>>> While it mostly works, this specific command fails:
>>>
>>> $ dnf provides '*/Droid Sans*'
>>
>> Is that first asterisk slash sequence the right characters, in
On 05/03/18 23:35, Tim wrote:
On Mon, 2018-03-05 at 12:55 +1100, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
Is that first asterisk slash sequence the right characters, in the
right order?
Yes, the pattern is a standard wildcard
On Mon, 2018-03-05 at 12:55 +1100, Eyal Lebedinsky wrote:
> While it mostly works, this specific command fails:
>
> $ dnf provides '*/Droid Sans*'
Is that first asterisk slash sequence the right characters, in the
right order?
I'm on an older release, but if I try your command, and similar
permu
On 05/03/18 08:50, John Pilkington wrote:
I know this thread is about dnf, but I've seen exactly this font problem.
mythtv will be looking for /usr/share/mythtv/fonts/DroidSans-Bold.ttf
which may be a real file derived from the mythtv distro or may be a link
to the system fonts location like
On 05/03/18 05:31, Eyal Lebedinsky wrote:
On 05/03/18 15:27, Ed Greshko wrote:
On 03/05/18 12:23, Samuel Sieb wrote:
On 03/04/2018 05:55 PM, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
This is consistent, and also happens on a sec
On 03/04/2018 09:17 PM, Ralf Corsepius wrote:
Interestingly on i386 the segfault is slightly more verbose:
# dnf provides '*/Droid Sans*'
Last metadata expiration check: 0:00:33 ago on Mon 05 Mar 2018 05:39:27
AM CET.
free(): invalid size
Aborted (core dumped)
I have hit various errors and s
On 03/04/2018 09:31 PM, Eyal Lebedinsky wrote:
True. I was trying to understand why mythtv-setup complains:
2018-03-05 16:28:02.602160 E MythFontProperties: Failed to load 'Droid
Sans', got 'Droid Sans [MONO]' instead
Location:
/usr/share/mythtv/themes/MythCenter-wide
On 05/03/18 15:27, Ed Greshko wrote:
On 03/05/18 12:23, Samuel Sieb wrote:
On 03/04/2018 05:55 PM, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
This is consistent, and also happens on a second machine. Both run f27 fully
updated.
On 03/05/2018 02:55 AM, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
This is consistent, and also happens on a second machine. Both run f27
fully updated.
The following does work:
$ dnf provides '*/Droid*'
But this one crashes:
On 03/04/2018 08:27 PM, Ed Greshko wrote:
OK, but isn't this searching for a file that has a "space" in it? Can't recall
ever
seeing one like that as part of the O/S.
It might not be a query that will return anything, but it's still a bad
crash that shouldn't happen.
I filed https://bugzill
On 03/05/18 12:23, Samuel Sieb wrote:
> On 03/04/2018 05:55 PM, Eyal Lebedinsky wrote:
>> While it mostly works, this specific command fails:
>>
>> $ dnf provides '*/Droid Sans*'
>>
>> This is consistent, and also happens on a second machine. Both run f27 fully
>> updated.
>>
>> The following does
On 03/04/2018 05:55 PM, Eyal Lebedinsky wrote:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
This is consistent, and also happens on a second machine. Both run f27
fully updated.
The following does work:
$ dnf provides '*/Droid*'
But this one crashes:
While it mostly works, this specific command fails:
$ dnf provides '*/Droid Sans*'
This is consistent, and also happens on a second machine. Both run f27 fully
updated.
The following does work:
$ dnf provides '*/Droid*'
But this one crashes:
$ dnf provides '*/x y*'
I suspect a python prob
Hi
On Sat, Jun 28, 2014 at 11:15 PM, Stephen Morris wrote:
> Hi,
> I was trying to install mysql packages from the yum repository for
> Fedora 20 provided by Oracle and the fist package dnf tried to install
> needed to have a key loaded from the key file specified in the repository
> defini
Hi,
I was trying to install mysql packages from the yum repository for
Fedora 20 provided by Oracle and the fist package dnf tried to install
needed to have a key loaded from the key file specified in the
repository definition but crashed with the following stack trace. Has
anybody else se
21 matches
Mail list logo
