From: Manuela H. <ma...@ma...> - 2011-06-13 22:27:11
|
Hey there, I just installed Rosegarden (11.06) on Ubuntu 11.04 today and gave it a shot. At some point it behaved weirdly, got rendering issues, which I "solved" by closing each single window/view, and finally killing the whole program. Unfortunately, I didn't pay too close attention to what I did, really. Anyway, now when I start Rosegarden, I get rendering problems with the main window. It's simply not drawn, as if the program had frozen. I know that it's there though (and not frozen), because by hovering certain invisible elements I can get their tooltips. I can also access the preferences or open other views just fine (e.g. by double-clicking an invisible spot). I tried re-installing rosegarden, installing the previous version (10.10 I believe), but I get the same behavior. I suspect that rosegarden still has a settings folder somewhere that didn't get deleted/recreated that might cause this behavior. (I can see in the preferences that some other settings are still set the way I set them on first run). I can't seem to find where Rosegarden saves its preferences though. The 'rosegarden' folder in my home directory doesn't seem to be it. Any ideas? Thanks, Manuela PS: here's what the console output has to say: Setting graphics system for Qt 4.5+ to: raster Thorn - false System Locale: en_US Qt translations path: /usr/share/qt4/translations Qt translations not loaded. RG Translation: trying to load :locale/en_US RG Translations loaded successfully. Loaded application icon "rg-rwb-rose3-16x16" Loaded application icon "rg-rwb-rose3-32x32" Loaded application icon "rg-rwb-rose3-48x48" Loaded application icon "rg-rwb-rose3-64x64" Loaded application icon "rg-rwb-rose3-128x128" NOTE: Found stylesheet at ":/rosegarden.qss", applying it Not loading stylesheet per user request. Caveat emptor. QSettings::endGroup: No matching beginGroup() AlsaDriver::AlsaDriver [begin] Rosegarden 10.10 - AlsaDriver [ALSA library version 1.0.23, module version 1.0.23, kernel version 2.6.38-8-generic] PluginFactory::instance(dssi): creating new DSSIPluginFactory LADSPAPluginFactory::discoverPlugins - discovering plugins; path is [/home/manu/.dssi] [/usr/local/lib/dssi] [/usr/lib/dssi] Cannot lock down memory area (Cannot allocate memory) Cannot use real-time scheduling (RR/5)(1: Operation not permitted) AcquireRealTime error LADSPAPluginFactory::discoverPlugins - done PluginFactory::instance(ladspa): creating new LADSPAPluginFactory LADSPAPluginFactory::discoverPlugins - discovering plugins; path is [/home/manu/.ladspa] [/usr/local/lib/ladspa] [/usr/lib/ladspa] JackDriver::initialiseAudio - JACK sample rate = 44100Hz, buffer size = 1024 JackDriver::initialiseAudio - creating disk thread JackDriver::initialiseAudio - found 2 JACK physical outputs JackDriver::initialiseAudio - connecting from "rosegarden:master out L" to "system:playback_1" JackDriver::initialiseAudio - connecting from "rosegarden:master out R" to "system:playback_2" JackDriver::initialiseAudio - found 2 JACK physical inputs JackDriver::initialiseAudio - connecting from "system:capture_1" to "rosegarden:record in 1 L" JackDriver::initialiseAudio - connecting from "system:capture_2" to "rosegarden:record in 1 R" JackDriver::initialiseAudio - initialised JACK audio subsystem ALSA Client information: 14,0 - (Midi Through, Midi Through Port-0) (DUPLEX) [ctype 2, ptype 655362, cap 99] 130,0 - (FLUID Synth (3043), Synth input port (3043:0)) (WRITE ONLY) [ctype 1, ptype 1048578, cap 66] AlsaDriver::setCurrentTimer((auto)) extractVersion: major = 1, minor = 0, subminor = 23, suffix = "" AlsaDriver::versionIsAtLeast: is version 1.0.23 at least 1.0.14? yes extractVersion: major = 2, minor = 6, subminor = 38, suffix = "generic" AlsaDriver::versionIsAtLeast: is version 2.6.38-8-generic at least 2.6.20? yes Using low-resolution system timer, sending a warning Current timer set to "system timer" with timer checks WARNING: using system timer with only 100Hz resolution! AlsaDriver::initialiseMidi - initialised MIDI subsystem LADSPAPluginFactory::discoverPlugins - done AlsaDriver::setCurrentTimer((auto)) extractVersion: major = 1, minor = 0, subminor = 23, suffix = "" AlsaDriver::versionIsAtLeast: is version 1.0.23 at least 1.0.14? yes extractVersion: major = 2, minor = 6, subminor = 38, suffix = "generic" AlsaDriver::versionIsAtLeast: is version 2.6.38-8-generic at least 2.6.20? yes Using low-resolution system timer, sending a warning Current timer set to "system timer" with timer checks WARNING: using system timer with only 100Hz resolution! Composition::getTrackById(0) - WARNING - track id not found, this is probably a BUG src/base/Composition.cpp:1560 Available track ids are: AlsaDriver::addDevice(0,0) CREATED OUTPUT PORT 3:out 1 - unnamed for device 0 Renamed 128:3 to General MIDI Device AlsaDriver::addDevice(0,1) AlsaDriver::setRecordDevice: device 1, action 1 WARNING: AlsaDriver::renameDevice: Cannot find device 1 in port map audio file manager emitting fake setValue(100) RosegardenDocument::openDocument: Successfully opened document "/home/manu/.local/share/rosegarden/autoload/autoload.rg" Object::connect: No such slot Rosegarden::AudioInstrumentParameterPanel::updateAllBoxes() in src/gui/editors/parameters/AudioInstrumentParameterPanel.cpp:81 Object::connect: (receiver name: 'Audio Instrument Parameter Panel') void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Open in &Default editor" under id 116 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Open in Matri&x Editor" under id 118 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Open in &Percussion Matrix Editor" under id 119 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Open in &Notation Editor" under id 120 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Open in &Event List Editor" under id 121 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Nothing to undo" under id 43 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "N&othing to redo" under id 44 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Cu&t" under id 46 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Copy" under id 47 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Paste" under id 48 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Delete" under id 50 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Join" under id 136 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Quantize..." under id 124 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Repe&at Last Quantize" under id 125 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "R&elabel..." under id 123 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "Transpose by &Interval..." under id 126 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Select and Edit" under id 165 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Move" under id 168 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Draw" under id 166 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Erase" under id 167 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "&Resize" under id 169 void DBusMenuExporterPrivate::addAction(QAction*, int): Already tracking action "S&plit" under id 170 Object::connect: No such signal Rosegarden::CompositionView::contentsMoving (int, int) in src/gui/editors/segment/compositionview/SegmentMover.cpp:58 Object::disconnect: No such signal Rosegarden::CompositionView::contentsMoving (int, int) in src/gui/editors/segment/compositionview/SegmentMover.cpp:65 Object::connect: No such signal Rosegarden::CompositionView::contentsMoving (int, int) in src/gui/editors/segment/compositionview/SegmentPencil.cpp:61 Connecting my port 3 to 130:0 on reconnection AlsaDriver::setPlausibleConnection: connection like "" requested for device 0 AlsaDriver::setPlausibleConnection: fuzzy match 130:0 Synth input port (3043:0) (write) available with fitness 1 AlsaDriver::setPlausibleConnection: connection like "" requested for device 1 AlsaDriver::setPlausibleConnection: nothing suitable available DataBlockRepository::clear() Studio::getMetronomeFromDevice: Having a look at device 1000 Studio::getMetronomeFromDevice: Having a look at device 10000 Studio::getMetronomeFromDevice: Having a look at device 0 Studio::getMetronomeFromDevice(0): device is a MIDI device rosegarden: could not connect to socket rosegarden: No such file or directory Rosegarden: WARNING: No accurate sequencer timer available (and kernel is new enough for RTC addendum) MAIN WINDOW DISPLAY WARNING: type 2 text<h3>System timer resolution is too low!</h3> Rosegarden: WARNING: No accurate sequencer timer available (and kernel is new enough for RTC addendum) SystemFont::loadSystemFont[Qt]: wanted family LilyPond-feta-rosegarden at size 12, got family LilyPond-feta-rosegarden (exactMatch 1) SystemFont::loadSystemFont[Qt]: wanted family LilyPond-feta-nummer-rosegarden at size 12, got family LilyPond-feta-nummer-rosegarden (exactMatch 1) SystemFont::loadSystemFont[Qt]: wanted family LilyPond-parmesan-rosegarden at size 12, got family LilyPond-parmesan-rosegarden (exactMatch 1) SystemFont::loadSystemFont[Qt]: wanted family bitstream vera serif at size 12, got family DejaVu Serif (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family luxi serif at size 12, got family DejaVu Serif (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family times new roman at size 12, got family Liberation Serif (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family times at size 12, got family Nimbus Roman No9 L (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family fughetta at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "fughetta" SystemFont::loadSystemFont[Qt]: wanted family georgia at size 12, got family DejaVu Sans (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family inkpen2 at size 12, got family DejaVu Sans (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family inkpen at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "inkpen2,inkpen" SystemFont::loadSystemFont[Qt]: wanted family inkpen2 text at size 12, got family DejaVu Sans (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family inkpen text at size 12, got family DejaVu Sans (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family comic sans ms at size 12, got family DejaVu Sans (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family maestro at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "maestro" Comparing current version "10.10" with latest version "11.06" MAIN WINDOW DISPLAY WARNING: type 4 text<h3>Newer version available</h3> SystemFont::loadSystemFont[Qt]: wanted family opus at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "opus" SystemFont::loadSystemFont[Qt]: wanted family opus text at size 12, got family DejaVu Sans (exactMatch 0) SystemFont::loadSystemFont[Qt]: wanted family petrucci at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "petrucci" SystemFont::loadSystemFont[Qt]: wanted family sonata at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "sonata" SystemFont::loadSystemFont[Qt]: wanted family steinberg notation at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "steinberg notation" SystemFont::loadSystemFont[Qt]: wanted family xinfonia at size 12, got family DejaVu Sans (exactMatch 0) Warning: Unable to load any of the fonts in "xinfonia" |
From: Vladimir S. <vla...@gm...> - 2011-06-14 00:12:13
|
On Tue, 2011-06-14 at 00:26 +0200, Manuela Hutter wrote: > Hey there, > > I just installed Rosegarden (11.06) on Ubuntu 11.04 today and gave it > a shot. At some point it behaved weirdly, got rendering issues, which > I "solved" by closing each single window/view, and finally killing the > whole program. Unfortunately, I didn't pay too close attention to what > I did, really. > > Anyway, now when I start Rosegarden, I get rendering problems with the > main window. It's simply not drawn, as if the program had frozen. I > know that it's there though (and not frozen), because by hovering > certain invisible elements I can get their tooltips. I can also access > the preferences or open other views just fine (e.g. by double-clicking > an invisible spot). > > I tried re-installing rosegarden, installing the previous version > (10.10 I believe), but I get the same behavior. I suspect that > rosegarden still has a settings folder somewhere that didn't get > deleted/recreated that might cause this behavior. (I can see in the > preferences that some other settings are still set the way I set them > on first run). I can't seem to find where Rosegarden saves its > preferences though. The 'rosegarden' folder in my home directory > doesn't seem to be it. > > Any ideas? Unfortunately, I have no idea how you could surely solve rendering glitches. Log says graphic system is "raster" which should be safe enough. Although you can easily ignore my words at this point because I'm really far from being rendering system expert. :) Anyway, rosegarden confinguration file should be located at .config/rosegradenmusic/ of your HOME directory. Try moving that file out of the way for a clean start. Regards, Vlada > Thanks, > Manuela |
From: D. M. M. <mic...@ro...> - 2011-06-14 06:40:02
|
On Monday, June 13, 2011, Manuela Hutter wrote: > know that it's there though (and not frozen), because by hovering > certain invisible elements I can get their tooltips. My first thought on that was that perhaps something was going wrong with the stylesheet, and I was going to suggest that you turn it off. However, according to the startup output you recorded, you already have the stylesheet turned off. Maybe turning it back on will do something helpful then. > Setting graphics system for Qt 4.5+ to: raster > Thorn - false > Not loading stylesheet per user request. Caveat emptor. > QSettings::endGroup: No matching beginGroup() The other thing I notice is that endGroup with no beginGroup. I've been trying to track down a settings amnesia problem for the longest time, and I think that maybe if I could ever pinpoint where this message is coming from, it might be the key to solving the settings mystery. I've never been able to figure it out. It's an elusive little bugger. Anyway, with those two things taken together, it's all the more reason why Vlada's suggestion seems like a really good place to start. Just delete or relocate ~/.config/rosegardenmusic/Rosegarden.conf and start over, and see if that helps. -- D. Michael McIntyre |
From: Manuela H. <ma...@ma...> - 2011-06-15 06:47:06
|
On Tue, Jun 14, 2011 at 8:39 AM, D. Michael McIntyre <mic...@ro...> wrote: > On Monday, June 13, 2011, Manuela Hutter wrote: > >> know that it's there though (and not frozen), because by hovering >> certain invisible elements I can get their tooltips. > > My first thought on that was that perhaps something was going wrong with the > stylesheet, and I was going to suggest that you turn it off. However, > according to the startup output you recorded, you already have the stylesheet > turned off. Maybe turning it back on will do something helpful then. > >> Setting graphics system for Qt 4.5+ to: raster >> Thorn - false >> Not loading stylesheet per user request. Caveat emptor. >> QSettings::endGroup: No matching beginGroup() > > The other thing I notice is that endGroup with no beginGroup. I've been > trying to track down a settings amnesia problem for the longest time, and I > think that maybe if I could ever pinpoint where this message is coming from, > it might be the key to solving the settings mystery. I've never been able to > figure it out. It's an elusive little bugger. > > Anyway, with those two things taken together, it's all the more reason why > Vlada's suggestion seems like a really good place to start. Just delete or > relocate ~/.config/rosegardenmusic/Rosegarden.conf and start over, and see if > that helps. Thanks for help, guys! Deleting the config file did indeed do the trick. Here's the faulty config file, in case you're interested: http://dl.dropbox.com/u/19924169/Rosegarden.conf Thanks again, Manuela |
From: D. M. M. <mic...@ro...> - 2011-06-15 09:14:44
|
On Wednesday, June 15, 2011, Manuela Hutter wrote: > Here's the faulty config file, in case you're interested: I was interested enough to glance through it, but I don't see anything really obviously out of line here. Oh well, at least whatever this was yielded to a simple remedy. It's the best we can hope for most of the time. -- D. Michael McIntyre |
From: sdsm933 <ad...@co...> - 2011-11-22 02:50:21
|
D. Michael McIntyre <michael.mcintyre@...> writes: > > On Wednesday, June 15, 2011, Manuela Hutter wrote: > > > Here's the faulty config file, in case you're interested: > > I was interested enough to glance through it, but I don't see anything really > obviously out of line here. > > Oh well, at least whatever this was yielded to a simple remedy. It's the best > we can hope for most of the time. I discovered that if you always "unmaximize" Rosegarden before you quit, the Rosegarden.conf will reflect your config changes, and also the gui will be visible the next time you start. You can maximize Rosegarden while using it, just remember to Unmaximize it before you close it. No need to delete the .conf file. Using Linux Mint 10 (Ubuntu Maverick) and Rosegarden 11.11.11 (Edelweise). |
From: D. M. M. <mic...@ro...> - 2011-11-22 03:08:52
|
On Monday, November 21, 2011, sdsm933 wrote: > I discovered that if you always "unmaximize" Rosegarden before you quit, > the Rosegarden.conf will reflect your config changes, and also the gui > will be visible the next time you start. More problems basically having to do with the store/restore window position code then. That's very frustrating, since there is plenty of evidence out there supporting the use of the mechanism we employ to accomplish exactly this job. There is no advice to be had seeking less buggy alternatives, and all arrows point in the same direction. It's a Qt library problem, I guess, but it's still our problem to deal with. I'm not sure what we could do about it. Write a window position store/restore routine from the ground up, I guess, and switch everything over to our own system. I just don't have time to do anything like that myself. Work, sleep, work... Sometimes I eat, but only sometimes. And I'm still overweight. Sigh. -- D. Michael McIntyre |
From: sdsm933 <ad...@co...> - 2011-11-22 03:21:01
|
D. Michael McIntyre <michael.mcintyre@...> writes: > > On Monday, November 21, 2011, sdsm933 wrote: > > > I discovered that if you always "unmaximize" Rosegarden before you quit, > > the Rosegarden.conf will reflect your config changes, and also the gui > > will be visible the next time you start. > > I just don't have time to do anything like that myself. Work, sleep, work... > Sometimes I eat, but only sometimes. > > And I'm still overweight. Sigh. This is a tiny workaround for such a wonderful piece of free software. I'm certainly happy with Rosegarden as it is. Thanks for all your work Michael. |
From: Tim R. <ti...@gm...> - 2012-02-06 01:55:11
|
sdsm933 <adam933@...> writes: > > D. Michael McIntyre <michael.mcintyre@...> writes: > > > > > On Monday, November 21, 2011, sdsm933 wrote: > > > > > I discovered that if you always "unmaximize" Rosegarden before you quit, > > > the Rosegarden.conf will reflect your config changes, and also the gui > > > will be visible the next time you start. > > > > > I just don't have time to do anything like that myself. Work, sleep, work... > > Sometimes I eat, but only sometimes. > > > > And I'm still overweight. Sigh. > > This is a tiny workaround for such a wonderful piece of free software. > I'm certainly happy with Rosegarden as it is. > That workaround does not work for me. And I only have the problem after a restart of the OS Ubuntu 10.10 It seems to be a problem with the config file and only on a reboot. Apparently something is not getting set in the config that is lost on reboot but maintained even upon multiple start and exit of the application. Only it doesn't open on the same monitor/workspace (dual monitors) which further indicates a config writing/reading problem. the workaround until fixed is to add a delete rosegarden config command to the /etc/rc.local file. which would be something like "rm /home/user/.config/rosegardenmusic/rosegarden.config" where user is you but note you may have to set graphic display in rosegarden preferences or other such preferences lost each time you reboot and use rosegarden and that means starting rosegarden once to set thing and exit and start again. |
From: D. M. M. <mic...@ro...> - 2012-02-06 03:30:20
|
On Sunday, February 05, 2012, Tim Rue wrote: > That workaround does not work for me. And I only have the problem after a > restart of the OS Ubuntu 10.10... I still can't find any reason why the stock, off-the-shelf code I used should misbehave in this fashion. I have no doubt that the problems you guys have experienced are real, but I really don't know what to do to work around it. What I've decided to do is wait and see what happens with the new Ubuntu LTS due out early this year. Rosegarden has no official supported version of an official supported distro, but Ubuntu LTS is pretty much the de facto, unofficial standard. If it works with Ubuntu LTS, that's good enough for me, and if it doesn't, something is grievously wrong. We'll see how it comes out, and go from there. -- D. Michael McIntyre |
From: david <gn...@ha...> - 2012-02-06 08:49:51
|
On 02/05/2012 05:30 PM, D. Michael McIntyre wrote: > On Sunday, February 05, 2012, Tim Rue wrote: > >> That workaround does not work for me. And I only have the problem after a >> restart of the OS Ubuntu 10.10... > > I still can't find any reason why the stock, off-the-shelf code I used should > misbehave in this fashion. I have no doubt that the problems you guys have > experienced are real, but I really don't know what to do to work around it. > > What I've decided to do is wait and see what happens with the new Ubuntu LTS > due out early this year. Rosegarden has no official supported version of an > official supported distro, but Ubuntu LTS is pretty much the de facto, > unofficial standard. If it works with Ubuntu LTS, that's good enough for me, > and if it doesn't, something is grievously wrong. We'll see how it comes out, > and go from there. And I've not had this problem with RG 10 or 11 on Debian Sid, either. Ubuntu's been getting kinda weird the last version or so - especially their Unity interface isn't very cooperative sometimes with non-Ubuntu apps - so it might be Ubuntu just being weird. -- David gn...@ha... authenticity, honesty, community |