The issue still can be reproduced by 18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1682637
Title:
during recovery mode, enable network failed due to
*** This bug is a duplicate of bug 1729389 ***
https://bugs.launchpad.net/bugs/1729389
Hi Daniel,
thanks for reply, I will follow the link you sent.
Best regards
Jiri
On 22.1.2018 03:42, Daniel van Vugt wrote:
> *** This bug is a duplicate of bug 1729389 ***
>
Note: my source.lust had no trailing / so for me it was
$ sed -i
's/http:\/\/archive.ubuntu.com\/ubuntu/mirror:\/\/mirrors.ubuntu.com\/mirrors.txt/g'
/etc/apt/sources.list
to trigger the issue
Note (2): Also this feature is still undocumented since all the time
:-/.
--
You received this bug
Interesting, thanks Mathias for the update.
@Julian - I think this means you have to tackle that from apt itself then? (or
at least find out via which path it triggers the issue now).
How far are you in regard to comment #9 number 3 atm - can you take it into apt
itself already?
--
You
I was made aware in bug #1667113 that this seems to be the root bug to dup this
onto.
I know this comes down to accountsservice, as others not using it like sddm are
just fine.
If we stick to depend on accountsservice, then it comes down to the following
$ dbus-send --print-reply=literal
*** This bug is a duplicate of bug 857651 ***
https://bugs.launchpad.net/bugs/857651
If we stick to depend on accountsservice, then it comes down to the following
$ dbus-send --print-reply=literal --system --dest=org.freedesktop.Accounts
/org/freedesktop/Accounts
*** This bug is a duplicate of bug 857651 ***
https://bugs.launchpad.net/bugs/857651
Arrr wanted to send that update to the dup target ...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
*** This bug is a duplicate of bug 857651 ***
https://bugs.launchpad.net/bugs/857651
@Spiegel - yes I think so, thanks for finding the old reference.
Marking as a Dup.
Could someone of the desktop Team give this a look from the 18.04/gnome-
shell POV - will this go away?
** This bug has
[Expired for iproute2 (Ubuntu) because there has been no activity for 60
days.]
** Changed in: iproute2 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1744631
Title:
package network-manager-config-connectivity-ubuntu
Public bug reported:
Happened during dist-upgrade from 17.04 to 17.10.
ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: network-manager-config-connectivity-ubuntu 1.8.4-1ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-42.46-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
*** This bug is a duplicate of bug 1729389 ***
https://bugs.launchpad.net/bugs/1729389
I think we can ignore that log message as unrelated to the problem of
bluetooth not working. Other people have been reporting that message
even while Bluetooth works.
It sounds like your new-ish machine
If it's been too long since you ran "apport-collect 1743710" then the
link probably won't work any more.
Please run "apport-collect 1743710" again and follow the links it gives
you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Public bug reported:
When I try to play a file in Rhythmbox. I get a "Thump" sound and a pop-
up message that it can't connect to gstreamer.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.4.0-109.132-powerpc-smp 4.4.98
Hi,
I don't think it is about a wrongly translated string, but more about the
combination of regional choices that makes the langage mecanism choose the
locale in german (all my interface is in right english but my calendar and
days of weeks in softwares).
I guess it is something because of:
-
WOW!!
This bug was reported in 2009, and almost 10 years later we have no solution!!
It's getting very difficult to find a cheap PCI sound card that works fine with
Ubuntu or any other Linux distribution.
Would a SoundBlaster Live work fine??
Talk about market reserve!!!
--
You received this
I tested this on a non-Libreboot (i.e., stock Lenovo BIOS) ThinkPad
X200s. Exactly the same problem.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1743259
Title:
3D
Any news for the newbie on how soon the fix will be applied?
I see the comment on downgrading and pinning a bunch of MESA packages --
but I don't know exactly how to do the downgrade, nor how to safely undo
the pinning once it's no longer necessary. I don't want to muck up my
machine.
--
You
Then why is there an option to mark duplicates if duplicates aren't
supposed to be marked?
so you think it's an xorg problem as well? I wasn't sure whether that
was the right package as I would have thought it would have been a
problem with displaylink, as it started to happen after I installed
Public bug reported:
the qt library software such as VLC, qbittorrent, and qtcreator, their
font rendering ugly than system font. But if you download Qt development
kit(that *.run file), you will found, its qtcreator has same render
effect with system.
ProblemType: Bug
DistroRelease: Ubuntu
** Changed in: kmod (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1337262
Title:
kmod should permit use of compressed modules
** This bug is no longer a duplicate of bug 1744496
Cursor flickering using DisplayLink and USB Monitor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1511244
Title:
** This bug is no longer a duplicate of bug 1744496
Cursor flickering using DisplayLink and USB Monitor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1278223
Title:
** This bug is no longer a duplicate of bug 1744496
Cursor flickering using DisplayLink and USB Monitor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1485682
Title:
** Changed in: gnome-session
Status: Unknown => Confirmed
** Changed in: gnome-session
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to d-conf in Ubuntu.
sevku, please don't mark other bugs duplicates of this one, or adjust
the title/Bug Description.
Regarding your question:
>"How do I properly report them?"
File a new report via a terminal:
ubuntu-bug xorg
>"How do I use the gnome flashback package?"
Install it, reboot, and it should be an
Is this the same issue as bug #857651 ??
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1667113
Title:
System users appears in Ligthdm and user switcher
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: bluez (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: click (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: xorg (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: fontconfig (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: ifupdown (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: libgsm (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: sudo (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: base-files (Debian)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to base-files in Ubuntu.
https://bugs.launchpad.net/bugs/13795
Title:
base-files: Insecure PATH in
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Package changed: xorg (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1744517
Title:
Ubuntu Software
Status in gnome-software package
Public bug reported:
I don't know
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: marco (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-hwe-16.04 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Description changed:
After upgrading gnome-terminal to 3.26 (from 3.24), that error is still
logged.
Some old workarounds (might be irrelevant now):
https://github.com/budgie-desktop/budgie-desktop/issues/532
** Summary changed:
- Cursor flickering using DisplayLink and HP EliteDisplay S140u USB Portable
Monitor
+ Cursor flickering using DisplayLink and USB Monitor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
** Description changed:
After upgrading gnome-terminal to 3.26 (from 3.24), that error is still
logged.
- This is a gtk3 fault, and is supposed to be fixed in git:
+ Some old workarounds (might be irrelevant now):
https://github.com/budgie-desktop/budgie-desktop/issues/532
+
** Summary changed:
- Cursor flickering using HP EliteDisplay S140u USB Portable Monitor
+ Cursor flickering using DisplayLink and HP EliteDisplay S140u USB Portable
Monitor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Public bug reported:
I am trying to use the HP EliteDisplay S140u external USB display,
therefore I have installed DisplayLink softwares. Now, when the display
is connected, the Computer quickly runs into 100% CPU load and crashes.
This only happens when the display is connected. It is enough to
*** This bug is a duplicate of bug 1744496 ***
https://bugs.launchpad.net/bugs/1744496
** This bug has been marked a duplicate of bug 1744496
Cursor flickering using HP EliteDisplay S140u USB Portable Monitor
** This bug is no longer a duplicate of bug 1744496
Cursor flickering using
*** This bug is a duplicate of bug 1744496 ***
https://bugs.launchpad.net/bugs/1744496
** This bug has been marked a duplicate of bug 1744496
Cursor flickering using HP EliteDisplay S140u USB Portable Monitor
--
You received this bug notification because you are a member of Ubuntu
Touch
*** This bug is a duplicate of bug 1744496 ***
https://bugs.launchpad.net/bugs/1744496
** This bug has been marked a duplicate of bug 1744496
Cursor flickering using HP EliteDisplay S140u USB Portable Monitor
--
You received this bug notification because you are a member of Ubuntu
Touch
** Description changed:
After upgrading gnome-terminal to 3.26 (from 3.24), that error is still
logged.
This is a gtk3 fault, and is supposed to be fixed in git:
https://github.com/budgie-desktop/budgie-desktop/issues/532
Related upstream discussions:
-
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1744033
Title:
package openssh-server 1:6.6p1-2ubuntu2.8 failed
64 matches
Mail list logo
