** Summary changed:
- Indicator-Datetime always shows UTC time for any online calendar added to
evolution
+ Indicator-Datetime always shows UTC time for any online calendar added to
evolution (Unity7, Xenial)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
[Expired for QtMir because there has been no activity for 60 days.]
** Changed in: qtmir
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1
[Expired for unity8 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: unity8 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.
[Expired for qtmir (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qtmir (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.la
[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]
** Changed in: xorg (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launch
I just discovered this issue in a newly upgraded version of Lubuntu
15.10. I tried two of the possible solutions in this thread. The "sudo
openvpn --config file.ovpn" doesn't work for me, it gives an error:
"Error: Object 'nm' is unknown"...This DNS leak is really annoying
because it makes my
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1068756
Title:
IPv6 Privacy Extensions enabled on Ubuntu Server by default
Status in cloud-init packag
Well, living with a single monitor for a while and seeing whether that
fixes the problems.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1509326
Title:
Various instabilities
I can't file reports for different issues because I can't even name a
single issue. All I'm seeing is sporadic but nonreproducible, somehow
related failures. Some of them may be unrelated, some of them might be
misconfiguration leftovers from previous installs or attempts at getting
the machine to
Joachim Durchholz, to advise, the only issue that this report is scoped
to is the resume from standby. For each issue different from this (ex.
resuming from hibernate, issues that occur after restarting or coming
back from a shutdown, etc.), you would want to file separate reports,
one per issue.
Public bug reported:
Screen is constantly dim. Tried updating intel GPU driver, updated from
Ubuntu 14.04 to 15.10, tried various fixes via google search. Nothing
works.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1526987
Title:
package systemd 225-1ubuntu9 failed to insta
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1518681
Title:
NM failed to initialize WiFi
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1527854
Title:
package linux-image-4.3.0-2-
I run an alias to do my updating and it's this:
sudo apt-get update && sudo apt-get upgrade && sudo apt-get autoclean
When the update happens and there is a kernel waiting to be dist-upgraded I
believe the
/etc/apt/apt.conf.d/01autoremovekernels file has been manipulated to include
parts of the
Łukasz, are you going to merge fully Network Manager 1.0.10 from Debian?
I'd like to know since I opened a new bug 1529294.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/
Public bug reported:
network-manager (1.0.10-1) unstable; urgency=medium
* New upstream release.
* Bump Build-Depend on libsoup2.4-dev to (>= 2.40) as per configure.ac.
* Rebase patches.
-- Michael Biebl Thu, 24 Dec 2015 00:43:55 +0100
network-manager (1.0.8-2) unstable; urgency=medium
The attached script leaves more kernels than one. It keeps some
automatically installed kernels, even if there are also newer manually
installed kernels such as upstream kernels installed.
(https://wiki.ubuntu.com/Kernel/MainlineBuilds)
** Attachment added: "Fixed /etc/kernel/postinst.d/apt-auto-
Can you give me some instructions how to nail down the actual cause of these
problems?
The symptoms are so varied and instrutable, it almost looks as if some race
conditions deep down in the software stack leave stuff in inconsistent state.
Logging pertinent status information for each startup mi
I already have nvidia-352 installed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1509326
Title:
Various instabilities after resuming from standby
Status in xorg package i
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/b
It is hard to know, if /etc/kernel/postinst.d/apt-auto-removal is called
in conjunction with removing a kernel or installing a kernel. The kernel
in question, whose version is passed as a command line argument, has
"install" as desired action according to dpkg at the time of calling the
script anyw
Glancing at DpkgTerminalLog.txt, you are doing weird things that will
kill your installation. Glad enough it does not let you do so, and push
that 'false' error to alert you.
Take time to learn how to update/upgrade by reading the howto/kiwi from the
community.
https://help.ubuntu.com/community/U
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: sudo (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bug
Please check if this is the same bug as bug #1368063.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu-camera in Ubuntu.
https://bugs.launchpad.net/bugs/1322121
Title:
pictures taken with flash are almost completely
Please check if this is the same bug as bug #1322121.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to camera-app in Ubuntu.
https://bugs.launchpad.net/bugs/1368063
Title:
[Nexus 4] The photo captured by Camera app show dark
Public bug reported:
Ok so.. i have a ASUS K450J Laptop and i have had Ubuntu through the last year
without any issues until now. I recently formatted my pc to fix my keyboard
issue but to no avail.
A few days ago my backspace button didn't delete and just added the character
p and p button w
MoonSky219, given this report is closed, if you would like your issue addressed
then please file a new report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
For more on this, please see https://wiki.ubuntu.com/ReportingBugs .
** No longer affects: network-manager (Ubun
More comment:
Pulseaudio strictly now needs:
- 'hda' bios setting (not ac97)
- jacks correctly plugged as expected: aka, strict same colors
then check the sound config/settings (via pavucontrol/paprefs)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
mohammad, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1307168/comments/8
regarding this being fixed with an update. For future reference you can
manage the status of your own bugs by clicking on the current status in
the yellow line a
Joachim Durchholz, regarding
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1509326/comments/3
what version of the nvidia driver are you using?
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
@Thomas
same issue found like yours:
https://askubuntu.com/questions/700167/no-sound-on-ubuntu-15-10
( still beleive in installing the latest packages/drivers to get support
(kernel/drm, ...) maybe try
https://launchpad.net/~ricotz/+archive/ubuntu/testing & staging)
Some googling can help find
Thanks for your response, dino99. But same with
4.4.0-040400rc6-generic:
[ 10.638237] snd_hda_intel :00:1f.3: No response from codec,
disabling MSI: last cmd=0x000f
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to al
** Description changed:
System: Asus S400CA with Linux Mint 17.3 Rosa, kernel 3.19.0-39-generic
#44~14.04.1-Ubuntu SMP Wed Dec 2 10:00:35 UTC 2015 x86_64 x86_64 x86_64
GNU/Linux
Running Skype, sound input from microphone does not work. When (in
alsa-mixer OR in pavucontrol) one chann
As regards comment #49: this
(http://forums.linuxmint.com/viewtopic.php?f=49&t=177730) is what
happened and how I solve it. Nothing to do with an inverted microphone.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-drive
Public bug reported:
Every time I try to play a youtube video the entire system freezes, a logout
sound plays but display remains black.
Ctrl + Alt + F1 has no effect only Ctrl + Alt + Del which restarts the system.
Ubuntu 14.04 with all updates installed.
ProblemType: Bug
DistroRelease: Ubuntu
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: mpg123 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mpg123 in Ubuntu
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: modemmanager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to modemmanag
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: rsyslog (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubun
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: procps (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: eject (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eject in Ubuntu.
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: usbmuxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to usbmuxd in Ubun
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: gconf (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gconf in Ubuntu.
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: qt4-x11 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubun
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: xz-utils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xz-utils in Ub
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: sysvinit (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ub
I think apt-get autoremove may even delete the current kernel, if you
run /etc/kernel/postinst.d/apt-auto-removal, boot to an older kernel
and then run apt-get autoremove. However, maybe that is not big issue,
since there is still another kernel that you can boot next time (if you
haven't removed
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: gstreamer0.10 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: shadow (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: rsyslog (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubun
That version is no more supported; and no expecting backport as it only
concern 'security' problem.
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
My two cents,
you have some recent hardwares but use quite old kernel. Your issue is
expected, and the solution is to use recent release/kernel with recent hardware.
Either dist-upgrade (or better do a fresh install to avoid possible settings
conflict disturbing the system) to at least wily or
Same on Ubunto 16.04 Daily Build (4.3.0-2-generic #11-Ubuntu SMP Fri Dec
4). The bug report is "incomplete" - what can I do to make it complete
or to help to fix it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver
65 matches
Mail list logo