On 07/07/2013 04:45 PM, antonio wrote:
When I insert an image in an Impress document and I want to resize
images keeping dimension ratio, it seems that it doesn't work, ratio
is dismissed!!!
I think you've gotta hold down ctrl or shift while dragging the corner.
something like that anyway.
One
When I insert an image in an Impress document and I want to resize
images keeping dimension ratio, it seems that it doesn't work, ratio is
dismissed!!!
--
Antonio M
Skype: amontag52
Linux Fedora F19(Schroedinger's cat) on Acer 5720
http://lugsaronno.altervista.org
http://www.campingmonterosa.c
On 07/07/2013 03:52 PM, Heinz Diehl wrote:
On 07.07.2013, lee wrote:
What kind of crap is that?
I don't know.
And does it mean that there again will be problems with updating when I try
to move to F19?
In general, I would always prefer a fresh install over any
update. Experience over the ye
On 07.07.2013, lee wrote:
> What kind of crap is that?
I don't know.
> And does it mean that there again will be problems with updating when I try
> to move to F19?
In general, I would always prefer a fresh install over any
update. Experience over the years has shown (for me) that updating is
On Sat, Jul 06, 2013 at 15:45:53 +0200,
Reindl Harald wrote:
Am 06.07.2013 15:40, schrieb Tim Evans:
# yum -y update
do *not* use "-y"
what are you doing if due a packaging-error half of the system
would be removed?
An update isn't going to do that. If you were doing an erase or distro
Hi,
so I've been running 'yum update' today and when I wanted to reboot, I
found that grub now has an entry to boot some vmlinuz-fedup instead of a
normal kernel, and that even as default :(
The vmlinuz-fedup isn't bootable --- apparently it tries to start some
sort of rescue mode and then says i
On Sat, 06 Jul 2013 21:56:28 +0200, Reindl Harald wrote:
> Am 06.07.2013 21:41, schrieb Amadeus W.M.:
>> I normally run sshd on a port different than 22 and I'm trying to do
>> the same on a fresh Fedora 19, but it fails with a permission denied
>> error:
>>
>> I am, however, able to run it e.g.
On 07/07/2013 01:12 AM, Frank wrote:
> I would like some help/opinions installing Fedora 19 on a new computer
> which came with Windows 7 installed.
> I have shrunk the Windows partition to 40 gigs ( it's an 80 gig hd) and now
> have 4 partitions, two devoted to Windows and two empty ones...I plan
I would like some help/opinions installing Fedora 19 on a new computer
which came with Windows 7 installed.
I have shrunk the Windows partition to 40 gigs ( it's an 80 gig hd) and now
have 4 partitions, two devoted to Windows and two empty ones...I plan to
put Fedora
in one of them.
Windows st
Am 06.07.2013 21:41, schrieb Amadeus W.M.:
> I normally run sshd on a port different than 22 and I'm trying to do the
> same on a fresh Fedora 19, but it fails with a permission denied error:
>
> I am, however, able to run it e.g. on port 34567. Any idea what's going
> on? As far as I can tell
Am 06.07.2013 22:11, schrieb antonio montagnani:
> Reindl Harald ha scritto / said the followingil giorno/on 06/07/2013
> 21:39:
>>
>>
>> Am 06.07.2013 21:31, schrieb antonio montagnani:
>>> Reindl Harald ha scritto / said the followingil giorno/on 06/07/2013
>>> 13:39:
A
Am 06.07.2013 16:02, schrieb Timothy Murphy:
> Incidentally, I've used fedup twice now, F-17->F-18 and F-18->F-19,
> and based on this sample of 2 I'd give it 150 out of 100.
> I was suspicious of it because the old Fedora upgrade (I forget its name)
> caused me endless trouble.
>
> My only sugg
Am 06.07.2013 21:31, schrieb antonio montagnani:
> Reindl Harald ha scritto / said the followingil giorno/on 06/07/2013
> 13:39:
>>
>>
>> Am 06.07.2013 08:51, schrieb antonio montagnani:
>>> I get this message:
>>>
>>> RPM Scriptlet: dracut-install: ERROR: installing
>>> '/usr/lib/kbd/conso
Am 06.07.2013 15:54, schrieb Ranjan Maitra:
> Of late (since later days of F18), I have been getting the following
> error whenever a new kernel gets installed: /boot/grub2/grub.cfg does
> not get updated and has to be "fixed" manually using
>
> sudo grub2-mkconfig -o /boot/grub2/grub.cfg
>
>
Am 06.07.2013 08:51, schrieb antonio montagnani:
> I get this message:
>
> RPM Scriptlet: dracut-install: ERROR: installing
> '/usr/lib/kbd/consolefonts/True.*'
> 08:49:39 : YUM: E: /usr/lib/dracut/dracut-install -D
> /var/tmp/initramfs.3dcDyn /usr/lib/kbd/consolefonts/True.
>
> what does it
Am 06.07.2013 15:40, schrieb Tim Evans:
> # yum -y update
do *not* use "-y"
what are you doing if due a packaging-error half of the system
would be removed?
> Loaded plugins: langpacks, presto, refresh-packagekit
> Resolving Dependencies
> --> Running transaction check
> ---> Package rcssserve
On 06.07.2013 16:02, Timothy Murphy wrote:
> Ed Greshko wrote:
>
>> On 07/06/13 15:50, Timothy Murphy wrote:
>>> Fedup 18 -> 19 went fine for me,
>>> but I noticed a few warnings came up during the process.
>>> Is there any command one could or should run after fedup
>>> to clean up yum records?
>>
Reindl Harald ha scritto / said the followingil giorno/on 06/07/2013
21:39:
Am 06.07.2013 21:31, schrieb antonio montagnani:
Reindl Harald ha scritto / said the followingil giorno/on 06/07/2013 13:39:
Am 06.07.2013 08:51, schrieb antonio montagnani:
I get this message:
RPM Scriptl
On Saturday, July 6, 2013, 2:20:51 PM, Paul wrote:
> Huh. With the full x86_64 install DVD, I can choose "use basic graphics
> mode" in the initial menu under Troubleshooting, and the installer comes up
> OK.Without that, the screen is f*cked up just like what happens with the
> live DVD. My
I normally run sshd on a port different than 22 and I'm trying to do the
same on a fresh Fedora 19, but it fails with a permission denied error:
32) root:~> systemctl status sshd.service
sshd.service - OpenSSH server daemon
Loaded: loaded (/usr/lib/systemd/system/sshd.service; enabled)
Acti
Reindl Harald ha scritto / said the followingil giorno/on 06/07/2013
13:39:
Am 06.07.2013 08:51, schrieb antonio montagnani:
I get this message:
RPM Scriptlet: dracut-install: ERROR: installing
'/usr/lib/kbd/consolefonts/True.*'
08:49:39 : YUM: E: /usr/lib/dracut/dracut-install -D /var/t
Huh. With the full x86_64 install DVD, I can choose "use basic graphics
mode" in the initial menu under Troubleshooting, and the installer comes up
OK.Without that, the screen is f*cked up just like what happens with the
live DVD. My video hardware is nVidia.
I think I'll let F19 stew for a
On Saturday, July 6, 2013, 12:08:44 PM, Paul Allen wrote:
> walksalot wrote
>> Booting the 64-bit F19 live DVD on my system results in many minutes of a
>> rattling optical drive, and then a uniform grey screen with a row of about
>> 16 PC block graphics characters in the upper left. The system is
Ed Greshko wrote
> On 07/06/13 09:02, walksalot wrote:
>> Mateusz Marzantowicz wrote
>>> Check CD/DVD media or better use USB. I had similar situation on broken
>>> CD several years ago.
>> The media matches the SHA256 checksum.
>>
>> But, I appear to be the only one reporting this problem. Anybod
walksalot wrote
> Booting the 64-bit F19 live DVD on my system results in many minutes of a
> rattling optical drive, and then a uniform grey screen with a row of about
> 16 PC block graphics characters in the upper left. The system is, umm,
> utterly non-responsive at this point. Have to power c
On Sat, 06 Jul 2013 09:40:56 -0400, Tim Evans wrote:
> Seems like a rev number is missing in this dependency error from Yum:
>
> # yum -y update
> Loaded plugins: langpacks, presto, refresh-packagekit
> Resolving Dependencies
> --> Running transaction check
> ---> Package rcssserver3d.i686 0:0.6.
On 07/05/2013 10:06 AM, Richard Vickery wrote:
>
>
> "systemctl reboot gdm" has too many arguments
>
That should be "systemctl restart gdm"
--Greg
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo
Ed Greshko wrote:
> On 07/06/13 15:50, Timothy Murphy wrote:
>> Fedup 18 -> 19 went fine for me,
>> but I noticed a few warnings came up during the process.
>> Is there any command one could or should run after fedup
>> to clean up yum records?
>
> What do you mean "clean up yum records"?
I don'
Hello,
Of late (since later days of F18), I have been getting the following
error whenever a new kernel gets installed: /boot/grub2/grub.cfg does
not get updated and has to be "fixed" manually using
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Is there any way to fix this problem?
The only erro
Seems like a rev number is missing in this dependency error from Yum:
# yum -y update
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package rcssserver3d.i686 0:0.6.6-3.fc18 will be updated
---> Package rcssserver3d.i686 0:0.6.7-1.f
Hi,
Can someone explain systemd's behaviour? Why is when I have the
following services enabled:
nfs-idmap.service nfs-lock.service nfs-mountd.service nfs-secure.service
I have to enable nfs.target otherwise they fail to start?
This is Fedora 19.
--
Ian Chapman.
--
users mailing list
us
Hi,
You are right! it is from an Edimax wireless router.
I know now for sure because with sniffer I see the address of
192.168.2.1 as a source address, and the 192.168.2.1 address is the
address of the Edimax wireless router.
However:
There is a UPnP setting - I can reach it from the web interfac
On 07/06/13 15:50, Timothy Murphy wrote:
> Fedup 18 -> 19 went fine for me,
> but I noticed a few warnings came up during the process.
> Is there any command one could or should run after fedup
> to clean up yum records?
What do you mean "clean up yum records"?
What were the warnings? What error
Maybe it's a router-generated traffic.
e.g. an Asus router has "Enable UPnP" option in "IP" settings.
2013/7/5 Kevin Wilson
> Hello,
> I see that from time to time I get in fedora 18 this traffic:
>
> SSDP - Simple Service Discovery Protocol
>
> every 2-3 minutes a couple of frames for address
Thanks, Poma.
I have compiled and installed the code in the URL you have provided.
However, I am still seeing the same issue.
Regards,
j
On Thu, Jun 27, 2013 at 12:04 PM, poma wrote:
> On 27.06.2013 19:59, Jerome Yanga wrote:
> > Here are the info you requested. :)
> >
> > I get these error
On 07/06/2013 01:19 PM, Kevin J. Cummings wrote:
On 07/05/2013 10:26 PM, Roger wrote:
I just now used Fedup to update Fedora 18 to 19. It did it's thing
quickly and efficiently and awaited a reboot.
I have both Ubuntu and Fedora on the hard drive. It boots to the Ubuntu
grub from which I select
Fedup 18 -> 19 went fine for me,
but I noticed a few warnings came up during the process.
Is there any command one could or should run after fedup
to clean up yum records?
[I grep-ped for error in fedup.log but didn't find anything
except RPMs with error/Error in their names.]
--
Timothy Murphy
37 matches
Mail list logo
