|
2005-10-21 20:44
|
scribus131_ubuntu.png (101,165 bytes) |
|
2005-10-21 20:45
|
scribus131_and_gimp_on_ubuntu.png (110,039 bytes) |
|
|
Sounds like an Ubuntu bug to me. |
|
|
hi malex, I've just tested your new breezy package from debian.tagancha.org (20051011), the issue is still unsolved |
|
|
I would make a suggestion to install qtconfig if it not installed and change the themes around to see if it changes the widget issue. We have had issues with Fedora Bluecurve and it was a broken theme. |
|
|
I've seen this a week ago and it doesn't look like Ubuntu bug, because just 1.3.1 (no CVS) works just fine. I will compile new anoncvs and give it a shot now. |
|
|
I've updated to the latest breezy package on debian.scribus.net (1.3.1+cvs2005-1) and made some more tests: 1. The missing widget issue is still there, even worse, scribus crashes with sig#11 on launch. maciej@pan:~$ LANG=en_EN scribus Scribus Crash ------------- Scribus crashes due to Signal 0000011 Calling Emergency Save Naruszenie ochrony pamieci (memory violation?) 2. I played around with many other Gnome themes (Human, Crux, Simple, etc.) -- it doesn't infuence this odd behaviour. 3. I installed qtconfig, changed the default font to Verdana 10pt and played with it's GUI Styles (Motif, Plantinum, Windows) -- no change apart that the polish fonts displayed correctly in Scribus GUI (see the issue 2751, font size remains still much to large) -- still no window widgets and a crash. BTW, if qtconfig is needed to correctly set up Scribus, shouldn't it be added to the deb package dependencies? Alex, do you test your breezy packages on a stock breezy distro (default environment after a new installation) or on a patched one? My Breezy is a fresh installation out of the box. I wanted to write a howto for Linux (but not DTP) newbies about setting Scribus on Ubuntu Breezy, but I'm rather stuck right now. |
|
|
i found chatting with Andy Fitz late last night that on his Ubuntu setup it seemed that even though kde was installed, Qt was not picking up the extra style plugins from KDE. So he could not enable Plastik for Scribus. I even walked him through adding the extra style lib directories in qtconfig. One though on this bug: Can you create a test user and login then load scribus ? It could be something with qt resources getting messed up. |
|
|
<quoting>One though on this bug: Can you create a test user and login then load scribus ? It could be something with qt resources getting messed up</quoting> Peter, I created the new test user, logged in and launched scribus, and it did help indeed -- the widgets are now in place :) Any ideas, how to make it work for the default user from start on? |
|
|
I am confirming that there is no problem either with Scribus, my breezy scribus-cvs package, or the stock Ubuntu install. I just finished installing Ubuntu Breezy in a qemu image. I installed Gnome and scribus-cvs and didn't have any problems with widgets. As your experience with creating another user shows it is something in your custom settings that creates this problem. I am glad it's not on my side or the Scribus side, or even Ubuntu side as it makes it easier :) |
|
|
Maciej, I'm about to close this issue as it's not a bug on our side. Do you have any other comments to add? I am not sure which one of your settings causes this as I run Gnome on my Debian system and in Ubuntu/breezy under qemu and it is fine. |
|
|
try renaming .qt in your home directory This does not solve the issue of why it is not correct in the first place, but at least removes Scribus from the issue. |
|
|
Alex, please don't close as long as we are not really sure what is it about. Have you installed qtconfig-qt3 before Scribus installation? Scribus worked for the other user after previous qtconfig installation -- is qtconfig needed by Scribus on Ubuntu/Gnome or not? If yes, would you mind adding it to the dependencies? As I see it, we need it anyway to properly set the GUI font for Scribus on Gnome. BTW, my "custom settings that creates this problem" were default settings after first install, Scribus was one of the first packages I installed, so expect more users like me. |
|
2005-10-27 06:41
|
|
|
|
I think, I know now what has happened. I renamed my .scribus directory (see the attached file) in my home directory to .scribus_old and launched scribus once again: everything worked fine:) I renamed it back to .scribus, and the odd behaviour was there again. Steps to reproduce: 1. I first installed the scribus 1.23 breezy package from Alex' repository, to see if it works. 2. It worked, so I deinstalled it again and installed the breezy 1.3.1+cvs package. 3. Launched Scribus > odd behaviour + crashes You could alternatively take my .scribus directory and see what happens on your system. |
|
|
Maciej, This is the problem line you had in your ~/.scribus/scribus13.rc file: <MAINWINDOW WIDTH="32767" HEIGHT="32767" YPOS="23" XPOS="5" /> once those numbers are changed to something sensible like 800, 600, 100, 300 Scribus started up just fine. I will close this bug after I try to persuade Craig or somebody else to implement some sort of boundary check for the window parameters. This is important since such behavior keeps coming up regularly on the IRC and the ML. |
|
|
malex: I committed some sanitychecks for windowpos in 1.3.2cvs prefsmanager.cpp. Can you test if this solves the problem for Ubuntu? |
|
|
I've tested last night's build (2005-11-29) on Ubuntu breezy and it started just fine with Maciej's scribus13.rc file. The only message produced at the console was: "QComboBox::changeItem: (LY) Index 0 out of range. I think avox resolved this bug. When I closed Scribus and looked at the scribus13.rc files I found out that <MAINWINDOW WIDTH="1024" HEIGHT="768" YPOS="26" XPOS="5" /> was appropriate and aparently set by avox's function. Maciej, please test and respond here if you still find something. Otherwise I'll close the bug. |
|
|
I've just tested it, all is fine now. So we've finally reached the point, when it's time to say: thank you Malex and Avox for solving this initially not so obvious bug :) |
|
|
Thanks to Avox, we beat this one. |
- Anonymous
