Public bug reported:
Steps to reproduce:
- Install an unrelated package, such as lxqt
Expected behavior:
- Nothing in particular happens until I choose to launch lxqt
Actual behavior:
- Wi-Fi is suddenly down
- nmcli conn up says “Error: Connection activation failed: No suitable device
found
Public bug reported:
$ ss -atn | head -n 5 | tr ' ' '_'
State__Recv-Q_Send-Q___Local_Address:Port_Peer_Address:Port_Process_
This way each application has to be specifically modified to use
$SNAP_USER_COMMON instead of $HOME? Why not let the applications keep
using $HOME but add an option to snapcraft.yaml that would specify what
exactly to set $HOME to, with options like “real home”, “versioned snap
directory”, “common
So in general it is not possible to connect an interface which the snap
didn’t request? If not, sounds like a powerful feature to add. Forcing a
custom interface on a snap can be used to affect its filesystem in the
desired way.
--
You received this bug notification because you are a member of
Ubuntu 20.04, snap version 81.0.4044.138.
I don’t think the mention of the three domain names docs.google.com,
youtube.com and lpcdn.lpsnmedia.net is anything special. Most likely
these are simply the domains that caused the highest number of
filesystem access requests that are for some reason
`snap connect chromium:alsa` and variations thereof fail with “error:
snap "chromium" has no plug named "alsa"”. How to connect?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877601
Title:
I’m not running any other snaps, which one would you recommend to test
this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877601
Title:
/usr/share/alsa missing within snap
To manage
Public bug reported:
On advice given in another bug, I ran `journalctl | fgrep DEN`. This
produced as much as a gigabyte of output which certainly sounds
excessive for one week that it represents. I replaced numbers with
placeholders so I could `uniq -c` it ( stands for N hex
characters), the top
Ah, I think the true source of the problem was that my .XCompose was a
symlink into a subdirectory of .config, so that’s what was actually
denied. This is at least understandable, even if it still makes no sense
(~/.config/my-dotfiles-git-repository is off limits but ~/Documents
I am not. This is certainly not the place to discuss advantages and
drawbacks of pulseaudio, of which it has both, but seeing as both
Chromium and snapd itself support ALSA, the chromium snap should also
support it.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
$ ls /snap/chromium/current/usr/share/alsa
alsa.conf alsa.conf.d cards pcm pulse-alsa.conf smixer.conf
sndo-mixer.alisp topology ucm
$ sudo nsenter -m -t $(pgrep --oldest chromium) ls /usr/share/alsa
ls: cannot access '/usr/share/alsa': No such file or directory
Public bug reported:
Unless I manually edit ~/.chromium-browser.init to include “export
XCOMPOSEFILE=” and take care
to put a copy of XCompose at such a path, Chromium does not see the
XCompose file and so can’t make use of user-defined Compose sequences.
Chromium needs to be able to see
Public bug reported:
$ fgrep -w cat -C4 /snap/chromium/current/bin/chromium.launcher
# Source ~/.chromium-browser.init for compatibility with the chromium-browser
# deb package (https://launchpad.net/bugs/1837746)
if [ -f $REALHOME/.chromium-browser.init ]; then
cat
This issue causes `ubuntu-bug chromium-browser` to hang.
Additionally, isn’t this an issue that’s best solved within snapd
itself?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864901
Title:
Public bug reported:
0. Upgrade to focal (the problem was not present in eoan).
1. Try pip3 install somepackage. It works.
2. Try sudo -u nobody pip3 install somepackage. It works (assuming appropriate
file permissions).
3. Try sudo pip3 install somepackage. It hangs for about 30 seconds.
4. Try
Public bug reported:
This happens in Ubuntu 18.04 LTS:
https://bugs.freedesktop.org/show_bug.cgi?id=104773
Please make sure the LTS kernel is updated to include the fix.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
You received this bug notification
Public bug reported:
Every couple weeks, some of my accounts silently stop receiving email as
though I’m not being sent any. I think this happens with my GMail
accounts and not with my own IMAP server, but I’m not sure. When I go to
akonadiconsole, the affected agent has nothing where other
Public bug reported:
This is either a resurgence of #1680904 or something close to it.
Despite running linux-generic=4.13.0.16.17 where the original issue is
supposedly fixed, I got the following error again. The effect is that X
becomes completely unresponsive while processes are running, SSH
That is not the core issue either. I, for example, have declined to
accept the license on purpose (I dislike the fonts and I prefer them not
to be installed even if some package suggests this one as a dependency),
yet I get the message.
As I said above, both print() statements in the
Public bug reported:
I took a fully functional EFI-based Ubuntu installation running artful
RC and decided to start using full disk encryption. I booted from
removable media, shrank my LVM PV and did cryptsetup-reencrypt --new.
Then I chrooted, added an entry to crypttab, added
Public bug reported:
Out of nowhere, my OS froze, failing to respond to anything but the
SysRq reboot.
The following was logged:
Jun 22 18:06:43 zen kernel: [64494.503613] BUG: unable to handle kernel NULL
pointer dereference at 0018
Jun 22 18:06:43 zen kernel: [64494.503675] IP:
I suggest removing the print() call that outputs the message in question
from /usr/lib/update-notifier/package-data-downloader. This script isn’t
meant to be run interactively anyway.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
As is the case with all packages depending on v5 ABI for libstdc++, the
v5 package conflicts with early versions of the non-v5 library. There
should be a Conflicts: or Breaks: package field to reflect this.
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package:
Attaching full sample of incorrect output in a separate file.
** Attachment added: libsmartcols-art-problem.txt
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1406133/+attachment/4288864/+files/libsmartcols-art-problem.txt
--
You received this bug notification because you are a
Public bug reported:
The libsmartcols component used by findmnt to draw the filesystem tree
is smart enough to wrap lines in case the output doesn’t fit into the
screen. However, it fails to draw the lines correctly in this case.
Attached patch fixes the problem. Someone more knowledgeable in
In case there’s another right parenthesis from the process name.
str.partition would get the first parenthesis while rpartition would get
the last one, which is guaranteed to be the right one (no pun intended
:−). Unlikely but why not play it safe when possible. ps does the same.
See for
Public bug reported:
When running do-release-upgrade inside a chroot, it insists on starting
an emergency sshd on port 1022. If it’s not possible, for the likely
reason that openssh-server is not installed inside the chroot, the
upgrade process crashes.
In a chroot environment, starting such an
Public bug reported:
Just in case process name in /proc/%d/stat contains the right
parenthesis character.
** Affects: ubuntu-release-upgrader (Ubuntu)
Importance: Undecided
Status: New
** Patch added: DistUpgrade.utils.py.diff
Actually I think CMake files were contaminated by a build attempt when
it tried to use Qt 5. Starting from scratch with QT_SELECT=qt4 set from
the very beginning seems to work OK.
What about just putting
QT_SELECT := qt4
export QT_SELECT
in debian/rules of KDE packages?
--
You received this
Public bug reported:
If Qt 5 is installed, then dpkg-buildpackage fails to work even if
explicitly passed QT_SELECT=qt4. CMakeCache.txt ends up full of
references to /usr/include/qt5 which have to be replaced manually with
qt4 counterparts.
To reproduce:
1. apt-get source plasma-desktop # for
My guess would be some kind of problem with KDE CMake configuration,
particularly with determining paths to Qt libraries, and not a problem
within Qt itself, am I mistaken?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I’ve had this problem, too, when upgrading to 4.2.3. I suggest not using
dpkg --force-anything though, most of time it’ll end up breaking
something the next time you upgrade. A less intrusive solution is
dpkg-divert --package kdebase-runtime --divert
A clean install of Jaunty (kernel 2.6.28-4-generic) solves the issue for
me without any workarounds.
--
Shut Down won't power off with an ASUS P5GD1 motherboard
https://bugs.launchpad.net/bugs/42160
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct
Greetings,
This is also an issue for me with Kubuntu 8.04.
When an application requests an 800x600 mode, the monitor only displays
‘Out of range’, xrandr -s 800x600 causes the same.
After setting the Nvidia parameter ‘DynamicTwinView’ to false, here’s what
xrandr -q shows:
Screen 0: minimum
Also, this doesn’t look like a bug of xrandr. I got the error first when
trying to play Tuxracer. It seems that whenever an 800x600 mode (640x480
works fine) is requested without specifying the refresh rate, X makes
the wrong choice.
--
xrandr -s 800x600 Black Screen (Out of Range)
Update:
The upgrade to Linux 2.6.24-21.43 broke even s2disk. The most recent
upgrade, which consisted of Linux 2.6.24-22.45 and related packages,
brought s2disk back to life.
It should also be noted that I’m using the nvidia proprietary driver,
version 180.06 beta. Other versions of it also
For me the situation is rather different.
I’m able to shut the computer down properly only when I use s2disk (from
µswsusp) and there aren’t any acpi=... kernel parameters.
Any other ways of turning off the computer, be it halt, shutdown, pm-
hibernate, fail for me. With the acpi=force
The log file shows ntp is started before ntpdate. Therefore, when ntpdate gets
started, the ntp socket is already in use, ntpdate fails and the clock can not
be corrected immediately. I can reproduce this on my own Gutsy system, when
roaming mode is used.
This looks like ntp should be started
38 matches
Mail list logo
