Re: libreoffice 4.2.1.1 update failing for dependency?

[Dario Lesca]

Il giorno dom, 23/02/2014 alle 18.30 +0100, Joachim Backes ha scritto:
> On 02/23/2014 06:22 PM, Michael D. Setzer II wrote:
> > Was just running the update on Fedora 20, and found that it files with the 
> > core needing libcmis-0.4, but 0.3.1-8 is available even in testing?
> > 
> > Had already installed the 4.2.1.1 on a machine with older Fedora from the 
> > source with no issue, so not sure why fedora version has this dependency?
> 
> Download and install libcmis-0.4.1-2.fc20 from KOJI
> (http://koji.fedoraproject.org/koji/packageinfo?packageID=13193)

IMHO:

I think this is not a solution.

The solution is fill the bug and wait that the maintainer will fix it.

I also believe that this incomplete update of libreoffice should not
have been published.

-- 
Dario Lesca - sip:da...@solinos.it
(Inviato da Linux Fedora20 con Gnome3.10)


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Even more yum breakage; this time with libreoffice

[Dario Lesca]

Il giorno lun, 24/02/2014 alle 10.01 +0800, Ed Greshko ha scritto:
> To get past the libreoffice problem
> 
> Download what you need from here  
> http://koji.fedoraproject.org/koji/buildinfo?buildID=499516
> 
> And then do
> 
> yum localinstall whatever.rpm

This is only a workaround, and many users cannot apply it.

IMHO, The final solution is:

A=libcmis
B=libreoffice

If [ "a new package version exist for A" \
and "it's useful for some other new package B" ]
then
push A and B to repo for update
else
none of A and B is pushed for update.
fi 

-- 
Dario Lesca - sip:da...@solinos.it
(Inviato da Linux Fedora20 con Gnome3.10)


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Even more yum breakage; this time with libreoffice

[Ed Greshko]

On 02/24/14 18:23, Dario Lesca wrote:
> Il giorno lun, 24/02/2014 alle 10.01 +0800, Ed Greshko ha scritto:
>> To get past the libreoffice problem
>>
>> Download what you need from here  
>> http://koji.fedoraproject.org/koji/buildinfo?buildID=499516
>>
>> And then do
>>
>> yum localinstall whatever.rpm
> This is only a workaround, and many users cannot apply it.

Yes, this is a "workaround" and was directed specifically in response to a 
question by Dan.   Many others can apply it.  Maybe many others aren't able to 
due to lack of knowledge.

>
> IMHO, The final solution is:
>
> A=libcmis
> B=libreoffice
>
> If [ "a new package version exist for A" \
>   and "it's useful for some other new package B" ]
> then
>   push A and B to repo for update
> else
>   none of A and B is pushed for update.
> fi 
>

Yes.  And for those unable to avail themselves of the "workaround" they can 
wait for the final solution. 

-- 
Getting tired of non-Fedora discussions and self-serving posts
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

AM/PM in Thunderbird -

[Bob Goodwin]

For a long time I have been doing:

/etc/locale.confchange:LANG="en_US.UTF-8"

LANG="en_GB.UTF-8"

To make Thunderbird list messages with 24 hour time.

Can someone suggest a better way to accomplish this?

Bob

--
http://www.qrz.com/db/w2bod
Box10 Fedora-20/64bit Linux/XFCE

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: AM/PM in Thunderbird -

[Ed Greshko]

On 02/24/14 20:43, Bob Goodwin wrote:
>
> For a long time I have been doing:
>
> /etc/locale.confchange:LANG="en_US.UTF-8"
>
> LANG="en_GB.UTF-8"
>
> To make Thunderbird list messages with 24 hour time.
>
> Can someone suggest a better way to accomplish this?
>
> Bob
>

Add

export LC_TIME=C

to your .bashrc

Of course you'll need to logout/login for this to take effect globally in your 
GUI

-- 
Getting tired of non-Fedora discussions and self-serving posts
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: AM/PM in Thunderbird -

[Bob Goodwin]

On 02/24/14 08:13, Ed Greshko wrote:

> To make Thunderbird list messages with 24 hour time.
>
> Can someone suggest a better way to accomplish this?
>
> Bob
>

Add

export LC_TIME=C

to your .bashrc

Of course you'll need to logout/login for this to take effect globally in your 
GUI


Thank you Ed. That answers an old question I've had for a long time. 
Worked as you said it would.


Bob

--
http://www.qrz.com/db/w2bod
Box10 Fedora-20/64bit Linux/XFCE

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Recovering/Restoring Boot Partition

[Don Levey]

On 2/22/2014 21:37, Chris Murphy wrote:
> 
> On Feb 22, 2014, at 12:46 PM, Don Levey 
> wrote:
> 
>> On 2/21/2014 11:38, Chris Murphy wrote:
...
>> 
>>> What do you get for:
>>> 
>>> mdadm -E /dev/sda mdadm -E /dev/sdc
>>> 
>>> 
>> (this time, with commands, because I can learn. :-) )
>> 
>> [root@localhost don]# mdadm -E /dev/sda /dev/sda: MBR Magic : aa55 
>> Partition[0] :102760449 sectors at   63 (type 07) 
>> Partition[1] :   409600 sectors at102760512 (type 83) 
>> Partition[2] :209326268 sectors at103170112 (type 8e) 
>> [root@localhost don]# mdadm -E /dev/sdc /dev/sdc: MBR Magic : aa55 
>> Partition[0] :102760449 sectors at   63 (type 07) 
>> Partition[1] :   409600 sectors at102760512 (type 83) 
>> Partition[2] :209326268 sectors at103170112 (type 8e)
>> 
>> So yes, they seem to be relating the same thing.
> 
> It's not finding the IMSM metadata if this is firmware raid. In the
> BIOS setup, you should find some setting related to this. Typically
> the option setting is either raid, ide, or ahci. Maybe it was set to
> raid when you initially did the install and then got changed to ide?
> I wouldn't change it from what it is now, but it's worth checking the
> setting to see if you recall it being changed recently.
> 
I will check when I can reboot next - hopefully tonight.

> Also show the result from each:
> 
> cat /proc/mdstat pvck /dev/sda3 pvck /dev/sdc3
> 
[root@localhost don]# cat /proc/mdstat
Personalities :
unused devices: 


[root@localhost don]# pvck /dev/sda3
  WARNING: Failed to connect to lvmetad: No such file or directory.
Falling back to internal scanning.
  Found label on /dev/sda3, sector 1, type=LVM2 001
  Found text metadata area: offset=4096, size=192512


[root@localhost don]# pvck /dev/sdc3
  WARNING: Failed to connect to lvmetad: No such file or directory.
Falling back to internal scanning.
  Found label on /dev/sdc3, sector 1, type=LVM2 001
  Found text metadata area: offset=4096, size=192512

> What I'm betting on at this point (guessing), is that the raid array
> is not active, and therefore two identical UUID physical volumes are
> present rather than appearing as one, and grub is becoming confused.
> 
On a separate machine, running software RAID1, I see active raid
devices.  That I am not seeing them here would support your suggestion
that the raid array isn't active, no?

> And the other problem is that there simply isn't enough space to
> embed core.img in the MBR gap as usual, because the support modules
> for RAID and LVM make it too big. There is a way to use block lists,
> but before doing that the whole raid thing needs to be figured out.
> 
Interesting.  This makes me wonder why it all worked before.

This was a machine I inherited from a friend, with the raid devices
already there, and running Windows.  When I installed on it, from what I
recall, it presented me with a single volume, and never behaved as if
there were two devices.

> I haven't done a lot of testing in this area with actual hardware but
> some people say using software raid between Windows and Linux is
> flakey. I think it ought to work or it's a bug. But the thing to
> realize is that you have a Windows driver doing software raid when
> Windows is running; and then you have a linux driver doing software
> raid when linux is running. So it's absolutely got to work correctly
> or you've totally defeated the purpose of even having raid1, and
> instead you're better off with just a regular consistent backup, like
> once an hour or something.
> 
> 
I can appreciate that.  If this were a mission-critical machine I might
be able to justify the setup for a regular, hourly, backup.  At this
point, though, that seems overkill.  If this hadn't been working before,
I would probably just accept that it's not going to work and move on.
Thank you again,
 -Don
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

LibreOffice pancake packaging

[poma]

$ file *
autocorr-en-4.2.1.1-1.fc20.noarch.rpm:  RPM v3.0 bin ARM
autocorr-en-1:4.2.1.1-1.fc20
libcmis-0.4.1-2.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libcmis-0.4.1-2.fc20
libreoffice-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-1:4.2.1.1-1.fc20
libreoffice-appdata-4.2.1.1-1.fc20.noarch.rpm:  RPM v3.0 bin ARM
libreoffice-appdata-1:4.2.1.1-1.fc20
libreoffice-base-4.2.1.1-1.fc20.x86_64.rpm: RPM v3.0 bin
i386/x86_64 libreoffice-base-1:4.2.1.1-1.fc20
libreoffice-bsh-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-bsh-1:4.2.1.1-1.fc20
libreoffice-calc-4.2.1.1-1.fc20.x86_64.rpm: RPM v3.0 bin
i386/x86_64 libreoffice-calc-1:4.2.1.1-1.fc20
libreoffice-core-4.2.1.1-1.fc20.x86_64.rpm: RPM v3.0 bin
i386/x86_64 libreoffice-core-1:4.2.1.1-1.fc20
libreoffice-draw-4.2.1.1-1.fc20.x86_64.rpm: RPM v3.0 bin
i386/x86_64 libreoffice-draw-1:4.2.1.1-1.fc20
libreoffice-emailmerge-4.2.1.1-1.fc20.x86_64.rpm:   RPM v3.0 bin
i386/x86_64 libreoffice-emailmerge-1:4.2.1.1-1.fc20
libreoffice-filters-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-filters-1:4.2.1.1-1.fc20
libreoffice-glade-4.2.1.1-1.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libreoffice-glade-1:4.2.1.1-1.fc20
libreoffice-graphicfilter-4.2.1.1-1.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libreoffice-graphicfilter-1:4.2.1.1-1.fc20
libreoffice-headless-4.2.1.1-1.fc20.x86_64.rpm: RPM v3.0 bin
i386/x86_64 libreoffice-headless-1:4.2.1.1-1.fc20
libreoffice-impress-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-impress-1:4.2.1.1-1.fc20
libreoffice-kde-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-kde-1:4.2.1.1-1.fc20
libreoffice-langpack-en-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-langpack-en-1:4.2.1.1-1.fc20
libreoffice-librelogo-4.2.1.1-1.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libreoffice-librelogo-1:4.2.1.1-1.fc20
libreoffice-math-4.2.1.1-1.fc20.x86_64.rpm: RPM v3.0 bin
i386/x86_64 libreoffice-math-1:4.2.1.1-1.fc20
libreoffice-nlpsolver-4.2.1.1-1.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libreoffice-nlpsolver-1:4.2.1.1-1.fc20
libreoffice-ogltrans-4.2.1.1-1.fc20.x86_64.rpm: RPM v3.0 bin
i386/x86_64 libreoffice-ogltrans-1:4.2.1.1-1.fc20
libreoffice-opensymbol-fonts-4.2.1.1-1.fc20.noarch.rpm: RPM v3.0 bin ARM
libreoffice-opensymbol-fonts-1:4.2.1.1-1.fc20
libreoffice-pdfimport-4.2.1.1-1.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libreoffice-pdfimport-1:4.2.1.1-1.fc20
libreoffice-postgresql-4.2.1.1-1.fc20.x86_64.rpm:   RPM v3.0 bin
i386/x86_64 libreoffice-postgresql-1:4.2.1.1-1.fc20
libreoffice-pyuno-4.2.1.1-1.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libreoffice-pyuno-1:4.2.1.1-1.fc20
libreoffice-rhino-4.2.1.1-1.fc20.x86_64.rpm:RPM v3.0 bin
i386/x86_64 libreoffice-rhino-1:4.2.1.1-1.fc20
libreoffice-sdk-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-sdk-1:4.2.1.1-1.fc20
libreoffice-sdk-doc-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-sdk-doc-1:4.2.1.1-1.fc20
libreoffice-ure-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
i386/x86_64 libreoffice-ure-1:4.2.1.1-1.fc20
libreoffice-wiki-publisher-4.2.1.1-1.fc20.x86_64.rpm:   RPM v3.0 bin
i386/x86_64 libreoffice-wiki-publisher-1:4.2.1.1-1.fc20
libreoffice-writer-4.2.1.1-1.fc20.x86_64.rpm:   RPM v3.0 bin
i386/x86_64 libreoffice-writer-1:4.2.1.1-1.fc20
libreoffice-xsltfilter-4.2.1.1-1.fc20.x86_64.rpm:   RPM v3.0 bin
i386/x86_64 libreoffice-xsltfilter-1:4.2.1.1-1.fc20

Has anyone noticed something oddly in this list? :)


poma


-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Recovering/Restoring Boot Partition

[Chris Murphy]

On Feb 24, 2014, at 8:05 AM, Don Levey  wrote:
> I can appreciate that.  If this were a mission-critical machine I might
> be able to justify the setup for a regular, hourly, backup.  At this
> point, though, that seems overkill.  If this hadn't been working before,
> I would probably just accept that it's not going to work and move on.
> Thank you again,

I don't know how a powercut munges the raid metadata on both drives, but the 
raid isn't running from the info you've provided, and I also don't see evidence 
of metadata. Two PV's show up instead of one because the raid1 isn't in effect, 
lvm is seeing them as separate PV's with the same UUID which is why it's 
confused.

I'm confused how the installer permitted this arrangement because it's supposed 
to flag the user whenever there isn't enough space for GRUB core.img in the MBR 
gap - and your setup definitely doesn't appear to have space. The 
/var/log/anaconda/anaconda.program.log might have a clue in the lines that 
appear after "grub2-install".

Anyway, make sure you have backups before changing BIOS raid settings. I'd then 
also make sure the hardware has the latest version of BIOS firmware, and that 
it also has the current firmware RAID software (it's usually part of utilities 
offered by the board manufacturer, it could also be a separate package from 
Intel if it's an Intel implementation). The user space utility in XP I'd like 
to think offers a way to repair the metadata but you'll have to check the 
documentation.

Obviously one of the drives is no longer updated since the raid1 is not in 
effect so it's possible any utility will find the state ambiguous and won't 
know how to sync the disks, does a overwrite c or does c overwrite a? Consider 
that this is probably the expected degraded behavior of the array - after all 
it is still bootable and working. But I don' t know the prescribed method for 
restoring it from this condition. It might actually be to take a full backup of 
everything, blow it all away and recreate everything from scratch (raid, system 
installs, then restore from backups). The idea of raid1 isn't as a backup 
substitute, it's to improve uptime and in that context it's doing that.


Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: libreoffice 4.2.1.1 update failing for dependency?

[Gary Artim]

same error here, holding up 12 updates to desktop...G. )

On Mon, Feb 24, 2014 at 12:09 AM, Dario Lesca  wrote:
> Il giorno dom, 23/02/2014 alle 18.30 +0100, Joachim Backes ha scritto:
>> On 02/23/2014 06:22 PM, Michael D. Setzer II wrote:
>> > Was just running the update on Fedora 20, and found that it files with the
>> > core needing libcmis-0.4, but 0.3.1-8 is available even in testing?
>> >
>> > Had already installed the 4.2.1.1 on a machine with older Fedora from the
>> > source with no issue, so not sure why fedora version has this dependency?
>>
>> Download and install libcmis-0.4.1-2.fc20 from KOJI
>> (http://koji.fedoraproject.org/koji/packageinfo?packageID=13193)
>
> IMHO:
>
> I think this is not a solution.
>
> The solution is fill the bug and wait that the maintainer will fix it.
>
> I also believe that this incomplete update of libreoffice should not
> have been published.
>
> --
> Dario Lesca - sip:da...@solinos.it
> (Inviato da Linux Fedora20 con Gnome3.10)
>
>
> --
> users mailing list
> users@lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Recovering/Restoring Boot Partition

[Chris Murphy]

On Feb 24, 2014, at 8:05 AM, Don Levey  wrote:
> I can appreciate that.  If this were a mission-critical machine I might
> be able to justify the setup for a regular, hourly, backup.  At this
> point, though, that seems overkill.  If this hadn't been working before,
> I would probably just accept that it's not going to work and move on.
> Thank you again,

Another option is the linux-raid@ list: 
http://vger.kernel.org/vger-lists.html#linux-raid

They answer md/mdadm questions related to IMSM raid, and maybe some other way 
to locate the missing metadata and resurrect the array.


Chris Murphy-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Recovering/Restoring Boot Partition

[Don Levey]

On 2/24/2014 13:14, Chris Murphy wrote:
> 
> ..
> 
> Obviously one of the drives is no longer updated since the raid1 is
> not in effect so it's possible any utility will find the state
> ambiguous and won't know how to sync the disks, does a overwrite c or
> does c overwrite a? Consider that this is probably the expected
> degraded behavior of the array - after all it is still bootable and
> working. But I don' t know the prescribed method for restoring it
> from this condition. It might actually be to take a full backup of
> everything, blow it all away and recreate everything from scratch
> (raid, system installs, then restore from backups). The idea of raid1
> isn't as a backup substitute, it's to improve uptime and in that
> context it's doing that.
> 
> 
OK, it looks like I've got my course of action.  I'll pull whatever data
I need from this and wipe clean.  Perhaps, if I'm feeling like I can
afford it, I'll pick up a couple of new disks.  Thank you *very* much
for your help!
 -Don
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Recovering/Restoring Boot Partition

[Don Levey]

On 2/24/2014 13:22, Chris Murphy wrote:
> 
> On Feb 24, 2014, at 8:05 AM, Don Levey  > wrote:
>> I can appreciate that.  If this were a mission-critical machine I might
>> be able to justify the setup for a regular, hourly, backup.  At this
>> point, though, that seems overkill.  If this hadn't been working before,
>> I would probably just accept that it's not going to work and move on.
>> Thank you again,
> 
> Another option is the linux-raid@
> list: http://vger.kernel.org/vger-lists.html#linux-raid
> 
> They answer md/mdadm questions related to IMSM raid, and maybe some
> other way to locate the missing metadata and resurrect the array.
> 
> 
Thank you for the pointer; I'll try them before wiping the machine.
 -Don

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: libreoffice 4.2.1.1 update failing for dependency?

[Michael Cronenworth]

Gary Artim wrote:

same error here, holding up 12 updates to desktop...G. )


The corrected update has been pushed and should arrive in your local mirror any 
hour now.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: LibreOffice pancake packaging

[Ed Greshko]

On 02/25/14 01:02, poma wrote:
> $ file *
> autocorr-en-4.2.1.1-1.fc20.noarch.rpm:  RPM v3.0 bin ARM
> autocorr-en-1:4.2.1.1-1.fc20
> libcmis-0.4.1-2.fc20.x86_64.rpm:RPM v3.0 bin
> i386/x86_64 libcmis-0.4.1-2.fc20
> libreoffice-4.2.1.1-1.fc20.x86_64.rpm:  RPM v3.0 bin
> i386/x86_64 libreoffice-1:4.2.1.1-1.fc20
> libreoffice-appdata-4.2.1.1-1.fc20.noarch.rpm:  RPM v3.0 bin ARM
> libreoffice-appdata-1:4.2.1.1-1.fc20
>
> Has anyone noticed something oddly in this list? :)
>
>
> poma

So, file a bz against "file".


-- 
Getting tired of non-Fedora discussions and self-serving posts
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored

[dennismccloud]

I need some assistance in troubleshooting problem with passing a modprobe 
parameter to the lirc_zilog module.

I'm running Fedora 19 with the most recent updates:

# uname -r
3.12.11-201.fc19.x86_64

I have a file /etc/modprobe.d/lirc_zilog.conf file that contains the following:

# cat /etc/modprobe.d/lirc_zilog.conf
options lirc_zilog tx_only=1

This file previously worked to disable the IR receive mode on the lirc_zilog 
module but something seems to have changed to prevent this from happening.

The above parameter is being ignored since the lirc_zilog module is running 
both transmit and receive.

Here is the command to receive IR signals:

#irw
17b5 00 play Hauppauge
17b5 01 play Hauppauge
17b5 02 play Hauppauge

The lirc_zilog module is being loaded at system boot time:

# lsmod | grep lirc
lirc_zilog 22473  0
i2c_core   38476  8 
drm,i915,i2c_i801,hdpvr,lirc_zilog,drm_kms_helper,i2c_algo_bit,videodev
lirc_dev   19504  1 lirc_zilog
rc_core26896  1 lirc_dev

The systemd-modules-load.service appears to have completed normally:

# systemctl status systemd-modules-load.service
systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
   Active: active (exited) since Mon 2014-02-24 18:06:33 EST; 1min 46s ago
 Docs: man:systemd-modules-load.service(8)
   man:modules-load.d(5)
  Process: 214 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, 
status=0/SUCCESS)

Feb 24 18:06:32 divo systemd[1]: Starting Load Kernel Modules...

The tx_only option is a valid option for lirc_zilog:

# modinfo lirc_zilog
filename:   
/lib/modules/3.12.11-201.fc19.x86_64/kernel/drivers/staging/media/lirc/lirc_zilog.ko
alias:  lirc_pvr150
license:GPL
author: Gerd Knorr, Michal Kochanowicz, Christoph Bartelmus, Ulrich 
Mueller, Stefan Jahn, Jerome Brock, Mark Weaver, Andy Walls
description:Zilog/Hauppauge infrared transmitter driver (i2c stack)
depends:i2c-core,lirc_dev
staging:Y
intree: Y
vermagic:   3.12.11-201.fc19.x86_64 SMP mod_unload
signer: Fedora kernel signing key
sig_key:FC:A0:01:2C:8A:A6:A3:A0:0F:CC:4E:16:E4:8C:17:FD:D9:C6:31:21
sig_hashalgo:   sha256
parm:   minor:Preferred minor device number (int)
parm:   debug:Enable debugging messages (bool)
parm:   tx_only:Only handle the IR transmit function (bool)

I can manually unload the lirc_zilog module and manually reload lirc_zilog with 
the tx_only=1 option and lirc_zilog module works as desired with IR receive 
disabled.

I've tried various filenames.conf and the different directories 
(/lib/modprobe.d) for modprobe without success.

If I run dmesg and grep for IR, I see that lirc_zilog is probing for IR Rx and 
IR Tx.

[Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Rx on Hauppage HD PVR I2C 
(i2c-8)
[Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C 
(i2c-8) done. Waiting on IR Tx.
[Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C 
(i2c-8) done
[Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C 
(i2c-8)
[Mon Feb 24 18:06:34 2014] lirc_zilog: IR unit on Hauppage HD PVR I2C (i2c-8) 
registered as lirc0 and ready
[Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C 
(i2c-8) done

Previously when the tx_only=1 option was being properly processes, the 
lirc_zilog module was only probing for IR Tx.

Looking at the systemd entries from dmesg doesn't give any hints for why the 
lirc_zilog.conf options file isn't being read.

Looking at the output from journalctl -b doesn't provide any clues.

I've exhausted my ability to troubleshoot the systemd-modules-load.service to 
see the details of what is going on during the boot process.

I need help with how to enable debug on the systemd-modules-load process or 
help of where to look next to resolve this issue.

Thanks in advance for any assistance you can provide.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 19 assistance on modprobe /etc/modprobe.d/ .conf file being ignored

[Ed Greshko]

On 02/25/14 07:56, dennismccl...@earthlink.net wrote:
> I need some assistance in troubleshooting problem with passing a modprobe 
> parameter to the lirc_zilog module.
>
> I'm running Fedora 19 with the most recent updates:
>
> # uname -r
> 3.12.11-201.fc19.x86_64
>
> I have a file /etc/modprobe.d/lirc_zilog.conf file that contains the 
> following:
>
> # cat /etc/modprobe.d/lirc_zilog.conf
> options lirc_zilog tx_only=1
>
> This file previously worked to disable the IR receive mode on the lirc_zilog 
> module but something seems to have changed to prevent this from happening.
>
> The above parameter is being ignored since the lirc_zilog module is running 
> both transmit and receive.
>
> Here is the command to receive IR signals:
>
> #irw
> 17b5 00 play Hauppauge
> 17b5 01 play Hauppauge
> 17b5 02 play Hauppauge
>
> The lirc_zilog module is being loaded at system boot time:
>
> # lsmod | grep lirc
> lirc_zilog 22473  0
> i2c_core   38476  8 
> drm,i915,i2c_i801,hdpvr,lirc_zilog,drm_kms_helper,i2c_algo_bit,videodev
> lirc_dev   19504  1 lirc_zilog
> rc_core26896  1 lirc_dev
>
> The systemd-modules-load.service appears to have completed normally:
>
> # systemctl status systemd-modules-load.service
> systemd-modules-load.service - Load Kernel Modules
>Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; 
> static)
>Active: active (exited) since Mon 2014-02-24 18:06:33 EST; 1min 46s ago
>  Docs: man:systemd-modules-load.service(8)
>man:modules-load.d(5)
>   Process: 214 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, 
> status=0/SUCCESS)
>
> Feb 24 18:06:32 divo systemd[1]: Starting Load Kernel Modules...
>
> The tx_only option is a valid option for lirc_zilog:
>
> # modinfo lirc_zilog
> filename:   
> /lib/modules/3.12.11-201.fc19.x86_64/kernel/drivers/staging/media/lirc/lirc_zilog.ko
> alias:  lirc_pvr150
> license:GPL
> author: Gerd Knorr, Michal Kochanowicz, Christoph Bartelmus, Ulrich 
> Mueller, Stefan Jahn, Jerome Brock, Mark Weaver, Andy Walls
> description:Zilog/Hauppauge infrared transmitter driver (i2c stack)
> depends:i2c-core,lirc_dev
> staging:Y
> intree: Y
> vermagic:   3.12.11-201.fc19.x86_64 SMP mod_unload
> signer: Fedora kernel signing key
> sig_key:FC:A0:01:2C:8A:A6:A3:A0:0F:CC:4E:16:E4:8C:17:FD:D9:C6:31:21
> sig_hashalgo:   sha256
> parm:   minor:Preferred minor device number (int)
> parm:   debug:Enable debugging messages (bool)
> parm:   tx_only:Only handle the IR transmit function (bool)
>
> I can manually unload the lirc_zilog module and manually reload lirc_zilog 
> with the tx_only=1 option and lirc_zilog module works as desired with IR 
> receive disabled.
>
> I've tried various filenames.conf and the different directories 
> (/lib/modprobe.d) for modprobe without success.
>
> If I run dmesg and grep for IR, I see that lirc_zilog is probing for IR Rx 
> and IR Tx.
>
> [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Rx on Hauppage HD PVR I2C 
> (i2c-8)
> [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C 
> (i2c-8) done. Waiting on IR Tx.
> [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Rx on Hauppage HD PVR I2C 
> (i2c-8) done
> [Mon Feb 24 18:06:34 2014] lirc_zilog: probing IR Tx on Hauppage HD PVR I2C 
> (i2c-8)
> [Mon Feb 24 18:06:34 2014] lirc_zilog: IR unit on Hauppage HD PVR I2C (i2c-8) 
> registered as lirc0 and ready
> [Mon Feb 24 18:06:34 2014] lirc_zilog: probe of IR Tx on Hauppage HD PVR I2C 
> (i2c-8) done
>
> Previously when the tx_only=1 option was being properly processes, the 
> lirc_zilog module was only probing for IR Tx.
>
> Looking at the systemd entries from dmesg doesn't give any hints for why the 
> lirc_zilog.conf options file isn't being read.
>
> Looking at the output from journalctl -b doesn't provide any clues.
>
> I've exhausted my ability to troubleshoot the systemd-modules-load.service to 
> see the details of what is going on during the boot process.
>
> I need help with how to enable debug on the systemd-modules-load process or 
> help of where to look next to resolve this issue.
>
> Thanks in advance for any assistance you can provide.

I think you're saying that if you manually unload the module and then load it 
the .conf file is honored and loaded as you want.

If so, did you run dracut to create a new initramfs with the changes you made?

-- 
Getting tired of non-Fedora discussions and self-serving posts
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: AM/PM in Thunderbird -

[g]

On 02/24/14 19:13, Ed Greshko wrote:

On 02/24/14 20:43, Bob Goodwin wrote:


For a long time I have been doing:

/etc/locale.confchange:LANG="en_US.UTF-8"

LANG="en_GB.UTF-8"

To make Thunderbird list messages with 24 hour time.

Can someone suggest a better way to accomplish this?

Bob



Add

export LC_TIME=C

to your .bashrc

Of course you'll need to logout/login for this to take effect

> globally in your GUI

instead of taking the time needed to logout and login to desktop,
i find that opening a terminal and entering;

   . ~/.bashrc

is a faster way to effect new .bashrc entries.


--

peace out.

in a world with out fences, who needs gates.

tc.hago.

g
.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

change repos for nvidia...

[Fred Smith]

I've got a 64-bit system using Nvidia drivers that came from rpmfusion.

I'd like to switch to the Nvidia drivers from elrepo instead, and wonder
if there is any particular set of steps to follow (to keep, one hopes,
from hosing one's system).

Thanks!

Fred
-- 
---
Under no circumstances will I ever purchase anything offered to me as
the result of an unsolicited e-mail message. Nor will I forward chain
letters, petitions, mass mailings, or virus warnings to large numbers
of others. This is my contribution to the survival of the online
community.
 --Roger Ebert, December, 1996
- The Boulder Pledge -
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: change repos for nvidia...

[Ed Greshko]

On 02/25/14 08:33, Fred Smith wrote:
> I've got a 64-bit system using Nvidia drivers that came from rpmfusion.
>
> I'd like to switch to the Nvidia drivers from elrepo instead, and wonder
> if there is any particular set of steps to follow (to keep, one hopes,
> from hosing one's system).

http://elrepo.org/tiki/kmod-nvidia  gives some guidance.

Notes for RPMForge users
Users migrating from the rpmforge dkms package are advised to uninstall the 
dkms-nvidia driver before attempting to install kmod-nvidia.
There is a potential conflict between elrepo and rpmforge in that both 
repositories provide the nvidia-x11-drv package. If you are using the yum 
priorities plugin then the priority for elrepo and rpmforge should be set to 
the same value to avoid dependency resolution failures, or rpmforge should be 
temporarily disabled whilst installing kmod-nvidia and nvidia-x11-drv. For 
example:


Other than that, I think I'd consult their mailing list as those folks may have 
more insight how to deal with moving to their repos.

-- 
Getting tired of non-Fedora discussions and self-serving posts
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: AM/PM in Thunderbird -

[Mark LaPierre]

On 02/24/14 19:31, g wrote:
> 
> 
> On 02/24/14 19:13, Ed Greshko wrote:
>> On 02/24/14 20:43, Bob Goodwin wrote:
>>>
>>> For a long time I have been doing:
>>>
>>> /etc/locale.confchange:LANG="en_US.UTF-8"
>>>
>>> LANG="en_GB.UTF-8"
>>>
>>> To make Thunderbird list messages with 24 hour time.
>>>
>>> Can someone suggest a better way to accomplish this?
>>>
>>> Bob
>>>
>>
>> Add
>>
>> export LC_TIME=C
>>
>> to your .bashrc
>>
>> Of course you'll need to logout/login for this to take effect
>> globally in your GUI
> 
> instead of taking the time needed to logout and login to desktop,
> i find that opening a terminal and entering;
> 
>. ~/.bashrc
> 
> is a faster way to effect new .bashrc entries.
> 
> 

That's an effective way to make the change active in the current shell
but that does not make the change effective in your current GUI session.

It's good practice to try that before you log off just in case you've
buggered up your .bashrc bad enough that it won't let you log on again
after you log off.

-- 
_
   °v°
  /(_)\
   ^ ^  Mark LaPierre
Registered Linux user No #267004
https://linuxcounter.net/

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org