Jérôme Desquilbet | 21 Apr 16:38 2014

MenuLibre in 14.04

Hi!
I can't manage to change the main menu entries with MenuLibre.
(xubuntu-14.04-desktop-amd64)
MenuLibre shows all the menu directories and menu entries, and a lot of 
menu entries are not dispayed in the main menu. I can't find in the 
documentation how to modify the main menu from MenuLibre.
I guess I am missing something obvious...
TIA for any help,
   Jérôme.

--

-- 
xubuntu-users mailing list
xubuntu-users@...
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/xubuntu-users

Ignious Drake | 21 Apr 04:12 2014
Picon

inkscape 0.48.4

I am trying to install inkscape 0.48.4 which is supposed to be in the repository but all I can get is  inkscape 0.48.3.1-1ubuntu1.1.
 I have tried installing the trunk branches but they won't load, giving me an 'internal error' on launch. I have the correct ppa, I think. Xubuntu 12.04 64bit. Any idea? Thanks!
<div><div dir="ltr">I am trying to install&nbsp;inkscape 0.48.4 which is supposed to be in the repository but all I can get is&nbsp;&nbsp;inkscape 0.48.3.1-1ubuntu1.1.<div>&nbsp;I have tried installing the trunk branches but they won't load, giving me an 'internal error' on launch. I have the correct ppa, I think. Xubuntu 12.04 64bit. Any idea? Thanks!</div>
</div></div>
Peter Flynn | 21 Apr 00:30 2014
Picon

13.10 to 14.04 nearly went smoothly

I upgraded one of my sacrificial machines yesterday, an old Dell 
Optiplex used as a spare print server and experimental client workstation.

The upgrade went smoothly until it hit a subdirectory of Emacs where I 
had carelessly left a soft-linked a file from my personal store of 
stuff, instead of copying it. That gagged the Emacs24 deferred 
post-installer byte-compilation, which brought the entire installation 
grinding to a halt with dire warnings that if I rebooted I risked having 
an incomplete system.

In fact I had been monitoring it, so I knew how far it had got. I 
deleted the offending file and rebooted, and everything came up clean 
except for re-running the byte-compilations and then removing all the 
no-longer-needed packages from apt.

Where would be the right place to report the error? That application 
byte-compilation should fail gracefully and pass on to the next 
operation, rather than crashing a system update. It's not really an 
Emacs problem, in that there's nothing wrong with the binary; but I 
don't know whereabouts in the Xubuntu tree responsibility for the 
post-installation stuff lives.

///Peter

810d4rk | 19 Apr 20:55 2014
Picon

Xubuntu 14.04 32 bits doesn’t boot by usb

I used unetbootin and ubuntu usb creation tool and it doesn’t work, thought the 64 bit iso works fine

--
Thanks
<div><div dir="ltr">I used unetbootin and ubuntu usb creation tool and it doesn&rsquo;t work, thought the 64 bit iso works fine<br clear="all"><div>
<br>-- <br>Thanks<br>
</div>
</div></div>
Fred Roller | 20 Apr 02:12 2014
Picon

Upgrade for GP...FYI stuff

I did the upgrade through updater, just for GP, resulting in a complete 
crash.  I have and Aspire 7520 with dual AMD K8 Athlon64 processors, 4 
Gb RAM, Nvidia GeForce 7000M, and Broadcom BCM4311 (not factory), and a 
second monitor attached to the laptop.  2x 500 Gb hdd (sda1 = / , sda2 = 
/tmp , sda3 = swap , sda4 = /Isolibrary (data), sdb1 = /Crypt (data).

I usually just do a fresh install so I thought I would give the update a 
spin for reporting purposes.  Generally updates go smooth but this one 
went south in a blink.  I made it through downloads and a good deal into 
installation when the laptop primary screen went black and the second 
screen was filled with alternating carrot and ampersand (^ <at> ^ <at> ^ <at> ^ <at> ^ <at> ^ <at>  
etc. etc.).  Caps lock was flashing which typically has been a kernel 
panic.  System was non-responsive.

Installing 14.04 using "Something else"  from a Unetbootin built 
thumbdrive worked as advertised until reboot then I confirmed kernel 
panic, at least in the build scenario.  I get at boot, sequence number 
was consistant in every attempt at 1.6 ish :
[  1.610263] Kernel panic - not syncing: No init found. Try passing 
init= option to kernel.

Final solution was to dd the iso to a thumbdrive and build as usual and 
here I am.  There is nothing to solve here, just did it for testing.  My 
system is from 2007 but has plenty of juice left.  I have had kernel 
panics in the past derived from trying to load the bcm additional 
drivers for the broadcom.  My wifi has to be activated via

sudo apt-get install linux-firmware-nonfree

So if 14.04 tried to load those drivers then it would explain the 
crashes.  I did see what looked like bcm activity during the thumbdrive 
installation processes so was thinking this may be the culprit.

Willing to answer questions or post bug if necessary.

Fred

Gary Charvat | 19 Apr 16:59 2014
Picon

Re: upgrade to 14.04???

I've been notified by the software updater that the new version, 14.04, 
is available.  Can my system be upgraded to via the updater, or do I 
have to go another procedure.  Please advise...

Regards,
Gary

--

-- 
<<<<>>>>

Gary P. Charvat

50 Greystone
Shelton, CT  06484

(203) 929-9187

eMail:  g.charvat@...

<<<<>>>>

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com

Steve | 19 Apr 16:09 2014
Picon

Upgrade

For anyone out there who may be wondering why the your update manager 
may not be giving you the option of upgrading right now, Upgrading to 
the new LTS release is not supported until the first point release(that 
would be 14.04.1). You can still do it from the command line with
  sudo do-release-upgrade -d

Just found this out myself.

Phil | 19 Apr 12:44 2014

Grub problems

Thank you for reading this.

I managed to install 14.04 from the mini.iso but the boot loader was 
installed on the USB stick instead of the internal drive. The internal 
drive is SDB and the USB stick is SDA. During the installation process 
the boot loader is installed on SDA and I don't recall that a choice as 
given.

Anyway, I attempted to install grub on the internal drive and now when 
the system boots I'm left with a command line prompt like this "grub>". 
Entering "boot" returns an error message something like "you need to 
load the kernel first".

Boot-repair looks like the answer but I don't have a working CD drive 
which is why I had to mess around with a USB stick in the first place.

It's been a long day, can anyone offer any help?

--

-- 
Regards,
Phil

Phil | 19 Apr 09:53 2014

Installation from mini.iso not booting

Thank you for reading this.

The installation process using the mini.iso went like clockwork. The 
problem is the the system won't boot. The only activity is a blank 
screen with a blinking cursor in the top left hand corner.

Has anyone moved beyond this point?

--

-- 
Regards,
Phil

Phil | 19 Apr 09:21 2014

mini.iso - Solved

Problem solved using Unetbootin and the mini.iso file.

--

-- 
Regards,
Phil

Phil | 19 Apr 06:30 2014

mini.iso corrupt?

Hello,

I've spent the better part of a day trying to upgrade Xubuntu. The 
upgrade failed initially because I needed another 459 MB of disk space. 
So I deleted /tmp to gain more space but then the menu was missing after 
rebooting and logging in.

So then I downloaded the mini.iso file and, using dd, copied it to a USB 
stick. Still no joy. A message flashes up saying, I think, "isolinux.bin 
missing or corrupt". It's not missing so it must be faulty in some way.

Has anyone succeeded with the 32 bit mini.iso?

--

-- 
Regards,
Phil


Gmane