Another Linux user with the same problem in AppArmor. Access the link.
https://forum.eset.com/topic/17266-apparmorselinux-support/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
Having `easy_install` available (or something similar) is likely an
ongoing need for at least one reason. If a user wants their system to
stay on the latest/upstream version of pip, one sensible way of doing
this is to install the `python-setuptools` package and use
`easy_install` to install `pip`
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
** This bug is no longer a duplicate of bug 1768625
Bluetooth headset HSP/HFP mode not working in Bionic
** This bug has been marked a duplicate of bug 1576559
Refused to switch profile to
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
** This bug has been marked a duplicate of bug 1576559
Refused to switch profile to headset_head_unit: Not connected
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
** This bug is no longer a duplicate of bug 1768625
Bluetooth headset HSP/HFP mode not working in Bionic
** This bug has been marked a duplicate of bug 1576559
Refused to switch profile to
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
** This bug has been marked a duplicate of bug 1576559
Refused to switch profile to headset_head_unit: Not connected
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
** This bug is no longer a duplicate of bug 1768625
Bluetooth headset HSP/HFP mode not working in Bionic
** This bug has been marked a duplicate of bug 1576559
Refused to switch profile to
Public bug reported:
I'm running ubuntu 18.04, and I've verified that this is true on two
different installs (one fresh, one updated from 16.04).
I wanted to load three modules from pulseaudio (module-ladspa-sink,
module-loopback, module-null-sink), but it kept saying "Failure on
module
And your fix helps:
Still with SRU version installed:
$ cat /sys/class/dmi/id/modalias
dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr:
So, edit edit /lib/udev/hwdb.d/60-keyboard.hwdb:
It seems as though the issue is in job_class_induct_job()
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/568860
Title:
init: "before" functionality should block all
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/358586
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
The patch to resolve this bug was just accepted to upstream gnome-shell
master: see https - gitlab.gnome dot org/GNOME/gnome-
shell/merge_requests/140 (For some reason launchpad is not letting me
submit a comment with a URL).
Might it be possible to back-port this patch to GNOME Shell 3.28 for
Public bug reported:
In order to support live migration in OCI, we need to filter enslaved
devices during boot.
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Assignee: Marcelo Cerri (mhcerri)
Status: In Progress
--
You received this bug notification because you
I add this extra information in case it works:
I have some "Bluedio F2" brand headphones that do not activate the microphone,
however, my Philips SHB4000 hearing aids detect them without any problem (the
input).
Where in Windows and Android the Bluedio & Philips Microphone works for me
without
Public bug reported:
Ubuntu worked perfectly with me twice only i don't know why its freezing
when i open any app cant even access ctrl alt f1
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux
This was fixed in Ubuntu 18.04 LTS. It can't be fixed in Ubuntu 17.10
since that release has reached End of Life.
** Also affects: gdebi (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: gdebi (Ubuntu Artful)
Status: Triaged => Won't Fix
** Changed in: gdebi
I've added a similar comment / request on this related launchpad bug:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1794655
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
Can confirm this bug as well. Bluetooth remains discoverable from other
devices when Bluetooth is On. - Thinkpad X220
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559
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
Edson, you have a different issue.
If you want to use ESET then you should add:
/tmp/esets.sock rw,
to the /etc/apparmor.d/abstractions/base file and run:
sudo systemctl reload apparmor
Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
As can be tested using this example snap:
- https://github.com/3v1n0/notify-send-test-snap
Basically the icons are referenced using absolute paths in snap
environment, while they should be readapted so that they depend on $SNAP
location.
As we do with appindicators and
Libnotify fix for xenial
** Patch added: "libnotify_0.7.6-2svn1-xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5210727/+files/libnotify_0.7.6-2svn1-xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch
Fix for bionic (and cosmic)
** Patch added: "libnotify_0.7.7-3+snap-support.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5210728/+files/libnotify_0.7.7-3+snap-support.debdiff
** Patch removed: "libnotify_0.7.6-2svn1-xenial.debdiff"
Public bug reported:
After upgrading to Ubuntu 18.10, the system won't boot any more
correctly. When booting, it will get stuck at a purple screen and never
show the login screen. Selecting the recovery boot in GRUB and continue
the boot in the recovery boots the system correctly. dmesg shows a
** Patch added: "libnotify_0.7.6-2svn1+snap-fix.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5210729/+files/libnotify_0.7.6-2svn1+snap-fix.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Hello Fred, or anyone else affected,
Accepted gnome-shell into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.28.3-0ubuntu0.18.04.3 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
Fix for disco (but could be used for bionic too) is at:
https://code.launchpad.net/~canonical-desktop-
team/ubuntu/+source/libnotify/+git/libnotify/+ref/ubuntu/master
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify
Below are the information about this slowdown problem:
1.cups-filters version:
Ubuntu 16.04：cups-filters 1.8.3-2ubuntu3.4
Ubuntu 14.04：cups-filters 1.0.52-0ubuntu1.7
2.Print file:
Log_PrintFile_Drivers.zip/j9_5Page.pdf
3.CUPS error_log
Log_PrintFile_Drivers.zip/error_log14.04
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mesa (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
And the Qt team are now working on implementing the patch, so this
should be resolving in a forthcoming Qt release :-) See
https://bugreports.qt.io/browse/QTBUG-71488
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The issue you are reporting is an upstream one and it
would be nice if somebody having it could send the bug to the developers
of the software by following the instructions at
-- Původní e-mail --
Od: Daniel van Vugt
Komu: jiri.taraso...@seznam.cz
Datum: 9. 11. 2018 3:19:11
Předmět: [Bug 1802402] Re: [UX430UNR, Realtek ALC294, Black Headphone Out,
Left] No sound
"Please run this command:
dpkg -l > allpackages.txt
and then send us the resulting file
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libdrm (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
I have found the source of the bug and provided a patch: see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913287
** Bug watch added: Debian Bug tracker #913287
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913287
--
You received this bug notification because you are a member of
** Description changed:
As can be tested using this example snap:
- - https://github.com/3v1n0/notify-send-test-snap
+ - https://github.com/3v1n0/notify-send-test-snap
Basically the icons are referenced using absolute paths in snap
environment, while they should be readapted so that
Guys ..
I have Nvidia 1050ti with nvidia-390 driver installed.
When i boot am on 900 resolution instead of a 1920x1080 normal
resolution.
Anyone got a solution for that ??
Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Public bug reported:
[impact]
udev (in trusty) does not create symlinks in /dev/disk/by-path/ for any
disks that are connected via sata.
[test case]
Install trusty onto a system with sata drives, and check /dev/disk/by-
path/ for symlink(s) to those sata drive(s).
[regression potential]
the
Hi,
Although on Xenial the problem is solved, I'm having same problem on
Bionic where is installed the libsphinxbase-dev 0.8+5prealpha+1-1.
I need to modify the following sources:
/usr/include/x86_64-linux-gnu/sphinxbase/ad.h
/usr/include/x86_64-linux-gnu/sphinxbase/prim_type.h
changing from
The error reported is:
unable to create '/etc/debian_version.dpkg-new' (while processing
'./etc/debian_version'): Read-only file system
You can certainly not upgrade packages while /etc is on a read-only
filesystem.
** Changed in: base-files (Ubuntu)
Status: New => Invalid
--
You
This bug is closed. If you have any problem at all then please open a
new bug.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1734960
Title:
Bluetooth headset profile
Public bug reported:
After I updated my server (no GUI) from 16.04 to 18.04 my system sometimes gets
stuck in emergency mode.
Normally my system needs about 20 seconds to get through the dmesg part, and
then another 2-5 seconds until the login prompt.
The dmesg part is still fine but, after
Same problem here using Ubuntu 18.04 with Sony WH-1000XM2.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1724919
Title:
Bluetooth headphones only use A2DP when
Public bug reported:
On switching to a new session, the existing session is closed and the
new opens at the same VT1.
Xorg crashes and restart, thus assigning VT1
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic
The attachment "libnotify_0.7.7-3+snap-support.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the
** Attachment added:
"1300661580_Capturadetelade2018-11-0715-25-33.png.8d71b9001fd8d3da9071dfeacf640e3d.png"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1802498/+attachment/5210799/+files/1300661580_Capturadetelade2018-11-0715-25-33.png.8d71b9001fd8d3da9071dfeacf640e3d.png
--
Public bug reported:
Hello Canonical team - Ubuntu
Eset Antivirus has some problems with apparmor.
In Eset I have observed in the last weeks that the updates are being
carried out, but the logs that have been installed successfully, where
it was in bold, no longer appear.
I also realize that
** Changed in: tracker (Ubuntu)
Status: Fix Committed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tracker in Ubuntu.
https://bugs.launchpad.net/bugs/1797224
Title:
Stay on 2.0 for cosmic, update next
Public bug reported:
TILIX SCREEN AFTER "SUDO APT UPDATE"
Сущ:13 http://fr.archive.ubuntu.com/ubuntu bionic-proposed InRelease
Сущ:14 http://ppa.launchpad.net/tista/adapta/ubuntu bionic InRelease
Сущ:15 http://security.ubuntu.com/ubuntu
Ok, so after some debugging the fix is working but it hits a bug on some
Dell laptops
>From my Inspirong 11 debugging
- sudo evemu-record
press the airplane key
-> double events are generated
then to fix it
- cat /sys/class/dmi/id/modalias and see what the "pn" is
- edit
Confirmed on Ubuntu 18.04.1 LTS, Evolution 3.28.5-0ubuntu0.18.04.1,
using EWS.
The usual workaround (delete cfg, cache and pkill) works fine.
https://askubuntu.com/questions/459504/evolution-appears-unable-to-store-mail-account-details
--
You received this bug notification because you are a
I'm also having an issue with my ux391ua running MATE18.04 with no
Windows 10 installed. There is sound output audible with headphones on
and volume >100% but it is very distorted and crackly. 18.10 was not
helpful and updating kerenel to 19 doesn't change anything.
aplay -l
List of PLAYBACK
I believe the issue was originally created by that systemd change,
https://github.com/systemd/systemd/pull/8762
I've submitted a revert on https://github.com/systemd/systemd/pull/10709
That change is going to have things working as designed, at least on the
Inspiron but I'm unsure your issue is
Public bug reported:
I have a fresh install of 18.10 on an old Thinkpad x220. Everything
works fine with the internal display or an external Dell G2410
(1920x1080) connected via VGA. But when I try to switch to an external
BenQ PD2710QC (2560x1440) I only see the screen for a few seconds at a
Public bug reported:
I;m usin geforce 8800GT
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..1c.00.0: Error:
** Changed in: totem
Status: Confirmed => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu.
https://bugs.launchpad.net/bugs/604333
Title:
Every second screenshot in created screenshot
Public bug reported:
I ran `ubuntu-bug gnome-terminal`, but then realized a second or so
later that's not what I had intended to do. I therefore clicked the
Cancel button on the "Collecting problem information / Information is
being collected that may help the developers fix the problem you
@Mario, could you copy the list of devices from "sudo evemu-record" and
a log of the record from the keyboard after pressing the key once?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
** Description changed:
[impact]
udev (in trusty) does not create symlinks in /dev/disk/by-path/ for any
disks that are connected via sata.
[test case]
Install trusty onto a system with sata drives, and check /dev/disk/by-
path/ for symlink(s) to those sata drive(s).
@Sebastien: Thank you very much. With the SRU version installed (I hope
that's right):
sudo evemu-record
Available devices:
/dev/input/event0: Lid Switch
/dev/input/event1: Power Button
/dev/input/event2: Sleep Button
/dev/input/event3: Power Button
/dev/input/event4: AT
systemd uses pcre2 for a useful journal feature that we can't enable
until pcre2 is in main LP: #1751006
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you
I've also got this problem in 18.04 with a Gigabyte motherboard.
When I use front jack input the problem disappears.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
62 matches
Mail list logo
