I don't hurry up with upgrading but I wonder which is the preferred way for upgrading in place: do-release-upgrade or muon on KDE? Which method is more reliable?
-
-
Use the terminal and sudo apt-get update && sudo apt-get distupgrade && sudo do-release-upgradeUsing Kubuntu Linux since March 23, 2007
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
-
ya ,,,exept for the typoOriginally posted by Snowhog View PostVINNYCode:sudo apt-get update && sudo apt-get dist-upgrade && sudo do-release-upgrade
i7 4core HT 8MB L3 2.9GHz
16GB RAM
Nvidia GTX 860M 4GB RAM 1152 cuda cores
Comment
-
Ok so i have a question this thread does this go any faster than the moun update ?
and with my system show here might i be better to wait for Hardware upgrades ?
let me knowCode:mike@LinuxBear:~$ sudo lshw linuxbear description: Computer product: 775Dual-VSTA vendor: TEMPLATE version: 1.00 serial: 00000000 width: 32 bits capabilities: smbios-2.3 dmi-2.3 smp-1.4 smp configuration: cpus=1 uuid=00020003-0004-0005-0006-000700080009 *-core description: Motherboard product: 775Dual-VSTA physical id: 0 version: 1.00 serial: 00000000 *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 0 version: P1.90 date: 09/14/2006 size: 64KiB capacity: 448KiB capabilities: pci upgrade shadowing cdboot bootselect socketedrom edd int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9keyboard int14serial int17printer int10video acpi usb agp ls120boot zipboot biosbootspecification *-cpu description: CPU product: Intel(R) Pentium(R) 4 CPU 2.80GHz vendor: Intel Corp. physical id: 3 bus info: cpu@0 version: 15.4.1 serial: 0000-0F41-0000-0000-0000-0000 slot: CPUSocket size: 2800MHz capacity: 2800MHz width: 64 bits clock: 200MHz capabilities: boot fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx x86-64 constant_tsc pebs bts pni dtes64 monitor ds_cpl cid cx16 xtpr configuration: id=0 *-cache:0 description: L1 cache physical id: 4 slot: L1-Cache size: 16KiB capacity: 16KiB capabilities: internal write-back data *-cache:1 description: L2 cache physical id: 5 slot: L2-Cache size: 1MiB capacity: 1MiB capabilities: internal write-back unified *-logicalcpu:0 description: Logical CPU physical id: 0.1 width: 64 bits capabilities: logical *-logicalcpu:1 description: Logical CPU physical id: 0.2 width: 64 bits capabilities: logical *-memory description: System memory physical id: 2 size: 1506MiB *-pci:0 description: Host bridge product: PT880 Ultra/PT894 Host Bridge vendor: VIA Technologies, Inc. physical id: 100 bus info: pci@0000:00:00.0 version: 00 width: 32 bits clock: 33MHz configuration: driver=agpgart-via latency=8 resources: irq:0 memory:f8000000-fbffffff *-generic UNCLAIMED description: PIC product: PT894 I/O APIC Interrupt Controller vendor: VIA Technologies, Inc. physical id: 0.5 bus info: pci@0000:00:00.5 version: 00 width: 32 bits clock: 33MHz capabilities: io_x_-apic bus_master configuration: latency=0 *-pci:0 description: PCI bridge product: VT8237/VX700 PCI Bridge vendor: VIA Technologies, Inc. physical id: 1 bus info: pci@0000:00:01.0 version: 00 width: 32 bits clock: 66MHz capabilities: pci pm normal_decode bus_master cap_list resources: memory:fc700000-fc7fffff *-pci:1 description: PCI bridge product: PT890 PCI to PCI Bridge Controller vendor: VIA Technologies, Inc. physical id: 2 bus info: pci@0000:00:02.0 version: 00 width: 32 bits clock: 33MHz capabilities: pci pciexpress pm msi normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:64 ioport:c000(size=4096) memory:fc800000-fe9fffff memory:bbf00000-dfefffff *-display description: VGA compatible controller product: GT218 [GeForce 210] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:02:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress vga_controller bus_master cap_list rom configuration: driver=nvidia latency=0 resources: irq:24 memory:fd000000-fdffffff memory:c0000000-cfffffff memory:dc000000-ddffffff ioport:cc00(size=128) memory:fe980000-fe9fffff *-multimedia description: Audio device product: High Definition Audio Controller vendor: NVIDIA Corporation physical id: 0.1 bus info: pci@0000:02:00.1 version: a1 width: 32 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:25 memory:fe97c000-fe97ffff *-ide:0 description: IDE interface product: VT8237A SATA 2-Port Controller vendor: VIA Technologies, Inc. physical id: f bus info: pci@0000:00:0f.0 logical name: scsi0 version: 80 width: 32 bits clock: 33MHz capabilities: ide pm bus_master cap_list emulated configuration: driver=sata_via latency=32 resources: irq:21 ioport:e000(size=8) ioport:dc00(size=4) ioport:d880(size=8) ioport:d800(size=4) ioport:d480(size=16) ioport:d000(size=256) *-disk description: ATA Disk product: ST3500418AS vendor: Seagate physical id: 0.0.0 bus info: scsi@0:0.0.0 logical name: /dev/sda version: CC44 serial: 9VMCK3EP size: 465GiB (500GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 signature=000c3494 *-volume:0 description: EXT3 volume vendor: Linux physical id: 1 bus info: scsi@0:0.0.0,1 logical name: /dev/sda1 version: 1.0 serial: a989dc84-3240-4898-be70-1e48f2afa8ef size: 248GiB capacity: 248GiB capabilities: primary bootable journaled extended_attributes large_files ext3 ext2 initialized configuration: created=2012-11-10 23:57:46 filesystem=ext3 modified=2014-07-23 06:51:50 mounted=2014-07-20 07:58:55 state=clean *-volume:1 description: Linux swap volume physical id: 2 bus info: scsi@0:0.0.0,2 logical name: /dev/sda2 version: 1 serial: aff52255-a317-4fd9-8abb-f6b560af0c20 size: 2070MiB capacity: 2070MiB capabilities: primary nofs swap initialized configuration: filesystem=swap pagesize=4096 *-volume:2 description: Extended partition physical id: 3 bus info: scsi@0:0.0.0,3 logical name: /dev/sda3 size: 215GiB capacity: 215GiB capabilities: primary extended partitioned partitioned:extended *-logicalvolume description: Linux filesystem partition physical id: 5 logical name: /dev/sda5 logical name: / capacity: 215GiB configuration: mount.fstype=ext3 mount.options=rw,relatime,errors=remount-ro,user_xattr,acl,barrier=1,data=ordered state=mounted *-ide:1 description: IDE interface product: VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE vendor: VIA Technologies, Inc. physical id: f.1 bus info: pci@0000:00:0f.1 logical name: scsi2 version: 07 width: 32 bits clock: 33MHz capabilities: ide pm bus_master cap_list emulated configuration: driver=pata_via latency=32 resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) ioport:376 ioport:fc00(size=16) *-cdrom description: DVD reader product: CB-5216A vendor: ASUS physical id: 0.1.0 bus info: scsi@2:0.1.0 logical name: /dev/cdrom logical name: /dev/cdrw logical name: /dev/dvd logical name: /dev/sr0 version: 1.13 capabilities: removable audio cd-r cd-rw dvd configuration: ansiversion=5 status=nodisc *-usb:0 description: USB controller product: VT82xxxxx UHCI USB 1.1 Controller vendor: VIA Technologies, Inc. physical id: 10 bus info: pci@0000:00:10.0 version: a0 width: 32 bits clock: 33MHz capabilities: pm uhci bus_master cap_list configuration: driver=uhci_hcd latency=32 resources: irq:20 ioport:e080(size=32) *-usb:1 description: USB controller product: VT82xxxxx UHCI USB 1.1 Controller vendor: VIA Technologies, Inc. physical id: 10.1 bus info: pci@0000:00:10.1 version: a0 width: 32 bits clock: 33MHz capabilities: pm uhci bus_master cap_list configuration: driver=uhci_hcd latency=32 resources: irq:22 ioport:e400(size=32) *-usb:2 description: USB controller product: VT82xxxxx UHCI USB 1.1 Controller vendor: VIA Technologies, Inc. physical id: 10.2 bus info: pci@0000:00:10.2 version: a0 width: 32 bits clock: 33MHz capabilities: pm uhci bus_master cap_list configuration: driver=uhci_hcd latency=32 resources: irq:21 ioport:e480(size=32) *-usb:3 description: USB controller product: VT82xxxxx UHCI USB 1.1 Controller vendor: VIA Technologies, Inc. physical id: 10.3 bus info: pci@0000:00:10.3 version: a0 width: 32 bits clock: 33MHz capabilities: pm uhci bus_master cap_list configuration: driver=uhci_hcd latency=32 resources: irq:23 ioport:ec00(size=32) *-usb:4 description: USB controller product: USB 2.0 vendor: VIA Technologies, Inc. physical id: 10.4 bus info: pci@0000:00:10.4 version: 86 width: 32 bits clock: 33MHz capabilities: pm ehci bus_master cap_list configuration: driver=ehci_hcd latency=32 resources: irq:21 memory:febff800-febff8ff *-isa description: ISA bridge product: VT8237A PCI to ISA Bridge vendor: VIA Technologies, Inc. physical id: 11 bus info: pci@0000:00:11.0 version: 00 width: 32 bits clock: 33MHz capabilities: isa pm cap_list configuration: latency=0 *-network description: Ethernet interface product: VT6102 [Rhine-II] vendor: VIA Technologies, Inc. physical id: 12 bus info: pci@0000:00:12.0 logical name: eth0 version: 7c serial: 00:13:8f:ed:3b:a7 size: 100Mbit/s capacity: 100Mbit/s width: 32 bits clock: 33MHz capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=via-rhine driverversion=1.5.1 duplex=full ip=192.168.2.2 latency=32 link=yes maxlatency=8 mingnt=3 multicast=yes port=MII speed=100Mbit/s resources: irq:23 ioport:e800(size=256) memory:febffc00-febffcff *-pci:1 description: Host bridge product: PT894 Host Bridge vendor: VIA Technologies, Inc. physical id: 101 bus info: pci@0000:00:00.1 version: 00 width: 32 bits clock: 33MHz *-pci:2 description: Host bridge product: PT894 Host Bridge vendor: VIA Technologies, Inc. physical id: 102 bus info: pci@0000:00:00.2 version: 00 width: 32 bits clock: 33MHz *-pci:3 description: Host bridge product: PT890 Host Bridge vendor: VIA Technologies, Inc. physical id: 103 bus info: pci@0000:00:00.3 version: 00 width: 32 bits clock: 33MHz *-pci:4 description: Host bridge product: PT894 Host Bridge vendor: VIA Technologies, Inc. physical id: 104 bus info: pci@0000:00:00.4 version: 00 width: 32 bits clock: 33MHz *-pci:5 description: Host bridge product: PT894 Host Bridge vendor: VIA Technologies, Inc. physical id: 105 bus info: pci@0000:00:00.7 version: 00 width: 32 bits clock: 33MHz *-pci:6 description: Host bridge product: VT8237/8251 Ultra VLINK Controller vendor: VIA Technologies, Inc. physical id: 106 bus info: pci@0000:00:11.7 version: 00 width: 32 bits clock: 33MHz configuration: latency=32 *-pci:7 description: Host bridge product: VT8237A Host Bridge vendor: VIA Technologies, Inc. physical id: 107 bus info: pci@0000:00:13.0 version: 00 width: 32 bits clock: 33MHz *-multimedia description: Audio device product: VT8237A/VT8251 HDA Controller vendor: VIA Technologies, Inc. physical id: 1 bus info: pci@0000:80:01.0 version: 10 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=snd_hda_intel latency=0 resources: irq:17 memory:feafc000-feafffffLast edited by SteveRiley; Aug 29, 2014, 05:42 PM.Comment
-
O.K., I'll bite. Why? Faster? Easier? More control? More reliability? Or just plain geekiness? *<{;o)Originally posted by Snowhog View PostThe next brick house on the left
Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.24.7 | Kubuntu 22.04.4 | 6.5.0-28-generic
Comment
-
More reliable. My advice is also to avoid Muon, I've had it botch an upgrade before. I haven't ever had a problem with the terminal way, and I've done quite a few upgrades for friends and family.Comment
-
Make sure you have a wireless connection. Last week I upgraded a laptop from Precise to Trusty online using the commands Snowhog listed. The update involved replace 950+ apps (IIRC), which was about 1.5+ gb (again, IIRC). Once the download was done the unpacking, installing and configuration took place. When it was all done , over 2 hours later (again IIRC) I rebooted and Trusty came up without problems. One advantage is that the b43 firmware that Precise had worked well to automatically bring up the BCM4011 wireless. (Before the Kubuntu upgrade I had added an additional 1GB of RAM to the Gateway m675prr laptop. It runs nicely and is looking for a good home."A nation that is afraid to let its people judge the truth and falsehood in an open market is a nation that is afraid of its people.”
– John F. Kennedy, February 26, 1962.Comment
-
O.K., so for the sake of argument, that would mean that Muon does not use the same logic as the command line scripts. It would also mean that the last 4 or 5 upgrades that I did via GUI, were either lucky, flukey, or otherwise unusual yet they worked.Originally posted by Feathers McGraw View Post
Now this (14.04.1) release did not go well. It ran to completion, including an ending reboot with left me with a proper, working system. i was able to install packages, verify the untouched presence and completeness of /home and on a separate hard drive /home/<name>/Multimedia. The only problem I had was when I manually selected to Reboot from the Leave menu on the kicker. Twice it resulted in a kernel panic. Still researching, but since almost no one else has reported this upon upgrade, there is something else going on.
I'll give it another try - perhaps 14.04.2 - but later on.The next brick house on the left
Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.24.7 | Kubuntu 22.04.4 | 6.5.0-28-generic
Comment
-
-
Yeah, it does call dpkg or at least appears to, but in doing some researchnow that I'm curioius, it's described as beingbuilt on the QApt library. So I think there is something else going on - maybe something still isn't being called correctly. More research!!The next brick house on the left
Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.24.7 | Kubuntu 22.04.4 | 6.5.0-28-generic
Comment
-
It appears that QApt ultimately resolves on dpkg to do the actual installation work, at least based on this fleeing reference in the code:
https://projects.kde.org/projects/ex...llprogress.cppComment
-
Agree. And so apt and dpkg are both used for their relative strengths, which makes sense for the fetching, unpacking, and installing of all the packages needed for an upgrade. So in my opinion, there's probably no actual difference between processing with Muon (GUI) or apt (commandline). In the experience I just had with using Muon to upgrade to 14.04.1 there's probably an incorrect (not faulty) package or application of a package - after all it is an old Dell
)
For the next try, I'll use the commandlineThe next brick house on the left
Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.24.7 | Kubuntu 22.04.4 | 6.5.0-28-generic
Comment
-
dpkg does the work, but does only what it's told to. APT ensures dependency resolutions are satisfied. QApt is a Qt wrapper for APT's APIs and presents an abstraction layer that Muon uses.
The challenge we face with graphical package managers is that they hide the complexity of package management. At the command line, the various APT utilites reveal so much more information, and therefore it becomes easier to detect -- and resolve -- problems.Comment
-
Thanks, SteveRiley. I remember fighting and resolving dependencies manually, and with early package managers such as RPM. So, hopefully, those who program the graphical utilities like Muon will become better at capturing and presenting critical events to help the user out.
I appreciate the discussion in this thread, and all the participants.The next brick house on the left
Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.24.7 | Kubuntu 22.04.4 | 6.5.0-28-generic
Comment
-
Well, finally resolved my upgrade problem. I assembled a new computer, moved the hard drives over to the new PC, stuck the 14.04.1 DVD in the new DVD combo drive, mashed the "go" button, and watched the magic ensue. At the end, I had a new Trusty installation with all my stuff still at /home, most of my applications upgraded, and the system just humming along like nothing happened. I snatched the packages I needed to complete the scene, and all is good.
Signature updated.The next brick house on the left
Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.24.7 | Kubuntu 22.04.4 | 6.5.0-28-generic
Comment
Comment