Public bug reported:
lsb_release -rd
Description:Ubuntu 21.10
Release:21.10
Wireguard from network-manager deosn't create route to server ip. It's a
problem when "allowed ips" '0.0.0.0/0' are used.
Steps to reproduce:
Create wireguard connection with 0.0.0.0/0
Steps to workaround:
hpad.net/ubuntu/+source/alsa-driver/+bug/1947466/+subscriptions
>
>
--
Paweł Bogaczewicz
http://bogaczew.blip.pl/
if (statusIsNotValid.compareTo( Boolean.FALSE ) != 0) skipValidation =
false;
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
o, and those sliders work. problem is 'only' with this 'głośność
systemu'
[image: obraz.png]
niedz., 17 paź 2021 o 16:14 Paweł Bogaczewicz
napisał(a):
> ⋊> ~ lsusb -t
>16:14:00
> /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver
466
>
> Title:
> [CREATIVE MUVO 1c, playback] volume slider does not change sound
> volume
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1947466/+subscriptions
>
>
--
Paweł Bogaczewicz
http://boga
on the Bluetooth. it worked on previous version of Ubuntu
niedz., 17 paź 2021, 04:50 użytkownik Hui Wang <1947...@bugs.launchpad.net>
napisał:
> From the log, your current active output sink is bluetooth headset, do
> you expect the sound volume changing on internal sound card or on the
>
I've noticed that the omshell as shipped in the package is doing bad
things memory access wise...
$ valgrind /usr/bin/omshell
==735304== Memcheck, a memory error detector
==735304== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==735304== Using Valgrind-3.15.0 and LibVEX; rerun
When could we expect this patch to be deployed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
Ok, reproduced with focal and broken seeds from an older image, symptoms
are exactly the same (including ps/pstree output). The problem is caused
by blocking on snapd.seeded.service (which waits for seeding to
complete, but it's never going to complete with broken seeds).
Given that this is an
@Mark does 'snap changes' (and then 'snap change ' if you see any
failed changes) reveal antyhing interesing? Some of the older focal
images had broken seeds that would never succeed, potentially causing
other issues.
--
You received this bug notification because you are a member of Ubuntu
Touch
Also, the list of installed snaps may be relevant in understanding what
happens.
--
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/1868706
Title:
Snapd postinst script hangs
I'm tentatively adding systemd/dpkg.
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: snapd
Status: New => Triaged
** Changed in: snapd
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1865519
Title:
This affects each system where /tmp is *not* on tmpfs which affects a
lot of cloud-built servers and effectively prevents usage of systemd-
analyze verify in Ansible, Puppet etc.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Adding ONLINK option to netplan is essential.
I have same problem.
systemd has GatewayOnlink option which can be used.
[Route]
*** This bug is a duplicate of bug 1779237 ***
https://bugs.launchpad.net/bugs/1779237
Public bug reported:
sudo apt install -f
Czytanie list pakietów... Gotowe
Budowanie drzewa zależności
Odczyt informacji o stanie... Gotowe
0 aktualizowanych, 0 nowo instalowanych, 0 usuwanych i 0
The problem is still affecting current Cosmic image (from 11th of June)
and has been reported on the https://forum.snapcraft.io/t/gnome-
calculator-failed-to-create-symbolic-link/5742/22 ; any reason the re-
order seed.yaml hasn't landed?
--
You received this bug notification because you are a
I am on 16.04 LTS, and have the same issue. I merely use bluetooth, but
from some time I have wireless headphones and need it more often. Please
fix this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
The same affects my setup - Ubuntu 16.04 on Thinkpad T460.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-bluetooth in
Ubuntu.
https://bugs.launchpad.net/bugs/1595695
Title:
Bluetooth indicator disappears every
Public bug reported:
When I install ntp package it won't start with /etc/init.d/ntp start.
Going inside the scripts and includes I've found, that ntp init script
is including /lib/lsb/init-functions which then includes files in
/lib/lsb/init-functions.d/ folder. Content of my folder is:
ls -lah
I can confirm this bug on ubuntu 17.04 armhf.
It seems dhcp client doesn't acquire dns adresses when first time connected.
Running dhclient cmd workarounds issue to next reboot.
/etc/resolv.conf contains in my case:
# Generated by NetworkManager
nameserver 127.0.1.1
and after dhclient cmd
** Description changed:
After upgrading from 14.04 LTS to 16.04 LTS, we noticed that LDAP-based
sudo roles stopped working, meaning users that were able to use sudo in
the past, are rejected now.
After investigation, it turned out to be a known upstream bug:
Public bug reported:
app crashed on login and on daily update call
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unattended-upgrades 0.92ubuntu1.2
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
Architecture:
** Description changed:
After upgrading from 14.04 LTS to 16.04 LTS, we noticed that LDAP-based
sudo roles stopped working, meaning users that were able to use sudo in
the past, are rejected now.
After investigation, it turned out to be a known upstream bug:
Public bug reported:
After upgrading from 14.04 LTS to 16.04 LTS, we noticed that LDAP-based
sudo roles stopped working, meaning users that were able to use sudo in
the past, are rejected now.
After investigation, it turned out to be a known upstream bug:
*** This bug is a duplicate of bug 1655936 ***
https://bugs.launchpad.net/bugs/1655936
Marked this bug as duplicate of #1655936 to unconfuse errors.ubuntu.com
(even though the bugs are technically different issues and the one from
this bug was fixed long time ago).
** This bug has been
@Daniel I see your point about Mir. Anyway, all I'm saying is this
problem manifested via
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
is completely different from the original problem described in this bug.
The only common thing is qFatal() gets called. In the
Public bug reported:
1. Go to Manage Dash. Make sure you have a few scopes favorited.
2. Long press to start the "edit mode". Move the 2nd scope on the fav list to
the last position in favs
3. Leave "edit mode" by pressing the big X button in Manage Dash view.
4. Unfavorite the last scope by
I think the cause of this problem are filters, they are apparently not
reset correctly in this scenario. If you expand the filters on the 2nd
search and select Applications, it works as a workaround too.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
See the first error reported by apt-get:
"Cannot start click due to a conflict with a different locally-installed
Python 'click' package. Remove it using Python packaging tools and try
again."
It seems there is a conflict between a locally installed 'click' python
package and the click machinery
Please ignore my last comment about this affecting scopes... It was a
different root cause afterwards (missing mime database and gdk-pixbuf
loaders/cache - https://code.launchpad.net/~stolowski/unity8-session-
snap/thumbnailer-fixes/+merge/310756 should fix it).
--
You received this bug
Here is the error returned by thumbnailer in the unity8-dash.log when
processing image://thumbnailer/file:/// uris:
[2016-11-08:16:59:24.600] Thumbnailer: RequestImpl::dbusCallFinished(): D-Bus
error: Handler::checkFinished(): no artwork for thumbnail:
As discussed no change is needed on scopes api level. Scopes should be
using scope_directory() getter to get the base dir and then use all
assets paths relative to that; scope_directory() uses $SNAP prefix
already.
There is a problem though with thumbnailer uris, such as
** Changed in: unity-scopes-api (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1639249
Title:
Result art not
This also affects scopes, we get empty art for thumbnailers uri such as
image://thumbnailer/file:///snap/unity8-session/...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
** Changed in: unity-scopes-api (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: unity-scopes-api (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
I haven't tested the attached branch yet; let's coordinate that since I
think you're working with a silo on all this.
** Branch linked: lp:~stolowski/unity-scopes-shell/art-uri-snap-root
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1639
A quickfix in the shell plugin may fix it for the initial approach
(scopes in same snap as the shell), but it gets more complicated when
scopes are in separate snaps.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => Triaged
--
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/1630845
Title:
unity8-dash crashed with SIGSEGV in
Setting up libunity-scopes1.0:amd64 (1.0.7+16.10.20160921-0ubuntu2) ...
Traceback (most recent call last):
File "/usr/bin/click", line 55, in
from click import commands
ImportError: cannot import name 'commands'
[1mdpkg:[0m error processing package libunity-scopes1.0:amd64 (--configure):
Daniel, it seems that all bugs that end up in qFatal() fall into the
same bucket.. The error you linked
https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb
aborts because of Mir:
#4 QMessageLogger::fatal (this=0xb6410088 ,
this@entry=0xb6fa9000, msg=0xb4160e50
Ok, I was able to reproduce the issue.
I've checked unity-scopes-shell plugin with a debug branch
(https://code.launchpad.net/~stolowski/unity-scopes-shell/debug-
category-link; packages available here https://code.launchpad.net
/~unity-api-team/+archive/ubuntu/dev-build-1/+packages) and it seems
Looks like it's related to the changes to settings model made from a
separate thread (QtConcurrent is used to update child scopes).
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => Confirmed
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Marcus
Please make sure you have latest everything from xenial overlay ppa
(looks like maybe your libunity scopes lib or unity-plugin-scopes are
outdated); tested with unity-scope-tool and it works here. This is what
I have:
ubuntu@ubuntu-xenial:~$ apt-cache policy libunity-scopes1.0
libunity-scopes1.0:
Hi Brian, I started working on the implementation in unity-scopes-shell
at the time we discussed this, but it turned out to be more complex than
expected.
First off, the solution with preview_by_key I suggested above turned out
to be a no-go, because it was incompatible with how preview actions
** Branch linked: lp:~stolowski/unity-scopes-shell/fix-bileto-hook-
script
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1612460
Title:
[MIR]
Yep, the attached MP fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1620297
Title:
First scope not rendered until unlocked
Status in Canonical System
** Description changed:
The pre-populating of first scope on startup (before the screen is
unlocked) doesn't seem to be fully working.
My early investigation shows that the shell plugin correctly pre-
populates scope model on startup when the screen is still locked, but
after
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
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/1620297
Title:
First scope not
Attaching a snippet of unity8-dash.log. Apps scope is my 1st scope.
Note, how it's pre-populated @15:03:44 on startup and delivers 29 results:
[2016-09-05:15:03:44.547] Pre-populating first scope: "clickscope"
I waited ~2 minutes before unlocking the device - this is when I think
rendering
Public bug reported:
The pre-populating of first scope on startup (before the screen is
unlocked) doesn't seem to be fully working.
My early investigation shows that the shell plugin correctly pre-
populates scope model on startup when the screen is still locked, but
after unlocking scope view
Hmm, Ubuntu 16.10 has boost 1.61. I agree we are defenseless, but are we
sure it was fixed in boost?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1615614
Title:
I agree this is a problem, it's an old bug and in fact you'll see a lot
of reports about "locale::facet::_S_create_c_locale name not valid"
exception thrown by boost - see e.g. the last comment here
https://github.com/udoprog/c10t/issues/203
There is nothing we can do at the level it surfaces
Looks like it's crashing on invalid locale setup (boost throws exception
on us); what is your locale (language) setup?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
** Description changed:
This test fails pretty consistently only on arm64 in yakkety:
22: [ RUN ] SmartScopesClientTest.consecutive_searches
22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test:
SmartScopesClient.search(): GET
Public bug reported:
This test fails pretty consistently only on arm64 in yakkety:
22: [ RUN ] SmartScopesClientTest.consecutive_searches
22: [2016-08-19 11:02:43.600] INFO: SmartScopesClient_test:
SmartScopesClient.search(): GET
Public bug reported:
Please update zmqpp to version 4.1.2 with the following patch that I proposed
upstream (it got merged into their "develop" branch):
https://github.com/zeromq/zmqpp/pull/167/files
(alternatively, use master + my patch or develop branch of zmqpp).
This will require the
*** This bug is a duplicate of bug 1607799 ***
https://bugs.launchpad.net/bugs/1607799
** This bug has been marked a duplicate of bug 1607799
Dash freezes after U1 login
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Branch linked: lp:~stolowski/unity-scopes-shell/favoriting-fixes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1583067
Title:
Lag when
** Branch linked: lp:~stolowski/unity-scopes-shell/favoriting-fixes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1603186
Title:
Apps scope not shown in the
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: unity-scopes-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: unity-scopes-shell (Ubuntu)
Status: New => In Progress
--
You received this bug not
** Changed in: unity-scopes-shell (Ubuntu)
Assignee: (unassigned) => Paweł Stołowski (stolowski)
** Changed in: unity-scopes-shell (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: unity-scopes-shell (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-shell in
Ubuntu.
https://bugs.launchpad.net/bugs/1603186
Title:
Apps scope not
>From the symptoms it seems that the list of favorited scopes got messed
up somehow. Did you uninstall unity-scope-click scope before at any
point?
This list can be (re)set with e.g.
$ gsettings set com.canonical.Unity.Dash favorite-scopes
"['scope://unity-scope-nearby', 'scope://clickscope']"`
*** This bug is a duplicate of bug 1547573 ***
https://bugs.launchpad.net/bugs/1547573
Yes, both these issues are known and were documented (+ bugs opened) in
the test plan https://wiki.ubuntu.com/Process/Merges/TestPlan/scopes
when the feature was implemented, both causes by issues outside
Same here. Using the option Show copy dialog from the context menu on
the launcher icon does not do anything.
Also if there are some actions to be taken during copying like deciding
Ignore/Merge/Replace etc. - the dialog does not appear and the copy
operation is halted...
Using the Cancel all
Here is screenshot from adding sender to contact list. You can see that it goes
with a string in place of mobile number (this cannot be done in other way).
The behaviour in r23 is a bit different - only senders that match the contact
will have an avatar as the contact. Previously adding even one
r23 - not yet fixed.
** Also affects: dialer-app
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1440128
Title:
Cannot
Still there in r22.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1438709
Title:
BQ Aquaris E4.5 - issues with SMS that has alphanumeric string in
sender field
Still there in r22.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1440128
Title:
Cannot add extenstion to number when dialing.
Status in messaging-app package in
Intel Pentium® Dual-Core CPU E6600 @ 3.06GHz
Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
Elementary OS freya 0.3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
The fix I implemented in my system was to add the following check to
/usr/lib/python2.7/dist-packages/apparmor/logparser.py, in lines 124:
if rmask and rmask not in [ 'send', 'receive', 'send receive' ]:
Originally it was:
if rmask:
The same in line 130 for dmask. This file comes from
Public bug reported:
Adding '+' in front of entered number in dialer ends up in adding '0' in
front, moving cursor to the end of entered number and replacing last
digit with '+'.
Found on BQ Aquaris E4.5, Ubuntu 14.10, r20.
** Affects: messaging-app (Ubuntu)
Importance: Undecided
** Summary changed:
- BQ Aquapark - issues with SMS that has alphanumeric string in sender field
+ BQ Aquaris E4.5 - issues with SMS that has alphanumeric string in sender field
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Public bug reported:
Hi,
I have a problem with SMSs from different senders that are not regular phone
numbers but strings (e.g. authentication messages ). I created separate
contacts for each such a message, but in the end all are displayed separately
but with a single contact name. Looks like
I have the 2.9 package but this bug still seems to affect me:
ii apparmor-utils 2.9.2~2880-0ubun amd64Utilities
for controlling AppArmor
# aa-logprof
Reading log entries from /var/log/syslog.
Updating AppArmor profiles in /etc/apparmor.d.
Traceback (most recent call last):
Same problem here, with ThinkPad x220
Mar 15 00:46:00 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c:
Skipping 61300 us (= 10812 bytes) in audio stream
Mar 15 00:46:00 x220 pulseaudio[2035]: [bluetooth] module-bluetooth-device.c:
Skipping 43008 us (= 7584 bytes) in audio stream
Public bug reported:
On Asus N551JM there is no sound from external subwoofer on fresh
Kubuntu 14.10 installation. There is no Bass speaker in alsamixer.
Adding options snd-hda-intel model=asus-mode4 to /etc/modprobe.d/alsa-
base.conf makes Bass speaker appears in alsamixer but I was unable to
78 matches
Mail list logo
