[Bug 1372409] [NEW] The monitor won't wake up after going to sleep (initiated by locking, automatic or manual)

2014-09-22 Thread Jan Corazza
Public bug reported: I am using the 3.16.3 kernel and Mesa/drivers/Xorg from the Oibaf PPA - but this also happens when using drivers from the regular repositories. I can leave the computer to lock itself, or lock it by pressing Ctrl+Alt+L, and it power off the monitor after a few seconds (blue

[Bug 1372409] Re: The monitor won't wake up after going to sleep (initiated by locking, automatic or manual)

2014-09-22 Thread Jan Corazza
** Description changed: I am using the 3.16.3 kernel and Mesa/drivers/Xorg from the Oibaf PPA - but this also happens when using drivers from the regular repositories. I can leave the computer to lock itself, or lock it by pressing Ctrl+Alt+L, and it power off the monitor after a few

[Bug 1372409] Re: The monitor won't wake up after going to sleep (initiated by locking, automatic or manual)

2014-09-23 Thread Jan Corazza
** Description changed: I am using the 3.16.3 kernel and Mesa/drivers/Xorg from the Oibaf PPA - but this also happens when using drivers from the regular repositories. - - I can leave the computer to lock itself, or lock it by pressing - Ctrl+Alt+L, and it power off the monitor after a few

[Bug 1372409] Re: The monitor won't wake up after going to sleep (initiated by locking, automatic or manual)

2014-09-23 Thread Jan Corazza
** Description changed: I am using the 3.16.3 kernel and Mesa/drivers/Xorg from the Oibaf PPA - but this also happens when using drivers from the regular repositories. I would say that this bug is SEVERE, because you can lose important work. Steps to reproduce: 1. Lock

[Bug 1372409] Re: The monitor won't wake up after going to sleep (initiated by locking, automatic or manual)

2014-09-23 Thread Jan Corazza
** Description changed: - I am using the 3.16.3 kernel and Mesa/drivers/Xorg from the Oibaf PPA - - but this also happens when using drivers from the regular repositories. + UPDATE: After around ten minutes of inactivity, it is again possible to + wake the monitor from sleep! + + I am using the

[Bug 1372409] Re: The monitor won't wake up after going to sleep (initiated by locking, automatic or manual)

2014-09-23 Thread Jan Corazza
** Description changed: UPDATE: After around ten minutes of inactivity, it is again possible to wake the monitor from sleep! I am using the 3.16.3 kernel (edit: now 3.17 RC6!) and Mesa/drivers/Xorg from the Oibaf PPA - but this also happens when using drivers from the regular

[Bug 1373118] Re: Vertical line of pixels separating the launcher from the rest of the screen

2014-09-25 Thread Jan Corazza
Yep, I can confirm that when setting a darker wallpaper, which I used to have at the time I thought this wasn't a feature, makes the line so unpronounced that I hadn't noticed it before setting a brighter wallpaper. If I may ask - why is this a feature? It looks awkward. -- You received this

[Bug 1377820] [NEW] Computer not suspending when inactive in the main log-in prompt

2014-10-06 Thread Jan Corazza
Public bug reported: #DESCRIPTION My computer is set to automatically dim the screen and lock after 10 minutes, and suspend after an hour of inactivity. That works fine - but only once I've logged in first. If I switch the computer on and then leave it, it won't suspend, although it will dim

[Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt

2014-10-06 Thread Jan Corazza
** Attachment added: dmesg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377820/+attachment/4226217/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377820 Title:

[Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt

2014-10-06 Thread Jan Corazza
** Attachment added: sudo lspci -vvnn https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377820/+attachment/4226216/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377820

[Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt

2014-10-06 Thread Jan Corazza
** Attachment added: uname -a uname-a.log https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377820/+attachment/4226215/+files/uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377820

[Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt (kernel 3.17)

2014-10-06 Thread Jan Corazza
As I said Joseph, this was reported after I manually fixed my computer by removing the mainline kernel. Only the kernel version has changed, everything else is the same on the system. ** Summary changed: - Computer not suspending when inactive in the main log-in prompt + Computer not suspending

[Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt (kernel 3.17)

2014-10-07 Thread Jan Corazza
I posted this from school so I wasn't paying full attention - I had a totally different bug in mind when I made that edit! Actually all of this **does** happen in 3.13 - something unrelated happens in 3.17. So basically all info I gave originally is correct. Can you validate the bug again? I

[Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt (official 3.13 kernel)

2014-10-07 Thread Jan Corazza
Hey, what do I need to do to complete the bug report? And why were the files removed? They contained correct information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377820 Title: Computer not

[Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt (official 3.13 kernel)

2014-10-07 Thread Jan Corazza
Hey, what do I need to do to complete the bug report? And why were the files removed? They contained correct information. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1377820 Title: Computer not

Re: [Bug 1377820] Re: Computer not suspending when inactive in the main log-in prompt (official 3.13 kernel)

2014-10-08 Thread Jan Corazza
: Jan Corazza, just to clarify, before you installed a mainline kernel, suspend was working, and afterwards it was not? -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1377820 Title: Computer not suspending when inactive

[Bug 1379704] [NEW] home, Network places, and Trash icons on the desktop are not searchable

2014-10-10 Thread Jan Corazza
Public bug reported: How to reproduce: 1. Enable the said icons to be displayed on the desktop, in Unity Tweak Tool: System-Desktop icons, click on the first three 2. Go to the desktop 3. Try to search for one of those newly-enabled icons What I expected to happen: - The searched icon would

[Bug 1385494] [NEW] Guake flashes white when closing

2014-10-24 Thread Jan Corazza
Public bug reported: When I switch on Guake, it opens normally by fading in. However, when I hit F12 again, it doesn't fade away, but flashes white while animating the exit (becoming smaller). This is extremely annoying because I often use darker backgrounds. - Ubuntu version: 14.10 -

[Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking

2014-10-29 Thread Jan Corazza
After typing the text, selecting it, and copying it with Ctrl+C, I did experience a similar issue. The gedit cursor did disappear, but I think that's normal - it disappears when you select text. But when I copied the text, the mouse curor disappeared as well, which was not expected. It also

[Bug 1387219] Re: Mouse pointer disappears and cursor stops blinking

2014-10-29 Thread Jan Corazza
Update: the flickering effect also happens when I press Ctrl, Shift, and escape. Practically any button which does not change the state of the document causes the effect it would seem. Please confirm whether this corresponds to the bug you are experiencing as well. -- You received this bug