[Bug 2024394] Re: Ubuntu 22.04.1 LTS libpod (package podman 3.4.4+ds1-1ubuntu1.22.04.1): broken network functionality for CNI plugins

[Ralf Hansen]

I can confirm this error and the workarounds.

The workaround to correct cniVersion in ~/.config/cni/net.d/*.conflist is 
working for me but it isnn't very intuitive for others.
The universe package containernetworking-plugins corrects this too but thats 
not easy maintable for a production system over time.

This is a showstopper for ubuntu container tools.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2024394

Title:
  Ubuntu 22.04.1 LTS libpod (package podman 3.4.4+ds1-1ubuntu1.22.04.1):
  broken network functionality for CNI plugins

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpod/+bug/2024394/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2009885] Re: Timeshift 21.09.1-1 broken after Rsync upgrade to 3.2.7-0ubuntu0.22.04.2

[Ralf W.]

Hello Timo,

after allowing packages from 'proposed' I manually upgraded these
packages:

rsync (version 3.2.3-8ubuntu3) ... upgraded to version 
3.2.7-0ubuntu0.22.04.2 
timeshift (version 21.09.1-1)  ... upgraded to version 21.09.1-1ubuntu1

(rsync had previously been held back)

Then I successfully ran
- an on-demand snapshot from timeshift gui
- an automated boot-snapshot

Both worked w/o problems recognized and show up in timeshift gui as
expected.

Thank you all for fixing that issue! :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009885

Title:
  Timeshift 21.09.1-1 broken after Rsync upgrade  to
  3.2.7-0ubuntu0.22.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/timeshift/+bug/2009885/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2009885] Re: Timeshift 21.09.1-1 broken after Rsync upgrade to 3.2.7-0ubuntu0.22.04.2

[Ralf W.]

On my Ubuntu 22.04 timeshift is still version 21.09.1-1 (02 Oct 2021).
No newer version is available from repository.

For the average user timeshift-snapshots stopped working ONE YEAR AGO -
afaik w/o any notification (apart from entries in log files). For this
reason, I consider this error to be rather critical and its importance
should really be increased.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2009885

Title:
  Timeshift 21.09.1-1 broken after Rsync upgrade  to
  3.2.7-0ubuntu0.22.04.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/timeshift/+bug/2009885/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [ext] [Bug 2054183] Re: nautilus not generating thumbnails anymore

[Ralf Hildebrandt]

* olive <2054...@bugs.launchpad.net>:

> the solution to not lose the configuration after the reboot :

by creating a file in /etc/sysctl.d, e.g.
/etc/sysctl.d/10-fix_nautilus
containing
kernel.apparmor_restrict_unprivileged_userns=0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054183

Title:
  nautilus not generating thumbnails anymore

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054183/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Ralf Dünkelmann]

Hi Seth,

if only it would be that easy.

Suspending and locking does not circumvent the problem. The only way to
be safe is shutting down on leave and newly boot on return.

Ubuntu is not safe here. This is a major vulnerability.

I love Ubuntu and appreciate all your work. I am a user only and if I
can help, let me know.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1887861).
https://bugs.launchpad.net/bugs/1532508

Title:
  Screen contents revealed briefly on resume, before even unlocking

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Ralf Dünkelmann]

Hi Seth, hi nem000,

the bug (https://bugs.launchpad.net/bugs/2013453), that nem000 created
was marked as a duplicate of this one. This is the case for most of the
related bugs listed here. So it seems that this here is the issue to go
ahead with?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (1818357).
https://bugs.launchpad.net/bugs/1532508

Title:
  Screen contents revealed briefly on resume, before even unlocking

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Ralf Dünkelmann]

with an Eizo monitor connected externally when ubuntu is "on lock", I
can unlock my Laptop completely without typing a password.

This isn't just a bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (2012672).
https://bugs.launchpad.net/bugs/1532508

Title:
  Screen contents revealed briefly on resume, before even unlocking

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking

[Ralf Dünkelmann]

Hi there,

I am using ubuntu budgie 22 on a tuxedo laptop and can reproduce
reveiling of content when I lock the screen and connect to an external
monitor afterwards. When connecting the monitor the lower part of the
screen is reveiled shortly. When disconnecting the monitor, the upper
part reveils (and stays visible). Everything before typing the password.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to a duplicate bug report (2012672).
https://bugs.launchpad.net/bugs/1532508

Title:
  Screen contents revealed briefly on resume, before even unlocking

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976365] Re: TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'int'

[Ralf Hildebrandt]

https://github.com/SpamExperts/pyzor/pull/58/commits/1385ab7c7e8ba051cd22e7eb5a16f0c60854358d

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976365

Title:
  TypeError: %b requires a bytes-like object, or an object that
  implements __bytes__, not 'int'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyzor/+bug/1976365/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1976365] [NEW] TypeError: %b requires a bytes-like object, or an object that implements __bytes__, not 'int'

[Ralf Hildebrandt]

Public bug reported:

May 31 11:02:23 mail-cbf-int pyzor[487539]: Traceback (most recent call last):
May 31 11:02:23 mail-cbf-int pyzor[487539]:   File "/usr/bin/pyzor", line 426, 
in 
May 31 11:02:23 mail-cbf-int pyzor[487539]: main()
May 31 11:02:23 mail-cbf-int pyzor[487539]:   File "/usr/bin/pyzor", line 152, 
in main
May 31 11:02:23 mail-cbf-int pyzor[487539]: if not dispatch(client, 
servers, config):
May 31 11:02:23 mail-cbf-int pyzor[487539]:   File "/usr/bin/pyzor", line 257, 
in check
May 31 11:02:23 mail-cbf-int pyzor[487539]: send_digest(digested, 
mock_runner, servers)
May 31 11:02:23 mail-cbf-int pyzor[487539]:   File "/usr/bin/pyzor", line 280, 
in send_digest
May 31 11:02:23 mail-cbf-int pyzor[487539]: _send_digest(runner, 
servers[0], digested)
May 31 11:02:23 mail-cbf-int pyzor[487539]:   File "/usr/bin/pyzor", line 271, 
in _send_digest
May 31 11:02:23 mail-cbf-int pyzor[487539]: runner.run(server, (digested, 
server))
May 31 11:02:23 mail-cbf-int pyzor[487539]:   File 
"/usr/lib/python3/dist-packages/pyzor/client.py", line 258, in run
May 31 11:02:23 mail-cbf-int pyzor[487539]: response = self.routine(*args, 
**kwargs)
May 31 11:02:23 mail-cbf-int pyzor[487539]:   File 
"/usr/lib/python3/dist-packages/pyzor/client.py", line 120, in _mock_check
May 31 11:02:23 mail-cbf-int pyzor[487539]: msg = (b"Code: %s\nDiag: 
OK\nPV: %s\nThread: 1024\nCount: 0\n"
May 31 11:02:23 mail-cbf-int pyzor[487539]: TypeError: %b requires a bytes-like 
object, or an object that implements __bytes__, not 'int'

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pyzor 1:1.0.0-3
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue May 31 13:44:15 2022
Dependencies:
 
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pyzor
UpgradeStatus: Upgraded to focal on 2021-04-07 (418 days ago)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2021-12-09T09:45:26

** Affects: pyzor (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1976365

Title:
  TypeError: %b requires a bytes-like object, or an object that
  implements __bytes__, not 'int'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyzor/+bug/1976365/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970957] Re: suspend problem

[Ralf Sternberg]

+1 for T460s.

Laptop suspends properly, but doesn't resume on any event (open the lid, 
pressing power button).
Both with Wayland and Xorg.

Graphics: Intel HD Graphics 520 (SKL GT2).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970957

Title:
  suspend problem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

[Ralf Sternberg]

*** This bug is a duplicate of bug 1933186 ***
https://bugs.launchpad.net/bugs/1933186

 Thanks for your patience!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973802

Title:
  Gnome Shell crashes when disconnecting external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973802/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

[Ralf Sternberg]

It just happened again and this time it seems a report has been uploaded:
https://errors.ubuntu.com/oops/f18abe5a-d79a-11ec-9ae6-fa163e55efd0

Disconnected the external monitor, the desktop is visible on the laptop
screen, and two seconds later, the UI session crashes.

The timestamp shown on https://errors.ubuntu.com/user/YOUR_ID is a bit
off, however, there weren't any other incidents so this must be the one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973802

Title:
  Gnome Shell crashes when disconnecting external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973802/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972115] Re: ubuntu-bug exits after dialog instead of sending data

[Ralf Sternberg]

This bug seems to prevent me from providing a crash log in
https://bugs.launchpad.net/bugs/1973802.

Is there any alternative way of attaching a crash log to a bug report?
Attachment doesn't work, apparently because of the file size. Thanks.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972115

Title:
  ubuntu-bug  exits after dialog instead of sending data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972115/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

[Ralf Sternberg]

Right. Now I call `apport-cli` with the crash file as parameter. As soon
as I press "S", the program terminates immediately. No browser window is
being opened.

$ apport-cli _usr_bin_gnome-shell.1000.crash

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
  S: Send report (79.5 MB)
  V: View report
  K: Keep report file for sending later or copying to somewhere else
  I: Cancel and ignore future crashes of this program version
  C: Cancel
Please choose (S/V/K/I/C): S
$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973802

Title:
  Gnome Shell crashes when disconnecting external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973802/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

[Ralf Sternberg]

So `ubuntu-bug ` fails and an error UI pops up, asking to
send an error report (which I did). After that, `apport-cli` tells me
that there are no pending crash reports.

Strangely, there are no recent items on
https://errors.ubuntu.com/user/, only some that are
several days, some several months old.

Trying to attach the crash log here failed again. I've opened
https://bugs.launchpad.net/launchpad/+bug/1974066 for that.

Seems I'm running out of options, sorry.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973802

Title:
  Gnome Shell crashes when disconnecting external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973802/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor

[Ralf Sternberg]

Thanks. I've found the corresponding crash log and tried to attach it
here, but the upload fails (always end up on a site saying "Uh oh :(".
Might be the file size (76M), even a gzipped version (55M) did not
succeed.

Using `ubuntu_bug` as recommended in
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
did not seem to do anything (perhaps running into that same problem).

Any ideas?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973802

Title:
  Gnome Shell crashes when disconnecting external monitor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1973802/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973802] [NEW] Gnome Shell crashes when disconnecting external monitor

[Ralf Sternberg]

Public bug reported:

Ubuntu 22.04, gnome-shell 42.0-2ubuntu1

When unplugging an external monitor connected via USB-C to my Thinkpad
P14s, the entire UI session crashes. While the external monitor is
plugged in, it is configured as the primary display. Here are the gnome-
shell logs of the latest incident, I suppose the relevant part is
`assertion 'window->stack_position >= 0' failed`.

May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212959 does not exist.
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available
May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212963 does not exist.
May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212964 does not exist.
May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212965 does not exist.
May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212966 does not exist.
May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for 
PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 212967 does not exist.
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 31 with keysym 31 (keycode a).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 32 with keysym 32 (keycode b).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 33 with keysym 33 (keycode c).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 34 with keysym 34 (keycode d).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 35 with keysym 35 (keycode e).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 36 with keysym 36 (keycode f).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 37 with keysym 37 (keycode 10).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 38 with keysym 38 (keycode 11).
May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting 
existing binding of keysym 39 with keysym 39 (keycode 12).
May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope for 
PID 213085: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 213085 does not exist.
May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope for 
PID 213089: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 213089 does not exist.
May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope for 
PID 213090: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: 
Process with ID 213090 does not 

[Bug 1959103] [NEW] polkitd crashes with segfault with specific config file

[Ralf Schulze]

Public bug reported:

The following config file in
`/etc/polkit-1/localauthority.conf.d/02-allow-colord.conf` can cause a
segfault in `polkitd`.

```
polkit.addRule(function(action, subject) {
if ((action.id == "org.freedesktop.color-manager.create-device" ||
action.id == "org.freedesktop.color-manager.create-profile" ||
action.id == "org.freedesktop.color-manager.delete-device" ||
action.id == "org.freedesktop.color-manager.delete-profile" ||
action.id == "org.freedesktop.color-manager.modify-device" ||
action.id == "org.freedesktop.color-manager.modify-profile") &&
subject.isInGroup("{group}")) {
return polkit.Result.YES;
}
});
```

1. As normal user: `systemctl restart cron.service`
2. Error message `Failed to restart cron.service: Message recipient 
disconnected from message bus without replying`
3. `dmesg` reports: 

```
   58.003893] polkitd[963]: segfault at 8 ip 558a96789856 sp 
7ffda31e45f0 error 4 in   polkitd[558a96784000+f000]
[   58.003899] Code: 50 c7 ff ff 4d 89 e5 48 89 44 24 08 eb 53 66 0f 1f 44 00 
00 48 8b 44 24 10 48 89 e9 be 10 00 00 00 31 ff 48 8d 15 0b af 00 00 <4c> 8b 40 
08 31 c0 e8 af cb ff ff 48 8b 7c 24 10 e8 65 c9 ff ff 4c
``

If you remove the 02-allow-colord.conf the segfault goes away and you
are normally prompted for a password. You can also find a couple of
references in the internet, e.g http://c-nergy.be/blog/?p=12043.

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "crash file"
   
https://bugs.launchpad.net/bugs/1959103/+attachment/5557607/+files/_usr_lib_policykit-1_polkitd.0.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1959103

Title:
  polkitd crashes with segfault with specific config file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1959103/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1953720] [NEW] OSError: [Errno 30] Read-only file system: '/var/crash/...

[Ralf Hildebrandt]

Public bug reported:

Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last):
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 408, 
in 
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: main()
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 152, 
in main
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: if not dispatch(client, 
servers, config):
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 239, 
in check
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: send_digest(digested, 
mock_runner, servers)
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 262, 
in send_digest
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: _send_digest(runner, 
servers[0], digested)
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File "/usr/bin/pyzor", line 253, 
in _send_digest
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: runner.run(server, (digested, 
server))
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File 
"/usr/lib/python3/dist-packages/pyzor/client.py", line 258, in run
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: response = self.routine(*args, 
**kwargs)
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File 
"/usr/lib/python3/dist-packages/pyzor/client.py", line 120, in _mock_check
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: msg = (b"Code: %s\nDiag: 
OK\nPV: %s\nThread: 1024\nCount: 0\n"
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: TypeError: %b requires a 
bytes-like object, or an object that implements __bytes__, not 'int'
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: Error in sys.excepthook:
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: Traceback (most recent call last):
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]:   File 
"/usr/lib/python3/dist-packages/apport_python_hook.py", line 153, in 
apport_excepthook
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: with 
os.fdopen(os.open(pr_filename,
Dec  6 12:02:32 mail-cbf-int pyzor[2966924]: OSError: [Errno 30] Read-only file 
system: '/var/crash/_usr_bin_pyzor.122.crash'

1) due to an encoding error, pyzor is throwing an exception.
2) /usr/lib/python3/dist-packages/apport_python_hook.py is the exception 
handler invoked (belonging to the python3-apport package)
3) This exception handler tries to write to 
/var/crash/_usr_bin_pyzor.122.crash, which fails

I checked the permissions:

# ls -l /var/crash
total 0

# ls -ld /var/crash
drwxrwxrwt 2 root root 4096 Dec  8 16:45 /var/crash

# ls -ld /var/
drwxr-xr-x 18 root root 4096 Jun 23  2020 /var/

# ls -ld /
drwxr-xr-x 24 root root 4096 Nov 30 06:19 /

/var/crash is sticky, so why can't it write?

# cat /proc/mounts  |fgrep crash
#

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: python3-apport 2.20.11-0ubuntu27.21
ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-36-generic x86_64
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Dec  9 09:39:40 2021
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to focal on 2021-04-07 (245 days ago)

** Affects: apport (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953720

Title:
  OSError: [Errno 30] Read-only file system: '/var/crash/...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1953720/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1949104] Re: netplan try is broken

[Ralf Heiringhoff]

I can confirm that #4 works for me as a workaround

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949104

Title:
  netplan try is broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1949104/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1929252] [NEW] package tango-db 9.2.5a+dfsg1-2ubuntu1 failed to install/upgrade: »installiertes tango-db-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück

[ralf kneistler]

Public bug reported:

keine ahnung

ProblemType: Package
DistroRelease: Ubuntu 21.04
Package: tango-db 9.2.5a+dfsg1-2ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu65
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri May 21 23:08:54 2021
ErrorMessage: »installiertes tango-db-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
Python3Details: /usr/bin/python3.9, Python 3.9.4, python3-minimal, 3.9.4-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.9ubuntu1
 apt  2.2.3
SourcePackage: tango
Title: package tango-db 9.2.5a+dfsg1-2ubuntu1 failed to install/upgrade: 
»installiertes tango-db-Skript des Paketes post-installation«-Unterprozess gab 
den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: tango (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package hirsute

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929252

Title:
  package tango-db 9.2.5a+dfsg1-2ubuntu1 failed to install/upgrade:
  »installiertes tango-db-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tango/+bug/1929252/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1924241] [NEW] update von 18.04 auf 20.04 geht nicht

[Ralf]

Public bug reported:

Es konnte nicht ermittelt werden, welche Systemaktualisierungen
verfügbar sind

Ein unlösbares Problem trat während der Berechnung der
Systemaktualisierung auf.

 Wenn keine dieser zutrifft, melden Sie bitte den Fehler mithilfe des
Befehls 'ubuntu-bug ubuntu-release-upgrader-core' in einem Terminal.
Wenn Sie dies selbst untersuchen möchten, finden Sie in den
Protokolldateien unter »/var/log/dist-upgrade« Details zur
Systemaktualisierung. Schauen Sie sich insbesondere »main.log« und
»apt.log« an.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.42
ProcVersionSignature: Ubuntu 4.15.0-141.145-generic 4.15.18
Uname: Linux 4.15.0-141-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 15 10:45:55 2021
InstallationDate: Installed on 2020-05-01 (348 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to bionic on 2021-04-15 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1924241

Title:
  update von 18.04 auf 20.04 geht nicht

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1924241/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922956] [NEW] package icinga2-ido-mysql 2.11.2-1ubuntu3 failed to install/upgrade: »installiertes icinga2-ido-mysql-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück

[Ralf G. Michaels]

Public bug reported:

Mysql noch nicht konfiguriert.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: icinga2-ido-mysql 2.11.2-1ubuntu3
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Apr  7 03:18:39 2021
ErrorMessage: »installiertes icinga2-ido-mysql-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2021-04-06 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: icinga2
Title: package icinga2-ido-mysql 2.11.2-1ubuntu3 failed to install/upgrade: 
»installiertes icinga2-ido-mysql-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: icinga2 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922956

Title:
  package icinga2-ido-mysql 2.11.2-1ubuntu3 failed to install/upgrade:
  »installiertes icinga2-ido-mysql-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icinga2/+bug/1922956/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920587] Re: cmake support files are installed into a wrong directory

[Ralf Habacker]

** Description changed:

  This problem was discovered when updating kmymoney's cmake build system
  with respect to libical (see
  https://invent.kde.org/office/kmymoney/-/merge_requests/63) with
  ubuntu:20.04.
  
  libical-dev:amd64 (3.0.8-1) ...
  /# sed -i -- 's/#[ ]*deb-src/deb-src/g' /etc/apt/sources.list
  /# apt update
  /# apt-get install libical-dev
  /# dpkg -L libical-dev | grep 'LibIcal$'
  /usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal
-  
+ 
+ The correct location is /usr/lib/x86_64-linux-gnu/cmake/LibIcal.
+ 
  The issue was not fixed with ubuntu 20.10.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920587

Title:
  cmake support files are installed into a wrong directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libical/+bug/1920587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1920587] [NEW] cmake support files are installed into a wrong directory

[Ralf Habacker]

Public bug reported:

This problem was discovered when updating kmymoney's cmake build system
with respect to libical (see
https://invent.kde.org/office/kmymoney/-/merge_requests/63) with
ubuntu:20.04.

libical-dev:amd64 (3.0.8-1) ...
/# sed -i -- 's/#[ ]*deb-src/deb-src/g' /etc/apt/sources.list
/# apt update
/# apt-get install libical-dev
/# dpkg -L libical-dev | grep 'LibIcal$'
/usr/lib/x86_64-linux-gnu/cmake/cmake/LibIcal
 
The issue was not fixed with ubuntu 20.10.

** Affects: libical (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920587

Title:
  cmake support files are installed into a wrong directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libical/+bug/1920587/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1888484] [NEW] package lxd (not installed) failed to install/upgrade: »neues lxd-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück

[Ralf Hildebrandt]

Public bug reported:

During do-release-upgrade...

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: lxd (not installed)
ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Wed Jul 22 12:00:12 2020
ErrorMessage: »neues lxd-Skript des Paketes pre-installation«-Unterprozess gab 
den Fehlerwert 1 zurück
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: lxd
Title: package lxd (not installed) failed to install/upgrade: »neues lxd-Skript 
des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to focal on 2020-07-22 (0 days ago)

** Affects: lxd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888484

Title:
  package lxd (not installed) failed to install/upgrade: »neues lxd-
  Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1
  zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1888484/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1887181] [NEW] package plasma-widgets-addons 4:5.18.4.1-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/share/metainfo/org.kde.plasma.konsoleprofiles.appdata.xml', which is also in

[Ralf Weinand]

Public bug reported:

I upgraded from 18.04 to 20.04, then Gnome extensions didn't work and
asked me for an update in the task bar up the top. I clicked "Try to
upgrade" (or similar wording) and it crashed.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: plasma-widgets-addons 4:5.18.4.1-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jul 11 00:04:47 2020
DuplicateSignature:
 package:plasma-widgets-addons:4:5.18.4.1-0ubuntu2
 Unpacking plasma-widgets-addons (4:5.18.4.1-0ubuntu2) over 
(4:5.12.9-0ubuntu0.1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-1BXuPG/07-plasma-widgets-addons_4%3a5.18.4.1-0ubuntu2_amd64.deb
 (--unpack):
  trying to overwrite 
'/usr/share/metainfo/org.kde.plasma.konsoleprofiles.appdata.xml', which is also 
in package plasma-dataengines-addons 4:5.12.9-0ubuntu0.1
ErrorMessage: trying to overwrite 
'/usr/share/metainfo/org.kde.plasma.konsoleprofiles.appdata.xml', which is also 
in package plasma-dataengines-addons 4:5.12.9-0ubuntu0.1
InstallationDate: Installed on 2018-07-30 (711 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: kdeplasma-addons
Title: package plasma-widgets-addons 4:5.18.4.1-0ubuntu2 failed to 
install/upgrade: trying to overwrite 
'/usr/share/metainfo/org.kde.plasma.konsoleprofiles.appdata.xml', which is also 
in package plasma-dataengines-addons 4:5.12.9-0ubuntu0.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: kdeplasma-addons (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal package-conflict

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887181

Title:
  package plasma-widgets-addons 4:5.18.4.1-0ubuntu2 failed to
  install/upgrade: trying to overwrite
  '/usr/share/metainfo/org.kde.plasma.konsoleprofiles.appdata.xml',
  which is also in package plasma-dataengines-addons 4:5.12.9-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdeplasma-addons/+bug/1887181/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885884] Re: package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade: »installiertes collectd-core-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück

[Ralf Hildebrandt]

Not really, this is more an issue with the broken python pluging support
:(

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885884

Title:
  package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade:
  »installiertes collectd-core-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1885884/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1885884] [NEW] package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade: »installiertes collectd-core-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwert 1 zurück

[Ralf Hildebrandt]

Public bug reported:

# systemctl status collectd.service
● collectd.service - Statistics collection and monitoring daemon
 Loaded: loaded (/lib/systemd/system/collectd.service; enabled; vendor 
preset: enabled)
 Active: activating (auto-restart) (Result: exit-code) since Wed 2020-07-01 
10:46:18 CEST; 8s ago
   Docs: man:collectd(1)
 man:collectd.conf(5)
 https://collectd.org
Process: 107884 ExecStartPre=/usr/sbin/collectd -t (code=exited, 
status=0/SUCCESS)
Process: 107885 ExecStart=/usr/sbin/collectd (code=exited, status=1/FAILURE)
   Main PID: 107885 (code=exited, status=1/FAILURE)

Jul 01 10:46:18 sympa systemd[1]: collectd.service: Main process exited, 
code=exited, status=1/FAILURE
Jul 01 10:46:18 sympa systemd[1]: collectd.service: Failed with result 
'exit-code'.
Jul 01 10:46:18 sympa systemd[1]: Failed to start Statistics collection and 
monitoring daemon.

-- The job identifier is 38331.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "network" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "exec" successfully 
loaded.
Jul 01 10:46:39 sympa collectd[107929]: ERROR: 
dlopen("/usr/lib/collectd/python.so") failed: /usr/lib/collectd/python.so: 
undefined symbol: PyFloat_Type. The most common cause for this problem is 
missin>
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: Load plugin "python" 
failed with status 2.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "cpu" successfully 
loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "df" successfully 
loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "load" successfully 
loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "memory" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "disk" successfully 
loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "interface" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "uptime" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "swap" successfully 
loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "processes" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "contextswitch" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "tcpconns" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "users" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "aggregation" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: plugin_load: plugin "match_regex" 
successfully loaded.
Jul 01 10:46:39 sympa collectd[107929]: Found a configuration for the `python' 
plugin, but the plugin isn't loaded or didn't register a configuration callback.
Jul 01 10:46:39 sympa collectd[107929]: Plugin python failed to handle option 
ModulePath, return code: -1
Jul 01 10:46:39 sympa collectd[107929]: Error: Parsing the config file failed!
Jul 01 10:46:39 sympa collectd[107929]: ===
Jul 01 10:46:39 sympa systemd[1]: collectd.service: Main process exited, 
code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: collectd-core 5.9.2.g-1ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-61.55-generic 5.3.18
Uname: Linux 5.3.0-61-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Jul  1 10:27:12 2020
ErrorMessage: »installiertes collectd-core-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2016-05-26 (1496 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: collectd
Title: package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade: 
»installiertes collectd-core-Skript des Paketes post-installation«-Unterprozess 
gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to focal on 2020-07-01 (0 days ago)

** Affects: collectd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1885884

Title:
  package collectd-core 5.9.2.g-1ubuntu5 failed to install/upgrade:
  »installiertes collectd-core-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/collectd/+bug/1885884/+subscriptions

-- 
ubuntu-bugs mailing list

[Bug 1858342] Re: mdcheck_start.service fails due to missing executable

[Ralf Ehlert]

*** This bug is a duplicate of bug 1852747 ***
https://bugs.launchpad.net/bugs/1852747

I can confirm the bug on my fresh installation.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858342

Title:
  mdcheck_start.service fails due to missing executable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1858342/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874195] Re: ansible is not able to install packages via apt on 20.04

[Ralf Spenneberg]

I just confirmed, that it is not the apt proxy I am using. I will now try the 
new automated installer instead of preseeding. 
Apparently it has something to do with the preseeding I did. Actually 
apt/apt-get/aptitude worked fine and have no problems to install packages. Just 
the ansible-apt module did not work. 
But since I no have a working setup based on the new automated installer (the 
playbook works there) closing this bug is fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874195

Title:
  ansible is not able to install packages via apt on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1874195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874195] Re: ansible is not able to install packages via apt on 20.04

[Ralf Spenneberg]

I just did a fresh install of 20.04 from the live cd, and the playbook
works there as well. It must be something with my automated installation
method. Currently I am still using preseed and an apt proxy. I will
continue debugging the setup, as it still does not work in this
environment.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874195

Title:
  ansible is not able to install packages via apt on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1874195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874195] Re: ansible is not able to install packages via apt on 20.04

[Ralf Spenneberg]

Thats great info. At least it generally is able to run. 
The shebang is there to be able to call the playbook as ./apt.yml. 
For testing I removed the first two lines (comments) and on my fresh focal 
system it still fails:


PLAY [Install packages] 
**

TASK [Gathering Facts] 
***
ok: [localhost]

TASK [install apt packages] 
**
fatal: [localhost]: FAILED! => {
"changed": false
}

MSG:

 returned a result with an error set

PLAY RECAP 
***
localhost  : ok=1changed=0unreachable=0failed=1
skipped=0rescued=0ignored=0   

root@station224:~# ansible-playbook -vvv apt.yml 
ansible-playbook 2.9.6
  config file = /root/ansible.cfg
  configured module search path = ['/root/.ansible/plugins/modules', 
'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python3/dist-packages/ansible
  executable location = /usr/bin/ansible-playbook
  python version = 3.8.2 (default, Mar 13 2020, 10:14:16) [GCC 9.3.0]
Using /root/ansible.cfg as config file
host_list declined parsing /root/hosts as it did not pass its verify_file() 
method
script declined parsing /root/hosts as it did not pass its verify_file() method
auto declined parsing /root/hosts as it did not pass its verify_file() method
Parsed /root/hosts inventory source with ini plugin

PLAYBOOK: apt.yml 

1 plays in apt.yml

PLAY [Install packages]
**

TASK [Gathering Facts] 
***
task path: /root/apt.yml:2
 ESTABLISH LOCAL CONNECTION FOR USER: root
 EXEC /bin/sh -c 'echo ~root && sleep 0'
 EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo 
/root/.ansible/tmp/ansible-tmp-1587704463.5635076-240295718517288 `" && echo 
ansible-tmp-1587704463.5635076-240295718517288="` echo 
/root/.ansible/tmp/ansible-tmp-1587704463.5635076-240295718517288 `" ) && sleep 
0'
 Attempting python interpreter discovery
 EXEC /bin/sh -c 'echo PLATFORM; uname; echo FOUND; command -v 
'"'"'/usr/bin/python'"'"'; command -v '"'"'python3.7'"'"'; command -v 
'"'"'python3.6'"'"'; command -v '"'"'python3.5'"'"'; command -v 
'"'"'python2.7'"'"'; command -v '"'"'python2.6'"'"'; command -v 
'"'"'/usr/libexec/platform-python'"'"'; command -v '"'"'/usr/bin/python3'"'"'; 
command -v '"'"'python'"'"'; echo ENDFOUND && sleep 0'
 EXEC /bin/sh -c '/usr/bin/python2.7 && sleep 0'
Using module file /usr/lib/python3/dist-packages/ansible/modules/system/setup.py
 PUT /root/.ansible/tmp/ansible-local-16080wx54l1hi/tmpm8hhr014 TO 
/root/.ansible/tmp/ansible-tmp-1587704463.5635076-240295718517288/AnsiballZ_setup.py
 EXEC /bin/sh -c 'chmod u+x 
/root/.ansible/tmp/ansible-tmp-1587704463.5635076-240295718517288/ 
/root/.ansible/tmp/ansible-tmp-1587704463.5635076-240295718517288/AnsiballZ_setup.py
 && sleep 0'
 EXEC /bin/sh -c '/usr/bin/python3 
/root/.ansible/tmp/ansible-tmp-1587704463.5635076-240295718517288/AnsiballZ_setup.py
 && sleep 0'
 EXEC /bin/sh -c 'rm -f -r 
/root/.ansible/tmp/ansible-tmp-1587704463.5635076-240295718517288/ > /dev/null 
2>&1 && sleep 0'
ok: [localhost]
META: ran handlers

TASK [install apt packages] 
**
task path: /root/apt.yml:5
 ESTABLISH LOCAL CONNECTION FOR USER: root
 EXEC /bin/sh -c 'echo ~root && sleep 0'
 EXEC /bin/sh -c '( umask 77 && mkdir -p "` echo 
/root/.ansible/tmp/ansible-tmp-1587704464.6301017-78793691417016 `" && echo 
ansible-tmp-1587704464.6301017-78793691417016="` echo 
/root/.ansible/tmp/ansible-tmp-1587704464.6301017-78793691417016 `" ) && sleep 
0'
Using module file 
/usr/lib/python3/dist-packages/ansible/modules/packaging/os/apt.py
 PUT /root/.ansible/tmp/ansible-local-16080wx54l1hi/tmprt46nqpu TO 
/root/.ansible/tmp/ansible-tmp-1587704464.6301017-78793691417016/AnsiballZ_apt.py
 EXEC /bin/sh -c 'chmod u+x 
/root/.ansible/tmp/ansible-tmp-1587704464.6301017-78793691417016/ 
/root/.ansible/tmp/ansible-tmp-1587704464.6301017-78793691417016/AnsiballZ_apt.py
 && sleep 0'
 EXEC /bin/sh -c '/usr/bin/python3 
/root/.ansible/tmp/ansible-tmp-1587704464.6301017-78793691417016/AnsiballZ_apt.py
 && sleep 0'
 EXEC /bin/sh -c 'rm -f -r 
/root/.ansible/tmp/ansible-tmp-1587704464.6301017-78793691417016/ > /dev/null 
2>&1 && sleep 0'
The full traceback is:
  File 

[Bug 1874195] Re: ansible is not able to install packages via apt on 20.04

[Ralf Spenneberg]

Yes,
I already reduced the playbook to the following:

#!/usr/bin/env ansible-playbook
#
---
- name: Install packages
  hosts: localhost
  tasks:
  - name: install apt packages
apt: 
  pkg:
- git
become: true


It still fails.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874195

Title:
  ansible is not able to install packages via apt on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1874195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874195] ProcCpuinfoMinimal.txt

[Ralf Spenneberg]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1874195/+attachment/5358301/+files/ProcCpuinfoMinimal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874195

Title:
  ansible is not able to install packages via apt on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1874195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874195] Re: ansible is not able to install packages via apt on 20.04

[Ralf Spenneberg]

apport information

** Tags added: apport-collected focal

** Description changed:

  When using ansible on 20.04, package installation via apt fail.
  
  Consider the following playbook:
  
  #!/usr/bin/env ansible-playbook
  #
  ---
  - name: Install packages
hosts: localhost
tasks:
- name: install apt packages
  apt: 
pkg:
  - git
update_cache: no
cache_valid_time: 3600
  become: true
  
  
  This playbook fails with:
   ansible-playbook apt.yml 
  
  PLAY [Install packages]
  
**
  
  TASK [Gathering Facts] 
***
  ok: [localhost]
  
  TASK [install apt packages] 
**
  fatal: [localhost]: FAILED! => {
  "changed": false
  }
  
  MSG:
  
   returned a result with an error set
  
  PLAY RECAP 
***
  localhost  : ok=1changed=0unreachable=0failed=1   
 skipped=0rescued=0ignored=0
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ DistroRelease: Ubuntu 20.04
+ Package: ansible 2.9.6+dfsg-1
+ PackageArchitecture: all
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
+ Tags:  focal
+ Uname: Linux 5.4.0-26-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1874195/+attachment/5358300/+files/Dependencies.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874195

Title:
  ansible is not able to install packages via apt on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1874195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874195] Re: ansible is not able to install packages via apt on 20.04

[Ralf Spenneberg]

I just confirmed that on Ubuntu 18.04 the playbook works fine.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874195

Title:
  ansible is not able to install packages via apt on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1874195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874195] [NEW] ansible is not able to install packages via apt on 20.04

[Ralf Spenneberg]

Public bug reported:

When using ansible on 20.04, package installation via apt fail.

Consider the following playbook:

#!/usr/bin/env ansible-playbook
#
---
- name: Install packages
  hosts: localhost
  tasks:
  - name: install apt packages
apt: 
  pkg:
- git
  update_cache: no
  cache_valid_time: 3600
become: true


This playbook fails with:
 ansible-playbook apt.yml 

PLAY [Install packages]
**

TASK [Gathering Facts] 
***
ok: [localhost]

TASK [install apt packages] 
**
fatal: [localhost]: FAILED! => {
"changed": false
}

MSG:

 returned a result with an error set

PLAY RECAP 
***
localhost  : ok=1changed=0unreachable=0failed=1
skipped=0rescued=0ignored=0

** Affects: ansible (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874195

Title:
  ansible is not able to install packages via apt on 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ansible/+bug/1874195/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1865461] [NEW] TLSProtocol is ignored -> TLSv1.3 is implicit accepted

[Ralf]

Public bug reported:

proftpd 1.3.5e-1build1
on 18.04.4 LTS (Bionic Beaver)

I have problems using TLSv1.3 connections.

Even with the configuration:
TLSProtocol TLSv1.1 TLSv1.2

the logs show TLSv1.3 connections, which should not be allowed:

mod_tls/2.6[10213]: TLS/TLS-C requested, starting TLS handshake
mod_tls/2.6[10213]: client supports secure renegotiations
mod_tls/2.6[10213]: TLSv1.3 connection accepted, using cipher
TLS_AES_256_GCM_SHA384 (256 bits)
mod_tls/2.6[10213]: Protection set to Private

The following negative directive is not known ans leads to startup errors:
TLSProtocol TLSv1.1 TLSv1.2 -TLSv1.3

Already discussed here: http://bugs.proftpd.org/show_bug.cgi?id=4389

Needs patch for ubuntu!

** Affects: proftpd-dfsg (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865461

Title:
  TLSProtocol is ignored -> TLSv1.3 is implicit accepted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/proftpd-dfsg/+bug/1865461/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1857217] [NEW] Lollypop crashes without gir1.2-gst-plugins-base-1.0 installed

[Ralf Morawe]

Public bug reported:

Using lollypop 1.1.4.16-4 on Ubuntu 19.10.

When I try to open a .flac file for example, the application immediately
crashes and shows the crash dialog. Running lollypop from the terminal
shows this trace:

mowalle@trenzalore ~/M/BABYMETAL-METAL_GALAXY> lollypop 13.Shine.flac 
Traceback (most recent call last):
  File "/usr/bin/lollypop", line 45, in 
from lollypop.application import Application
  File "/usr/lib/python3/dist-packages/lollypop/application.py", line 15, in 

gi.require_version("GstAudio", "1.0")
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 129, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GstAudio not available

I figured that to start lollypop, I need to install the gir1.2-gst-
plugins-base-1.0 package. Indeed, by installing the package lollypop
starts correctly and plays the file without a problem.

I should note that I previously removed Rhythmbox via apt remove --auto-
remove, which removed the gir1.2-gst-plugins-base-1.0 automatically.
Since gir1.2-gst-plugins-base-1.0 is not a dependency of lollypop, it
was not automatically installed with it.

I checked other distros (Arch and Fedora for example) where this package
is a dependency of lollypop. So maybe this can be fixed by setting
gir1.2-gst-plugins-base-1.0 as a dependency of lollypop in Ubuntu as
well.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: lollypop 1.1.4.16-4
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Dec 22 09:14:57 2019
InstallationDate: Installed on 2019-12-21 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: lollypop
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lollypop (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1857217

Title:
  Lollypop crashes without gir1.2-gst-plugins-base-1.0 installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lollypop/+bug/1857217/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819280] Re: Existing configuration file seems to stop skanlite functionality

[Ralf Beckesch]

Since then I really needed to use my scanners .. so I migrated my
laptops to manjaro. bye Ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819280

Title:
  Existing configuration file seems to stop skanlite functionality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/skanlite/+bug/1819280/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1852072] Re: Conntrackd segfault when flushing tables

[Ralf Spenneberg]

Running conntrackd with valgrind provides the attached log.

The Segfault is on line 36030.

** Attachment added: "valgrind.log"
   
https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/1852072/+attachment/5306286/+files/valgrind.log.bz2

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852072

Title:
  Conntrackd segfault when flushing tables

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/1852072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1852072] [NEW] Conntrackd segfault when flushing tables

[Ralf Spenneberg]

Public bug reported:

Hi,
I have a setup using conntrackd and keepalived for a ha-firewall. When 
stress-testing the system by stopping and starting keepalived eventually the 
conntrackd segfaults.

Nov  4 15:29:46 host conntrackd[1122]: [Mon Nov  4 15:29:46 2019] (pid=1122) 
[notice] committing all external caches
Nov  4 15:29:46 host Keepalived_logscript: user.info GROUP VG11 MASTER 0
Nov  4 15:29:46 host kernel: [20484.383544] show_signal_msg: 7 callbacks 
suppressed
Nov  4 15:29:46 host kernel: [20484.383546] conntrackd[1122]: segfault at 10 ip 
5649a5693ab4 sp 7ffeb5aafec0 error 4 in conntrackd[5649a5688000+34000]

It does not segfault every time. Sometimes it takes 5-10 iterations
starting and stopping the keepalived daemon which will invoke conntrackd
to flush the caches and subsequently segfault.

Kernel: 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux

Conntrackd: 1.4.4+snapshot20161117

** Affects: conntrack-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1852072

Title:
  Conntrackd segfault when flushing tables

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/conntrack-tools/+bug/1852072/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1845874] Re: Screen blotches/flickering on XFCE (Ubuntu Studio) Eoan 19.10

[Ralf Mardorf]

Apart from mentioning the graphics and the used driver, keep in mind
that recording the desktop with vokoscreen or any other tool like this,
does not record what is displayed. To show what is displayed consider to
record the screen with an external camera. The video definitely doesn't
show something unusual. If you would cut the cable of one colour of a
VGA cable, you would see a picture with a missing colour, but if you
would take a screenshot with a screenshot tool from some video buffer,
we still would see all colours. Next time consider to not ban people
from your Ubuntu Studio mailing lists, because they contribute by
providing technical knowledge you are missing. You seem to miss way more
basic knowledge, than I thought.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1845874

Title:
  Screen blotches/flickering on XFCE (Ubuntu Studio) Eoan 19.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1845874/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1771525] Re: Scanner not detected if plugged once Kubuntu 18.04 is running

[Ralf Beckesch]

** Package changed: usbutils (Ubuntu) => skanlite (Ubuntu)

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to skanlite in Ubuntu.
https://bugs.launchpad.net/bugs/1771525

Title:
  Scanner not detected if plugged once Kubuntu 18.04 is running

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/skanlite/+bug/1771525/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

[Bug 1820924] [NEW] DNS Servers added to resolv.conf, but not remived afterwards

[Ralf Hildebrandt]

Public bug reported:

My openvpn setup pushes internal DNS servers to clients.

a) The DNS server is added to resolv.conf, but at the end of the list, instead 
as the first DNS
b) same for the search domain

After the connection has been cut, the DNS servers and search domain
REMAIN in /etc/resolv.conf.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager-openvpn 1.8.6-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Mar 20 00:04:12 2019
InstallationDate: Installed on 2014-02-07 (1866 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager-openvpn
UpgradeStatus: Upgraded to cosmic on 2018-09-29 (171 days ago)

** Affects: network-manager-openvpn (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820924

Title:
  DNS Servers added to resolv.conf, but not remived afterwards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1820924/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819439] [NEW] reload hangs with systemd

[Ralf]

Public bug reported:

Hi,

there is a reload problem with unbound "1.5.8-1ubuntu1.1" on "Ubuntu
16.04.6 LTS", same as already fixed in debian: https://bugs.debian.org
/cgi-bin/bugreport.cgi?bug=892914

any suggestions?

Thanks!

** Affects: unbound (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819439

Title:
  reload hangs with systemd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1819439/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819280] Re: Existing configuration file seems to stop skanlite functionality

[Ralf Beckesch]

I forgot. I have a second laptop, also running Kubuntu 18.04, fresh
installed. On this machine the exact same error occurs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819280

Title:
  Existing configuration file seems to stop skanlite functionality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/skanlite/+bug/1819280/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1819280] [NEW] Existing configuration file seems to stop skanlite functionality

[Ralf Beckesch]

Public bug reported:

I got a laptop with Kubuntu 18.04. There are two scanners are connected,
both working fine with Xsane via Gimp.

Skanlite starting without any existing config file (previously deleted
it), skanlite starts, detects the two scanners. I choose one of the
scanners, and skanlite works like it used to in previous Kubuntu
versions. If i quit skanlite now, and restart ist, skanlite detects the
two scanners correctly again, but now it does not scan anything
correctly. The Preview shows an nearly white image (some yellow space in
the upper rigth conner of the preview image), the scanned image data is
completely useless.

If I quit skanlite again, and remove the config file, and restart
skanlite, for this time skanlite will work correctly again.

** Affects: skanlite (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819280

Title:
  Existing configuration file seems to stop skanlite functionality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/skanlite/+bug/1819280/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

Now I'm on
linux-image-4.18.0-14-generic 4.18.0-14.15
(without btusb.enable_autosuspend=0) and it's broken again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

After a few days of testing (work, suspend, resume, work) it seem to
work OK with the new kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

Testing the kernel from  https://people.canonical.com/~khfeng/lp1796553/ 
without btusb.enable_autosuspend=0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1235945] Re: Xorg crashed with SIGABRT

[Ralf P]

have the bug on 18.04 bionic with nvidia-driver-390

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235945

Title:
  Xorg crashed with SIGABRT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-319/+bug/1235945/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1440509] Re: dleyna-renderer-service crashed with SIGSEGV in dlr_device_unsubscribe()

[Ralf P]

have the same crash some time after every reboot (18.04 Bionic /
originally installed on Vivid Vervet (UbuntuGnome))

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440509

Title:
  dleyna-renderer-service crashed with SIGSEGV in
  dlr_device_unsubscribe()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dleyna-renderer/+bug/1440509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

btusb.enable_autosuspend=0  definitely made the issue go away.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

btusb.enable_autosuspend=0 seems to have worked (so far)...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

hildeb@humbaba:~$ ls -lihsa /lib/firmware/intel/
total 16M
3801225  12K drwxr-xr-x  2 root root  12K Sep 29 20:24 .
3801094  40K drwxr-xr-x 85 root root  36K Sep 29 20:25 ..
38171590 lrwxrwxrwx  1 root root   21 Aug  6 20:26 dsp_fw_bxtn.bin -> 
dsp_fw_bxtn_v3366.bin
3814817 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_bxtn_v2219.bin
3814818 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_bxtn_v3366.bin
38171610 lrwxrwxrwx  1 root root   20 Aug  6 20:26 dsp_fw_cnl.bin -> 
dsp_fw_cnl_v1191.bin
3814819 572K -rw-r--r--  1 root root 571K Aug  6 20:26 dsp_fw_cnl_v1191.bin
38171630 lrwxrwxrwx  1 root root   20 Aug  6 20:26 dsp_fw_glk.bin -> 
dsp_fw_glk_v3366.bin
3814820 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v1814.bin
3814821 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v2768.bin
3814822 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v2880.bin
3814823 496K -rw-r--r--  1 root root 494K Aug  6 20:26 dsp_fw_glk_v3366.bin
38171660 lrwxrwxrwx  1 root root   20 Aug  6 20:26 dsp_fw_kbl.bin -> 
dsp_fw_kbl_v3402.bin
3814824 236K -rw-r--r--  1 root root 234K Nov 17  2017 dsp_fw_kbl_v1037.bin
3814825 236K -rw-r--r--  1 root root 234K Aug  6 20:26 dsp_fw_kbl_v2042.bin
3814826 240K -rw-r--r--  1 root root 238K Aug  6 20:26 dsp_fw_kbl_v2630.bin
3814827 240K -rw-r--r--  1 root root 238K Aug  6 20:26 dsp_fw_kbl_v3266.bin
3814828 244K -rw-r--r--  1 root root 242K Aug  6 20:26 dsp_fw_kbl_v3402.bin
3814829 240K -rw-r--r--  1 root root 238K Aug  6 20:26 dsp_fw_kbl_v3420.bin
3814830 236K -rw-r--r--  1 root root 234K Nov 17  2017 dsp_fw_kbl_v701.bin
38171690 lrwxrwxrwx  1 root root   24 Aug  6 20:26 dsp_fw_release.bin -> 
dsp_fw_release_v3402.bin
3814831 244K -rw-r--r--  1 root root 242K Aug  6 20:26 dsp_fw_release_v3402.bin
3814832 216K -rw-r--r--  1 root root 216K Aug  6 20:26 dsp_fw_release_v969.bin
3814833 688K -rw-r--r--  1 root root 686K Aug  6 20:26 fw_sst_0f28.bin
3814834 260K -rw-r--r--  1 root root 260K Mär 30  2017 
fw_sst_0f28.bin-48kHz_i2s_master
3814835 688K -rw-r--r--  1 root root 686K Aug  6 20:26 fw_sst_0f28_ssp0.bin
3814836 688K -rw-r--r--  1 root root 686K Aug  6 20:26 fw_sst_22a8.bin
3814837 4,0K -rw-r--r--  1 root root   18 Mär  5  2018 ibt-11-5.ddc
3814838 584K -rw-r--r--  1 root root 581K Aug 30 21:57 ibt-11-5.sfi
3814839 4,0K -rw-r--r--  1 root root   14 Aug  6 20:26 ibt-12-16.ddc
3814840 580K -rw-r--r--  1 root root 579K Aug 30 21:57 ibt-12-16.sfi
3814841 4,0K -rw-r--r--  1 root root   14 Apr 24 16:28 ibt-17-0-1.ddc
3814842 612K -rw-r--r--  1 root root 611K Aug  6 20:26 ibt-17-0-1.sfi
3814903 4,0K -rw-r--r--  1 root root   29 Aug 30 21:57 ibt-17-16-1.ddc
3814904 616K -rw-r--r--  1 root root 614K Aug 30 21:57 ibt-17-16-1.sfi
3814843 4,0K -rw-r--r--  1 root root   14 Apr 24 16:28 ibt-17-1.ddc
3814844 612K -rw-r--r--  1 root root 611K Aug  6 20:26 ibt-17-1.sfi
3814905 4,0K -rw-r--r--  1 root root   29 Aug 30 21:57 ibt-17-2.ddc
3814906 616K -rw-r--r--  1 root root 614K Aug 30 21:57 ibt-17-2.sfi
3814907 4,0K -rw-r--r--  1 root root   14 Apr 24 16:28 ibt-18-0-1.ddc
3814908 612K -rw-r--r--  1 root root 611K Aug  6 20:26 ibt-18-0-1.sfi
3814911 4,0K -rw-r--r--  1 root root   29 Aug 30 21:57 ibt-18-16-1.ddc
3814912 616K -rw-r--r--  1 root root 614K Aug 30 21:57 ibt-18-16-1.sfi
3814909 4,0K -rw-r--r--  1 root root   14 Apr 24 16:28 ibt-18-1.ddc
3814910 612K -rw-r--r--  1 root root 611K Aug  6 20:26 ibt-18-1.sfi
3814913 4,0K -rw-r--r--  1 root root   29 Aug 30 21:57 ibt-18-2.ddc
3814914 616K -rw-r--r--  1 root root 614K Aug 30 21:57 ibt-18-2.sfi
3814915  24K -rw-r--r--  1 root root  22K Aug  6 20:26 
ibt-hw-37.7.10-fw-1.0.1.2d.d.bseq
3814916  28K -rw-r--r--  1 root root  26K Aug  6 20:26 
ibt-hw-37.7.10-fw-1.0.2.3.d.bseq
3814917  24K -rw-r--r--  1 root root  23K Aug 30 21:57 
ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq
3814918  28K -rw-r--r--  1 root root  26K Okt 11 08:54 
ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
3814919 4,0K -rw-r--r--  1 root root   96 Mär 30  2017 ibt-hw-37.7.bseq
3814920  32K -rw-r--r--  1 root root  31K Aug  6 20:26 
ibt-hw-37.8.10-fw-1.10.2.27.d.bseq
3814921  40K -rw-r--r--  1 root root  39K Aug 30 21:57 
ibt-hw-37.8.10-fw-1.10.3.11.e.bseq
3814922  48K -rw-r--r--  1 root root  48K Aug 30 21:57 
ibt-hw-37.8.10-fw-22.50.19.14.f.bseq
3814923 4,0K -rw-r--r--  1 root root   96 Mär 30  2017 ibt-hw-37.8.bseq
3814816 256K -rw-r--r--  1 root root 255K Mär 30  2017 IntcSST2.bin
38171710 lrwxrwxrwx  1 root root   52 Aug  6 20:26 ipu3-fw.bin -> 
irci_irci_ecr-master_20161208_0213_20170112_1500.bin
3814924 1,2M -rw-r--r--  1 root root 1,2M Aug  6 20:26 
irci_irci_ecr-master_20161208_0213_20170112_1500.bin

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

Still the same issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798315] [NEW] purging a kernel causes unneeded recreation of initramfs

[Ralf Hildebrandt]

Public bug reported:

I removed an old, not currently booted kernel:

 apt-get purge linux-image-4.4.0-135-generic 
linux-image-extra-4.4.0-135-generic 
Paketlisten werden gelesen … Fertig
Abhängigkeitsbaum wird aufgebaut.   
Statusinformationen werden eingelesen. … Fertig
Die folgenden Pakete werden ENTFERNT:
  linux-image-4.4.0-135-generic* linux-image-extra-4.4.0-135-generic*
0 aktualisiert, 0 neu installiert, 2 zu entfernen und 0 nicht aktualisiert.
Nach diesem Vorgang werden 224 M B Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n] y
(Datenbank wird gelesen … 130438 Dateien und Verzeichnisse sind derzeit 
installiert.)
linux-image-extra-4.4.0-135-generic (4.4.0-135.161) wird entfernt …
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-135-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-135-generic /boot/vmlinuz-4.4.0-135-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic
Grub-Konfigurationsdatei wird generiert …
Linux-Abbild gefunden: /boot/vmlinuz-4.4.0-137-generic
initrd-Abbild gefunden: /boot/initrd.img-4.4.0-137-generic
Linux-Abbild gefunden: /boot/vmlinuz-4.4.0-135-generic
initrd-Abbild gefunden: /boot/initrd.img-4.4.0-135-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
erledigt
Konfigurationsdateien von linux-image-extra-4.4.0-135-generic (4.4.0-135.161) 
werden gesäubert …
linux-image-4.4.0-135-generic (4.4.0-135.161) wird entfernt …
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic
update-initramfs: Deleting /boot/initrd.img-4.4.0-135-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic
Grub-Konfigurationsdatei wird generiert …
Linux-Abbild gefunden: /boot/vmlinuz-4.4.0-137-generic
initrd-Abbild gefunden: /boot/initrd.img-4.4.0-137-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
erledigt
The link /vmlinuz.old is a damaged link
Removing symbolic link vmlinuz.old 
 you may need to re-run your boot loader[grub]
The link /initrd.img.old is a damaged link
Removing symbolic link initrd.img.old 
 you may need to re-run your boot loader[grub]
Konfigurationsdateien von linux-image-4.4.0-135-generic (4.4.0-135.161) werden 
gesäubert …
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-135-generic 
/boot/vmlinuz-4.4.0-135-generic


Although the kernel was scheduled for removal, the lenghty creation of 
initramfs was run

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.137.143
ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144
Uname: Linux 4.4.0-137-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Okt 17 11:18 seq
 crw-rw 1 root audio 116, 33 Okt 17 11:18 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Date: Wed Oct 17 11:21:19 2018
HibernationDevice: RESUME=UUID=b1ab759c-f679-4e71-af05-24c040877711
InstallationDate: Installed on 2012-05-07 (2353 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 
(20120424.1)
IwConfig:
 lono wireless extensions.
 
 ens192no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: VMware, Inc. VMware Virtual Platform
PciMultimedia:
 
ProcFB: 0 svgadrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-137-generic 
root=/dev/mapper/vgsys-root ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-137-generic N/A
 linux-backports-modules-4.4.0-137-generic  N/A
 linux-firmware 1.157.20
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2017-06-10 (493 days ago)
dmi.bios.date: 09/21/2015
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 

[Bug 1798091] [NEW] thumbnailer cannot create tempfiles

[Ralf Hildebrandt]

Public bug reported:

While trying to create thumbnails in a directory from within nautilus, I
got:

[781429.784125] audit: type=1400 audit(1539694722.247:989): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30937 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[781429.940592] audit: type=1400 audit(1539694722.403:990): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30941 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[781430.314591] audit: type=1400 audit(1539694722.779:991): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30945 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[781431.283522] audit: type=1400 audit(1539694723.747:992): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30949 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
[781431.518566] audit: type=1400 audit(1539694723.983:993): apparmor="DENIED" 
operation="mknod" profile="/usr/bin/evince-thumbnailer" 
name="/tmp/gnome-desktop-thumbnailer.png" pid=30953 comm="evince-thumbnai" 
requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: evince 3.30.1-1
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 16 14:59:00 2018
InstallationDate: Installed on 2014-06-19 (1580 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to cosmic on 2018-10-07 (9 days ago)

** Affects: evince (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apparmor apport-bug cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798091

Title:
  thumbnailer cannot create tempfiles

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1798091/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

I cloned the repo and copied the new firmware to the appropriate place.
Testing now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

Tested:

$ uname -a
Linux humbaba 4.19.0-041900rc7-generic #201810071631 SMP Sun Oct 7 16:33:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

and the error is still there.

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

My next step is to test the upstream kernels, I guess?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

Bluetooth adapter is builtin. so I can't change the port.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] Re: BT mouse getting reset during operation

[Ralf Hildebrandt]

It's definitely NOT happening while supending/resuming.
It happens while I'm using the machine, literally while moving the mouse.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796553

Title:
  BT mouse getting reset during operation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1796553] [NEW] BT mouse getting reset during operation

[Ralf Hildebrandt]

Public bug reported:


(note: It's unclear to me if that's a kernel regression or an issue with bluez)


I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

It used to work with 18.04 and 17.10, but with 18.10 I'm encountering a
strange disconnect behaviour:

1) Mouse is working ok
2) Mouse suddenly stops
3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

when this happens, dmesg reports:

[57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
ehci-pci

Disabling bluetooth and enabling it again results in:

[57833.455866] usb 1-1.3: USB disconnect, device number 18
[57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
[57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
[57837.016248] usb 1-1.3: New USB device found, idVendor=8087, idProduct=07dc, 
bcdDevice= 0.01
[57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
[57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
[57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
[57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
[57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

$ bluetoothctl --version
bluetoothctl: 5.50

$ hciconfig -a
hci0:   Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

$ bluetoothctl
Agent registered
[TECKNET BM306]# show
Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
[TECKNET BM306]# devices
Device 20:9B:A5:68:AE:67 SoundBuds Flow
Device DC:2C:26:01:24:23 TECKNET BM306
Device 88:71:E5:0E:6B:99 Echo-HPT
Device 00:0B:E4:A0:A2:14 Nokia BH-103
Device A8:96:75:8B:4F:49 Moto G5S Plus
Device 00:02:5B:20:75:3C Trust SPK-02
Device 88:75:98:F2:5C:9E NS9+
Device 00:E0:4C:D5:E0:F5 SoundCore mini
[TECKNET BM306]# info DC:2C:26:01:24:23
Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129


$ rfkill list
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
4: dell-wwan: Wireless WAN
Soft blocked: yes
Hard blocked: no
5: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
46: nfc0: NFC
Soft blocked: no
Hard blocked: no
48: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon 

[Bug 1779827] Re: failure to boot with linux-image-4.15.0-24-generic

[Ralf Hersel]

Installing the entropy daemon 'haveged' (sudo apt install haveged)
worked on my notebook (Clevo, Tuxedo MS-1753, Kernel 4.15.0-24-generic).
Boot time is as normal. Also manually adding entropy by moving the mouse
like hell, reduced the boot time from 5 to 1.4 minutes.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779827

Title:
  failure to boot with linux-image-4.15.0-24-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1779827/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747340] Re: flickering graphics with intel gfx card

[Ralf Meyer]

problem has disappeared (with newer kernel?)

** Changed in: linux-hwe (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747340

Title:
  flickering graphics with intel gfx card

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1747340/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747340] Re: flickering graphics with intel gfx card

[Ralf Meyer]

Hi Patrick,

it went like this:
- GUI ok
- black screen
and so on in quick succession.

Happened only after suspend to RAM.

I have a fresh installtion of Ubuntu 16.04 for some weeks now and
haven't seen this happening since.


Yours sound different so I think you should open a new bugreport.
And I close this one.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747340

Title:
  flickering graphics with intel gfx card

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1747340/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753131] Re: gnome-shell crashes occasionally (libmutter)

[Ralf Sternberg]

I just noticed that the crash leaves a $HOME/core file:

$ file core
core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from 
'/usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 
-displayfd', real uid: 1000, effective uid: 1000, real gid: 1000, effective 
gid: 1000, execfn: '/usr/bin/Xwayland', platform: 'x86_64'

Could this be helpful?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753131

Title:
  gnome-shell crashes occasionally (libmutter)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753131] Re: gnome-shell crashes occasionally (libmutter)

[Ralf Sternberg]

It just happened again. There is no file in /var/crash, just the
aforementioned line in dmesg and also in /var/log/syslog.

It seems that everytime this crash happens I'm working with the Eclipse
IDE. I also find those lines in syslog which might be related:

java[30229]: Allocating size to GtkScrolledWindow 0x7fee4ab40de0
without calling gtk_widget_get_preferred_width/height(). How does the
code know the size to allocate?

Anything else I could do to track it down?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753131

Title:
  gnome-shell crashes occasionally (libmutter)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1754620] Re: ERROR: This tool requires libclamav with functionality level 85 or higher (current f-level: 84)

[Ralf Hildebrandt]

Had an old version of libclamav in /usr/local/lib. My bad.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754620

Title:
  ERROR: This tool requires libclamav with functionality level 85 or
  higher (current f-level: 84)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1754620/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1754620] [NEW] ERROR: This tool requires libclamav with functionality level 85 or higher (current f-level: 84)

[Ralf Hildebrandt]

Public bug reported:

# clamscan
ERROR: This tool requires libclamav with functionality level 85 or higher 
(current f-level: 84)

# dpkg -l |fgrep clam
ii  clamav  0.99.4+addedllvm-0ubuntu0.16.04.1   
   amd64anti-virus utility for Unix - command-line interface
ii  clamav-base 0.99.4+addedllvm-0ubuntu0.16.04.1   
   all  anti-virus utility for Unix - base package
ii  clamav-daemon   0.99.4+addedllvm-0ubuntu0.16.04.1   
   amd64anti-virus utility for Unix - scanner daemon
ii  clamav-freshclam0.99.4+addedllvm-0ubuntu0.16.04.1   
   amd64anti-virus utility for Unix - virus database update utility
ii  clamdscan   0.99.4+addedllvm-0ubuntu0.16.04.1   
   amd64anti-virus utility for Unix - scanner client
ii  libclamav-client-perl   0.11-2  
   all  Perl client for the ClamAV virus scanner daemon
ii  libclamav-dev   0.99.4+addedllvm-0ubuntu0.16.04.1   
   amd64anti-virus utility for Unix - development files
ii  libclamav7  0.99.4+addedllvm-0ubuntu0.16.04.1   
   amd64anti-virus utility for Unix - library

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: clamav 0.99.4+addedllvm-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Mar  9 11:46:50 2018
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: clamav
UpgradeStatus: Upgraded to xenial on 2016-10-31 (493 days ago)

** Affects: clamav (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754620

Title:
  ERROR: This tool requires libclamav with functionality level 85 or
  higher (current f-level: 84)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1754620/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753131] Re: gnome-shell crashes occasionally (libmutter)

[Ralf Sternberg]

Thanks, I've applied the workaround. My /var/crash is currently empty,
I'll follow your advice when the crash occurs again.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753131

Title:
  gnome-shell crashes occasionally (libmutter)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753131] [NEW] gnome-shell crashes occasionally (libmutter)

[Ralf Sternberg]

Public bug reported:

I see occasional crashes of gnome-shell that get me back to the login
screen.

After these crashes I find something like the following line in dmesg:

gnome-shell[8428]: segfault at b0 ip 7fddec8387d1 sp
7ffdf2061a80 error 4 in libmutter-1.so.0.0.0[7fddec763000+142000]

Ubuntu: 17.10
gnome-shell: 3.26.2-0ubuntu0.1
mutter: 3.26.2-0ubuntu0.1

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753131

Title:
  gnome-shell crashes occasionally (libmutter)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747340] Re: flickering graphics with intel gfx card

[Ralf Meyer]

no more flicker after reboot. reportbug info:
---
Package: linux-image-4.13.0-32-generic
Version: 4.13.0-32.35~16.04.1
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where
appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-32-generic (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-4.13.0-32-generic depends on:
ii  kmod  22-1ubuntu5

Versions of packages linux-image-4.13.0-32-generic recommends:
ii  grub-efi-amd64  2.02~beta2-36ubuntu3.15
ii  initramfs-tools [linux-initramfs-tool]  0.122ubuntu8.10

Versions of packages linux-image-4.13.0-32-generic suggests:
pn  fdutils  
ii  linux-headers-4.13.0-32-generic  4.13.0-32.35~16.04.1
pn  linux-tools  

-- no debconf information

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747340

Title:
  flickering graphics with intel gfx card

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1747340/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1747340] [NEW] flickering graphics with intel gfx card

[Ralf Meyer]

Public bug reported:

graphics are flickering
on 3 different monitors
- hdmi
- vga
- laptop builtin

newest 4.13 kernel, not this one

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Feb  5 04:32:06 2018
InstallationDate: Installed on 2016-01-20 (746 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
SourcePackage: linux-hwe
UpgradeStatus: Upgraded to xenial on 2016-07-27 (557 days ago)

** Affects: linux-hwe (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747340

Title:
  flickering graphics with intel gfx card

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1747340/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1737212] Re: Can we include WEBEX-TOKEN sasl patch from upstream?

[Ralf]

additionally to applying the above patch it is required to add
"--enable-webex-token" to DEB_CONFIGURE_EXTRA_FLAGS before build.

I have tested the build on top of artful universe pidgin-src
2.12.0-1ubuntu2_amd64 and the patch works for me in regards that I can
use my corporate SingleSignOn to connect to Cisco WebEx XMPP.

additional infos from original patch related to be able to use the
provided SSO Method:

>From a Cisco Jabber Client install, look for a SSOAuthInfoStore.xml
file. In my example on my Windows Cisco Jabber install I used
C:\Users\\AppData\Roaming\Cisco\Unified
Communications\Jabber\CSF\Config\SSOAuthInfoStore.xml

This should contain a URL on loginp.webexconnect.com (or the like)
specifying a SSO login url for your corporate SSO. It should look
similar to:
https://loginp.webexconnect.com/cas/FederatedSSO?org==connect2

Once you open that URL with a browser and complete whatever
authentication workflow is needed, you will get an XML stanza back
called FederatedSSO. If you already have an SSO cookie set in your
Browser, because you already authenticated your Corp SSO for another
service, you'll just get an XML response with the required token data.

In the returned stanza, you will need to copy the  element,
and use that as your password. Returned  should match your
user and domain elements in your account configuration in Pidgin,
regardless of your usual corporate username and domain name. Finally,
you will want to use the server in the  element as
your target server to connect to (note there is also a 
element, do not use that). Port 5222 should work for Cisco Jabber via
WebEx.

Note that the token will expire (the XML will tell you when) and after
that when you restart pidgin you'll need to get a new token and update
your config with the new token as password.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737212

Title:
  Can we include WEBEX-TOKEN sasl patch from upstream?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1737212/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1737212] Re: Can we include WEBEX-TOKEN sasl patch from upstream?

[Ralf]

** Patch added: "webex.patch"
   
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1737212/+attachment/5020250/+files/webex.patch

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737212

Title:
  Can we include WEBEX-TOKEN sasl patch from upstream?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1737212/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1737212] [NEW] Can we include WEBEX-TOKEN sasl patch from upstream?

[Ralf]

Public bug reported:

The following patch:

https://developer.pidgin.im/ticket/17070#no1
https://bitbucket.org/pidgin/main/pull-requests/91/implmeth-webex-token-sasl-auth-for-jabber/diff

is providing CISCO Jabber Webex SASL auth via corporate SSO as used in
many corporates.

Can we include this into the pidgin Ubuntu package, as of now
(1:2.12.0-1ubuntu2 in 17.10) it is not included.

Problem signature in debug due to the missing sasl mech:

(17:52:26) sasl: Mechs found: WEBEX-TOKEN
(17:52:26) sasl: No worthy mechs found


The patch is not very user friendly as of now and would require the use of 
external (browser based) token exchange, but that's better than not being able 
to use it at all. Generally the patch would not change existing functionality, 
so it would allow to use WEBEX-TOKEN for experienced users with the method 
stated in pidgin tikcet 17070 (see link above) but not impact any current 
functionality, so risk is low in my opinion.

** Affects: pidgin (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737212

Title:
  Can we include WEBEX-TOKEN sasl patch from upstream?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/1737212/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732780] [NEW] Gnome-Shell activities file search does not find any file below /home/user/

[Ralf Hersel]

Public bug reported:

Description:
Searching for files in Gnome-Shell activities does not work because it returns 
no search results for files stored deeper than /home/user/.

Environment:
Ubuntu 17.04
Gnome-Shell 3.26.1
Language German (Swiss)

Steps to reproduce:
1. Create whatever file in a directory located under /home/user/ e.g. 
/home/user/documents/test.txt
2. Open Gnome-Shell activities by hitting SUPER-key
2. Enter the name of that existing file in the search field
3. Wait or press RETURN
4. Effect: no files found

Positive indication:
If that file is located exactly in /home/user/, the file search will find it.

Negative indication:
a) Recursive search is broken.
b) Ubuntu Settings, Search, Files, Configuration cog button is disabled

Work-around:
Use Nautilus file search instead.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: gnome-17.10

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732780

Title:
  Gnome-Shell activities file search does not find any file below
  /home/user/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732780/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1169568] Re: aa-unconfined does not always display unconfined processes with dual-stack

[Ralf Spenneberg]

This is still the fact on LTS 16.04. A patch was posted on 
https://lists.ubuntu.com/archives/apparmor/2016-December/010307.html

It would be great if this would be added to the apparmor-utils.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1169568

Title:
  aa-unconfined does not always display unconfined processes with dual-
  stack

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1169568/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1577192] Re: package gcc-doc 4:4.8.2-1ubuntu6 failed to install/upgrade: there is no script in the new version of the package - giving up

[Ralf Ganswindt]

** Description changed:

  Tried to update from 14.04 to 16.04 and a lot more than this failed to
  install.
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gcc-doc 4:4.8.2-1ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sun May  1 10:33:35 2016
  ErrorMessage: there is no script in the new version of the package - giving up
  InstallationDate: Installed on 2012-12-23 (1225 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1
-  apt  1.2.10ubuntu1
+  dpkg 1.18.4ubuntu1
+  apt  1.2.10ubuntu1
  SourcePackage: gcc-defaults
  Title: package gcc-doc 4:4.8.2-1ubuntu6 failed to install/upgrade: there is 
no script in the new version of the package - giving up
  UpgradeStatus: Upgraded to xenial on 2016-05-01 (0 days ago)
+ 
+ Attempted to uninstall the package: gcc-doc
+ Resulted in the following error:
+ dpkg: error processing package gcc-doc (--purge):
+  package is in a very bad inconsistent state; you should
+  reinstall it before attempting a removal
+ Errors were encountered while processing:
+  gcc-doc
+ E: Sub-process /usr/bin/dpkg returned an error code (1)
+ A package failed to install.  Trying to recover:
+ 
+ Package also can not be de-selected in the update manager.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1577192

Title:
  package gcc-doc 4:4.8.2-1ubuntu6 failed to install/upgrade: there is
  no script in the new version of the package - giving up

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-defaults/+bug/1577192/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1705030] [NEW] "Ubuntu" session starts Wayland instead of X11 after first reboot

[Ralf Morawe]

Public bug reported:

Testing Artful 17.10 daily from 18th July 2017.

When installed to my laptop after the first reboot, GDM shows two
possible sessions on login: "Ubuntu" and "Ubuntu with Wayland". However,
both will open a Wayland session for me. The issue fixes itself after
rebooting once more.

How to reproduce: After fresh installation and reboot, choose "Ubuntu"
in GDM and log in.

What I expected: An X11 GNOME session should open up.

What actually happens: A Wayland GNOME session opens up.
I confirmed this by Alt + F2 -> r -> Enter (giving the message "Restart is not 
available on Wayland").
Also, 'loginctl show-session  -p Type' shows "Type=wayland" ( 
is the session number given by 'loginctl').

I could also reproduce this behaviour on a new fresh install.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-session (not installed)
ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
Uname: Linux 4.11.0-10-generic x86_64
ApportVersion: 2.20.5-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jul 18 15:25:32 2017
InstallationDate: Installed on 2017-07-18 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170718)
SourcePackage: gnome-session
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful julyshakedown

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705030/+attachment/4916857/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705030

Title:
  "Ubuntu" session starts Wayland instead of X11 after first reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1705030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1702469] [NEW] iptraf doesn't allow for PredictableNetworkInterfaceNames

[Ralf Hildebrandt]

Public bug reported:

# ifconfig
ens192Link encap:Ethernet  Hardware Adresse 00:50:56:9c:25:de  
  inet Adresse:141.42.206.34  Bcast:141.42.207.255  Maske:255.255.254.0
  inet6-Adresse: fe80::250:56ff:fe9c:25de/64 
Gültigkeitsbereich:Verbindung
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
  RX-Pakete:1040896 Fehler:0 Verloren:31 Überläufe:0 Fenster:0
  TX-Pakete:1030267 Fehler:0 Verloren:0 Überläufe:0 Träger:0
  Kollisionen:0 Sendewarteschlangenlänge:1000 
  RX-Bytes:463592288 (463.5 MB)  TX-Bytes:470005597 (470.0 MB)

but iptraf:

# iptraf -i ens192
results in:

Specified interface not supported

One can workaround this using the "-u" option.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: iptraf 3.0.0-8.1build1
ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
Uname: Linux 4.4.0-83-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Wed Jul  5 13:57:17 2017
InstallationDate: Installed on 2017-06-01 (34 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: iptraf
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: iptraf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702469

Title:
  iptraf doesn't allow for PredictableNetworkInterfaceNames

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptraf/+bug/1702469/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

ii  linux-image-4.10.0-22-generic
4.10.0-22.24amd64Linux kernel
image for version 4.10.0 on 64 bit x86 SMP

is working OK for me!

$ uname -a
Linux vsw-it-nw-10 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

Which version would that be? Currently, my system has:

ii  linux-image-4.10.0-21-generic   4.10.0-21.23
amd64Linux kernel image for version 4.10.0 
on 64 bit x86 SMP
ii  linux-image-4.10.0-22-generic   4.10.0-22.24
amd64Linux kernel image for version 4.10.0 
on 64 bit x86 SMP
ii  linux-image-extra-4.10.0-21-generic 4.10.0-21.23
amd64Linux kernel extra modules for version 
4.10.0 on 64 bit x86 SMP
ii  linux-image-extra-4.10.0-22-generic 4.10.0-22.24
amd64Linux kernel extra modules for version 
4.10.0 on 64 bit x86 SMP

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:
> The reverse bisect indicated the following commit as the fix:
> 
> commit 28ee1b746f493b7c62347d714f58fbf4f70df4f0
> Author: Florian Westphal <f...@strlen.de>
> Date:   Fri Mar 24 19:42:37 2017 +0100
> 
> secure_seq: downgrade to per-host timestamp offsets
> 
> 
> However, to apply this commit it required commits 2c956a60778c and 
> 7cd23e5300c1 as prereqs.  I built a Zesty test kernel with these three 
> commits.  The test kernel can be downloaded from:
> 
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/patched
> 
> 
> Can you see if this kernel resolves the bug?  With this test kernel, you need 
> to install both the linux-image and linux-image-extra .deb packages.

Linux vsw-it-nw-10 4.10.0-21-generic #23~lp1686636 SMP Fri May 19 17:59:12 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
is working OK and does NOT expose the bug!

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:
> I built the next test kernel, up to the following commit:
> 
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/28ee1b746f493b7c62347d714f58fbf4f70df4f0
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705181210 SMP Thu May 18 
16:13:25 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Kernel is working OK!

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:
> I built the next test kernel, up to the following commit:
> 95f255211396958c718aef8c45e3923b5211ea7b
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/95f255211396958c718aef8c45e3923b5211ea7b
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705170654 SMP Wed May 17 
10:57:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
has the bug!

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:
> I built the next test kernel, up to the following commit:
> 13a8cd191a2b470cfd435b3b57dbd21aa65ff78c
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/13a8cd191a2b470cfd435b3b57dbd21aa65ff78c
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

Kernel is working OK.
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705161235 SMP Tue May 16 
16:37:55 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:
> Sorry for the delay.
> 
> I built the next test kernel, up to the following commit:
> 834a61d455ff8069552f44140b2c1de85e6bc84d
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/834a61d455ff8069552f44140b2c1de85e6bc84d
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

This kernel is working OK!
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705151753 SMP Mon May 15 
21:57:15 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury :

> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/a80db69e47d764bbcaf2fec54b1f308925e7c490
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

This kernel HAS the bug!
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705041331 SMP Thu May 4 
17:37:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1682171] Re: No way to disable tap-to-click in Mouse & Touchpad settings

[Ralf]

Status changed, this issue STILL affects those running the HWE stack on
Ubuntu 16.04 with Gnome. ( sudo apt-get install --install-recommends
linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 ) will result in outdated
version of xserver-xorg-core ( <2:1.17.99.902) being installed which
results in an unmet dependency for xserver-xorg-input-libinput and still
breaks the tap to click dialogue. Removing the interfering xserver-xorg-
input-synaptics obviously breaks things even more...

** Changed in: gnome-settings-daemon (Ubuntu)
   Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1682171

Title:
  No way to disable tap-to-click in Mouse & Touchpad settings

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1682171/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:

> I built the next test kernel, up to the following commit:
> a80db69e47d764bbcaf2fec54b1f308925e7c490
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/a80db69e47d764bbcaf2fec54b1f308925e7c490
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

This kernel HAS the bug!
Linux vsw-it-nw-10 4.11.0-041100rc3-generic #201705041331 SMP Thu May 4 
17:37:08 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury :
> I built the next test kernel, up to the following commit:
> b768b16de58d5e0b1d7c3f936825b25327ced20c
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/b768b16de58d5e0b1d7c3f936825b25327ced20c
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

4.11.0-041100rc3-generic #201705031345 is also working ok!

(why am I seeing rc3 and r5 in the kernels' names, when we're
bisecting between v4.11-rc5 and v4.11-rc6?)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:
> I built the next test kernel, up to the following commit:
> 61b9a047729bb230978178bca6729689d0c50ca2
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/61b9a047729bb230978178bca6729689d0c50ca2
> 
> Can you test that kernel and report back if it has the bug or not? I
> will build the next test kernel based on your test results.

That kernel is also working OK!
It does NOT have the bug.

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1686636] Re: outgoing tcp connections sometimes fail to be established

[Ralf Hildebrandt]

* Joseph Salisbury <joseph.salisb...@canonical.com>:
> I built the first test kernel, up to the following commit:
> 4691f4a6d4aadb67eab06c6659136bc2b00db851
> 
> The test kernel can be downloaded from:
> http://kernel.ubuntu.com/~jsalisbury/lp1686636/4691f4a6d4aadb67eab06c6659136bc2b00db851
> 
> Can you test that kernel and report back if it has the bug or not?

This kernel is working OK! No problems.

-- 
Ralf Hildebrandt   Charite Universitätsmedizin Berlin
ralf.hildebra...@charite.deCampus Benjamin Franklin
https://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1686636

Title:
  outgoing tcp connections sometimes fail to be established

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686636/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1685742] Re: MTU 9000 not possible on openvswitch bridge

[Ralf Trezeciak]

This might be necessary?

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/net/openvswitch
/vport-internal_dev.c?id=425df17ce3a26d98f76e2b6b0af2acf4aeb0b026

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1685742

Title:
  MTU 9000 not possible on openvswitch bridge

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1685742/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs