Public bug reported:
Installing vanilla-gnome-desktop on a fresh 23.04 install, fails with:
The following packages have unmet dependencies:
pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be
installed
pipewire-audio : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to
I realize that the conflict is probably intended and my issue is that
vanilla-gnome-desktop relies on pulseaudio still. I'll create a separate
bug, sorry.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
I seem to hit the same dep issues on a freshly installed 23.04 system
when trying to install vanilla-gnome-desktop.
The following packages have unmet dependencies:
pipewire-alsa : Conflicts: pulseaudio but 1:16.1+dfsg1-2ubuntu3 is to be
installed
pipewire-audio : Conflicts: pulseaudio but
Possibly related to https://gitlab.gnome.org/GNOME/gtk/-/issues/2971
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1993594
Title:
Scrolling in a view with many files is broken
** Attachment added: "Video showing problem. Using mouse wheel to ONLY scroll
up."
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1993594/+attachment/5625351/+files/Screencast%20from%202022-10-19%2021-52-35.webm
** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #2971
Public bug reported:
Scrolling up and down in a Files window, in a directory with many files,
the scrolling is erratic and seems to often jump to the bottom of the
view.
It happens only when scrolling while hovering the actual files (eg.
using the mouse wheel). If hovering the scrollbar instead,
This update makes it possible to connect to VPNs where the "cipher" (now
"data-ciphers") option is needed, as long as the connection is manually
modified. This part works great.
The Gnome settings interface however, still looks for the "cipher"
option, so this part does not work. The settings
lspci -k
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610691/+files/lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
journalctl -b0
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1987076/+attachment/5610690/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Thanks for the directions...
It's not that hard to reproduce here, I just have to move between places
(or I could bring my other monitor closer, for more intense
troubleshooting if need be). But it just happened...
There are no recent crashes and nothing reported by whoopsie. The
requested files
Public bug reported:
My setup is this:
Ubuntu: 22.04.1 LTS (Vanilla Gnome session on Wayland)
Laptop: Lenovo ThinkPad P14s Gen 2a (AMD).
Display: Lenovo T34w-20, connected via USB-C
The problem started with upgrade to 22.04
I have had the same exact problem with my previous laptop, a ThinkPad
I haven't been able to find other actual bugs/issues describing this
issue, but there are threads on reddit and such that seem to indicate
that this is a wayland/gnome42 issue, and that it affects all
distributions.
Still a problem here. I'm on 22.04 with all updates (including proposed)
installed, latest firefox snap (99.0-2, rev 1188).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1947210
This is still an issue in Ubuntu 21.04 (development, as of March 30,
2021)
It looks like people have been complaining about this for years, and
while some people have tried to fix it, those fixes never made it in.
Surely it must be of some type of urgency to support 2FA one-time
passwords in the
I am no longer able to reproduce the crash after installing the proposed
fix! Looks good to me! :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1918033
Title:
gnome-shell crashed
Problem occurs on Wayland as well as Xorg.
Please let me know what kind of info you need.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1918127
Title:
gnome-shell crash when
Public bug reported:
Whenever I perform an action in the Gnome Panel (Activate a VPN has 100%
failure-rate, but I have seen it when clearing notifications and other
things too), the entire session crashes and I'm back at login.
I'm running gnome-session on Hirsute.
journalctl
Never mind - Somehow my local package simply looked newer from a
versioning perspective. I found the right version and as far as I can
tell the problems are gone in this version.
I have not seen any of the dbus messages and roaming works better (less
erratic) here.
Thanks a lot for getting this
I've been looking for the package but cannot seem to find it for
testing. Please help me find it and I will test it immediately.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1879087
Thank you for taking care of this so swiftly.
I don't believe I have much to add to the test-case. From testing
locally I can see that the warnings disappear from the log and the
connection _seems_ more stable. I underscore _seems_ because I have not
been able to figure out which other parts of
Public bug reported:
When using this version of wpa_supplicant with my company
WPA2-Enterprise wireless setup, I'm experiencing far too frequent
roaming events (even when not moving around) accompanied by hiccups in
connectivity. I also see these messages in the wpa_supplicant log:
dbus:
On a fully updated Ubuntu 19.10, I feel most of my problems occur, when
copying from a Wayland application, and pasting to an XWindow
application. Most of the time, that doesn't work at all.
As an example. Running my Firefox as a native Wayland application, I am
experiencing problems copying a
Looking through the code, these outputs may differ because of the
different ways to authenticate... I'm not sure but both messages are
certainly present in the latest openvpn code.
FWIW, I'm connecting to an OpenVPN-AS solution with Certificates and
Password
--
You received this bug
Looks like the message that's being looked for might have changed:
This is from my log now:
AUTH: Received control message:
AUTH_FAILED,CRV1:R,E:93NBZNaOH799HLoxv7tWefldc8JtIpbf:eHRod3Q=:Enter PASSCODE
But based on the commit, it might be looking for:
This is from the commit below:
This doesn't seem to work for me on Ubuntu 17.10:
openvpn 2.4.3-4ubuntu1
network-manager 1.8.4-1ubuntu3
network-manager-gnome 1.8.4-1ubuntu3
network-manager-openvpn 1.2.10-0ubuntu2
network-manager-openvpn-gnome 1.2.10-0ubuntu2
When activating an OpenVPN connection that's challenge/response
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
** This bug is no longer a duplicate of bug 1629611
dns server priority broken
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
** This bug is no longer a duplicate of bug 1629611
dns server priority broken
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
This is not fixed, but is marked as a duplicate of #1624317
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You received this bug
*** This bug is a duplicate of bug 1624317 ***
https://bugs.launchpad.net/bugs/1624317
** This bug is no longer a duplicate of bug 1629611
dns server priority broken
** This bug has been marked a duplicate of bug 1624317
systemd-resolved breaks VPN with split-horizon DNS
--
You
Seems to work in 1.4.4-1ubuntu3 in 17.04 at least... Thanks
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1629611
Title:
dns server priority broken
Status in
That is certainly a possibility, but unfortunately returns us to a state
where applications have to be restarted when nameservers change (glibc
resolved.conf issue). That's probably even worse in my situation at
least.
--
You received this bug notification because you are a member of Desktop
Unfortunately not much traction here, and this appears to annoy people
across distros.
In the meantime, an ugly hack is to manually add all internal domains to
the NetworkManager VPN config file's dns-search= parameter:
dns-search=domain1.lan;domain2.lan;domain3.lan;example.com;
This causes
Wow - Long message, but what I got from it was "I need to see a debug
log", correct? I'll attach that...
I'll also point you to the problematic part:
Dec 5 15:14:48 bar14860 NetworkManager[921]: [1480961688.1915]
dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain
Here's the thing,
I'm on 16.10 which has the debian equiv listed as stretch/sid and my
network-manager version is 1.2.4-0ubuntu1.
Looking at Debian stretch and sid, they have network-manager packages in
various versions but not 1.2.4.
Furthermore, since Ubuntu employ their own patches,
I'll do it :)
Any helpful pointers to which package/version i should reference, since
I don't have the real debian version of this package anywhere?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
No, that does not seem like the problem to me - Or it's not described
correctly. I can't seem to find a proper match in that list.
resolv.conf is not the issue here - the problem is in the DNS servers
that dnsmasq uses. I.e. one is added to dnsmasq when my wireless
connection comes up, and when I
This bug seems to bite me in a slightly different way. Please let me
know if you feel that this is really a separate bug...
Also, this is happening on Yakkety - network-manager-1.2.4-0ubuntu1
When I connect to my work VPN, I'm not using split-tunnelling. Still the
DNS resolution is split,
Public bug reported:
network-manager: 1.2.4-0ubuntu1
Yakkety appears to have switched back from resolved to dnsmasq, but it seems
server priority/order is broken.
Example: In split DNS setups, connecting to VPN will not cause us to
query the DNS provided by the VPN first (or only), which
You're absolutely right - Changed to systemd
** Package changed: transmission (Ubuntu) => systemd (Ubuntu)
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in
After this, I have no indication that anything should be wrong with
transmission-daemon regarding this, so I'm closing the case.
** Changed in: transmission (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is
I was wrong. It appears as if the XFS filesystem on / is the actual culprit
here.
The way XFS works, makes it lose last-second changes such as the new settings
file written by transmission-daemon, whet the power is cut after halt. I've
added a "sync" to my UPS power-off script and everything
Public bug reported:
Ubuntu-15.10, amd64
systemd-225-1ubuntu9
transmission-daemon-2.84-1ubuntu1
I've noticed more than once, that "halt" can cause transmission-daemon
to loose it's settings. AFAIK, "halt" is not that different from
"poweroff" or "reboot" in regards to the shutdown sequence, so
Public bug reported:
Ubuntu 15.10, amd64
systemd-225-1ubuntu9
/etc/halt.local seems to have moved to /usr/sbin/halt.local which IMO is
bad for a couple of reasons.
1) This is not where it's supposed to be
2) Locally modified (non-dpkg managed) scripts under /usr is bad
I have not been able to
** Visibility changed to: Public
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1057833
Title:
soffice.bin crashed with SIGSEGV in Menu::~Menu()
Status in “libreoffice” package
Public bug reported:
In gnome-terminal CTRL-'+' and CTRL-'-' is supposed to zoom in and out
respectively:
Zoom in should: increase the font size and resize the window to match the new
font size (keep rows and cols consistent)
Zoom out should do the exact opposite: reduce the font size and
This is on quantal (up to date as per now) - Problem existed on
precise last I checked too.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1046822
Title:
Zooming does not work
Not a firefox bug but a missing driver AFAICT
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/951246
Title:
13b1:002f Linksys AE1000 v1 802.11n [Ralink RT3572] not usable in
network
I have this exact problem on a freshly installed Precise.
This is what I had to do, to fix the problem:
in /etc/samba/smb.conf add the following to the bottom of the [global]
section:
client lanman auth = yes
client ntlmv2 auth = no
I could gvfs-mount a Windows 2008 share, but not an Alfresco
In my case, I seem to loose the windows controls some times. Some times
they are there... My feeling is, it usually has something to do with
leaving fullscreen mode...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
49 matches
Mail list logo
