Page 2 of 6 FirstFirst 1234 ... LastLast
Results 11 to 20 of 54

Thread: No More Dolphin Root Workaround?

  1. Back To Top    #11
    Newbie
    Join Date
    Jun 2015
    Posts
    8
    Threads
    2
    Local Date
    May 29th 2020
    Local Time
    05:23 AM
    Now it works again. Many thanks. I am so glad for the workaround. The anarchist in me rebels against being told what I can and cannot do on my system.

  2. Back To Top    #12
    Kubuntu Padawan Don B. Cilly's Avatar
    Join Date
    Nov 2012
    Location
    Ibiza, Spain
    Posts
    1,132
    Threads
    57
    Local Date
    May 29th 2020
    Local Time
    05:23 AM
    Quote Originally Posted by claydoh View Post
    Install dbus-x11
    Brilliant Click image for larger version. 

Name:	icon_smile_inchino.gif 
Views:	56 
Size:	260 Bytes 
ID:	8471

  3. Back To Top    #13
    Kubuntu as a Second Language jglen490's Avatar
    Join Date
    Jul 2006
    Location
    Montgomery AL
    Posts
    1,599
    Threads
    53
    Local Date
    May 28th 2020
    Local Time
    10:23 PM
    Quote Originally Posted by BarryHavenga View Post
    Now it works again. Many thanks. I am so glad for the workaround. The anarchist in me rebels against being told what I can and cannot do on my system.
    Tell your anarchist to chill. Good counsel is more useful than bad frustration :doh:

    Oh yeah, I know, I have one inside me, too ;)
    Last edited by jglen490; Dec 5th 2019 at 09:50 PM.
    I feel more like I do now than I did when I got here.
    Home Brew PC: ASRock H110M-HDS R3.0, 120GB+500GB, 16GB RAM
    Kubuntu 18.04.4.LTS Bionic, 5.3.0-53-generic x86_64, Plasma 5.12.9

  4. Back To Top    #14
    Insert Pithy Nothingness here claydoh's Avatar
    Join Date
    Sep 2005
    Location
    Savannah GA
    Posts
    8,222
    Threads
    228
    Local Date
    May 28th 2020
    Local Time
    11:23 PM
    Homepage: Go to claydoh's homepage
    Quote Originally Posted by Don B. Cilly View Post
    Brilliant Click image for larger version. 

Name:	icon_smile_inchino.gif 
Views:	56 
Size:	260 Bytes 
ID:	8471
    Thanks, but I don't feel brilliant, I feel a bit sad, as I have a fairly firm belief that this sort of thing a user needs to figure out on their own, or at least search for it a bit.

    I think half the reason is to nip the bud of the usual tired, old, boring, non-productive , and false-premise rants about bla bla bla my rights blah blah my system blah blah blargity blah forced blahblahblah i demand that they blahblahhblllahh 'I do what I want"

  5. Back To Top    #15
    Ascendant oshunluvr's Avatar
    Join Date
    Feb 2010
    Location
    New Bern, NC USA
    Posts
    10,660
    Threads
    435
    Local Date
    May 28th 2020
    Local Time
    11:23 PM
    Quote Originally Posted by claydoh View Post
    Thanks, but I don't feel brilliant, I feel a bit sad, as I have a fairly firm belief that this sort of thing a user needs to figure out on their own, or at least search for it a bit.

    I think half the reason is to nip the bud of the usual tired, old, boring, non-productive , and false-premise rants about bla bla bla my rights blah blah my system blah blah blargity blah forced blahblahblah i demand that they blahblahhblllahh 'I do what I want"
    There is an interesting moral dilemma here.

    Not referring to anyone specifically including those on this thread; Do I tell a user how to do something that is highly likely to allow them to damage their install beyond repair, so likely so that the developer(s) have taken steps to block or at least obfuscate that ability? Or do I throw all caution to the wind and just dump the info on them, even though they appear to be unable to figure it out themselves? The premise being that if the user is not well enough versed to solve what is a minor problem, are they experienced enough to avoid the obvious pitfalls now open to them? This doesn't rise to the level of "sudo rm -f *" type stuff, but it's in the same ballpark sometimes.

    A simple example is how the *Buntu's do not enable a root password by default. This prevents someone who isn't experienced enough to enable root login themselves unable to stumble into it and wreak havoc. I can say for sure that when I was a noob 20 years ago and pre-buntu, I killed at least three installs this way. Now-a-days if I really need root login (never to the GUI) for something specific I enable the root login log enough to complete the task, then remove the root password to disable root login so I don't do myself in again. However, it's been so long since I needed to do that I can't remember why I did.

    My usual method to gauge my replies to a question that may lead to something potentially dangerous is to glean what I can about the user's abilities, and if I decide to go ahead, caveat strongly but pass on the knowledge. I err on the side of providing the info and let the user be responsible for the outcome. I have even talked users down off of the ledge on more than one occasion.
    Please Read Me
    Be not the first by whom the new are tried, Nor yet the last to lay the old aside. - Alexander Pope, An Essay on Criticism, 1711

  6. Back To Top    #16
    Kubuntu as a Second Language TWPonKubuntu's Avatar
    Join Date
    Nov 2013
    Location
    Western US
    Posts
    1,287
    Threads
    119
    Local Date
    May 28th 2020
    Local Time
    08:23 PM
    I've logged in to the forum again just to respond to the direction this thread has taken.

    1) I'm old enough (contemporary of GregGeek) that my inner anarchist resents being told "you can't get there from here". I started on mainframes when they were all we had.

    2) A simple advisory that "Here be dragons" is all that is necessary.

    3) We ALL learned by making mistakes, even if we kick ourselves in the rear for doing it again.
    -
    4) I know it is a PITA to repeat instructions which are already on the forum. If we don't remember the exact thread containing the answer (very likely at my age), then a simple, polite: "Search this forum for xxxxxx" is easier on the newbie and encourages good skills.It also keeps the blood pressure from spiking.

    Remember, we were all newbies at one time...

    Ok, I have a core dump to analyze and my dot matrix printer needs more paper.Back later.
    If You're Not Paranoid Yet, You Should Be. Kubuntu 20.04 64bit under Kernel 5.6.15, Hp Pavilion, 6MB ram.

  7. Back To Top    #17
    Ascendant GreyGeek's Avatar
    Join Date
    Feb 2009
    Posts
    16,475
    Threads
    1168
    Local Date
    May 28th 2020
    Local Time
    10:23 PM
    Quote Originally Posted by BarryHavenga View Post
    Now it works again. Many thanks. I am so glad for the workaround. The anarchist in me rebels against being told what I can and cannot do on my system.
    Especially on a Linux system. Total user control isn't a goal, it is a requirement.

    Quote Originally Posted by claydoh View Post
    Thanks, but I don't feel brilliant, I feel a bit sad, as I have a fairly firm belief that this sort of thing a user needs to figure out on their own, or at least search for it a bit.

    I think half the reason is to nip the bud of the usual tired, old, boring, non-productive , and false-premise rants about bla bla bla my rights blah blah my system blah blah blargity blah forced blahblahblah i demand that they blahblahhblllahh 'I do what I want"
    Searching for answers to problems on a Linux (or any OS) installation involves two fundamental skills:
    1) the ability to frame the question on DuckDuckGo in such a way that a viable answer may be in the results of the query and
    2) being able to implement the "answer" from the result.
    Most newbs fail, especially those from a Windows environment, fail at both of those skills. They hardly ever do a satisfactory search, even of this forum, and when the get an "answer" they often do not know how to implement it.

    This leads to oshunluver's dilemma:


    Quote Originally Posted by oshunluvr View Post
    There is an interesting moral dilemma here.

    Not referring to anyone specifically including those on this thread; Do I tell a user how to do something that is highly likely to allow them to damage their install beyond repair, so likely so that the developer(s) have taken steps to block or at least obfuscate that ability? Or do I throw all caution to the wind and just dump the info on them, even though they appear to be unable to figure it out themselves? The premise being that if the user is not well enough versed to solve what is a minor problem, are they experienced enough to avoid the obvious pitfalls now open to them? This doesn't rise to the level of "sudo rm -f *" type stuff, but it's in the same ballpark sometimes.

    A simple example is how the *Buntu's do not enable a root password by default. This prevents someone who isn't experienced enough to enable root login themselves unable to stumble into it and wreak havoc. I can say for sure that when I was a noob 20 years ago and pre-buntu, I killed at least three installs this way. Now-a-days if I really need root login (never to the GUI) for something specific I enable the root login log enough to complete the task, then remove the root password to disable root login so I don't do myself in again. However, it's been so long since I needed to do that I can't remember why I did.

    My usual method to gauge my replies to a question that may lead to something potentially dangerous is to glean what I can about the user's abilities, and if I decide to go ahead, caveat strongly but pass on the knowledge. I err on the side of providing the info and let the user be responsible for the outcome. I have even talked users down off of the ledge on more than one occasion.
    Quote Originally Posted by TWPonKubuntu View Post
    I've logged in to the forum again just to respond to the direction this thread has taken.

    1) I'm old enough (contemporary of GregGeek) that my inner anarchist resents being told "you can't get there from here". I started on mainframes when they were all we had.

    2) A simple advisory that "Here be dragons" is all that is necessary.

    3) We ALL learned by making mistakes, even if we kick ourselves in the rear for doing it again.
    -
    4) I know it is a PITA to repeat instructions which are already on the forum. If we don't remember the exact thread containing the answer (very likely at my age), then a simple, polite: "Search this forum for xxxxxx" is easier on the newbie and encourages good skills.It also keeps the blood pressure from spiking.

    Remember, we were all newbies at one time...

    Ok, I have a core dump to analyze and my dot matrix printer needs more paper.Back later.
    On other forums we've witnessed simple question being responded to in an arrogant and dismissive manner with a "Read The Fine Manual". We don't do that here. If we don't give the answer to the question we at least give them a link to an answer. Some newbs are so arrogant themselves in dismissing their own ignorance and/or blaming their problems on Kubuntu, when it is, most of the time, their own attitude, lack of knowledge and their demand that others do their basic work for them. These kinds of visitors are usually ignored because the fault is never theirs and they are never pleased with the answers given, even if the answers are spot on.

    Linux users gain power because of knowledge. For that reason I will not withhold dangerous information from a newb, but will deliver such information with a warning as to the damage abusing that information will cause. Censoring information leads by necessity to a determination of what is dangerous and what is not. What is not dangerous for user A to do may be system suicide for user B. But, if user A asks about something that user C decides is knowledge too dangerous for A to have, if A is like me, A will simply seek answers at another site and never bother to return here again. That would be bad for both us and A.

  8. Back To Top    #18
    Kubuntu as a Second Language TWPonKubuntu's Avatar
    Join Date
    Nov 2013
    Location
    Western US
    Posts
    1,287
    Threads
    119
    Local Date
    May 28th 2020
    Local Time
    08:23 PM
    @GreyGeek, Hear hear!
    If You're Not Paranoid Yet, You Should Be. Kubuntu 20.04 64bit under Kernel 5.6.15, Hp Pavilion, 6MB ram.

  9. Back To Top    #19
    Ascendant GreyGeek's Avatar
    Join Date
    Feb 2009
    Posts
    16,475
    Threads
    1168
    Local Date
    May 28th 2020
    Local Time
    10:23 PM
    Quote Originally Posted by TWPonKubuntu View Post
    @GreyGeek, Hear hear!
    I forgot to add that the newb question I hate the most is the one in which the newb starts a post with demands and ultimatums. I never respond to a newb question that contains that content.

  10. Back To Top    #20
    Insert Pithy Nothingness here claydoh's Avatar
    Join Date
    Sep 2005
    Location
    Savannah GA
    Posts
    8,222
    Threads
    228
    Local Date
    May 28th 2020
    Local Time
    11:23 PM
    Homepage: Go to claydoh's homepage
    Quote Originally Posted by GreyGeek View Post

    Searching for answers to problems on a Linux (or any OS) installation involves two fundamental skills:
    I didn't use a search engine to find the solution in this case, I simply read the error message, and ran the command it explicitly suggested, and the output said :

    Code:
    Command 'dbus-launch' not found, but can be installed with:
    
    sudo apt install dbus-x11
    And Viola! it worked.
    Learning about what this package contains and does could involve web searches, of course

Page 2 of 6 FirstFirst 1234 ... 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
  •