I can reproduce this bug
** Changed in: libvirt (Ubuntu)
Status: Invalid = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1386465
Title:
apparmor profile prevents
Public bug reported:
Ubuntu Trusty seems to be affected by the scenario number 1 described in
this post on OpenSSL's bug tracker:
http://rt.openssl.org/Ticket/Attachment/45105/25601/
To summarize, verifying the peer's identifer fails when the peer's DN
contains a component of ASN.1 type
** Branch linked: lp:~ubuntu-branches/debian/experimental/dbconfig-
common/experimental
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/584943
Title:
Problem with a password
** Branch linked: lp:~ubuntu-branches/debian/experimental/dbconfig-
common/experimental
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/520872
Title:
dbconfig-common:
** Branch linked: lp:~ubuntu-branches/debian/experimental/dbconfig-
common/experimental
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dbconfig-common in Ubuntu.
https://bugs.launchpad.net/bugs/252882
Title:
crash on multiple db
Please try with Unity. I have no idea how much you have removed nor how
to restore them. You can try to install ubuntu-desktop, but not sure if
it will reinstall unity.
You opened bug for gnome-panel... If it will crash in Unity than it is
not bug in gnome-panel, but in other pacakge.
And please
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
** Changed in: compiz
Status: New = Invalid
--
You received this bug notification because you
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
** Changed in: compiz
Status: New = Invalid
--
You received this bug notification because you
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
** Changed in: compiz
Status: New = Invalid
--
You received this bug notification
Reproduced again this morning, but did not affect super-w shortcut. Also
new : numlock LED is off, but the function is on. Pressing it twice re-
enable it, but it goes off again after a few minutes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
** Changed in: compiz
Status: Confirmed = Invalid
--
You received this bug notification
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
** Changed in: compiz
Status: New = Invalid
--
You received this bug notification
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: mesa (Ubuntu)
Status: New = Invalid
** Changed in: compiz (Ubuntu)
Status: New = Invalid
** Changed in: compiz
Status: New =
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
** Changed in: compiz
Status: New = Invalid
--
You received this bug notification because you
The issue was fixed sometime back during regular updates provided by the
Update Manager. I am now able to start Nautilus as root on Ubuntu
14.04..
The status of the bug should be changed. I am not doing it myself, since
I am a bit unexperienced and not sure if bugs that are fixed during
regular
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
** Changed in: compiz
Status: New = Invalid
--
You received this bug notification because you
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz
Status: New = Invalid
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification
The issue I've faced is that somehow the media key of X86PlayPause event
cannot be thrown if not the xbindkeys package is sending it through that
specific setting.
It could be that somewhere else I've set some setting for that to
happen, but I have no idea where to look.
I've now purged
Please let the user decide if using a /tmp noexec mount point is more
secure or not.
That doesn't even make sense. It's a fact that mounting /tmp with
noexec doesn't give you any extra security simply because you can
simply circumvent it by invoking the executable with the help of the
dynamic
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I believe this bug was more to do with full localisation rather than
just language packs, hence it was assigned to the LoCo and was a general
Ubuntu bug. For further detail please see the linked blueprint in the
comments.
I'm going to change it back to what it was prior to the recent changes,
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407263
Title:
package libkio5 (not installed) failed to install/upgrade: cannot copy
extracted data for
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: Incomplete = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please consider sponsoring the attached changes:
* Mark libopus0, libopus-dev and libopus-dbg as Multi-Arch: same.
(LP: #1404475)
* Update the symbols file.
** Patch added: opus_1.1-0ubuntu2.debdiff
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1. gnome-contacts bug of course for gnome-contacts package.
2. menu bug for gnome-panel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407015
Title:
Both nemo and nautilus chrash when opening a
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
EOL have been reached, so no more maintenance. If that issue still
exist, then report again using ubuntu-bug.
** Changed in: metacity (Ubuntu)
Status: Confirmed = Invalid
** Changed in: exaile (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you
Launchpad has imported 32 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1034337.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Still buggy here. Elementary OS Freya
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1218322
Title:
Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
To manage notifications about
My computer has slow boot times because this error
Tail of dmesg
[ 44.672089] input: Bluetooth Laser Travel Mouse as
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/bluetooth/hci0/hci0:35/input12
[ 44.672198] hid-generic 0005:046D:B008.0001: input,hidraw0: BLUETOOTH HID
v3.13
Public bug reported:
when mail arrives, the number will show in the tux, but the tux does not
shake its wings (nor jump)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gnubiff 2.2.15-3
ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
Uname: Linux 3.13.0-43-generic x86_64
+1 thank you Ruslan.
I'm guessing that at this point we should be asking for this to be
implemented on Wayland, as it seems that X will be deprecated soon
enough and its input code is complex and strange enough (no screensaver
when a pop-up menu is open, for instance) that this won't make it.
--
Thank you Ruslan. I do stress to the developers that this is a
workaround, not a solution, due to issues such as the user of sticky
keys.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/531208
Title:
+ 10 for the implementation of this UNICODE-FEATURE.
At the moment I'm coding on a Keyboard-Firmware (ErgoDox). Problem is
that I can send UNICODE-Chars easy and nice with the GNOME-Method :
CTRL+Shift+digits, but there is no way to send them to QT-Based
Programms.
So keep calm and implement the
This time I got it right. The USB vendor:product description needs to be
in the blacklist section of the btusb file; it only worked by chance the
first time I tried; now it works after a reboot. (We have to prevent
btusb from managing this before its firmware is loaded or whatever, see
ath3k on
Hi Stephane,
Can you see if this issue was already fixed in the latest 3.13 upstream kernel:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13.11-ckt13-trusty/
If it was not, we can bisect the issue.
It might also be worth testing the latest mainline kernel, to see if this issue
came down
dino99:
That version has reached EOL since a while, so it will not receive update.
...
status: Confirmed → Invalid
AFAIK, you should instead use the Incomplete bug status in such cases
(in 60 days of inactivity it automatically gets Expired):
https://wiki.ubuntu.com/Bugs/Bug%20statuses
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: unity (Ubuntu)
Status: Incomplete = Invalid
** Changed in: compiz (Ubuntu)
Status: Incomplete = Invalid
** Changed in: unity
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Incomplete = Invalid
** Changed in: compiz
Status: New = Invalid
--
You received this bug notification
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
** Changed in: compiz-core
Status: New = Invalid
** Changed in: compiz
Status: New =
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Fix Committed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The issue I described in post #39 is still present (I'm stuck to
ubuntu-drivers-common to version 1:0.2.91.4), but seems what I described is a
different bug than many users reported here. What I need to do? Open a new bug?
Thanks
--
You received this bug notification because you are a member
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: debdiff
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1407241/+attachment/4291552/+files/debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1407241
Title:
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
same problem with an ASRock Q1900DC-ITX Mainboard.
It has 4 external ports - the 2 external USB 2 ports work without problems -
but on the 2 USB 3 no device works without problems (even mouse and keyboard
only work after they are pluged-out and in again after each restart).
--
You received
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Confirmed = Invalid
** Changed in: compiz
Status: Triaged = Invalid
--
You received this bug notification
Public bug reported:
.
** Affects: transmission (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/1407241
Title:
please merge transmission
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
That version has reached EOL since a while, so it will not receive
update. If that issue still exist, report again using ubuntu-bug.
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
apport information
** Tags added: apparmor apport-collected
** Description changed:
What is expected to happen is when one opens
https://launchpadlibrarian.net/179309521/example.pdf in Evince and
prints to either a Canon Pixma MG3540 or a Ricoh SP 202SN, it prints
correctly.
What
apport information
** Attachment added: Locale.txt
https://bugs.launchpad.net/bugs/1337956/+attachment/4291627/+files/Locale.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337956
Title:
apport information
** Attachment added: KernLog.txt
https://bugs.launchpad.net/bugs/1337956/+attachment/4291626/+files/KernLog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337956
Title:
apport information
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/1337956/+attachment/4291625/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337956
apport information
** Attachment added: Lpstat.txt
https://bugs.launchpad.net/bugs/1337956/+attachment/4291628/+files/Lpstat.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337956
Title:
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1337956/+attachment/4291624/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1337956
Looks like the bug is related on conflict of the modules rts5139 (card
reader) and uvcvideo (webcam). After some googling i've blacklisted the
rts5139 module and the webcam is being detected fair. Then I've tested
the problem with both modules and mainline kernel
3.15.0-031500rc2-generic
Public bug reported:
Ubuntu Trusty seems to be affected by the scenario number 1 described in
this post on OpenSSL's bug tracker:
http://rt.openssl.org/Ticket/Attachment/45105/25601/
To summarize, verifying the peer's identifer fails when the peer's DN
contains a component of ASN.1 type
** Changed in: xfce4-terminal (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1023826
Title:
xfce4-terminal freezes on mouse input
To manage
** Tags added: kernel-bug-exists-upstream kernel-bug-exists-
upstream-3.15.0-031500rc2-generic
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug also appears to happen on my Dell Inspiron 13 7347. Is there
any information I can provide to help find an actual resolution?
Thanks, odie, for the work-around; I'm going to give that a shot here in
a minute.
--
You received this bug notification because you are a member of Ubuntu
BTW both the onboard devices are attached to the same USB bus.
** Summary changed:
- Lenovo Ideapad S 205 - webcam is not detected after installing 14.04 (works
well on 12.04l)
+ Lenovo Ideapad S 205 - webcam is not detected after installing 14.04 (works
well on 12.04)
--
You received this
Please test with 0.9.9+svn6422+dfsg1-2 and let us know if the problem
still exists.
** Changed in: handbrake (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: codelite (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1210500
Title:
Upload latest version to Ubuntu archives
To manage
** Changed in: synaptic (Ubuntu)
Assignee: (unassigned) = Weiller (weillerronfini)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405928
Title:
Deprecated properties in synaptic
To manage
merci
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1287571
Title:
can not upgrade saucy to trusty
To manage notifications about this bug go to:
Problem still happening after BIOS upgrade. Requested info below:
$ sudo dmidecode -s bios-version sudo dmidecode -s bios-release-date
1003
06/11/2009
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In Evince upstream, we have seen similar reports in the past, but all of
them have turned out to be Ubuntu specific (i.e. issues with apparmor).
As per comment https://bugzilla.gnome.org/show_bug.cgi?id=661936#c9:
File named test:
[12219.529055] type=1400 audit(1420318053.543:106):
1 - 100 of 475 matches
Mail list logo
