On Tue, 2014-12-09 at 10:51 +0100, Freek de Kruijf wrote:

Op maandag 8 december 2014 11:56:37 schreef u:

...

On Mon, 2014-12-08 at 11:53 +0100, Freek de Kruijf wrote:

...

Op maandag 8 december 2014 10:45:02 schreef u:

...

On Sun, 2014-12-07 at 23:21 +0100, Freek de Kruijf wrote:

...

Irregularly I loose the ability to use the mouse on my laptop with fully updated Tumbleweed, which is connected via USB. Removing the USB device shows with lsusb that it really is removed. Reinserting shows with lsusb it is really present. However I can't move the pointer with the mouse. It just does nothing. Only after powering off the laptop and booting it again, I can use the mouse as it should. Anybody having the same problem?

BTW, sometimes, not very often, I have the same type of problem in my desktop with an USB stick. After the software remove, really removing the stick and reinserting, the stick does not show up the Device Notifier. Again I have to power down the system to be able to use the stick again.

This can't be solved over the list. Please open a bugzilla entry and add lsusb and dmesg (preferable with a debug kernel flavor)

Regards

Oliver

Does this mean installing kernel-desktop-debuginfo and booting using that kernel?

No. It means installing kernel-debug

HTH Oliver

I did that and got an entry in grub2. However booting that kernel made the system go around and around filling the messages file with numerous repeating messages. In the bug report I was advised to use a kernel from the Kernel: repository. Which I did, but that kernel is apparently not signed, so I could not boot it on my UEFI laptop.

Oh well, in that case just use the default kernel. Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 09 Dec 2014 10:51:03 +0100 Freek de Kruijf <f.de.kruijf@gmail.com> wrote:

In the bug report I was advised to use a kernel from the Kernel: repository. Which I did, but that kernel is apparently not signed, so I could not boot it on my UEFI laptop.

Or perhaps the kernel is signed with a different key that is not recognized by "shim". If you disable "secure-boot" in your BIOS, then you should be able to boot that kernel (whether unsigned or signed by an unrecognized key). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 2014-12-09 at 10:51 +0100, Freek de Kruijf wrote:

Op maandag 8 december 2014 11:56:37 schreef u:

...

On Mon, 2014-12-08 at 11:53 +0100, Freek de Kruijf wrote:

...

Op maandag 8 december 2014 10:45:02 schreef u:

...

On Sun, 2014-12-07 at 23:21 +0100, Freek de Kruijf wrote:

...

Irregularly I loose the ability to use the mouse on my laptop with fully updated Tumbleweed, which is connected via USB. Removing the USB device shows with lsusb that it really is removed. Reinserting shows with lsusb it is really present. However I can't move the pointer with the mouse. It just does nothing. Only after powering off the laptop and booting it again, I can use the mouse as it should. Anybody having the same problem?

BTW, sometimes, not very often, I have the same type of problem in my desktop with an USB stick. After the software remove, really removing the stick and reinserting, the stick does not show up the Device Notifier. Again I have to power down the system to be able to use the stick again.

This can't be solved over the list. Please open a bugzilla entry and add lsusb and dmesg (preferable with a debug kernel flavor)

Regards

Oliver

Does this mean installing kernel-desktop-debuginfo and booting using that kernel?

No. It means installing kernel-debug

HTH Oliver

I did that and got an entry in grub2. However booting that kernel made the system go around and around filling the messages file with numerous repeating messages. In the bug report I was advised to use a kernel from the Kernel: repository. Which I did, but that kernel is apparently not signed, so I could not boot it on my UEFI laptop.

Oh well, in that case just use the default kernel. Regards Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Tue, 09 Dec 2014 10:51:03 +0100 Freek de Kruijf <f.de.kruijf@gmail.com> wrote:

In the bug report I was advised to use a kernel from the Kernel: repository. Which I did, but that kernel is apparently not signed, so I could not boot it on my UEFI laptop.

Or perhaps the kernel is signed with a different key that is not recognized by "shim". If you disable "secure-boot" in your BIOS, then you should be able to boot that kernel (whether unsigned or signed by an unrecognized key). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org