Announcement

Collapse
No announcement yet.

Problems with a HD, video card and Adept Manager

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Problems with a HD, video card and Adept Manager

    Hi, first time linux user so please be kind

    Anyway, first the important stuff

    Asus A7N8X-X mobo (nForce3 chipset) with Athlon64 3000+, 1 GB of Ram
    nVidia GeForce 6600GT display adapter (connected to a Acer AL1914 monitor and a TV via svideo)
    a 30 GB WDC Ide drive (NTFS win2k)
    an 80 GB WDC ide drive (home to kubuntu 8.04.1 live-cd installation)
    a 160 GB ST sata drive (NTFS for data)
    a 300 GB Maxtor ide drive (NTFS for data)

    ...and a bunch of miscallanious other devices. Since I'm very, very new to kubuntu I don't yet know what else works and what doesn't. I'll add to the list as issues arise.

    And now, onto the problems

    A) I can't access my maxtor in dolphin. The 300gig drive is formatted as NTFS and shows under Disk Managment in win2k as two partitions (128,00 GB and 151,48 GB) but is accessible as a single G: drive in explorer (and where ever...). I can access both of my other NTFS hd's in dolphin (though I at first need to type in my passwd, kinda irritating). However, what can I do to be able to access the Maxtor? It's home to all of my media.

    EDIT: regarding the irritating bit, it says something like "system policy prevents mounting internal media" and then asks for the passwd. Any help here?

    B) From the moment I turn on my computer, I can see what's happening on my TV as well, but after I'm logged in, it's all black. I'd like to be able to view my media on the TV (mostly video clips) but ATM this isn't happening. I like how in win2k VLC takes over the video output signal and automatically scales it to fit my TV, is this possible in kubuntu? I'd guess so, but I don't know how to tweak my settings yet. Any help here? From what I've read, envyng-qt should do the trick, right? But this brings me to my third problem.


    C) I used Adept Manager to install the "kubuntu-restricted-extras", but due to stupid user error, I failed to notice that I needed to scroll the screen down to find the "I accept" checkbox with java and instead just clicked next twice in a row. It gave an error message, which I though I saved to my desktop but can't find there (still very unfamiliar with how to access files, though Dolphin seems simple enough).

    Now, whenever I activate Adept manager I get an error message saying "Database locked - Another process is using the packaging system database (probably some other Adept application or apt-get or aptitude).
    Would you like to attempt to resolve this problem? No will enter read-only mode and Cancel to quit and resolve this issue yourself." If I click no, it opens up and I can browse and locate files, like before mentioned envyng-qt and I can even check the "request install", but after that everything but "preview changes" is grey and unaccessible.

    EDIT:Okay, being dense as I am, I compleatly failed to type in the report I get if I click "OK" on the error message. Here's what it says:

    "Short description - The application Adept Installer (adept_installer) crashed and caused signal 6 (SIGBRT).

    What is this? - An application terminates with a SIGBRT signal when it detects an internal onconsistency caused by a bug in the program.

    What can I do? - You might want to send a bug report for this application. Check if it is listed on http://bugs.kde.org, otherwise mail the author. Please include as much information as possible, maybe the original documents. If you have a way to reproduce the error, include this also"

    Now since this quite appearently is my own fubar, I don't think a bug report is nessesary. Or is it? Is this a real bug?? Here is what is found in the "Backtrace" window in The KDE Crash Handler:

    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [Thread debugging using libthread_db enabled]
    [New Thread 0xb65ae6c0 (LWP 8267)]
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    (no debugging symbols found)
    [KCrash handler]
    #6 0xb7f4b410 in __kernel_vsyscall ()
    #7 0xb74b7085 in raise () from /lib/tls/i686/cmov/libc.so.6
    #8 0xb74b8a01 in abort () from /lib/tls/i686/cmov/libc.so.6
    #9 0xb76c7480 in __gnu_cxx::__verbose_terminate_handler ()
    from /usr/lib/libstdc++.so.6
    #10 0xb76c4d05 in ?? () from /usr/lib/libstdc++.so.6
    #11 0xb76c4d42 in std::terminate () from /usr/lib/libstdc++.so.6
    #12 0xb76c4e6a in __cxa_throw () from /usr/lib/libstdc++.so.6
    #13 0x0810e796 in ?? ()
    #14 0x0810eb9a in ?? ()
    #15 0x0810f405 in ?? ()
    #16 0x0810f4e5 in ?? ()
    #17 0x0810cedd in ?? ()
    #18 0x0816254e in ?? ()
    #19 0x0809d3d0 in ?? ()
    #20 0x08075845 in ?? ()
    #21 0x08077b7a in ?? ()
    #22 0xb6a9c704 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
    #23 0xb6e2baba in QSignal::signal () from /usr/lib/libqt-mt.so.3
    #24 0xb6abb7b2 in QSignal::activate () from /usr/lib/libqt-mt.so.3
    #25 0xb6ac3936 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
    #26 0xb6a30c36 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
    #27 0xb6a32a5f in QApplication::notify () from /usr/lib/libqt-mt.so.3
    #28 0xb7136672 in KApplication::notify () from /usr/lib/libkdecore.so.4
    #29 0xb69c128d in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
    #30 0xb6a23b19 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
    #31 0xb69d664b in QEventLoop:rocessEvents () from /usr/lib/libqt-mt.so.3
    #32 0xb6a4bf90 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
    #33 0xb6a4bc8e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
    #34 0xb6a327df in QApplication::exec () from /usr/lib/libqt-mt.so.3
    #35 0x08072665 in ?? ()
    #36 0xb74a2450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
    #37 0x080723b1 in ?? ()


    I do belive this is something I clearly messed up myself, but I can't imagine it's anything that can't be fixed. I just haven't got the faintest idea how so any help would be much appreciated.

    Thanks in advance


    -ankara halla


    Tags: None
    • Top
    • Bottom
    #2
    Re: Problems with a HD, video card and Adept Manager

    I cannot help you with your HD or your video card, but as to the adept problem, you might try to open a console and type sudo dpkg --configure -a.
    • Top
    • Bottom

    Comment

      #3
      Re: Problems with a HD, video card and Adept Manager

      First off welcome to the party.

      As mentioned above run this in a terminal:
      Code:
      sudo dpkg --configure -a.
      Code:
      sudo apt-get clean
      Code:
      sudo apt-get autoclean
      then do:
      Code:
      sudo apt-get update
      Code:
      sudo apt-get upgrade
      Code:
      sudo apt-get install kubuntu-restricted-extras
      You can copy / paste all of the above into the terminal.

      I hope this points you in the right direction.

      As for your HD problem could you post your /etc/fstab file?

      Open up dolphin.
      Navigate to base folder and open /etc then find fstab (text file) and open that with kate (text editor)

      It may give us insight in the way your system is treating partitions / drives.

      I would also suggest posting a separate thread for that.

      I can't help you much on that.
      HP Pavilion dv6 core i7 (Main)
      4 GB Ram
      Kubuntu 18.10
      • Top
      • Bottom

      Comment

        #4
        Re: Problems with a HD, video card and Adept Manager

        Okay, thanks for the replies.
        I'll be helping my missus move house this evening, but I'll give those a try tomorrow and will post the results.

        Thanks again for the help!
        • Top
        • Bottom

        Comment

          #5
          Re: Problems with a HD, video card and Adept Manager

          Originally posted by Fintan
          First off welcome to the party.

          As mentioned above run this in a terminal:
          Code:
          sudo dpkg --configure -a.
          Code:
          sudo apt-get clean
          Code:
          sudo apt-get autoclean
          then do:
          Code:
          sudo apt-get update
          Code:
          sudo apt-get upgrade
          Code:
          sudo apt-get install kubuntu-restricted-extras
          You can copy / paste all of the above into the terminal.

          I hope this points you in the right direction.

          As for your HD problem could you post your /etc/fstab file?

          Open up dolphin.
          Navigate to base folder and open /etc then find fstab (text file) and open that with kate (text editor)

          It may give us insight in the way your system is treating partitions / drives.

          I would also suggest posting a separate thread for that.

          I can't help you much on that.
          Okey, I got to try this today afterall and the terminal seemed to work like a charm. At least I think I got everything fixed. I'll keep reading and studying more to get a grip with everything that goes on in there, but thank you very much for helping me out here.

          Also, as you suggested I created a new thread here

          EDIT: Regarding the video card, I managed to install envyng and on the first screen it has three options for nvidia drivers, two for install and one for uninstall. Now I know I haven't installed any drivers thru envy, but I do recall installing *some* drivers when prompted to do so in the very first boot up of kubuntu (among all the other updates).

          Now, should I uninstall my current drivers and should I do it thru envy or by some other means (konsole?). If by other means, what would be the best or correct way?
          Then again, would it be cool to just install new drivers thru envy?
          • Top
          • Bottom

          Comment

          Previous template Next
          Working...
          X