WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Core v6.0rc1  (Read 14491 times)

Offline jls

  • Hero Member
  • *****
  • Posts: 2133
Re: Core v6.0rc1
« Reply #30 on: December 19, 2014, 02:03:36 AM »
the build scripts for pidgin are in https://code.google.com/p/tc-ext-tools/
dCore user

Offline a

  • WikiUser
  • *
  • Posts: 15
Re: Core v6.0rc1
« Reply #31 on: December 19, 2014, 08:46:59 PM »
VLC does not start. It says, libiconv.so.2 cannot be opened: No such file.

Offline a

  • WikiUser
  • *
  • Posts: 15
Re: Core v6.0rc1
« Reply #32 on: December 20, 2014, 03:44:16 AM »
mpg123 does not work, saying that it is unable to load any output module, although I installed alsa prior to mpg123's installation, which used to work in TC 5.x and 4.x.

Offline a

  • WikiUser
  • *
  • Posts: 15
Re: Core v6.0rc1
« Reply #33 on: December 20, 2014, 04:36:58 AM »
Sound in the browser also doesn't work. Tested YouTube with minefield21.tcz. Again, used to work in TC 5.x.

Offline pq5190362

  • Sr. Member
  • ****
  • Posts: 286
Re: Core v6.0rc1
« Reply #34 on: December 20, 2014, 01:31:41 PM »
Hello,

Hello,

Why is the graphics stack in the 32-bit repo so much older than in the 64-bit repo?

The x86_64 Xorg was updated for various gnome stuff - there is no gnome wm in the x86 repo...

thanks for your reply.

And what about those who would need an updated graphics stack for, let's say, support of new GPUs / bugfixes / new features / better performance?

Would those not count as valid reasons to update the graphics stack?

Any chance you could still update the graphics stack in the 32-bit repo for the reasons mentioned above?

Regards

here is another reason to update:

http://www.phoronix.com/scan.php?page=news_item&px=MTg2OTc

Regards

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Core v6.0rc1
« Reply #35 on: December 20, 2014, 10:15:00 PM »
Sound in the browser also doesn't work. Tested YouTube with minefield21.tcz. Again, used to work in TC 5.x.
I'm not having any problem with firefox-official, flash and alsa  combined.  you shouldn't need it but I like to use pavucontrol to set audio output devices and volume control.    I like to listen to Pandora all day and tc6 works great for that.   I'd give that combination a shot

bel

  • Guest
Re: Core v6.0rc1
« Reply #36 on: December 21, 2014, 07:06:37 AM »
Those with sound problems might try adding alsa-config.tcz onboot; that made sound work for me in 6.0rc1 but I didn't need it in 5.x.

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11094
Re: Core v6.0rc1
« Reply #37 on: December 22, 2014, 04:35:20 AM »
mpg123 does not work, saying that it is unable to load any output module, although I installed alsa prior to mpg123's installation, which used to work in TC 5.x and 4.x.

..works for me - it seems to default to pulseaudio, so for anything else you have to put (for example) "-o alsa"

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11094
Re: Core v6.0rc1
« Reply #38 on: December 22, 2014, 04:36:05 AM »
VLC does not start. It says, libiconv.so.2 cannot be opened: No such file.

thanks - pm sent to the maintainer

Offline coreplayer2

  • Hero Member
  • *****
  • Posts: 3020
Re: Core v6.0rc1
« Reply #39 on: December 22, 2014, 06:25:49 AM »
I noticed that Xvesa now supports 1920x1200 resolution OOB   which is really nice thanks



with Ctr + Alt + Backspace   >  xsetup > startx
« Last Edit: December 22, 2014, 06:34:10 AM by coreplayer2 »

Offline rufi

  • WikiUser
  • *
  • Posts: 7
Re: Core v6.0rc1
« Reply #40 on: December 23, 2014, 06:23:13 AM »
Installed qemu-x86 on v6.0rc1, when run qemu-system-i386 get an error:
Quote
qemu-system-i386: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory

Look like a bug, v6.0 beta doesn't have this issue.

Offline a

  • WikiUser
  • *
  • Posts: 15
Re: Core v6.0rc1
« Reply #41 on: December 23, 2014, 04:32:53 PM »
The mirrorpicker was also adjusted to avoid failing on fast servers.

Not exactly sure what was fixed there, but since another thing hit me again, I'd like to suggest that the "Apps" program (and the "tce" command line program) be made more robust against failures of (repo.)tinycorelinux.net. Yesterday wasn't the first time that the server couldn't be reached, and when that happens, a freshly started CorePlus cannot fetch extensions from any mirror, since "Select fastest mirror" fails, if the first mirror "repo.tinycorelinux.net" somehow behaves weird, and a different mirror also cannot be selected manually, since "Select mirror" also fails, because it requires "mirrors.tcz", which cannot be fetched for the reasons mentioned.

Using "wget" and "cat" to simulate a poor man's text browser to find links on web pages to a "mirrors.tcz" that could then be manually copied to /tmp/tce/optional, from where it could be loaded to stop the pain, felt seriously stupid. Maybe "mirrors.tcz" should not be an extension but just part of base. The "links" web browser would also have felt better than the wget-and-cat pain.
« Last Edit: December 23, 2014, 04:35:37 PM by a »

Offline gerald_clark

  • TinyCore Moderator
  • Hero Member
  • *****
  • Posts: 4254
Re: Core v6.0rc1
« Reply #42 on: December 23, 2014, 06:04:50 PM »
Mirrors come and go, so it cannot be part of base.
You can manually edit /opt/tcemirror

Offline Juanito

  • Administrator
  • Hero Member
  • *****
  • Posts: 11094
Re: Core v6.0rc1
« Reply #43 on: December 23, 2014, 11:22:00 PM »
Look like a bug, v6.0 beta doesn't have this issue.

Although they do need to be fixed, extensions are not part of the base - nothing much changed in the base between v6.0beta1 and v6.0rc1, so I would presume that something changed in one or more of the extensions concerned.

Offline rufi

  • WikiUser
  • *
  • Posts: 7
Re: Core v6.0rc1
« Reply #44 on: December 23, 2014, 11:52:00 PM »
Although they do need to be fixed, extensions are not part of the base - nothing much changed in the base between v6.0beta1 and v6.0rc1, so I would presume that something changed in one or more of the extensions concerned.
[/quote]

I compared the installed extensions, no difference found.