[Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.

2013-10-25 Thread Sys
There is also a problem with different apps, liks X2GO Client for example. If inside a remote desktop i have an ALT+Shift combo for a language cycling and if i choose the same combo on my local PC i end up with the problem that on a local PC layout switches normally, but when i connect to a remote

[Bug 1226962] Re: Hotkeys not functional in non-latin keyboard layout in 13.10

2013-10-25 Thread Sys
Confirm this bug. Someone suggested to switch into non latin layout and set a hotkey using non latin letters. I did that and ended up with a ctrl+alt+t working only with a non-latin layout ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ub

[Bug 150579] Re: Whole screen covered and has no borders or titlebar when using compiz

2012-09-05 Thread SyS
I'm using Unity 2D (which is not using compiz) (Ubuntu 12.04 Precise) and the same problem happens when I quit LibreOffice while in Full Screen mode and then start it again. Considering the Unity layout, there is not even the title bar (picture: http://www.stockme.fr/img7a9cdcc608/Screenshot_fr

[Bug 1046491] [NEW] Calf Reverb LADSPA effect won't work properly

2012-09-05 Thread SyS
Public bug reported: Ubuntu version: 12.04.1 Precise (using Ubuntu 2D) Audacity version: 2.0.0 Package: audacity 2.0.0-1ubuntu0.1 Whenever using Calf Reverb LADSPA effect, modifying the parameters (Decay Time, High Frq Damp, Room Size, Diffusion, Wet Amount, Dry Amount, Pre Delay, Bass Cut, Trebl

[Bug 1046491] Re: Calf Reverb LADSPA effect won't work properly

2012-09-05 Thread SyS
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1046491 Title: Calf Reverb LADSPA effect won't work properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aud

[Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-12-11 Thread Alexey Sys
Uncommenting "WaylandEnable=false" worked for me in 18.10 fresh install and applying nvidia-390 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical displa

[Bug 106931] Re: Unable to detect ITE8212 RAID0 array

2008-10-29 Thread Rob at Mo-Sys
Tried with the 8.10rc live cd. I'm still getting errors with RAID1. I have 400GB drives, which are only seen as being 128GB. I suspect the problem may be with LBA48 support on it8212 in raid config. There appears to be a patch for this problem on the kernel mailing list: http://thread.gmane.org/gm

[Bug 106931] Re: Unable to detect ITE8212 RAID0 array

2008-04-16 Thread Rob at Mo-Sys
Just tried this with a recen beta of hardy. My ITE8212 is running in RAID1, Please see attached kernel log for errors. Key error seems to be: ata5.00: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) ** Attachment added: "kern.log" http://launchpadlibrarian.net/13528976/kern.log

[Bug 55197] Re: ethernet devices are not always detected in same order

2007-08-20 Thread Rob at Mo-Sys
I'm having this problem in ubuntu 6.06. I have 2 ethernet cards connected. An on-board card, and a PCI gigabit card. The PGI gigabit card keeps jumping from eth1 to eth2. Will provide further details soon. -- ethernet devices are not always detected in same order https://bugs.launchpad.net/bugs

[Bug 55197] Re: ethernet devices are not always detected in same order

2007-08-20 Thread Rob at Mo-Sys
Other than comments, iftab contains the following line: eth0 mac 00:1a:a0:3f:78:a1 arp 1 I have also attached the output of lspci -vv ** Attachment added: "lspci.out" http://launchpadlibrarian.net/8894332/lspci.out -- ethernet devices are not always detected in same order https://bugs.laun

[Bug 55197] Kenel log when gigabit card on eth2

2007-08-20 Thread Rob at Mo-Sys
Fragment of kernel log when on eth2: Aug 20 13:13:15 localhost kernel: [17179585.124000] skge 1.5 addr 0xfdbf8000 irq 58 chip Yukon rev 1 Aug 20 13:13:15 localhost kernel: [17179585.124000] skge eth0: addr 00:30:bd:b2:7b:eb Aug 20 13:13:15 localhost kernel: [17179585.188000] b44.c:v0.97 (Nov 30,

[Bug 55197] Kenel log when gigabit card on eth1

2007-08-20 Thread Rob at Mo-Sys
Fragment of kernel log when on eth1: Aug 20 12:26:43 localhost kernel: [17179587.216000] eth0: Broadcom 4400 10/100BaseT Ethernet 00:1a:a0:3f:78:a1 Aug 20 12:26:43 localhost kernel: [17179587.512000] hda: IT8212 RAID 1 volume. Aug 20 12:26:43 localhost kernel: [17179587.512000] ide0 at 0x9c00-0x

[Bug 106931] Re: Unable to detect ITE8212 RAID0 array

2007-08-08 Thread Rob at Mo-Sys
I too am having this problem with a raid card. I'm not getting having probems booting, but I do have the following error: IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80) uname -a result: Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux I've attached the

[Bug 106931] Re: Unable to detect ITE8212 RAID0 array

2007-08-08 Thread Rob at Mo-Sys
And here's the dmesg.log ** Attachment added: "dmesg.log" http://launchpadlibrarian.net/8737061/dmesg.log -- Unable to detect ITE8212 RAID0 array https://bugs.launchpad.net/bugs/106931 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubu

[Bug 106931] Re: Unable to detect ITE8212 RAID0 array

2007-08-08 Thread Rob at Mo-Sys
2 Final points: 1. This 2.6.20 kernel info was taken from running the 7.04 live CD. 2. Using the ubuntu 6.06 live CD, I can see and mount the raid volume. -- Unable to detect ITE8212 RAID0 array https://bugs.launchpad.net/bugs/106931 You received this bug notification because you are a member

[Bug 106931] Re: Unable to detect ITE8212 RAID0 array

2007-08-09 Thread Rob at Mo-Sys
Currently running the raid happily on ubuntu 6.06 If situation changes, will try upgrade to later ubuntu. -- Unable to detect ITE8212 RAID0 array https://bugs.launchpad.net/bugs/106931 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu.