January 2012

[opensuse-kde3] Libreoffice open/save dialog kde3 style
by Istvan Gabor 14 Feb '12

14 Feb '12

Hello: I have installed libreoffice-kde3 package on my openSUSE 12.1/KDE3 system hoping that it sets LibreOffice open/save dialog to my KDE3 style. But the open/save window looks like this: http://i44.tinypic.com/121e6iw.jpg instead of what I expected (and have in oS 11.2): http://i39.tinypic.com/2vjofwz.jpg How could I have this style in oS 12.1? I have Libreoffice packages from openSUSE OSS repo and KDE3 packages from KDE3 build service repo. Thanks, Istvan -- To unsubscribe, e-… [View More]

3 7

[opensuse-kde3] knetworkmanager
by Ilya Chernykh 13 Feb '12

13 Feb '12

knetworkmanager should now work with wi-fi. I have just connected my laptop to wlan with knetworkmanager-kde3. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org

3 7

Re: [opensuse-kde3] kpowersave is Greyed out as normal user??
by David C. Rankin 12 Feb '12

12 Feb '12

On 08/26/2011 07:26 PM, Larry Stotler wrote: > Hey David, did we ever get a fix for the powersave issue? I just > added 11.4/KDE3 to my laptop and the lack of the power meter is a pain > as you mentioned...... > > Debating going back to 11.0 and giving up on newer versions.......11.0 > still does everthing i need. Althought 11.4 does seems to use > slightly less RAM > > Larry, Never did. Honestly, I haven't checked in a while. I'm on my 11.4/kde3 laptop right … [View More]now - still no kpowersave battery icon in the tray. Clicking on kmenu -> System -> Desktop -> kpowersave launches and restores the icon to systray. The "battery meter" is working, but looks like it needs to configure itself again to know the proper time left. I think that will happen automatically during the first batter cycle. I needed to configure kpowersave to start on login again. Configure kpowersave -> General Settings -> Miscellaneous -> Autostart [X] KPowersave starts automatically on login. Looks like Ilya worked a bit more magic and got it working again. Great job Ilya. I don't know if this is the old kpowersave or if this is upower with the kpowersave interface on it -- can you fill us in Ilya? Regardless, it seems to be working again. HTH Larry. > > > > On Wed, Apr 6, 2011 at 6:45 PM, David C. Rankin > <drankinatty(a)suddenlinkmail.com> wrote: >> On 04/06/2011 12:36 PM, Robert Xu wrote: >>> >>> On Wed, Apr 6, 2011 at 11:37, David C. Rankin >>> <drankinatty(a)suddenlinkmail.com> wrote: >>>> >>>> On 04/06/2011 08:55 AM, Larry Stotler wrote: >>>>> >>>>> On Tue, Apr 5, 2011 at 10:43 PM, David C. Rankin >>>>> <drankinatty(a)suddenlinkmail.com> wrote: >>>>>> >>>>>> Bummer :( >>>>>> >>>>>> How will I know if my laptop battery is about to run out? >>>>> >>>>> Can you do: >>>>> >>>>> cat /proc/acpi/battery/BAT#/* >>>>> >>>>> ? Replace # with 0 or 1. >>>>> >>>>> That's how I keep an eye on my battery on my old Thinkpad because it >>>>> reports incorrectly, so it tries to shutdown with 50% power so I have >>>>> to kill powersaved to keep using it. >>>>> >>>>> I open a small terminal and use watch with the above command. >>>> >>>> Thanks Larry, >>>> >>>> That will work in the interim until we get a fix in Trinity. Robert, you >>>> know anything about this in Trinity? >>> >>> Yes, hence the move to upower upcoming as soon as cmake is done. >>> >>> >> >> You da man... :p >> >> -- >> David C. Rankin, J.D.,P.E. >> -- >> To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org >> For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org >> >> > -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-kde3+help(a)opensuse.org [View Less]

4 6

[opensuse-kde3] New packages
by Ilya Chernykh 31 Jan '12

31 Jan '12

The following packages has been added to KDE:KDE3 repository recently: kde3-ksmoothdock cheesetracker-qt3 kde3-kannasaver -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org

1 0

[opensuse-kde3] New kdm screen for kde3 - give it a look and give me your thoughts, likes & not-likes
by David C. Rankin 30 Jan '12

30 Jan '12

Guys, I did a kdm login screen for kde3 this past week to match a fairly cool desktop image I have been using. the main image is a background of lights from office buildings reflecting on water which has been manipulated so that the background is only the reflection on water which projects colors off the water surface (looks great - at least IMHO) The elements are from the Peace login by the login graphics are mine. The session and system icons shown are from the iceglass theme. All and all, … [View More]

1 0

[opensuse-kde3] KDE3 and sftp protocol in oS12.x
by Istvan Gabor 30 Jan '12

30 Jan '12

Hello: In openSUSE 11.2 sftp protocol is working in KDE3 applications. But in oS 11.4 and 12.4 it gives and error message, something like "an error occurred while talking to ssh" (I can't remember the exact message). I know that this is a known issue in KDE3. See eg: http://lists.opensuse.org/opensuse-kde3/2011-03/msg00087.html As I use sftp in KDE3 krusader extensively I am wondering when will this issue be fixed? Or is there a plan at all to fix this problem? I tried other sftp clients (… [View More]

2 1

[opensuse-kde3] QString::QString(QString const&) () from /usr/lib/qt3/lib64/libqt-mt.so.3 - gcc 4.5?
by David C. Rankin 30 Jan '12

30 Jan '12

Ilya, all I've seen some Qt3 crashes lately. The latest was in kalazium. I have seen a few others and I wonder if we are not having an issue with Qt3 sneaking in. The 11.4 builds have been superb with very few problems. I think this is a problem with the new gcc and Qt3. IIRC, from Trinity, when there were objects defined as (for example): QString::QString(QString const&) () The newer gcc would cause errors. If I recall, it required a syntax change removing the first class reference '… [View More]QString::' in order to be compatible with gcc 4.5+. I don't know if this is the issue here, but it looks similar. To reproduce this crash, just open kalazium and pick, for example, Ti (titanium), then choose "Spectrum" and finally choose "Export Spectrum as Image", you will then get the crash on the 'save'. The full crash I got was: System configuration startup check disabled. [Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007fa2fe72d540 in QString::QString(QString const&) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #6 0x00000000004203c2 in ?? () #7 0x000000000042065c in ?? () #8 0x0000000000416d54 in ?? () #9 0x00007fa2fe4d7b84 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #10 0x00007fa2fe4d7c6c in QObject::activate_signal(int) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #11 0x00007fa2fe503a48 in QWidget::event(QEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #12 0x00007fa2fe485185 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #13 0x00007fa2fe4854c8 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #14 0x00007fa2fef7e4fe in KApplication::notify (this=0x7fff0e5bcb40, receiver=0xc91bf0, event=0x7fff0e5bc4e0) at kdecore/kapplication.cpp:552 #15 0x00007fa2fe430d66 in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #16 0x00007fa2fe42fb91 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #17 0x00007fa2fe43ebb2 in QEventLoop::processEvents(unsigned int) () from /usr/lib/qt3/lib64/libqt-mt.so.3 #18 0x00007fa2fe496bf1 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #19 0x00007fa2fe496b42 in QEventLoop::exec() () from /usr/lib/qt3/lib64/libqt-mt.so.3 #20 0x0000000000441ba2 in ?? () #21 0x00007fa2fd8b0bfd in __libc_start_main () from /lib64/libc.so.6 #22 0x00000000004162a9 in ?? () #23 0x00007fff0e5bcdc8 in ?? () #24 0x000000000000001c in ?? () #25 0x0000000000000007 in ?? () #26 0x00007fff0e5be54d in ?? () #27 0x00007fff0e5be555 in ?? () #28 0x00007fff0e5be55e in ?? () #29 0x00007fff0e5be566 in ?? () #30 0x00007fff0e5be56c in ?? () #31 0x00007fff0e5be574 in ?? () #32 0x00007fff0e5be57e in ?? () #33 0x0000000000000000 in ?? () Let me know if anyone else has seen anything similar with segfaults and the QString::QString(QString const&) () type reference causing it. Also, if you have any more information or need anything else, please let me know and I'll be happy to help. (Thanks again Ilya!) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org [View Less]

1 0

[opensuse-kde3] KJobViewer lies
by Felix Miata 24 Jan '12

24 Jan '12

With all openSUSE versions after 11.2 I've had nothing but trouble with my Canon MF4370dn IP connected printer. New proprietary drivers have come out several times since I bought it, including last week, but it's hard to say whether they've truly been any part of the problem or any solution. Today after many hours (starting between 14:00 & 15:00 -0500) with updating drivers, zypper updates, adding/deleting printers and printer settings and FF profiles and Konq settings and deleting … [View More]various *cups*/* from /var and starting all over, even rebooting into 11.2 and rebooting 11.4 multiple times, I cannot figure out what is and isn't going on, but the latest discovery is that apparently KJobViewer when told to delete jobs only deletes them from the viewer, not from the system. With a fresh installation of the printer in YaST2, usually printing a test page will succeed. When it does, printing a local plain text file from FF 3.6.24 and FF 9.0.1 will succeed as well. But, if I try to print a web page with FF, the job never finishes. Sometimes, the printer will data error. Other times, it simply gets awakened, then goes back to sleep. When I check KJobViewer after nothing prints, there's always something there, usually "processing". After deleting whatever is there, I can goto YaST2 to try another test page, and YaST2 will report pending jobs exist, both before and after telling it to delete them, printing the page, then clicking the success button, though at the latter step it's not entirely clear whether pending jobs exist, since the deleta all pending jobs button is not inactivated. Once I've exited YaST2 Printer, I can again print from FF, but only plain text files, not web pages, whether local or not, again getting printer data errors instead. I tried a sample web page (my bank's recent transactions list, which is what started the trouble again today, saved to disk) with Konq, but instead of printing, Konq dumps the job off to Gimp, where I get totally lost what I'm supposed to do. I can take a screenshot of the transactions page, open that image in Gwenview, and Gwenview prints the image just fine. Obviously there are multiple problems here, but it would be a big help if KJobViewer would actually delete the jobs it claims to delete. At least I can print text in many fewer steps that way. FF on WinXP prints fine, as long as I first remember to reset the power on the Canon after Linux print attempts have confounded it. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-kde3+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-kde3+owner(a)opensuse.org [View Less]

1 0

[opensuse-kde3] 12.1 and kde3
by kanenas 18 Jan '12

18 Jan '12

It took a while, but everything i want out of my 'puters is being delivered by suse 12.1/kde3, that of course being " ALMOST everything," there is just one thing remaining: The only issue is that kde3 somehow fails to recognize my digital camera, a fuji 500esr; the camerta can be seen in gnome and kde4, but *not* in kde3. my ancient olympus *is* visible.(Olympus has a std mini usb plug, fuji has a micro-usb plug if that means anything). The maddening thing is that virtualbox windoze vms … [View More]

5 11

[opensuse-kde3] Seems some macros are broken in Factory
by Ilya Chernykh 17 Jan '12

17 Jan '12

For example, this line leads to fail of packages in Factory: %{?suse_update_config:%{suse_update_config -f}} also the %configure macro is broken: it tries to patch the configure file for 64-bit library paths but incorrectly. For example it changes the Qt3 directory on 64-architecture from /usr/lib to /user/lib64 which is incorrect (Qt3 directory is always /usr/lib with libraries go to either /usr/lib/qt3/lib or /usr/lib/qt3/lib64). Please correct the macros. -- To unsubscribe, e-mail: … [View More]

1 0

Main

Development

Information

Community

Social Media

Other

openSUSE KDE 3