Bug#796956: Note that this is a docked laptop using external monitor
Control: severity -1 important On 08/09/15 10:04, eric2.vale...@orange.com wrote: > I now have half a dozen boxes that works correctly and this is the only one > that is a docked laptop using an external monitor with internal LVDS display > off. So far as I had multiple temporary breakage on various boxes due to > partial/incompatible packages versions uploads, I did not consider it was a > specific case but now only this docked laptop remains broken. Ok, that sounds more like another issue. This seems to be another effect of a problem in qt5.4 regarding QScreen returning null in unexpected places. And is currently known to reproducibly fail on machines with one display off, for instance, closing the lid in a laptop that has an external monitor connected. This is supposedly fixed in qt5.5, currently in experimental. I'm downgrading the severity as the problem went from every machine to only one. Happy hacking, -- "I decry the current tendency to seek patents on algorithms. There are better ways to earn a living than to prevent other people from making use of one's contributions to computer science." -- Donald Knuth Saludos /\/\ /\ >< `/ signature.asc Description: OpenPGP digital signature
Bug#796956: Note that this is a docked laptop using external monitor
On 09/16/2015 03:08 PM, Maximiliano Curia wrote: Control: severity -1 important On 08/09/15 10:04, eric2.vale...@orange.com wrote: I now have half a dozen boxes that works correctly and this is the only one that is a docked laptop using an external monitor with internal LVDS display off. So far as I had multiple temporary breakage on various boxes due to partial/incompatible packages versions uploads, I did not consider it was a specific case but now only this docked laptop remains broken. Ok, that sounds more like another issue. This seems to be another effect of a problem in qt5.4 regarding QScreen returning null in unexpected places. And is currently known to reproducibly fail on machines with one display off, for instance, closing the lid in a laptop that has an external monitor connected. This is supposedly fixed in qt5.5, currently in experimental. Do you know if installing qt5.5 from experimental will break many other things badly? It did break breeze in the past if partially installed (some qt5.5 packages were installing themselves via experimental upgrade even if core qt5.5 was not there Konsole outpu). -- eric
Bug#796956: Note that this is a docked laptop using external monitor
Hi, On 16/09/15 15:18, Eric Valette wrote: > On 09/16/2015 03:08 PM, Maximiliano Curia wrote: > > Control: severity -1 important > > > > On 08/09/15 10:04, eric2.vale...@orange.com wrote: > >> I now have half a dozen boxes that works correctly and this is the only one > >> that is a docked laptop using an external monitor with internal LVDS > >> display > >> off. So far as I had multiple temporary breakage on various boxes due to > >> partial/incompatible packages versions uploads, I did not consider it was a > >> specific case but now only this docked laptop remains broken. > > Ok, that sounds more like another issue. This seems to be another effect of > > a > > problem in qt5.4 regarding QScreen returning null in unexpected places. And > > is > > currently known to reproducibly fail on machines with one display off, for > > instance, closing the lid in a laptop that has an external monitor > > connected. > > This is supposedly fixed in qt5.5, currently in experimental. > > Do you know if installing qt5.5 from experimental will break many other things > badly? It did break breeze in the past if partially installed (some qt5.5 > packages were installing themselves via experimental upgrade even if core > qt5.5 was not there qt5.5 has an abi blocker for things that link against its private symbols, so Konsole outputthings that depend on qtbase-abi-5-4-2 will need to be recompiled against the new qt version. frameworkintegration is the one the I see that directly depends on that. Happy hacking,
Bug#796956: Note that this is a docked laptop using external monitor
On Wednesday 16 September 2015 16:23:23 Maximiliano Curia wrote: > Hi, [snip] > qt5.5 has an abi blocker for things that link against its private symbols, > so Konsole outputthings that depend on qtbase-abi-5-4-2 will need to be > recompiled against the new qt version. > > frameworkintegration is the one the I see that directly depends on that. In other words: you need to either recompile the necessary stuff yourself or wait until Qt 5.5 arrives to unstable. It also helps if you complain to upstream for using private Qt stuff ;) -- porque no respeta el orden natural en el que se leen las cosas >¿por qué top-posting es tan molesto? >>top-posting >>>¿cuál es la peor molestia en los emails de respuesta? Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#796956: Note that this is a docked laptop using external monitor
On Wednesday 16 September 2015 12:44:02 Lisandro Damián Nicanor Pérez Meyer wrote: > > qt5.5 has an abi blocker for things that link against its private symbols, > > so Konsole outputthings that depend on qtbase-abi-5-4-2 will need to be > > recompiled against the new qt version. > > > > frameworkintegration is the one the I see that directly depends on that. > > In other words: you need to either recompile the necessary stuff yourself > or wait until Qt 5.5 arrives to unstable. Is it a possibility to get those packages compiled against Qt 5.5 in experimental? signature.asc Description: This is a digitally signed message part.
Bug#796956: Note that this is a docked laptop using external monitor
I now have half a dozen boxes that works correctly and this is the only one that is a docked laptop using an external monitor with internal LVDS display off. So far as I had multiple temporary breakage on various boxes due to partial/incompatible packages versions uploads, I did not consider it was a specific case but now only this docked laptop remains broken. --eric _ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
