Re: PA 4 update release?
On January 26, 2014 04:50:10 PM Marco Martin wrote: > On Sunday 26 January 2014, Matthew Dawson wrote: > > On January 25, 2014 06:42:52 PM Marco Martin wrote: > > > Right now there are 8 packages that doesn't build correctly against > > > 4.11. > > > you can see it there > > > https://build.merproject.org/project/monitor?project=kde%3Adevel%3Aux > > > > For NetworkManager-kde, should this be changed to use the new repository > > at > > plasma-nm? The failure is occurring as a warning that the repository is > > no > > longer updated. If the old repository is correct, it is easy enough to > > fix > > the issue. > > yeah, definitely. > > since it was automatically updated, probably the jenkins job that updates it > should be updated to the new repo as well (or disabled) > > Cheers, > Marco Martin Ok. Where is the jenkins job configured, and do I have access to modify it? And could I setup a similar job to Analitza so its tarball will stay up to date? Also, I'm working on upstreaming some of my patches for kdepim (one of which has been committed), which then caused the build to fail (I didn't expect it to get a new tarball). Do you want me to submit another fix for that? (I'm idling in the #active irc channel (nick is MJD), if it would be easier to discuss there) -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA 4 update release?
On January 25, 2014 06:42:52 PM Marco Martin wrote: > Right now there are 8 packages that doesn't build correctly against 4.11. > you can see it there > https://build.merproject.org/project/monitor?project=kde%3Adevel%3Aux For KAlgebra , the compile fails as the Analitza is from 4.9 and is missing functions relied upon in KAlgebra. As the tarballs are automatically created/uploaded, it appears Analitza needs to be added back into update process. For now, should I just grab a new tarball for Analitza and continue from there? -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA 4 update release?
On January 25, 2014 06:42:52 PM Marco Martin wrote: > Right now there are 8 packages that doesn't build correctly against 4.11. > you can see it there > https://build.merproject.org/project/monitor?project=kde%3Adevel%3Aux > For NetworkManager-kde, should this be changed to use the new repository at plasma-nm? The failure is occurring as a warning that the repository is no longer updated. If the old repository is correct, it is easy enough to fix the issue. -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: PA 4 update release?
On January 25, 2014 06:42:52 PM Marco Martin wrote: > On Saturday 25 January 2014, Aaron J. Seigo wrote: > > hi... > > > > there were some changes in kde-workspace in 4.11 that breaks the build of > > plasma-mobile. yet another person came into #active on irc tonight stumped > > by this. plasma-mobile’s master branch does build, however. > > > > i’d like to propose that we do an interim PA4 release based on what is in > > master right now so that it builds against 4.11 > > > > the packages being delivered on the most recent MerOS that sports Plasma > > Desktop and SDDM have a build from master iirc, anyways? > > > > Marco, what do you think? > > It would be nice. > For this I would like to try an experiment. > > Right now there are 8 packages that doesn't build correctly against 4.11. > you can see it there > https://build.merproject.org/project/monitor?project=kde%3Adevel%3Aux > > This really soulds like 8 Junior jobs to me. > fixing the build of a package shouldn't be an huge job and less scary than > creating a package from scratch > Any takers? > > Cheers, > Marco Martin I've started working through the build failures. I've fixed plasma-addons (and submitted a change request on obs), and will move on to kdepim next. -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: notice on active builds
On December 9, 2013 08:41:58 PM Wolfgang Romey wrote: > > In Virtualbox i only reach the console of my linux system which runs > virtualbox. I cannot try it on my weTab, were i will try it with the usb- > keyboard next monday (if it is necessary then). > Take a look at this:: http://blog.tordeu.com/?p=322 The problem is that Xorg is intercepting the keystrokes. There is usually a way around that, but it is specific to whatever software you are using. -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Installing PA (mer) on Nexus 7
On September 3, 2013 12:24:49 PM Matthias Raives wrote: > It seems the primary difference is that the tutorial you linked has me > erase the boot and userdata partitions before flashing MOSLO onto my > device. I could imagine the former helping, but I don't see why I would > need to erase the userdata partition (it should be erased upon unlocking > the bootloader anyways). > > In any case, I was assuming the problem was due to the fact that I was > using a newer model of the Nexus 7. Can you confirm/deny this assumption? > That will be an issue for sure. The PA images are for the 2012 model, and due to the way the ARM world works, it is highly doubtful that the 2012 image would ever work for the 2013 model (At the very least, the GPU drivers are different, along with different CPU manufactures. That will break things). Of course, if someone wants to add support/build an image for the 2013 model (in theory) it should be able to run PA. -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: On screen keyboard no longer working after update
On August 31, 2013 08:52:19 PM Bogdan Cristea wrote: > Hi > After a zypper dup today the onscreen keyboard no longer appears when I > need to type something in an edit box (e.g. kwallet password). Any ideas > how to fix this ? > thanks > Bogdan Hi Bogdan, According to this thread: http://lists.kde.org/?l=kde-active&m=137781003010495&w=2 Updating to the latest PA through zypper is broken for now, and instead the recommended course of action is to back up your data and install the latest image. -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Nexus 7 images
On June 6, 2013 10:19:19 AM Ruediger Gad wrote: > Alright, I found the problem. This is actually quite an old issue. > > To summarize: there are still issues with QT_DEFAULT_RUNTIME_SYSTEM=opengl > > Back then we had this setting only in: /etc/profile.d/tegra3-env.sh > Because of above mentioned issues we disabled that environment variable > there. > > Apparently, that setting crept in again via: /etc/sysconfig/nemo-mobile-hw > Afaik, QT_DEFAULT_RUNTIME_SYSTEM=opengl doesn't cause issues on > nemomobile. Hence, nemo uses this setting. > Which runtime system is desired to be used by PA? Would there be any benefit to getting the opengl renderer working properly? Or should I ignore it and work on other things? -- Matthew signature.asc Description: This is a digitally signed message part. ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Nexus 7 images
On June 5, 2013 06:03:15 PM Daniel Kreuter wrote: > Hi Matthew, > > can you post snippets of that log file? Maybe Martin has any idea what the > generic messages mean. Unfortunately, I don't have that log file anymore, as I've since upgraded my tablet. If someone has PA working on the N7, the error messages appeared in the general log file in /tmp. Also, I've done some GL work. The error message was being printed from the end of the entire draw in KWin, and was some generic OpenGL error. I was working on digging into what exactly was throwing the error, but ran out of time. If I have some time I'll try working on it again, and see if I can figure out it's source. I've played with OpenGL before (but not KWin), and that error isn't helpful without knowing the call causing it. I think it was some GL_INVALID_*. Also, since you mentioned some crashes, I had hunted down the crash in KDED and last I remember, Powerdevil caused some GUI to display, which caused Qt to try and render something using OpenGL ES, which promptly crashed as some Qt(?) class called Context(?) which wasn't initialized. That is from memory, and I was trying to update my tablet at the time I was hunting that down, so I don't have that stack trace either. I actually wanted to first get image generation for the N7 stable so I could more easily deal with it before tackling those issues. But I never have enough time :). I first wanted to deal with SSU as it was causing my images to be missing debug symbols, important for bug hunting! -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Re: Nexus 7 images
On June 5, 2013 12:27:26 AM Ruediger Gad wrote: > Hi, > > Unfortunately, there will be the next problem. The UI freezes instantly > under some circumstances (e.g., when trying to pull down the top bar). > You should(tm) be able to switch between activities, which shows that it > is generally working, but you will encounter lots of situations in which > the UI just freezes. I've been playing with an older version of PA on my Nexus 7, and I've started trying to narrow down this issue. I'm not sure exactly why yet, but I've gathered a few clues about this: 1) The UI freezes because KWin starts throwing GL errors and stops updating the display. You can see the errors in the logs, but it is a generic error so I'm not sure what is causing it. 2) Killing/restarting KWin stops the errors and UI starts acting normally. It only happens with the first instance of KWin. 3) While KWin stops drawing, I believe that the UI continues to receive events, it just doesn't draw. Hope that helps, -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
Some questions regarding Plasma Active
Hi all, I've been playing around with PA, and I'm looking to get involved with the project. I also have a Nexus 7 to play with, and a 10 I'd like to get PA on. I've installed the Mer SDK and read its documentation. I have a few questions regarding PA: 1) Aaron mentioned in one of his video cast that PA was using zypper for it's package management, but the kickstarter files default to yum. Which manager is meant to be used by PA? If zypper is supposed to be the default, I'll post a patch to change it. 2) When building development images for the Nexus 7, there is the ssu script run, but it doesn't have tokens mapped by default. Is this by design, and I should I be specifying appropriate token map arguments to mic? Or is this a bug? 3) Is ssu system the future for repository management? The latest image I have using it is missing various debuginfo packages (from the repositories), making debugging a pain. 4) When trying to build a PA4 image for the Nexus 7, it fails with the error: Error : Unable to find package: graphics-adaptation-tegra3-libEGL Which seems to come from the tegra3 repositories not having packages in testing. Thus, is PA4 currently targeting the N7, and if so, is there some way I can help get those packages ready? Or is the N7 not going to be included in PA4? Development images are fine, as long as I target latest- devel, and the repositories are all found so the yaml files seem to be fine in general. Thanks for any help, -- Matthew smime.p7s Description: S/MIME cryptographic signature ___ Active mailing list Active@kde.org https://mail.kde.org/mailman/listinfo/active
