Daniel,
I took a few days, but it did again fail with the same issue. I'm
attaching the log, collected shortly after the failure by switch to
console while running the Wayland session, as you requested. Had to
reboot afterwards, to be able to log on to the desktop.
Hope this helps you spot the
Public bug reported:
When I start screencast by pressing Alt+Ctrl+Shift+R, it auto-stops
itself exactly after 30 seconds. That is highly unexpected, there is no
explanation as to why the sudden stop. That leaves me confused as an
user.
Workaround is to increase the screencast max duration:
** Tags removed: wayland-session
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Title:
Greeter/lockscreen fails to authenicate in an endless loop
To manage notifications
Also a problem with the Wayland session. Not a big surprise. For now,
I've turn off the screen lock.
Not sure what else to do.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1755800
Addendum: I was running the Xorg ("Ubuntu") session when the problems
occurred. I'm trying the Wayland session now, so the autogenerated tag
is not correct, and maybe not relevant.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3
Public bug reported:
After a recent install of the 18.04 (why is a separate story), I notice
that after some number of successful screen locks, I become locked out
of the desktop with an authentication failure. During those
unsuccessful attempts to log in, syslog shows:
Mar 13 22:46:04 magpie
Thank you very much for your quick reply! There are in fact two crash
report files:
$ ubuntu-bug /var/crash/_usr_bin_Xwayland.1000.crash
reported that it's already reported as
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1731911
$ ubuntu-bug
lspci:
00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev
07)
00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:14.0 USB controller: Intel Corporation Sunrise
Public bug reported:
I have a notebook with dual graphic cards: Intel+Nvidia (handled by
nouveau). The miniDP port is apparently connected to nvidia since it
stops working when I use nouveau.modeset=0. I am able to start a Wayland
session when there's no secondary monitor connected; as soon as I
syslog
** Attachment added: "syslog.gz"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1755588/+attachment/5078582/+files/syslog.gz
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
** Also affects: a11y-profile-manager (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-mate
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to a11y-profile-manager in Ubuntu.
** Changed in: ubuntu-mate-meta (Ubuntu)
Status: New => In Progress
** Changed in: ubuntu-mate-meta (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: ubuntu-mate-meta (Ubuntu)
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
--
You received
This happened to me only when I tried to format an USB with NTFS to make
a friend a windows USB boot disk. Probably he is guilty touse windows
instead of nicer versions of Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
I have exactly the same. All working fine with 17.04 since upgrade on
17.10 or new install on 17.10 Im facing the issue. I tried everything I
found on the net that could possibly solve the issue but without
success. So much hours spend on the issue already.
--
You received this bug notification
*** This bug is a duplicate of bug 1280300 ***
https://bugs.launchpad.net/bugs/1280300
>From the discussion upthread this doesn't seem to be actually caused by any
particular wm.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
The playlist is nowhere to be found in Totem. Apparently it was
perceived being too complex by the Gnome guys.
The problem is that there are previous/next buttons which apparently
navigate through some kind of an invisible playlist, so there is a
notion of a playlist. That is extremely confusing
Hi, actually I've completely overlooked the button "Playlist" above browser.
https://askubuntu.com/questions/452094/accessing-menus-in-rhythmbox-on-gnome
describes exactly the same issue.
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
Public bug reported:
Affects Ubuntu 17.10 and Sound Recorder 3.24.0.1.
gnome-sound-recorder reads files from ~/Recordings, but some strange
file names (unicode?) break the application, that it doesn't work at
all, at least works faulty.
You can reproduce this bug:
rm -rf ~/Recordings
gs-daemon (Ubuntu) => gnome-shell
> (Ubuntu)
>
> ** Changed in: gnome-shell (Ubuntu)
>Importance: Undecided => Low
>
--
Martin Weinberg
6 Grass Hill Rd
West Whately, MA
010039
** Bug watch added: GNOME Bug Tracker #790040
https://bugzilla.gnome.org/show_bug.cgi?id=790040
Just to make sure, I again repeated the sequence of events outlined
above on the stock 17.10 kernel:
Linux magpie 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
The behavior is identical to that reported above.
One minor elaboration: when I open the
Public bug reported:
In the default configuration, resuming my T440s on the Lenovo ultradock
results in not detecting the external monitor followed by a suspend.
If I open the lid while on the dock, gnome detects the external monitor
and blanks the laptop display. Then, closing the lid results
Still present in Ubuntu 17.10 using Wayland.
Reproduce this bug in three simple steps:
1. Start Gedit.
2. Start searching Ctrl+f.
3. Change keyboard layout Win+Space.
BUG: Search widget is gone, focus is nowhere(?).
Step 3. should change keyboard layout, nothing else.
--
You received this bug
Yes, no problem with GNOME on Xorg. Thanks for the heads up.
I found another problem with Wayland handling the dock + laptop lid that
works correctly with Xorg. Just trying to help. Not sure what package
to file a bug on, do you? Would that be xwayland?
--
You received this bug notification
Yes, GNOME on Wayland. I will try GNOME on X.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1725698
Title:
Size decreases when cycling between full-screen mode using F11
It worked! I switched my machine back to hybrid mode (so that both Intel
and Nvidia cards are visible in lspci) and added the nouveau.modeset=0
kernel parameters. And now I am able to select the Ubuntu (wayland)
option and indeed it works: XDG_SESSION_TYPE=wayland, and the About
dialog shows
Daniel, thank you so much for your time investigating this, I appreciate
it.
The /etc/modprobe.d definitely exists:
$ ls -la /etc/modprobe.d/
total 76
drwxr-xr-x 2 root root 4096 okt 23 11:51 .
drwxr-xr-x 153 root root 12288 okt 23 11:51 ..
-rw-r--r-- 1 root root 2507 júl 31 2015
Public bug reported:
Launch an gnome-terminal and cycle between full screen and normal by
pressing F11 twice. The original size of the terminal is not restored.
Doing this multiple times, the window continues to shrink.
This did not occur on 17.04 or earlier. I use this regularly as part of
my
** Attachment added: "journalctl"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4978285/+files/huhu
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1724583
** Attachment added: "mutter log 3"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975773/+files/mutter-2156-debug-log-D3L47Y-nokeycode
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Attaching mutter log; but removing lines such as these:
KEYBINDINGS: Grabbing keybinding keycode 133 mask 0x0 on 0x15a
Since it may reveal my password.
** Attachment added: "mutter log 2"
** Attachment added: "mutter log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975771/+files/mutter-1662-debug-log-H7DC8Y
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Correction: *those two cards are not completely separate but need to
cooperate somehow (since Intel's connected to the panel while Nvidia's
connected to HDMI, but they need to cooperate, for example when Intel
needs to draw over HDMI when an external monitor is connected)
--
You received this
Thank you for your responses, and I apologize if I sounded rude - I
didn't meant to.
I rebooted in the hybrid mode and added the abovementioned lines into
/etc/environment, unfortunately the /tmp/mutterlogs file is not created.
There are other files though:
$ ls -la /tmp/mutter*
-rw--- 1 gdm
I believe this is a bug in GDM3 detection algorithm which incorrectly
disables Wayland support on a system which runs just fine with Wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Thanks. I know Wayland+KMS doesn't work with NVIDIA proprietary.
However, I don't use NVIDIA proprietary drivers and I don't have them
installed and I don't want to use Wayland on NVIDIA proprietary. Thus,
your conclusion is not right.
When I enable "Hybrid" mode in BIOS, I believe that both VGA
Thanks for the info on Hybrid mode - really nice! However, what I'd like
is to run Ubuntu+Wayland on my Intel card only. So, I don't want to run
it in hybrid mode, I don't want to run it on NVIDIA proprietary, just on
the Intel card. KDE Plasma+Wayland runs fine and uses Intel only; GDM3
forces me
I have switched to the Hybrid mode. Now the only session available is
the Xorg-based session; About dialog shows that the Intel® HD Graphics
530 (Skylake GT2) is now being used. Could it be that it is not
compatible with Wayland?
Anyway, attaching the lspci -k of the Hybrid mode. In the hybrid
** Attachment added: "lspci -k of the Hybrid mode"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975632/+files/lsp_hybrid
** Summary changed:
- gdm3 doesn't list wayland-based sessions
+ gdm3 doesn't list wayland-based sessions on Intel® HD Graphics 530 (Skylake
I actually have a nvidia card, and since I switched to Discrete mode in
BIOS, Wayland session works properly; moreover it seems to be working on
top of Nouveau (the About dialog says that Graphics is NV117).
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
** Attachment added: "lspci -k"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975580/+files/lsp
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1724583
*** This bug is a duplicate of bug 1723577 ***
https://bugs.launchpad.net/bugs/1723577
Solved! I went to BIOS and switched the Video card setting from Hybrid
to Discrete. Now gdm3 offered the wayland option (or, rather, both
"Ubuntu" and "Ubuntu on Xorg"). I now run Wayland as confirmed by
*** This bug is a duplicate of bug 1723577 ***
https://bugs.launchpad.net/bugs/1723577
** Attachment added: "Output of journalctl -u gdm.service"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4975011/+files/gdm.log
** Summary changed:
- gdm no wayland
+ gdm3
*** This bug is a duplicate of bug 1723577 ***
https://bugs.launchpad.net/bugs/1723577
I disagree about the duplicate status.
This bug: gdm3 itself starts in Wayland successfully, but it doesn't
list the wayland sessions (it only lists the xorg-based sessions).
The bug #1723577 is that gdm3
*** This bug is a duplicate of bug 1723577 ***
https://bugs.launchpad.net/bugs/1723577
Attaching my /etc/gdm3/custom.conf:
** Attachment added: "custom.conf"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1724583/+attachment/4974887/+files/custom.conf
--
You received this bug
I enabled the debug logs for gdm3 in /etc/gdm3/custom.conf, but the logs
are nowhere to be found: /var/log/gdm3 is empty.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1724583
Title:
Public bug reported:
I've just upgraded to Ubuntu 17.10 and switched the login manager from
sddm to gdm3. Unfortunately it doesn't list the -wayland sessions. The
/usr/share/xsessions folder indeed only contains the -xorg -related
sessions:
$ ls -la /usr/share/xsessions
total 36
drwxr-xr-x 2
Hm, there actually is /usr/share/wayland-sessions/ubuntu.desktop - could
it be that gdm3 for some reason ignores this folder?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1724583
Public bug reported:
gnome-software spams this message to journald:
Okt 13 11:00:19 zenbook gnome-software[3582]: g_byte_array_remove_range:
assertion 'index_ + length <= array->len' failed
Okt 13 11:00:19 zenbook gnome-software[3582]: Ignoring unexpected response
ProblemType: Bug
Same Problem, I am trying to move dropbox folders into owncloud folders,
too.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1636514
Title:
nautilus crashed with SIGSEGV in
I installed `gnome-software-plugin-flatpak`.
I had to download the `flatpakref` file, then double click it via the
file manager, which caused GNOME Software to spit assorted errors and
claims of something going wrong. I was however presented with an Install
button which when clicked prompted for
Ubuntu MATE 16.04.3 also.
Followed the test case on the Ubuntu MATE forum:
* https://ubuntu-mate.community/t/help-test-a-critical-bug-fix-in-
ubuntu-mate-16-04/14624
I confirm that this update resolves the issue. I've actually been
running the fixed version of gvfs on another Ubuntu MATE
** Also affects: firefox (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-mate
Status: New => Invalid
** Changed in: ubuntu-mate
Status: Invalid => Opinion
** Changed in:
This is due to a change of behaviour in GTK+3.
** Also affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-mate
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1710507
Title:
** Also affects: gimp (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-mate
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gimp in Ubuntu.
** Changed in: gvfs (Ubuntu Xenial)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in Ubuntu.
https://bugs.launchpad.net/bugs/1133477
Title:
[SRU] cut-n-paste move files got stuck forever
Public bug reported:
There is no xserver-xorg-video-ast-hwe-16.04 package. So i can not use
the ASpeed graphics for output anymore. I needed the hwe for the GTX
1060 nouveau driver.
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: evince 3.18.2-1ubuntu4.1
ProcVersionSignature: Ubuntu
Interestingly this bug has resurfaced in Ubuntu MATE 17.10. I have
tracked this does to `unity-gtk-module` which is loaded in Ubuntu MATE
17.10 but has not been used in prior releases.
If GTK_MODULES does not includes `unity-gtk-module` then this issue does
not present.
** Also affects: caja
It really seems like some old bug in GTK+2. It crashes on this line,
always with the same stacktrace.
* https://bugzilla.redhat.com/1293096
* https://bugzilla.redhat.com/1343807
I'm doubt that rc_style will ever be fixed as this is replaced with
GtkStyleProvider in GTK3+. Ubuntu MATE was
** Changed in: gtk+3.0 (Ubuntu Yakkety)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1641914
Title:
Please backport two recent-manager patches
Yakkety 16.10 goes EOL this month.
** Changed in: gtk+2.0 (Ubuntu Yakkety)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1641912
Title:
whoa, this is indead a really old bug. i've since updated several times
ubuntu and thus have not got this problem again.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1461510
** Also affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1689927
Title:
and still nothing ..
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1551003
Title:
Xenial Files cannot browse network
To manage notifications about this bug go to:
This bug is still present in gedit 3.18.3 under 16.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/797485
Title:
SRU: Status Bar Covers File Name at Bottom
To manage
Still exists in Gnomebuntu 17.04.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1244090
Title:
Pressing any global keyboard shortcut causes temporary loss of focus
Public bug reported:
When you debug a node.js application by running:
$ node --inspect main.js
...then in the latest versions of node inspector it prints an URL to
chrome devtools, similar to:
chrome-
devtools://devtools/bundled/inspector.html?experiments=true=true=127.0.0.1:9229/ffd8c6e0
Some further information:
The background is *not* the X root window; xwininfo says its called "Desktop".
Modifying the X root window with xsetroot doesn't change anything. However,
when turning compositing on or off, the proper root window background can be
seen for a split second.
--
You
*** This bug is a duplicate of bug 1626756 ***
https://bugs.launchpad.net/bugs/1626756
This bug is *not* a duplicate of #1626756.
#1626756 is about a missing wallpaper depending on the state of
org.gnome.desktop.background.show-desktop-icons.
This is about a missing wallpaper depending on
Update: Not a problem of FileRoller - ZIP was created under Windows
using PowerShell and that thing has a bug in creating ZIPs. They use
backslashes in filenames rather than forward slashes which does not
meet the standard.
Best regards, Martin.
--
You received this bug notification because you
Public bug reported:
Since ibus did not work for me (it ignored any configured layout and
always used english) I tried to install fcitx as a workaround. Fcitx
works, yet I am not able to type in á by pressing = and a, only by
pressing the "8" key. Yet this only apparently applies to KDE
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd-shim in Ubuntu.
https://bugs.launchpad.net/bugs/1624171
Title:
systemd-logind error at startup if systemd-shim and upstart-sysv
To manage
** Also affects: gvfs (Ubuntu)
Importance: Undecided
Status: New
** Also affects: caja (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1663421
Title:
systemd-udevd crashed with SIGABRT in __open_nocancel()
To manage notifications
still does not work ... any chance to fix ?? It takes a month,, THANK
YOU
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1551003
Title:
Xenial Files cannot browse network
To
Carlos Garnacho [2017-03-01 10:59 -]:
> > - Is it acceptable to have approximate search results if the indexing isn't
> > (yet) up to date?
>
> If tracker-miner-fs is not paused/throttled down, it will pick up
> changes in monitored folders just as fast as any other app, there is
> very
> To summarize, I see 2 performance questions:
I'd add:
- Is it acceptable to have approximate search results if the indexing isn't
(yet) up to date?
- Does it significantly affect battery life?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
Hello Carlos,
Carlos [2017-02-28 13:58 -]:
> Just wanted to mention I disagree with your statements and that I have
> the opposite experience and feedback from users (we agree we disagree,
> which is fine of course :)).
Yep :-) (I'm not making the call anyway). Thanks for sharing your
Carlos [2017-02-28 12:08 -]:
> "Tracker imposes a huge cost due to always indexing everything"
> As long as is low priority and the kernel scheduler works fine it shouldn't
> be an issue.
This isn't true. This will use a lot more CPU and disk cycles, thus decreasing
battery life. Or, if you
So all of this tells me that tracker isn't a replacement for typeahead
search. They have two entirely different use cases:
* Typeahead search only affects the currently displayed directory (or
should anyway -- you search through what you see, not through the
entirety of the file system). It is
I can also confirm fix after upgrading from something older to
4.4.0-63-generic. Thanks to everybody who was involved bringing the
solution!
Best wishes, Martin.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu
Approximately every 2 weeks I am downloading a few ZIP files from the
same location (they change usually about once a week containing windows
setup files). Suddenly I am experiencing this issue (using Ubuntu 14.04
- Archive Manager v3.10.2.1) with these zips. I cannot see any related
update being
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/797485
Title:
SRU: Status Bar Covers File Name at Bottom
To
@Scott:
https://git.launchpad.net/postfix/commit/?h=stable/v3.1=1a190cf17cc02
looks rather complicated and also creates an unmanaged config file. Why
not just always add those After= to the .service? If resolved is not
enabled, then After=systemd-resolved is a no-op (it's only ordering, not
a
** Also affects: resolvconf (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847440
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
Public bug reported:
On shutdown or "systemctl stop systemd-resolved" you get a long hang:
● systemd-resolved.service - Network Name Resolution
CGroup: /system.slice/systemd-resolved.service
└─control
├─15479 /bin/sh -c [ ! -e /run/resolvconf/enable-updates ] ||
This is still being discussed upstream, so let's get to an agreement
there first, land it in upstream master, and then backport the change.
Note that there is not much point with debdiffs, it's easier to cherry-
pick the fix directly into the packaging branches with gbp pq and debian
I'm afraid this is by design and wontfix, see
https://github.com/systemd/systemd/issues/4821#issuecomment-264995354
for details. This isn't something which we reasonably can/should change
downstream, so I suggest to direct discussions to the upstream bug.
Thanks!
** Changed in: systemd (Ubuntu)
> Before=networking.service
> +Before=systemd-networkd.service
FTR, this should be generalized to Before=network-pre.target. This is
also applicable to Debian.
** Also affects: resolvconf (Ubuntu)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu)
Status: New
> In CUPS everything is OK and as intended.
No -- as above, the maintainer scripts need to stop cups.{socket,path}
first before stopping cups.service. Also, as it seems you can entirely
drop that .path unit as it's fairly useless -- we don't start cups on
demand, but it always starts on boot (in
** Bug watch added: github.com/systemd/systemd/issues #4821
https://github.com/systemd/systemd/issues/4821
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4821
Importance: Unknown
Status: Unknown
** Changed in: systemd (Ubuntu)
Status: Confirmed =>
** Bug watch added: github.com/systemd/systemd/issues #4801
https://github.com/systemd/systemd/issues/4801
** Also affects: systemd via
https://github.com/systemd/systemd/issues/4801
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
** Also affects: dpkg (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- package systemd 229-4ubuntu4 failed to install/upgrade: triggers looping,
abandoned
+ several packages failed to install/upgrade: triggers looping, abandoned
--
You received this bug notification
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
This is a duplicate of bug 1624729, but for some reason Launchpad keeps
timing out in trying to mark it as such, so I'm closing this.
** Changed in: systemd (Ubuntu)
Status: New => Invalid
--
You
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** This bug has been marked a duplicate of bug 1573322
package systemd 229-4ubuntu4 failed to install/upgrade: triggers
*** This bug is a duplicate of bug 1573322 ***
https://bugs.launchpad.net/bugs/1573322
** This bug has been marked a duplicate of bug 1646767
package systemd 232-6 failed to install/upgrade: gatilhos em "loop",
abandonado
** This bug is no longer a duplicate of bug 1646767
package
** No longer affects: systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1645631
Title:
Sending files fails because obex not loaded
To manage notifications about
I suppose you want this for yakkety too, so backported:
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h
=ubuntu-yakkety=648c659e9
** Description changed:
Ubuntu Core 16 images using cloud-init fail to function when the
DataSource is over the network (Like OpenStack) as
Hello Robert, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
Hello Will, or anyone else affected,
Accepted gnome-software into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
software/3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1 in a few hours,
and then in the -proposed repository.
Please help
301 - 400 of 13303 matches
Mail list logo
