*** This bug is a duplicate of bug 1459571 ***
https://bugs.launchpad.net/bugs/1459571
** This bug has been marked a duplicate of bug 1459571
Keyboard shortcuts stop working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Ubuntu is successfully closing TICKETS again. Hooray!
Too bad that analyzing and fixing PROBLEMS takes such a backseat these
days...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[R
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
T
** This bug is no longer a duplicate of bug 1354180
Regression: Ctrl+Alt+T shortcut, volume & printScreen keys randomly stop
working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
*** This bug is a duplicate of bug 1354180 ***
https://bugs.launchpad.net/bugs/1354180
Users observing issue 1354180 (including me) seem to always observe this
issue at the same time, so marking this as duplicate of that one, which
has been confirmed.
** This bug has been marked a duplicate o
By the way:
> by not testing the upstream kernel, you are limiting the developers who are
> going to look at this to only downstream (Ubuntu) developers.
And by marking it as incomplete and let it expire, you are limiting the
developers who are going to look at this to nobody.
--
You received t
FIRST
>Hence, if you are not willing to help debug this at all, how would you
expect any developers to want to work on your issue?
It is not "my" issue, it's everybody's issue. I just happen to be
somebody who experienced and reported it.
I don't "expect" anything from any developer if by "exp
Teo, by not testing the upstream kernel, you are limiting the developers
who are going to look at this to only downstream (Ubuntu) developers.
Hence, if you are not willing to help debug this at all, how would you
expect any developers to want to work on your issue?
** Changed in: linux (Ubuntu)
I'm not upgrading the BIOS (nonsense requirement) and I'm not testing
the mainstream kernel (no time to do that).
That should not be a reason for closing the bug. I have reported it and it's as
much as I can do.
This might not even be in the kernel, I reported it against linux just because
I hav
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
T
If the bug is fixed in the mainline kernel, please set this bug status
back to "confirmed". Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[REGRESSION 2014-08] Volume up/dow
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.19 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
> Why do you think asking to upgrade your BIOS is rigid criteria?
Asking to upgrade the BIOS is fine.
Refusing to look into the issue unless the BIOS is updated is ridiculous.
Updating the BIOS is a tremendously cumbersome (and risky) process for a
user whose main working OS is Ubuntu. Hence mos
teo1978:
> That's funny. Have you ever considered how dismissing tons of bug
> reports just because they don't meet some rigid criteria is actually
> disrespectful to those who took the time to report them, if not to
> users who simply suffer from them?
Why do you think asking to upgrade your BIOS
In reply to
> @Teo, for the future, you can also report bugs against
> Ubuntu itself without pre-assigning any package at all.
I'll try next time.
I gave up trying that long ago because
1)
$ ubuntu-bug ubuntu
dpkg-query: no packages found matching ubuntu
2) The "Report a bug" link used to point
> along with if you remember when the computer had last been rebooted
before you did last reboot you mention in this bug report.
Sorry, no idea. I usually only suspend and resume. I only shut down
when I have to carry the laptop somewhere, in which case I either
actually shut down or just hiberna
> Teo, could you please confirm whether or not you've used hibernate again and
> if it has triggered the bug?
> You mention later that it happens randomly, but I just want to make it very
> certain that it can't be reliably
> triggered by hibernation... rather than assuming anything.
I'm sorry,
apt log history
** Attachment added: "history.log.4"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/+attachment/4283714/+files/history.log.4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
> if someone treats you steadily disrespectful there's
> no single reason for continuing the business. Because there's no single
> excuse for mistreating other people.
That's funny. Have you ever considered how dismissing tons of bug
reports just because they don't meet some rigid criteria is ac
There were mentions of it happening after a resume from hibernate. Teo,
could you please confirm whether or not you've used hibernate again and
if it has triggered the bug? You mention later that it happens randomly,
but I just want to make it very certain that it can't be reliably
triggered by hib
When you have upgraded your BIOS, if this bug reproduces again, please
set this bug status back to confirmed. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[REGRESSION 2014
@Teo, for the future, you can also report bugs against Ubuntu itself
without pre-assigning any package at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[REGRESSION 2014-08] Volum
I won't say sorry for the typos (typing from mobile) because i'd edit my
comment if i could.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[REGRESSION 2014-08] Volume up/down keys, an
Can't tell, sorry.
I only use Unity, and as i mentioned this only occurs sporadically, very
rarely, and with no way to reproduce at will that i know of. (I did see it
again not long ago, btw)
So even if i tried a given shell for the sake of it, i couldn't but wait for
ages for it to happen or no
Teo can you reproduce the same problem on different shells (gnome shell,
gnome classic, etc)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[REGRESSION 2014-08] Volume up/down keys, a
Rolf Leggewie, first, please again stop being rude by calling me a bot.
As you have signed the Ubuntu Code of Conduct, and as a Ubuntu community
member representing Ubuntu Bug Control, you have attested to be someone
who is respectful, and considerate. However, calling me a bot,
unreasonable, etc.
@penalv-bot: I will not even try to reason with you, because you have
amply demonstrated over the years you cannot be reasoned with and all
you are concerned about is to get tickets "off-radar". My interest is
in fixing problems not in closing tickets or reasoning with unreasonable
people.
I am i
Teo, with all the links that the penalv-bot had been spewing about he
forget the one that might actually be helpful. Please have a look
through https://wiki.ubuntu.com/Hotkeys/Troubleshooting and see if you
can gather some information that would be helpful in nailing this issue
down. It would cer
** Tags added: vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[REGRESSION 2014-08] Volume up/down keys, and printScreen key, have
stopped working
To manage notifications about
Rolf Leggewie, thank you for your comment. First, I wanted to apologize
if you were offended by my removing the bug task you added, or words I
chose to use. It was not meant to anger you, but there has been no
technical evidence presented so far that this is a unity instead of a
linux kernel issue.
On 18.12.2014 04:53, Christopher M. Penalver wrote:
> Rolf Leggewie, please do not add bug tasks unless you can point to the code
> precisely that is at fault.
Yadda, yadda.
Dude, you must be by FAR the single most-hated guy on LP. You must hear
to get lost and leave people alone at least a goo
Rolf Leggewie, please do not add bug tasks unless you can point to the code
precisely that is at fault. If you have a bug in Ubuntu, and so your problem
and hardware may be tracked, could you please file a new report with Ubuntu by
executing the following in a terminal while booted into the defa
I just ran into this in my vivid test installation (no, just like the
OP, I will not jump through silly hoops requested from the penalv-bot
only to have the issue at hand ignored). Setting to 'confirmed' and
'affecting me'. In fact, my computer hung after I tried the volume
keys.
As with almost
Readding unity to the ticket since bug 1354180 is being triaged there as
well
** Also affects: unity (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
I did not add a *random* package. I added the most generic one that I
could think of, as this is probably not in the linux package, and the
linux package is the one that has this stupid policy of not taking bug
into consideration unless they are reported on the latest bios.
--
You received this b
Teo, please do not add random packages to this report. While this report
isn't being ignored, as previously outlined to you, bugs can manifest
themselves after package upgrading due to an outdated BIOS.
** No longer affects: unity (Ubuntu)
--
You received this bug notification because you are a
It's no surprise that Ubuntu is still what it is as long as bug reports
get managed this ridiculous way.
This issue is intermittent, happens randomly, and is a regression (i.e. has
started happening at a certain update, never happened before).
Ignoring it just because the reporter doesn't have th
It's no surprise that Ubuntu is still what it is as long as bug reports
get managed this way.
This issue is intermittent, happens randomly, and is a regression (i.e. has
started happening at a certain update, never happened before).
Ignoring it just because the reporter doesn't have the latest bi
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
T
I had a few reboots without observing the issue.
Now, after resuming from an hibernation (not suspension), the issue has
reappeared. I don't know if hibernation is what triggers the issue or if
it is just intermittent.
Could you please forget the bios bullshit and mark this bug as confirmed
and a
What needs to happen?
That I update the bios? That's definitely not going to happen (what
needs to happen is that ubuntu provide a decent way of upgrading bios
without relying on booting other OSes).
And there's no reason why you should need me to update the bios, when this
regression has happen
Teo, it still needs to happen. Please do not toggle the Status until
it's completed as noted in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1353129/comments/4
.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a m
:O Oddly, after rebooting the issue disappeared...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1353129
Title:
[REGRESSION 2014-08] Volume up/down keys, and printScreen key, have
stopped working
** Summary changed:
- Volume up/down keys, and printScreen key, have stopped working
+ [REGRESSION 2014-08] Volume up/down keys, and printScreen key, have stopped
working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
44 matches
Mail list logo
