[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there
has been no activity for 60 days.]
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Can confirm #43
The latest I experienced of this bug, all I have to do is click on
**show applications** ( 9 dots ) icon to get rid of the freeze. Looks
like not necessary to click on the search box or type a letter in it.
--
You received this bug notification because you are a member of
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1837266
Title:
package python-gi 3.12.0-1ubuntu1 failed to install/upgrade:
subprocess new
Public bug reported:
I'm running Ubuntu 114.04 on a 32-bit Lenovo T61.
When I try to launch alacarte from the menus or from the command line I get
$ alacarte
Traceback (most recent call last):
File "/usr/bin/alacarte", line 23, in
from Alacarte.MainWindow import main
File
As I wrote on the snapcraft forums, that's a problem then as long as the
snap continues to be out of date/unstable, as the snap replaces the deb
version for users that don't have Thunderbird installed.
I don't mind if non-stable snaps appear in the store, but they should
not be default if a deb
Any opinions?
https://bugzilla.redhat.com/show_bug.cgi?id=1670504#c102
:-)
** Bug watch added: Red Hat Bugzilla #1670504
https://bugzilla.redhat.com/show_bug.cgi?id=1670504
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I have also been trying to see what are the packages difference between
the OEM version and 19.04 since I suspect that Dell might have addressed
this issue in their version. I have a list of all packages that were on
the OEM but that might be tedious. If we contacted Dell directly, would
they be
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
Hello all, I believe that I have this same bug, also after a 19.04 fresh
install. I initially posted on that bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826125 but they
kindly directed me here.
Of note, I am glad you tried wayland as I wanted to try if that made any
difference. I
This is still an issue!
It is also more important than "low".
We need to have a way to secure desktops when users forget to log out
when stepping away.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-session in Ubuntu.
oh okay. I actually updated from ubuntu 18.04 to 19.04 in the expectation
that the bug disappears. I do not have enough time now for trying to figure
out this issue due to some academic deadline. But I will follow the steps
as soon as the bug happens again in version 19.04 though. Thank you very
So finally this has been fixed also in 18.04. I want to thank Steven
Santos who called my attention to the problem as well as the solution.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
That's good news. :) sane-backends was updated yesterday for 18.04 (bug
#1728012). I didn't realize that that change applies to your problem
description, but apparently it does (somehow).
Closing this bug then.
** No longer affects: systemd (Ubuntu)
** Changed in: sane-backends (Ubuntu)
I have just ried this again and it is now working.
No changes other than the normal updates.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1835647
Title:
Saned does not
This bug was fixed in the package mesa - 19.0.2-1ubuntu1.1~18.04.2
---
mesa (19.0.2-1ubuntu1.1~18.04.2) bionic; urgency=medium
* i965-revert-enabling-softpin.diff: Don't enable softpin, causes
issues on 32bit installs. (LP: #1836721)
-- Timo Aaltonen Thu, 18 Jul 2019
The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Nevermind then, this is working well enough for a stable release.
** Changed in: network-manager (Ubuntu Bionic)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
I confirm that using a valid IP works better:
In the config:
route1=fe80:2::/60,fe80::99,42
# ip -6 route show dev eth2
fe80::/64 proto kernel metric 101 pref medium
fe80::/64 proto kernel metric 256 pref medium
fe80:2::/60 via fe80::99 proto static metric 42 pref medium
It's still missing the
The journal says why:
NetworkManager[1295]: [1563552648.1667] platform: route-sync: failure
to add IPv6 route: 1:2::/60 via 1:2::3 dev 6 metric 42 mss 0 rt-src user: No
route to host (113)
NetworkManager[1295]: [1563552648.1672] device (eth2): failed to apply
manual IPv6 configuration
Public bug reported:
I have a system connection like this:
-- /etc/NetworkManager/system-connections/eth2 ---
[connection]
id=eth2
uuid=c73fb4d2-8383-4d03-a87c-04c8251961bd
type=ethernet
gateway-ping-timeout=12
interface-name=eth2
permissions=
timestamp=1563551266
[ethernet]
Thanks for the report.
Can you please run the following command in a terminal to attach additional
information to the bug report?
apport-collect 1824507
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
I wrote a comment on the upstream fixing commit asking if there are
other commits that are required to apply the fix on Poppler 0.62.0, no
answer yet, and I don't think upstream is interested in 0.62.0 any more.
--
You received this bug notification because you are a member of Desktop
Packages,
I'm attaching a screenshot demonstrating my claim above, showing gnome-
calculator as a snap on the left, and from the deb on the right. This is
in a clean and up-to-date disco VM, with Adwaita as the default theme.
Colours clearly aren't right with the snap.
--
You received this bug
(and both are focused, of course)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1800260
Title:
[snap] with CSD and Yaru, background color of the header bar is
incorrect
** Attachment added: "left: snap / right: deb"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1800260/+attachment/5278047/+files/gnome-calculator-left-snap-right-nonsnap-adwaita.png
--
You received this bug notification because you are a member of Desktop
Packages, which is
* Uninstalled all extensions
* restarted
* ran apport-collect.
For some reason, the extensions show as enabled in the bug report. This
is not the case.
- K
On 2019-07-18 10:27 p.m., Daniel van Vugt wrote:
> Please run this command to send us more information about the machine:
>
>
** Changed in: xorg-server (Ubuntu)
Assignee: fallo7...@gmail.com (fallo78) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1755232
Title:
Xorg
This doesn't appear to be chromium-specific, nor Yaru-specific. I
initially thought that only Yaru was exhibiting an incorrect background
color for the focused headerbar, but I am now seeing an incorrect color
with the gnome-calculator snap when using Adwaita.
--
You received this bug
Thanks Dmitry.
I'm tentatively closing the bug for firefox. To anyone affected, feel free to
re-open if you're not using the GNOME Flashback session.
** Changed in: firefox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
$ echo $GTK_IM_MODULE
ibus
I don't know which session I use, I set this up a loong time ago and I have no
idea how to find out.
But yes, it looks like it's flashback:
$ ps -ef|grep -i flash
hajma 1742 1503 0 čec16 ? 00:00:00 /bin/sh
/usr/lib/gnome-session/run-systemd-session
Closing then. Thanks.
** Changed in: network-manager (Ubuntu)
Status: New => Won't Fix
--
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/1824425
Title:
network-manager
excellent, thanks for confirming!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1836721
Title:
Black screen after updating mesa from 18.2 to 19.0 on i386 Ubuntu
18.04
Status in mesa
If mine is the only report of this problem, then yes, it should probably
be closed wontfix.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
Hello yparitcher, or anyone else affected,
Accepted modemmanager into disco-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.10.0-1ubuntu0.19.04.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new
This is a bug in gnome-flashback, not in Firefox. I am working on a fix.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-flashback/issues #16
https://gitlab.gnome.org/GNOME/gnome-flashback/issues/16
** Also affects: gnome-flashback via
I tested in an XFCE/XUbuntu session, and the focused headerbar color was
correct, so there's something specific to the Ubuntu/GNOME session.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
vorlon, as it only happens during the Cosmic -> Disco upgrade and Cosmic
is EOL, should we close this then?
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I tested a few more things, unsuccessfully:
- I modified the Yaru theme css in gtk-common-themes to remove the
".titlebar:not(headerbar)," selector, keeping only the "headerbar"
selector for header bars, but no difference
- I modified the custom selector in gtk_ui.cc to be just "#headerbar"
No. This only happened the one time during the cosmic to disco upgrade.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Please provide a log of network-manager in debug mode, following the
instructions on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages,
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
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/1793763
Title:
NetworkManager interaction with
Pavel and Ross, can you confirm that you are seeing this with the GNOME
Flashback session, not the default Ubuntu session?
** Also affects: gnome-flashback (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages,
Please follow the instructions of Thomas Haller in your upstream bug
report.
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
As manual setup of networking also does not work it looks more like a
kernel problem, moving ...
** Package changed: network-manager (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
Please report this bug to Trisquel. Thanks.
** Changed in: network-manager (Ubuntu)
Status: New => Invalid
--
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/1818666
Title:
I can reliably reproduce the crash about half of the time with the following
steps:
- create a symlink to a folder on the desktop
- right-click on that symlink and choose the option to send to trash
Corresponding crash report:
I have managed to reproduce in a clean and fully up-to-date disco VM,
but not in an eoan VM, which suggests the problem was fixed in eoan.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-desktop-icons in
Ubuntu.
*** This bug is a duplicate of bug 1422004 ***
https://bugs.launchpad.net/bugs/1422004
BUG still existing also for model
HP Color LaserJet Pro MFP M281fdw
Printing works but scanning is not possible because of failure when installing
plugin!
No solution actually seems to be available!
Does this happen repeatedly since your update, for example at every
boot? If so, could you provide a log of network-manager in debugging
mode, as described on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You
I have just updated mesa from bionic-proposed and now everything is fine
on i386 Ubuntu 18.04:
~# apt-cache policy libgl1-mesa-glx
libgl1-mesa-glx:
Встановлено: 19.0.2-1ubuntu1.1~18.04.2
Кандидат:19.0.2-1ubuntu1.1~18.04.2
Таблиця версій:
*** 19.0.2-1ubuntu1.1~18.04.2 500
500
Ubuntu 19.04 (disco) will switch to read-only when a automatically mounted VFAT
filesystem with errors is detected.
You have to umount the filesystem and then run "sudo fsck.vfat /dev/sd"
multiple times, until fsck.vfat do no more ask to correct the new errors
detected in the filesystem.
Hello Lars, or anyone else affected,
Accepted libsoup2.4 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/libsoup2.4/2.62.1-1ubuntu0.3 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Did I miss something?
--
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/1827953
Title:
when you have "world clocks" configured (e.g. from the Gnome Clocks
application), Gnome
** Changed in: xorg-server (Ubuntu)
Assignee: Timo Aaltonen (tjaalton) => fallo7...@gmail.com (fallo78)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1755232
Title:
Xorg
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
Could you do the logging like in your comment #4 of your question again
but in debug mode, as described on
https://wiki.ubuntu.com/DebuggingNetworkManager
** Changed in: network-manager (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
btw, would be helpful to see if installing linux-image-hwe-edge together
with the bad mesa would still work.. so, ppa-purge the ppa, then install
the edge kernel, reboot
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
Reported upstream as
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213
** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
#213
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/213
** Also affects: network-manager via
Hello Roman, or anyone else affected,
Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/19.0.2-1ubuntu1.1~18.04.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Package changed: ubuntu => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1836756
You have been subscribed to a public bug:
i have to hard reboot the system for ubuntu froze,so please fix the bug
.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libinput (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Desktop
64 matches
Mail list logo
