Quoting Andrea Florio andrea@opensuse.org:
I'm really not sure what is that is breaking lxdm startup. On suse 13.2 i can upgrade from 0.4 to 0.5.0 without breaking anything.
this needs more investigation. But that is what factory is for, find those issues before they end up in the upcoming 13.3 , and this is why i re-submitted 0.5.0 after 13.2 was released, so that i could have several month ahead of me to be able to identify what breaks lxdm startup.
Andrea
Andrea,
No, sorry, I have to disappoint you here. Factory/Tumbleweed are NOT to test things. This is to be done in a devel project. Factory/Tumbleweed is targetting end-users and we do have a increasingly large userbase relying on this for their day-to-day work... Tests are to be conducted BEFORE submissions to Factory; otherwise we can't uphold the statement that Tumbleweed is ready for prime time usage.
Best regards, Dominique
2014-11-19 16:01 GMT+01:00 Dominique Leuenberger a.k.a. Dimstar < dimstar@opensuse.org>:
Hi all,
It seems we have (again) an issue with LXDE/LXDM in Factory, which blocks us from publihsing it without breaking existing systems using LXDM
As you can see in the various tests
- https://openqa.opensuse.org/tests/32620/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32638/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32583/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32597/modules/first_boot/steps/1
LXDM seems not to to be starting up at all since the upgrade to 0.5 (or maybe on the wrong VT?)
Can I please get a fix from the LXDE Maintainers to get this corrected ASAP? Also, please ensure packages are tested/working prior to submitting them to Factory/Tumbleweed. We are targetting to publish the tree often, but this requires that we get packages passing the test suites.
Thanks for your great help and I'm looking forward to get a fix soon.
Dominique
--
Andrea Florio AT&T Brno - Senior Network Architect CISCO CCNA Wireless and Security, CCNP Certified openSUSE Official Member (anubisg1) Email: andrea@opensuse.org Email: af973u@intl.att.com Cell: +39-328-7365667 Cell: +420-778-033288 Website: http://journey4ccie.com/
Am 19.11.2014 um 10:26 schrieb Dominique Leuenberger a.k.a. Dimstar:
Can I please get a fix from the LXDE Maintainers to get this corrected ASAP? Also, please ensure packages are tested/working prior to submitting them to Factory/Tumbleweed. We are targetting to publish the tree often, but this requires that we get packages passing the test suites.
Thanks for your great help and I'm looking forward to get a fix soon.
So we tried to revert to the 13.2 version in Factory to get that fixed, but unfortunately that version no longer builds.
So we're stuck with 20141112 till someone fixes the lxdm problem.
Greetings, Stephan
On 11/20/2014 06:53 AM, Stephan Kulow wrote:
Am 19.11.2014 um 10:26 schrieb Dominique Leuenberger a.k.a. Dimstar:
Can I please get a fix from the LXDE Maintainers to get this corrected ASAP? Also, please ensure packages are tested/working prior to submitting them to Factory/Tumbleweed. We are targetting to publish the tree often, but this requires that we get packages passing the test suites.
Thanks for your great help and I'm looking forward to get a fix soon.
So we tried to revert to the 13.2 version in Factory to get that fixed, but unfortunately that version no longer builds.
So we're stuck with 20141112 till someone fixes the lxdm problem.
Greetings, Stephan
I downloaded the openSUSE-Tumbleweed-DrstVD-x86_64-Snapshot20141115-Media.iso from qa and installed LXDE on a virtalbox first boot failed but a second boot succeeded
Am 20.11.2014 um 07:53 schrieb Dale Ritchey:
I downloaded the openSUSE-Tumbleweed-DrstVD-x86_64-Snapshot20141115-Media.iso from qa and installed LXDE on a virtalbox first boot failed but a second boot succeeded
Yeah, but we're not windows
Greetings, Stephan
On 11/20/2014 08:38 AM, Stephan Kulow wrote:
Am 20.11.2014 um 07:53 schrieb Dale Ritchey:
I downloaded the openSUSE-Tumbleweed-DrstVD-x86_64-Snapshot20141115-Media.iso from qa and installed LXDE on a virtalbox first boot failed but a second boot succeeded
Yeah, but we're not windows
Greetings, Stephan
I installed openSUSE-Tumbleweed-DVD-x86_64-Snapshot20141115 on a live system init 3 then init 5 succeed. would the Xorg.0.log and lxdm.log help
On Thursday 20 November 2014 06:53:19 Stephan Kulow wrote:
So we tried to revert to the 13.2 version in Factory to get that fixed, but unfortunately that version no longer builds.
So we're stuck with 20141112 till someone fixes the lxdm problem.
Hi Stephan,
Are there any error logs available ??
I guess another option to consider is to drop LXDM from factory until this is fixed ?
Raymond
Am 20.11.2014 um 08:33 schrieb Raymond Wooninck:
On Thursday 20 November 2014 06:53:19 Stephan Kulow wrote:
So we tried to revert to the 13.2 version in Factory to get that fixed, but unfortunately that version no longer builds.
So we're stuck with 20141112 till someone fixes the lxdm problem.
Hi Stephan,
Are there any error logs available ??
Quite some - check https://openqa.opensuse.org/tests/32620
I guess another option to consider is to drop LXDM from factory until this is fixed ?
I find that a bit harsh - and how can we verify it's fixed? I guess the main problem is: not everything we consider critical for tumbleweed is also tested in staging.
Greetings, Stephan
Stephan Kulow schrieb:
Am 20.11.2014 um 08:33 schrieb Raymond Wooninck:
On Thursday 20 November 2014 06:53:19 Stephan Kulow wrote:
So we tried to revert to the 13.2 version in Factory to get that fixed, but unfortunately that version no longer builds.
So we're stuck with 20141112 till someone fixes the lxdm problem.
Hi Stephan,
Are there any error logs available ??
Quite some - check https://openqa.opensuse.org/tests/32620
I guess another option to consider is to drop LXDM from factory until this is fixed ?
I find that a bit harsh - and how can we verify it's fixed? I guess the main problem is: not everything we consider critical for tumbleweed is also tested in staging.
Why do we consider LXDE critical for tumbleweed anyways? Can't we just treat it like any other optional desktop, like e.g. mate or plasma5, ie ignore it in openqa?
cu Ludwig
Am 20.11.2014 um 09:03 schrieb Ludwig Nussel:
Why do we consider LXDE critical for tumbleweed anyways? Can't we just treat it like any other optional desktop, like e.g. mate or plasma5, ie ignore it in openqa?
As I wrote in the lxdm SR: it *is* an option to remove lxde from DVD and make it a random package.
Greetings, Stephan
Hi,
On Thu, Nov 20, 2014 at 08:43:34AM -0500, Stephan Kulow wrote:
Am 20.11.2014 um 08:33 schrieb Raymond Wooninck:
On Thursday 20 November 2014 06:53:19 Stephan Kulow wrote:
So we tried to revert to the 13.2 version in Factory to get that fixed, but unfortunately that version no longer builds.
So we're stuck with 20141112 till someone fixes the lxdm problem.
Hi Stephan,
Are there any error logs available ??
Quite some - check https://openqa.opensuse.org/tests/32620
Could this be a problem (the message looks severe enough):
[ 32.457] (WW) CIRRUS: More than one matching Device section found: Autoconfigured Video Device cirrus [ 32.457] (--) Chipset CLGD5446 found [ 32.457] (EE) cirrus: The PCI device 0xb8 at 00@00:02:0 has a kernel module claiming it. [ 32.457] (EE) cirrus: This driver cannot operate until it has been unloaded.
In the journal, however, the cirrus module is loaded:
Nov 16 01:17:17 linux-4e9f kernel: vgaarb: setting as boot device: PCI:0000:00:02.0 Nov 16 01:17:17 linux-4e9f kernel: vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none Nov 16 01:17:17 linux-4e9f kernel: vgaarb: loaded Nov 16 01:17:17 linux-4e9f kernel: vgaarb: bridge control possible 0000:00:02.0 ... Nov 16 01:17:17 linux-4e9f kernel: pci 0000:00:02.0: Video device with shadowed ROM ... Nov 16 01:17:18 linux-4e9f kernel: cirrus 0000:00:02.0: fb0: cirrusdrmfb frame buffer device Nov 16 01:17:18 linux-4e9f kernel: cirrus 0000:00:02.0: registered panic notifier Nov 16 01:17:18 linux-4e9f kernel: [drm] Initialized cirrus 1.0.0 20110418 for 0000:00:02.0 on minor 0
Some kind of race perhaps?
Thanks,
Dejan
I guess another option to consider is to drop LXDM from factory until this is fixed ?
I find that a bit harsh - and how can we verify it's fixed? I guess the main problem is: not everything we consider critical for tumbleweed is also tested in staging.
Greetings, Stephan
-- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi.
El Miércoles, 19 de noviembre de 2014 15:26:07 Dominique Leuenberger a.k.a. Dimstar escribió:
Quoting Andrea Florio andrea@opensuse.org:
I'm really not sure what is that is breaking lxdm startup. On suse 13.2 i can upgrade from 0.4 to 0.5.0 without breaking anything.
this needs more investigation. But that is what factory is for, find those issues before they end up in the upcoming 13.3 , and this is why i re-submitted 0.5.0 after 13.2 was released, so that i could have several month ahead of me to be able to identify what breaks lxdm startup.
Andrea
Andrea,
No, sorry, I have to disappoint you here. Factory/Tumbleweed are NOT to test things. This is to be done in a devel project. Factory/Tumbleweed is targetting end-users and we do have a increasingly large userbase relying on this for their day-to-day work... Tests are to be conducted BEFORE submissions to Factory; otherwise we can't uphold the statement that Tumbleweed is ready for prime time usage.
Best regards, Dominique
2014-11-19 16:01 GMT+01:00 Dominique Leuenberger a.k.a. Dimstar <
dimstar@opensuse.org>:
Hi all,
It seems we have (again) an issue with LXDE/LXDM in Factory, which blocks us from publihsing it without breaking existing systems using LXDM
As you can see in the various tests
- https://openqa.opensuse.org/tests/32620/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32638/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32583/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32597/modules/first_boot/steps/1
LXDM seems not to to be starting up at all since the upgrade to 0.5 (or maybe on the wrong VT?)
Can I please get a fix from the LXDE Maintainers to get this corrected ASAP? Also, please ensure packages are tested/working prior to submitting them to Factory/Tumbleweed. We are targetting to publish the tree often, but this requires that we get packages passing the test suites.
Thanks for your great help and I'm looking forward to get a fix soon.
Dominique
--
Andrea Florio AT&T Brno - Senior Network Architect CISCO CCNA Wireless and Security, CCNP Certified openSUSE Official Member (anubisg1) Email: andrea@opensuse.org Email: af973u@intl.att.com Cell: +39-328-7365667 Cell: +420-778-033288 Website: http://journey4ccie.com/
From the Arch wiki: "LXDM provides the lxdm systemd service. Enable it to
start LXDM at boot."
I don't know how it is done, but could this be a path to explore?
Greetings.
On 11/19/2014 10:26 AM, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting Andrea Florio andrea@opensuse.org:
I'm really not sure what is that is breaking lxdm startup. On suse 13.2 i can upgrade from 0.4 to 0.5.0 without breaking anything.
this needs more investigation. But that is what factory is for, find those issues before they end up in the upcoming 13.3 , and this is why i re-submitted 0.5.0 after 13.2 was released, so that i could have several month ahead of me to be able to identify what breaks lxdm startup.
Andrea
Andrea,
No, sorry, I have to disappoint you here. Factory/Tumbleweed are NOT to test things. This is to be done in a devel project. Factory/Tumbleweed is targetting end-users and we do have a increasingly large userbase relying on this for their day-to-day work... Tests are to be conducted BEFORE submissions to Factory; otherwise we can't uphold the statement that Tumbleweed is ready for prime time usage.
Best regards, Dominique
2014-11-19 16:01 GMT+01:00 Dominique Leuenberger a.k.a. Dimstar < dimstar@opensuse.org>:
Hi all,
It seems we have (again) an issue with LXDE/LXDM in Factory, which blocks us from publihsing it without breaking existing systems using LXDM
As you can see in the various tests
- https://openqa.opensuse.org/tests/32620/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32638/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32583/modules/first_boot/steps/1
- https://openqa.opensuse.org/tests/32597/modules/first_boot/steps/1
LXDM seems not to to be starting up at all since the upgrade to 0.5 (or maybe on the wrong VT?)
Can I please get a fix from the LXDE Maintainers to get this corrected ASAP? Also, please ensure packages are tested/working prior to submitting them to Factory/Tumbleweed. We are targetting to publish the tree often, but this requires that we get packages passing the test suites.
Thanks for your great help and I'm looking forward to get a fix soon.
Dominique
--
Andrea Florio AT&T Brno - Senior Network Architect CISCO CCNA Wireless and Security, CCNP Certified openSUSE Official Member (anubisg1) Email: andrea@opensuse.org Email: af973u@intl.att.com Cell: +39-328-7365667 Cell: +420-778-033288 Website: http://journey4ccie.com/
Are you sure the problem is lxdm? using build 20141119 with auto login disabled first boot succeeds with auto log in enabled first boot fails
On Fri, 2014-11-21 at 11:42 -0500, Dale Ritchey wrote:
Are you sure the problem is lxdm? using build 20141119 with auto login disabled first boot succeeds with auto log in enabled first boot fails
an't say for sure... fact is though: updating LXDM to 0.5.0 causes the issue, reverting to 0.4.1 makes the issue go away.
Cheers, Dominique
-
Dale Ritchey -
Dejan Muhamedagic -
Dominique Leuenberger -
Dominique Leuenberger a.k.a. Dimstar -
jcsl -
Ludwig Nussel -
Raymond Wooninck -
Stephan Kulow