Re: Help please. Kdoctools build.
Scarlett Clark ha scritto: > I need some help please. I am working through a new rebuild on my sandbox CI > system and I was quickly halted due to kdoctools.I am not even sure where to > start with this. > > https://build-sandbox.kde.org/job/kdoctools%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/2/console What is the login to access the logs? (I tried my identity login but I don't have the proper rights) On the other side, could the jobs be made public? Ciao -- Luigi
Re: Help please. Kdoctools build.
Oops, this has been my playground up until now. I have fixed ( I hope ) that developers should be able to access jobs and public can view jobs. Keep in mind this is my space to develop new stuff for CI and is generally a mess ! :) Thanks! Scarlett On Fri, Nov 27, 2015 at 4:12 PM, Luigi Toscanowrote: > Scarlett Clark ha scritto: > > I need some help please. I am working through a new rebuild on my > sandbox CI > > system and I was quickly halted due to kdoctools.I am not even sure > where to > > start with this. > > > > > https://build-sandbox.kde.org/job/kdoctools%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/2/console > > What is the login to access the logs? (I tried my identity login but I > don't > have the proper rights) > On the other side, could the jobs be made public? > > Ciao > -- > Luigi >
Re: Causes of session management problems in Plasma 5
On Donnerstag, 26. November 2015 08:55:19 CET Thomas Lübking wrote: > On Donnerstag, 26. November 2015 05:19:34 CEST, Nicolás Alvarez wrote: > > What do you mean with "konsole asks"? Things like "You have > > multiple tabs open, are you sure you want to quit?" and "You > > have unsaved changes"? > > Yes. > > > If so, the scenario you describe is bad regardless of session > > restoration. > > Yes. Unfortunaltely. > > > If konsole has to ask the user and the user has a > > chance to say no and cancel the logout at that point, then > > kwrite shouldn't have exited yet! > > That's what the spec says, but the ksmserver change suggestion is > about buggy clients that behave exactly this way. > > If "app canceling logout" is a thing, then logout should feel > > transactional to the user. Either logout happens and all apps > > exit, or logout doesn't happen and nothing exits. > > Yes. That's what the spec says ... > > > I guess the implementation of that would be: all apps should be > > given a chance to ask their questions and approve or stop the > > logout > That'S exactly what happens, but ... > > > before *any* app exits. > > We cannot stop process from doing stupid things, like exiting in the > wrong moment. > > This is how MS Windows works, by the way (or used to work). > > No, it's how not buggy applications work on windows. > > Cheers, > Thomas I was going to write pretty much the same things, Thomas was just faster :) XSMP is a fairly well thought out spec although the full text, which I haven't read in its entirety, seems to be too long for what the spec is supposed to achieve. Logout being transactional is a big item in it.
Help please. Kdoctools build.
I need some help please. I am working through a new rebuild on my sandbox CI system and I was quickly halted due to kdoctools.I am not even sure where to start with this. https://build-sandbox.kde.org/job/kdoctools%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/2/console Piles of memory leaks. I guess this is the new ASAN flag? Am I to guess libxml2 is somehow involved here? I can tell you ICU was updated so that is why I have to rebuild everything, is that somehow involved? I am integrating docker into our build system, though that should be irrelevant. Thanks to anyone that can shed some light on this for me. Scarlett