Public bug reported:
After upgrading to KDE 4.2 Beta 1 I found that Kwin was not working(
unable to resize, close, minimize windows). The problem can be
temporarily fixed by using
Kwin --replace
This works temporarily however gives this output
Output = ro...@rogan:~$ kwin --replace
Public bug reported:
After upgrading to KDE 4.2 Beta 1 I found that Kwin was not working(
unable to resize, close, minimize windows). The problem can be
temporarily fixed by using
Kwin --replace
This works temporarily however gives this output
Output = ro...@rogan:~$ kwin --replace
Public bug reported:
After upgrading to KDE 4.2 Beta 1 I found that Kwin was not working(
unable to resize, close, minimize windows). The problem can be
temporarily fixed by using
Kwin --replace
This works temporarily however gives this output
Output = ro...@rogan:~$ kwin --replace
Public bug reported:
After upgrading to KDE 4.2 Beta 1 I found that Kwin was not working(
unable to resize, close, minimize windows). The problem can be
temporarily fixed by using
Kwin --replace
This works temporarily however gives this output
Output = ro...@rogan:~$ kwin --replace
Public bug reported:
After upgrading to KDE 4.2 Beta 1 I found that Kwin was not working(
unable to resize, close, minimize windows). The problem can be
temporarily fixed by using
Kwin --replace
This works temporarily however gives this output
Output = ro...@rogan:~$ kwin --replace
Public bug reported:
After upgrading to KDE 4.2 Beta 1 I found that Kwin was not working(
unable to resize, close, minimize windows). The problem can be
temporarily fixed by using
Kwin --replace
This works temporarily however gives this output
Output = ro...@rogan:~$ kwin --replace
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
Ok, this is just informational -- I think I've made some headway but
unfortunately I haven't figured out a solution yet.
I fixed a couple problems:
* xsetwacom was not being found when the sleep.d script was running
* root did not have access to the :0.0 display (as evidenced by "Failed to
I tested this with an ultrabay hdd adapter, and the problem persists if
there is a drive in the bay, but when the hdd adapter is empty, the
problem goes away.
I made a bootable usb key with the latest ubuntu beta, and I does boot,
but I haven't had a chance to see if it fixes the problem or not.
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
Ok, this is just informational -- I think I've made some headway but
unfortunately I haven't figured out a solution yet.
I fixed a couple problems:
* xsetwacom was not being found when the sleep.d script was running
* root did not have access to the :0.0 display (as evidenced by "Failed to
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
Ok, this is just informational -- I think I've made some headway but
unfortunately I haven't figured out a solution yet.
I fixed a couple problems:
* xsetwacom was not being found when the sleep.d script was running
* root did not have access to the :0.0 display (as evidenced by "Failed to
I tested this with an ultrabay hdd adapter, and the problem persists if
there is a drive in the bay, but when the hdd adapter is empty, the
problem goes away.
I made a bootable usb key with the latest ubuntu beta, and I does boot,
but I haven't had a chance to see if it fixes the problem or not.
I tested this with an ultrabay hdd adapter, and the problem persists if
there is a drive in the bay, but when the hdd adapter is empty, the
problem goes away.
I made a bootable usb key with the latest ubuntu beta, and I does boot,
but I haven't had a chance to see if it fixes the problem or not.
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
I tested this with an ultrabay hdd adapter, and the problem persists if
there is a drive in the bay, but when the hdd adapter is empty, the
problem goes away.
I made a bootable usb key with the latest ubuntu beta, and I does boot,
but I haven't had a chance to see if it fixes the problem or not.
Ok, this is just informational -- I think I've made some headway but
unfortunately I haven't figured out a solution yet.
I fixed a couple problems:
* xsetwacom was not being found when the sleep.d script was running
* root did not have access to the :0.0 display (as evidenced by "Failed to
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
Ok, this is just informational -- I think I've made some headway but
unfortunately I haven't figured out a solution yet.
I fixed a couple problems:
* xsetwacom was not being found when the sleep.d script was running
* root did not have access to the :0.0 display (as evidenced by "Failed to
I tested this with an ultrabay hdd adapter, and the problem persists if
there is a drive in the bay, but when the hdd adapter is empty, the
problem goes away.
I made a bootable usb key with the latest ubuntu beta, and I does boot,
but I haven't had a chance to see if it fixes the problem or not.
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
brate thaw) and as you said, it is running on
resume. Opening up x to all connections (xhost +) had no noticeable
effect either.
--Rogan
--
[intrepid] suspend/resume with wacom pointers rotated loses calibration
https://bugs.launchpad.net/bugs/295292
You received this bug notification because y
Ok, this is just informational -- I think I've made some headway but
unfortunately I haven't figured out a solution yet.
I fixed a couple problems:
* xsetwacom was not being found when the sleep.d script was running
* root did not have access to the :0.0 display (as evidenced by "Failed to
I tested this with an ultrabay hdd adapter, and the problem persists if
there is a drive in the bay, but when the hdd adapter is empty, the
problem goes away.
I made a bootable usb key with the latest ubuntu beta, and I does boot,
but I haven't had a chance to see if it fixes the problem or not.
30 matches
Mail list logo
