PCLinuxOS KDE 64bit RC1

[TNTman]

Thank you.
The output of you guys is prodigious.

I installed KDE_Desktop_64bit to a desktop from a USB stick on SDA to a spare
partition, used it for 10 days. No problems.

Now have installed KDE_Desktop_64bit from same stick to SDB a cleaned and
formated SATA 3 SSDisk SDB Journalised FS: ext4.
On the first try  Use Entire
Disk but it installed to free space on SDA. Not SDB as expected.
Gave that method a second try, same result.

Next try selected SDB from the drop down menu then select Custom Disk.
All OK, good install only took minutes.
All up and running no errors

[BMaytum]

Apologies for posting here, seems I'm not allowed to post a "Reply" in the appropriate thread stated by the OP.

I got a KDE Crash Reporting Assistant popup upon first LiveCD boot into PCLOS x64 RC1 (I haven't installed it yet, doing a test drive U C?). I "installed" dbg pkg as per the KDE CRA, even so CRA said I was missing some files needed to produce a useful report (and the missing files weren't found by Synaptic (but again, I didn't add the "testing" area to my Repo spec.

Anyway, here's the report I did get:

Code: [Select]

Application: kded4 ($Id$)
KDE Platform Version: 4.9.5
Qt Version: 4.8.4
Operating System: Linux 3.2.18-pclos2.bfs x86_64
Distribution: "PCLinuxOS"

-- Information about the crash:
<In detail, tell us what you were doing  when the application crashed.>

-- Backtrace:
Application: KDE Daemon (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0x00007fa891cd61f5 in raise () from /lib64/libc.so.6
#7  0x00007fa891cd7986 in abort () from /lib64/libc.so.6
#8  0x00007fa891ccea65 in __assert_fail () from /lib64/libc.so.6
#9  0x00007fa8738f56e0 in snd_hctl_handle_events () from /usr/lib64/libasound.so.2
#10 0x00007fa873900939 in snd_mixer_handle_events () from /usr/lib64/libasound.so.2
#11 0x00007fa873bc5c5d in ?? () from /union/usr/lib64/kde4/kded_kmixd.so
#12 0x00007fa873bbdc8a in ?? () from /union/usr/lib64/kde4/kded_kmixd.so
#13 0x00007fa893abad36 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#14 0x00007fa892bf5a54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#15 0x00007fa892bfa5df in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007fa894b00fb6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#17 0x00007fa893aa5fac in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007fa893aa95d8 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#19 0x00007fa893ad5383 in ?? () from /usr/lib64/libQtCore.so.4
#20 0x00007fa88e2e090a in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fa88e2e0cc8 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007fa88e2e0d84 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007fa893ad551f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007fa892c9b90e in ?? () from /usr/lib64/libQtGui.so.4
#25 0x00007fa893aa4d22 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007fa893aa4fdd in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007fa893aa9a7b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#28 0x00007fa87c972497 in kdemain () from /union/usr/lib64/libkdeinit4_kded4.so
#29 0x0000000000406c3c in _start ()

Report to https://bugs.kde.org/
Apologies if this condition was reported and solved earlier in this 9-page thread.

PC Control Center > Hardware all looks fine to me, only thing is the (default) resolution doesn't match my actual 1080p x 1920 HDMI monitor [guess I can specify that pre-boot).  Even though the KDE CRA popped up, the desktop so far is working fine (I didn't reboot), obviously I used FireFox 18.x to get here.

Regards,
Bruce

[gseaman]

today's updates/additions to our 64bit repo include:
- ntfs-3g (updated to 2013.1.13)
- geeqie (updated to 1.1; added gps and lirc), new in 64bit
- kraft (updated to 0.50), new in 64bit
- kile (updated to 2.1.3), 32bit working; 64bit version was broken, now fixed but still requires recompiling/updating tetex, will see what can be done about that...  

-p.

texlive is updated tetex.

Galen

[macemm]

yes to galen: that is right, the discussions about tetex or texlive are over.

to pinoc: textex has been deprecated for a very long time - please, please do not bring it back.

When you have a good sleep and rise refreshed from your labours you will see the merit in texlive.

thanks.

[JohnW_57]

 

Hopefully  there's no complains then!
Texlive is a 200 MB +...... stuff!

JohnW

[gseaman]

The size of texlive is a packaging problem. It is an extension of the same code, I believe. Other distros have it broken out into smaller packages.

Galen

[kalwisti]

yes to galen: that is right, the discussions about tetex or texlive are over.

to pinoc: textex has been deprecated for a very long time - please, please do not bring it back.

When you have a good sleep and rise refreshed from your labours you will see the merit in texlive.

I'd just like to add that teTeX was officially declared obsolete in March 2007 (although Thomas Esser had stopped supporting it even earlier). The announcement is here:

http://www.mail-archive.com/ctan-ann@dante.de/msg01091.html

TeX Live (TL) is the recommended replacement for teTeX, and I believe that almost everyone has switched over to it -- except for Windows users who prefer the MiKTeX distribution (http://www.miktex.org/about).

I hope it's OK for me to make a suggestion (it is certainly not intended as criticism). I've installed TeX Live independently (from an .iso image) for several years now and haven't run into any problems or system instability. But I've noticed that most of the popular front-end LaTeX editors, i.e., Kile, Texmaker, TeXworks and even AUCTeX, are packaged in such a way that they all include TL dependencies. I have not been able to successfully compile those programs from source, so that limits my choice of editors to TeXstudio and/or Geany.

Would it be possible to package the aforementioned editors "independently", so that they don't pull in any TL dependencies? (I don't think this would pose a big problem from the user perspective because I think most people installing a LaTeX editor are savvy enough to know that they must have an underlying TeX distribution installed for the editor to work). 

I realize that, due to its size and complexity, packaging TeX Live is a major task and I'm grateful to everyone who's willing to undertake such a job.

Thanks,
=david

[allen9013]

February 16, 2013
I have been waiting for the PClos 64 bit system for a long time and am delighted with it with one exception --
and that is my failure to find a way to install my printer -- an HP 4000. It's an old workhorse, but I have
been able to properly install and use it in the latest 32 bit version -- the 2012.08. The printer is working well via a
parallel port card that the 32 bit system quickly found and utilized.

In the 64 bit RC1, the hplip-hpijs and hplip files are both installed in RC1 but when I go to the "Configuration Center"
it fails to locate the printer. Use of the "self help troubleshooting system" does not produce any results whatsoever.
I need to be able to print, so use of this fast RC1, a very nice system I would prefer to use, just won't cut it for me
until this "problem" is overcome. It may be a simple fix, but unfortunately, it seems to be beyond my ability.

Can anyone assist me or is there something missing in the OS that has been overlooked or is something else scheduled
for inclusion in a future update? I would be most appreciative for any assistance or info anyone can offer.

allen9013

Allen Webb, Richmond VA

[johnmart]

Hey Allen9013,
Yeah, I too love the 64bit. Sorry I can't help you with your printer problem.  If nobody chimes in for you, I suggest you start your own thread in the Desktop Hardware section to get more attention.
Welcome, & see you around.
john

[DeBaas]

Google cups parport
So many questions so many answers
Sorry I don't have a direct solution

[pinoc]

today's updates/fixes/upgrades/additions to come soon to our 32/64bit repo include:
- mplayer/mencoder (thanks to Daniel & ghostbunny)
- ffmpeg, amarok (thanks to ghostbunny)
- 64bit: dtsdec, linphone, gstreamer-plugins-bad, avidemux, pulseaudio3 (incl. fixed paprefs)
- 64bit: fixed GoogleEarth disappearing desktop-file  and updated duplicity to latest version 0.6.21

- Firefox 19 and latest Thunderbird 17.0.3 + languages

and YES, I will take a break soon.  
-p.

[agmg]

Come on, pinoc, we all know your secret...

In your place, each day has 40 hours, that is how you manage it  

[deathromantik]

Could we please have a 64 bit support section on the forum?
I am also having my own issue with WINE: http://www.pclinuxos.com/forum/index.php/topic,113435.0.html

[littlenoodles]

Is this system bootable directly through UEFI?  Not talking about 'secure boot'.  Just that I think recent 64-bit linux kernels can be booted directly without having to run grub.  I have the rEFInd boot loader installed on my machine, and it is able to locate and boot the linuxmint 64-bit kernel that's installed there.  32-bit Mageia (and I assume PCLOS) need to be booted via the EFI grub loader (which I was able to get linuxmint, with much difficulty and confusion, to install).  But direct booting through rEFInd would be even nicer.

In any case, is PCLOS EFI-ready these days?

[indiolinux]

Excellent!...
PCLOS : The best KDE distro. Now 64 

PCLOS >>> kubuntu >>> opensuse kde etc.