Page 1 of 5 123 ... LastLast
Results 1 to 10 of 42

Thread: 13.1 NOT ready for prime time.

  1. #1

    Default 13.1 NOT ready for prime time.

    I want to post these ideas in the hope that some issues will be addressed and I won't have to start a thread for each of these. If you happen to know a thread that addresses any of these I would like to know and I will assume I'm not the only one.

    bluetooth, where the h is it ?
    USB Device notifier sometimes not working. -Satan?
    /tmp filling up and blocking KDE, WHAT? -Come on rainbow wheel.
    No easy way to dump /tmp from init3. -Threw it on the ground.
    Sound is falling apart. Alsa working, wish to NEVER use it again. It is completely without GUI control. the Mixer is garbage. No tone control. Doesn't connect to JACK. -in a box
    Phonon is a pain and won't connect to JACK.
    USB external sound not optimized right.
    Don't get me started on pulseaudio. That stopped working and I haven't been able to get it going again.
    Kmail dead as dead. dead.
    Wallet is a real pain in the A.

    This stuff worked in 12.2. Or, in the case of wallet and Kmail I was able to just ignore them and live in peace.

    What chance is there of giving full control of sound over to vlc?

    I personally, am terrible at code so I have complete admiration for the heroes who have been working on these projects, but maybe collaboration has been a little scant.

    I don't know what to do except switch distros. Does openSUSE need money?

    Any rate, any thoughts may help my frustration so, don't hesitate to respond.

    Thanks,
    AARON
    11.3 on 3 GHz Phenom X4 with 4GB ram and NVIDIA
    11.3 on HP Pavillion dv2700 laptop 1.9 GHz dual core AMD 2 GB ram
    11.4 6 of 6 on HP Pavilion dv5020 1.9 GHz single core AMD 2 GB ram That was saved from the trash after someone spilled a drink into it.

  2. #2
    Join Date
    Jun 2008
    Location
    UK
    Posts
    5,500

    Default Re: 13.1 NOT ready for prime time.

    How and where did you search for information on those problems?
    Leap 42.3 (ext4, KDE Plasma 5.8.7) ~ stable
    Manjaro (ext4, Xfce) ~ rolling updates
    Tumbleweed (ext4, KDE Plasma5) ~ managed updates via "Tumbleweed Snapshots" service.

  3. #3

    Default Re: 13.1 NOT ready for prime time.

    On 2014-05-14, ConfederacyOfDunces <ConfederacyOfDunces@no-mx.forums.opensuse.org> wrote:
    > Any rate, any thoughts may help my frustration so, don't hesitate to
    > respond.


    It's understandable to rant in Soapbox given your frustrations. However, the answer of how to deal with each of your
    concerns is very simple: head-on. Any GNU/Linux distribution will pepper your installation with some irritations that
    you'd best correct using what I call the JFDI mentality (i.e. Just ********** Do It) and sort it out rather than languish
    or complain. GNU/Linux isn't free so support comes in the form of community help. I recommend you carefully detail each
    of your problems and post each issue as a separate post in the most relevant subforum. Remember to:

    1. Mention exactly which version of openSUSE you have e.g. openSUSE_13.1_x86_64 (KDE).
    2. List all the hardware relevant to each post.
    3. If there's console output - copy-paste the text inside code-tags iconfified by octothorpes (`#') in the forum
    toolbar.

    Good luck!

  4. #4

    Default Re: 13.1 NOT ready for prime time.

    Quote Originally Posted by consused View Post
    How and where did you search for information on those problems?
    Actually, that's a good question.

    In the past I have found relief here.

    In general, I will paste an error message into google and check this forum and Ubuntu and linux questions and others.
    I fought Kmail for waaay too long trying to try different configs and bla bla and reading more about what works and none of it works for me.

    Part is my fault because I get annoyed with the CLI, but just over the last couple days I've been really fighting the sound system and the explanations of the different layers is not well integrated. Not only that, but I feel there are too many layers that just don't seem to want to get along. I'm trying to do some recording. I also want full ability to adjust all of my output. JACK will do all of that, but all of my Pulseaudio won't start.

    I didn't even mention the bucket of cr-- that android threw us into by letting ****** do the USB drivers for our phones.


    ALL OF THIS STUFF WORKED IN 12.2 KDE 64 bit!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    Last edited by hendersj; 14-May-2014 at 16:36.
    11.3 on 3 GHz Phenom X4 with 4GB ram and NVIDIA
    11.3 on HP Pavillion dv2700 laptop 1.9 GHz dual core AMD 2 GB ram
    11.4 6 of 6 on HP Pavilion dv5020 1.9 GHz single core AMD 2 GB ram That was saved from the trash after someone spilled a drink into it.

  5. #5

    Default Re: 13.1 NOT ready for prime time.

    I understand this and have been enjoying, more or less, every upgrade since 11.1. I think.

    But, the feeling I'm getting from this release is that it just wasn't ready.

    This is a lot of threads to punch in and I'm running out of time on this planet.
    11.3 on 3 GHz Phenom X4 with 4GB ram and NVIDIA
    11.3 on HP Pavillion dv2700 laptop 1.9 GHz dual core AMD 2 GB ram
    11.4 6 of 6 on HP Pavilion dv5020 1.9 GHz single core AMD 2 GB ram That was saved from the trash after someone spilled a drink into it.

  6. #6
    Join Date
    Jun 2008
    Location
    UK
    Posts
    5,500

    Default Re: 13.1 NOT ready for prime time.

    Quote Originally Posted by ConfederacyOfDunces View Post
    In general, I will paste an error message into google and check this forum and Ubuntu and linux questions and others.
    That's all good, but often error messages are too general or from a process that is too deep to be understandable by a user. If that doesn't help, I usually use a few keywords on google search (as few as possible). I often leave out "openSUSE" to cast the net wider, and usually put linux as the first.

    I fought Kmail for waaay too long trying to try different configs and bla bla and reading more about what works and none of it works for me.
    Yes, to much unrewarded loyalty in this case. I gave up on kmail when the KDE developers followed up a working version with one that was really buggy, although it had spent much time in the "beauty parlour". That really was style over substance! Then it probably fell foul of the semantic desktop, or akonadi or whatever. I ditched it for Thunderbird which had the added benefit of being cross-platform, and never looked back.

    Part is my fault because I get annoyed with the CLI
    Why is that your fault(?) It's mainly productive for those who use it a lot, such as [real-world] system administrators, system engineers. If it was easy, the GUI wouldn't have evolved as a productivity aid, which empowered the non-technical users in work and at home.

    just over the last couple days I've been really fighting the sound system and the explanations of the different layers is not well integrated. Not only that, but I feel there are too many layers that just don't seem to want to get along. I'm trying to do some recording. I also want full ability to adjust all of my output. JACK will do all of that, but all of my Pulseaudio won't start.
    The linux sound documentation is appalling. It's written by system engineers, who can't see the forest for the trees. It wasn't that easy on Windows 95 and it helped if one had some experience as a sound engineer (BTW I don't). As far as the applications go, Linux has just about caught up with that era. However now there are two sound servers to complicate matters.

    JACK for professional level audio (very low latency), and PulseAudio (low enough latency for simple everyday audio), where the two servers do not cohabit well unless they each use a different sound device, i.e. separate sound cards/chips. The simple answer is to have one or the other - not both.

    If you must have both, and share the same sound card, you must suspend P/A in order to use JACK, but on 13.1 I found that shutting down JACK doesn't cleanly activate P/A. Welcome to frustration and the CLI, in order to kill P/A, check its status and restart it.

    Are you also trying to use Rosegarden, by any chance?

    ALL OF THIS STUFF WORKED IN 12.2 KDE 64 bit!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    See, no need to SHOUT! I have some sympathy for you since I recently abandoned 12.2 KDE 64bit where it was working just fine - but not at the beginning of 12.2 necessarily. It had to go for security reasons and its partial implementation of systemd which eventually started to exhibit a little instability on my system.
    Leap 42.3 (ext4, KDE Plasma 5.8.7) ~ stable
    Manjaro (ext4, Xfce) ~ rolling updates
    Tumbleweed (ext4, KDE Plasma5) ~ managed updates via "Tumbleweed Snapshots" service.

  7. #7
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: 13.1 NOT ready for prime time.

    On 2014-05-14 13:16, ConfederacyOfDunces wrote:

    > But, the feeling I'm getting from this release is that it just wasn't
    > ready.


    Well, everything I use works in 13.1 for me, almost perfectly :-)

    You will simply have to ask on each issue, separately.

    --
    Cheers / Saludos,

    Carlos E. R.

    (from 13.1 x86_64 "Bottle" (Minas Tirith))

  8. #8
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,317

    Default Re: 13.1 NOT ready for prime time.

    On Wed, 14 May 2014 11:16:10 +0000, ConfederacyOfDunces wrote:

    > I understand this and have been enjoying, more or less, every upgrade
    > since 11.1. I think.
    >
    > But, the feeling I'm getting from this release is that it just wasn't
    > ready.


    There are plenty of people, though, who would disagree with you. I've
    been using 13.1 since release, and have found it to be one of the best
    releases in recent history.

    Does it have problems? Sure - that's the nature of software as complex
    as a full operating system.

    > This is a lot of threads to punch in and I'm running out of time on this
    > planet.


    Well, we all are.

    But in order to get /help/, you need to detail your problems in the
    proper place and outline what you've done to try to resolve them.

    Just posting a rant isn't going to get you help. For example, posting:

    "bluetooth, where the h is it?" isn't a problem statement. Bluetooth
    works fine here on both of my laptops running 13.1. I use it
    occasionally and generally it just works.

    So to help you with that problem, you'd need to post in an appropriate
    forum with details about your setup and what exactly you're seeing.

    Yes, it takes time. But if you're not willing to take the time to
    provide the people who can help you with the information they need in
    order to help you, what exactly do you expect anyone to be able to do to
    help you?

    With life in general, you get out of it what you're willing to put into
    it.

    Jim

    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  9. #9
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    17,317

    Default Re: 13.1 NOT ready for prime time.

    On Wed, 14 May 2014 11:06:02 +0000, ConfederacyOfDunces wrote:

    > I didn't even mention the bucket of cr-- that android threw us into by
    > letting ****** do the USB drivers for our phones.


    We'll also remind you to watch your language in these forums. Please
    refer to the forum rules (linked in my signature) and be sure you're
    following them.

    Jim
    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  10. #10

    Default Re: 13.1 NOT ready for prime time.

    Quote Originally Posted by consused View Post
    If you must have both, and share the same sound card, you must suspend P/A in order to use JACK, but on 13.1 I found that shutting down JACK doesn't cleanly activate P/A. Welcome to frustration and the CLI, in order to kill P/A, check its status and restart it.

    Are you also trying to use Rosegarden, by any chance?


    ALL OF THIS STUFF WORKED IN 12.2 KDE 64 bit!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!


    See, no need to SHOUT! I have some sympathy for you since I recently abandoned 12.2 KDE 64bit where it was working just fine - but not at the beginning of 12.2 necessarily. It had to go for security reasons and its partial implementation of systemd which eventually started to exhibit a little instability on my system.

    I know, I know. And I really do love the living daylights out of you all. You have come through for me many times in the past. I love the distro. I have tried many. Starting with Mandrake and fighting the WinModem debacle. And eventually losing....

    .....then openSUSE 11 came along and I was finally able to leave all the hellishness behind. Through the years I have solved, with your help, cases like the BCMess, and the wierd ATInstability, the getting NVidisassociation to finally write a driver, many others. Bravo, because I know you are working like crazy over there and the results are really phenomenal. I really do appreciate it, but sometimes I get a little cranky.

    It's funny because I started running into these snags the day after I got all sanctimonious with a salesman at BstBuy about how 13.1 was so easy to install and it was all just working. WELL, I CAN NEVER GO TO THAT STORE AGAIN. Just kidding. I'll still go, but I'll wear one of those disguises; with the glasses. and nose and. mustache; all integrated into one do-all disguise system. That guy will never figure out that it was I, the one who sent him down Dante's dark path.

    13.1 Uh oh, (bad luck)x1/10. Of course we need to skip all the 13 versions and go straight to 14.1. hope it's not too late.

    I will put up a thread to see about the possibility of someone who may be interested in a recording plugin for VLC with a cool layout with bezier connects like the blender composite editor. In which category would that be the most effective?
    11.3 on 3 GHz Phenom X4 with 4GB ram and NVIDIA
    11.3 on HP Pavillion dv2700 laptop 1.9 GHz dual core AMD 2 GB ram
    11.4 6 of 6 on HP Pavilion dv5020 1.9 GHz single core AMD 2 GB ram That was saved from the trash after someone spilled a drink into it.

Page 1 of 5 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •