[Bug 2047303] Re: Partitions on dmraid managed array are not mounted, system cannot boot

[Evgeny Grin]

** Changed in: dmraid (Debian)
   Importance: Undecided => Unknown

** Changed in: dmraid (Debian)
   Status: New => Unknown

** Changed in: dmraid (Debian)
 Remote watch: None => Debian Bug tracker #1078223

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

Title:
  Partitions on dmraid managed array are not mounted, system cannot boot

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


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

[Bug 2047303] Re: Partitions on dmraid managed array are not mounted, system cannot boot

[Evgeny Grin]

I can confirm that my patch works for 22.04 (or a few other outdated versions).
My patch is identical to what is used in the PPA.

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

Title:
  Partitions on dmraid managed array are not mounted, system cannot boot

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


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

[Bug 1923845] Re: Please compress packages with zstd by default

[Evgeny]

debsigs fixed in upstream
https://gitlab.com/debsigs/debsigs/-/commit/5c843dcd283357c56531b41317faa98a12084eb8

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

Title:
  Please compress packages with zstd by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/appstream-glib/+bug/1923845/+subscriptions


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

[Bug 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)

[Evgeny Morozov]

Tested openssh-client/bionic-proposed,now 1:7.6p1-4ubuntu0.7 and
confirmed that group's and others' read permissions are now preserved.
Write and execute permissions are still removed, that is, a umask of
0133 seems to be applied.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

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

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

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


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

[Bug 1966591] Re: ssh-keygen -R changes known_hosts file permissions (mode)

[Evgeny Morozov]

Thanks a lot! 0644 are really the important bits, so while the behavior
is still "user-surprising" it shouldn't cause any practical problems for
us.

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

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

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


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

[Bug 1966591] [NEW] ssh-keygen -R changes known_hosts file permissions (mode)

[Evgeny Morozov]

Public bug reported:

When I use ssh-keygen -R to remove a host from known_hosts it changes
permissions on the file. This causes problems particularly when used on
the global known hosts file (/etc/ssh/ssh_known_hosts), because then
only root can read it. Programs running non-interactively as non-root
users suddenly fail to SSH and it's not immediately obvious why.

To reproduce:

$ ssh-keyscan github.com >test_known_hosts
$ chmod 741 test_known_hosts
$ ssh-keygen -R github.com -f test_known_hosts
$ stat test_known_hosts
...
Access: (0600/-rw---) ...

Expected behavior: file permissions remain unchanged (mode 0741 in this
example).

$ lsb_release -rd
Description:Ubuntu 18.04.6 LTS
Release:18.04

$ apt-cache policy openssh-client
openssh-client:
  Installed: 1:7.6p1-4ubuntu0.6

** Affects: openssh (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/1966591

Title:
  ssh-keygen -R changes known_hosts file permissions (mode)

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


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

[Bug 1918265] Re: Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2

[Evgeny]

Same problem here with Ubuntu server 20.04 and Hyper-v on Windows Server 2016 
with VM's gen 2.
We also noticed that if you set virtual switch to "Not connected" for the 
affected VM, it will boot every time. And you can set back the required swith 
after boot. But when any other switch is selected, the VM won't boot most of 
the time or at all with the same symptoms.

Any progress in solving this?

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

Title:
  Random boot failure with Ubuntu 20.04 / grub 2.04 and Hyper-V 2012r2

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


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

[Bug 1899800] Re: Runtime deadlock: pthread_cond_signal failed to wake up pthread_cond_wait due to a bug in undoing stealing

[Evgeny Morozov]

Yes, that would be very nice. I'm not holding out much hope of this
being fixed for 18.04, but even if we have to upgrade to 20.04 to get
the fix we might prioritise that.

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

Title:
  Runtime deadlock: pthread_cond_signal failed to wake up
  pthread_cond_wait due to a bug in undoing stealing

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


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

[Bug 1899800] Re: Runtime deadlock: pthread_cond_signal failed to wake up pthread_cond_wait due to a bug in undoing stealing

[Evgeny Morozov]

Thank you, but workstation GC is not a realistic option for us,
unfortunately. This is still affecting us. Is there some other
workaround?

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

Title:
  Runtime deadlock: pthread_cond_signal failed to wake up
  pthread_cond_wait due to a bug in undoing stealing

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


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

[Bug 1940499] [NEW] nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build

[Evgeny Kurbatov]

Public bug reported:

Ubuntu just has notified there was a system error. I don't know where
and how this error manifested itself.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: nvidia-340 340.108-0ubuntu5.20.04.2
ProcVersionSignature: Ubuntu 5.8.0-63.71~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-63-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
DKMSKernelVersion: 5.11.0-27-generic
Date: Thu Aug 19 08:35:08 2021
InstallationDate: Installed on 2020-06-16 (428 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageVersion: 340.108-0ubuntu5.20.04.2
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: nvidia-graphics-drivers-340
Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package 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/1940499

Title:
  nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed
  to build

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


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

[Bug 1899800] Re: Runtime deadlock: pthread_cond_signal failed to wake up pthread_cond_wait due to a bug in undoing stealing

[Evgeny Morozov]

Could someone clarify the status of this, please? Our .NET Core
application freezes from time to time and I believe it's because of this
issue (see https://github.com/dotnet/runtime/issues/47700). The linked
glibc bug [https://sourceware.org/bugzilla/show_bug.cgi?id=25847] is now
"UNCONFIRMED". So is there a glibc fix that has not made it into Ubuntu
or is there not even a glibc fix (that doesn't break something else)? Is
this expected to be fixed in 18.04 or 20.04 at all? 21.10? 22.04?

** Bug watch added: github.com/dotnet/runtime/issues #47700
   https://github.com/dotnet/runtime/issues/47700

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

Title:
  Runtime deadlock: pthread_cond_signal failed to wake up
  pthread_cond_wait due to a bug in undoing stealing

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


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

[Bug 1936741] [NEW] GPU aceleration on RPi 4

[Evgeny]

Public bug reported:

Hi, guys!

Is this package has GPU acceleration for RPi 4?

I try to run cog:

cog -P drm https://akirodic.com/p/jellyfish

or

cog -P fdo https://akirodic.com/p/jellyfish

and haven't one

Also can't play an mp4 video.
Maybe some additional configurations are required?

--
Best wishes
Evgeny

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


** Tags: gpu rpi4

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

Title:
  GPU aceleration on RPi 4

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


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

[Bug 1935890] [NEW] package avahi-utils 0.7-4ubuntu7.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

[Evgeny Ohremenko]

Public bug reported:

1

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: avahi-utils 0.7-4ubuntu7.1
ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-59-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
AptOrdering:
 avahi-utils:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Jul 11 06:22:50 2021
ErrorMessage: проблемы зависимостей — оставляем не настроенным
InstallationDate: Installed on 2021-05-13 (60 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: avahi
Title: package avahi-utils 0.7-4ubuntu7.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: avahi (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/1935890

Title:
  package avahi-utils 0.7-4ubuntu7.1 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

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

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

[Bug 1920631] [NEW] package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit st

[Evgeny Zubkov]

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

Public bug reported:

occured after installation clear ubuntu

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4
ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Mar 20 19:49:48 2021
ErrorMessage: installed grub-efi-amd64-signed package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-03-20 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10
SourcePackage: grub2-signed
Title: package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to 
install/upgrade: installed grub-efi-amd64-signed package post-installation 
script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package groovy

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

Title:
  package grub-efi-amd64-signed 1.155.4+2.04-1ubuntu35.4 failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1920631/+subscriptions

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

[Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Evgeny Brazgin]

@hydrogencl
> I have reported this issue to ASUS support

Thank you! I also requested tech support for the drivers for ExpertBook
B9.

Today I got the reply:

> In regards to drivers for Ubuntu Linux 20.10, you will be required to
contact Linux directly for drivers and tools for the fingerprint sensor
and Numpad as we do not support Linux.

So they are hoping that Linux developers will write drivers themselves :D
I asked them to request the drivers or specs from Elantech, let's see what they 
say next.

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

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

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

[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Evgeny Brazgin]

@xnox,

I think for bionic it may be possible to port changes from
https://github.com/xapienz/curl-debian-scripts (branch ppa_bionic) into
upstream ubuntu (currently debs are in PPA
https://launchpad.net/~xapienz/+archive/ubuntu/curl34). I can't
guarantee that such constructed binaries will work for all cases, but
during the last 2.5 years I haven't got any complaints from PPA users.

For focal - maybe it is already fixed, but I see that around 900 people
are still using my PPA in focal, so maybe there are some apps which
still require it.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

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

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

[Bug 1871849] Re: Full screen videos suddenly change scale when using fractional scaling

[EVGENY]

I have the same problem using Davinci Resolve in fullscreen mode, as
well as VLC. With two 27" 4K monitors it's impossible to use any other
scaling factor except 150%.

Ubuntu 20.10
GNOME 3.38.1

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

Title:
  Full screen videos suddenly change scale when using fractional scaling

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

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

[Bug 1900104] Re: Garbage is displayed on a separate page instead of a picture or table

[Evgeny Kurbatov]

Hi, Norbert. Thank you for testing.
Should I tweak a maintainer of the texlive-latex-base package to implement the 
latest patches or just wait for Ubuntu 20.10 to use its repo (which is dirty)?

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

Title:
  Garbage is displayed on a separate page instead of a picture or table

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1900104/+subscriptions

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

[Bug 1900104] Re: Garbage is displayed on a separate page instead of a picture or table

[Evgeny Kurbatov]

Sorry, I tried to reattach the example and deleted it. Here it is,
again.

** Attachment removed: "To bug #1900104"
   
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1900104/+attachment/5422950/+files/bug.tar

** Attachment added: "Tu bug #1900104"
   
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1900104/+attachment/5422990/+files/bug.tar.gz

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

Title:
  Garbage is displayed on a separate page instead of a picture or table

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/1900104/+subscriptions

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

[Bug 1900104] Re: Garbage is displayed on a separate page instead of a picture or table

[Evgeny Kurbatov]

I have made a minimal working example of the bug. See attach.
It's working with just a single `pdflatex paper'.
As seen, it crashes on the paper break.

** Attachment added: "To bug #1900104"
   
https://bugs.launchpad.net/ubuntu/+bug/1900104/+attachment/5422950/+files/bug.tar

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

Title:
  Garbage is displayed on a separate page instead of a picture or table

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

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

[Bug 1900104] [NEW] Garbage is displayed on a separate page instead of a picture or table

[Evgeny Kurbatov]

Public bug reported:

Hello, guys.

When the text becomes long enough and there are sections, figures, and
tables of the half-page height, then the last figure or table may
disappear. A separate page appears instead, containing a few garbage
symbols like `,ы,' and nothing else.

This bug is reproducible on my text in a latex-latex-bibtex-latex chain,
as well as in a pdflatex-... chain. The problem arises at the last
stage, at the very last latex/pdflatex, after the `bbl' is generated,
and `aux' is updated.

If to add a few paragraphs of some Lorem ipsum somewhere in the text, to
any place, then the problem disappears. It looks like the compiler can't
handle placing large figures and tables on the pages.

I cannot show the bug with a short example, although I'll try again.
Unfortinately, I can't provide you the text that I'm currently working on, 
since this is an unpublished article.

In sum, I can list some of the factors that contribute to the bug:
1. At least two figures and/or tables. They should not be too small.
2. Presence of the bibliography, either inline or as '.bbl'.
3. A situation where the compiler must decide, where to break the page or not.

This never happened on Debian 10, and on any [stable] Ubuntu <20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: texlive-latex-base 2019.20200218-1
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 16 11:06:08 2020
InstallationDate: Installed on 2020-06-16 (121 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: texlive-base
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: 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/1900104

Title:
  Garbage is displayed on a separate page instead of a picture or table

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

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

[Bug 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound

[Evgeny Kuznetsov]

Looks like there's a way to set the sample rate for a particular device 
explicitly, and that's what is called for in this case:
https://evgenykuznetsov.org/en/posts/2020/webcam-sound/

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

Title:
  Logitech camera microphone does not work / makes "chipmunk" sound

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

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

[Bug 1569521] Re: Logitech C310 makes voice sound too fast (Chipmunk Effect)

[Evgeny Kuznetsov]

The solution seems to be explicitly informing pulseaudio of the frequency those 
cameras' mics support:
https://evgenykuznetsov.org/en/posts/2020/webcam-sound/

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

Title:
  Logitech C310 makes voice sound too fast (Chipmunk Effect)

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

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

[Bug 1877696] Re: [MIR] openscap

[Evgeny Kolesnikov]

Just FYI, the newer 1.3 branch has a lot of fixes related to Debian-
based distributions, including the test suite, dpkg probe and others.
Moreover, this branch is now gated in upstream CI against the latest
Ubuntu.

We (OpenSCAP team) tried to contact Debian's maintainer regarding the
package upgrade, but there was no response 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/1877696

Title:
  [MIR] openscap

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

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

[Bug 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

[Evgeny]

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

Same with Kubuntu 20.

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

Title:
  Unable to use  shortcuts with  keyboard
  layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/mate-desktop/+bug/1720364/+subscriptions

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

[Bug 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so

[Evgeny Kolesnikov]

Okay, this happens. But I can't help but wonder why it wasn't deprecated
first and why it still present in public headers then?

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

Title:
  The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-
  pkg.so

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

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

[Bug 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so

[Evgeny Kolesnikov]

nm -D -C libapt-pkg.so.5.0 | grep MMap (Ubuntu 18.04)

...
000c97d0 T MMap::Map(FileFd&)
000c9e10 T MMap::Sync(unsigned long, unsigned long)
000c9b80 T MMap::Sync()
000c9c20 T MMap::Close(bool)
000c97a0 T MMap::MMap(unsigned long)
000c9b40 T MMap::MMap(FileFd&, unsigned long)
000c97a0 T MMap::MMap(unsigned long)
000c9b40 T MMap::MMap(FileFd&, unsigned long)
000c9d20 T MMap::~MMap()
000c9d00 T MMap::~MMap()
000c9d00 T MMap::~MMap()
...

** Tags added: focal

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

Title:
  The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-
  pkg.so

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

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

[Bug 1883079] [NEW] The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so

[Evgeny Kolesnikov]

Public bug reported:

The "MMap::MMap(FileFd&, unsigned long)" function is missing in libapt-
pkg.so.6.0.0.


nm -D -C /usr/lib/x86_64-linux-gnu/libapt-pkg.so.6.0.0 | grep MMap

001701f0 T pkgCacheGenerator::MakeStatusCache(pkgSourceList&, 
OpProgress*, MMap**, bool)
0016e9c0 T pkgCacheGenerator::MakeOnlyStatusCache(OpProgress*, 
DynamicMMap**)
00167b10 T pkgCache::pkgCache(MMap*, bool)
00167b10 T pkgCache::pkgCache(MMap*, bool)

** Affects: apt (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/1883079

Title:
  The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-
  pkg.so

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

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

[Bug 1883079] Re: The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-pkg.so

[Evgeny Kolesnikov]

cat /etc/os-release

NAME="Ubuntu"
VERSION="20.04 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/";
SUPPORT_URL="https://help.ubuntu.com/";
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

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

Title:
  The "MMap::MMap(FileFd&, unsigned long)" symbol is missing in libapt-
  pkg.so

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

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

[Bug 1870779] Re: [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an Nvidia-only desktop (GeForce GTX 1060)

[EVGENY]

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

I have the same problem with fractional display scaling. After I change
my default drivers to Nvidia and I try to use fractional scaling my
system is crushing and I get black screen.

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

Title:
  [nvidia] Ubuntu 20.04 beta: Blank/black screen after login on an
  Nvidia-only desktop (GeForce GTX 1060)

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

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

[Bug 1844623] Re: pdf presenter console not resetting timer

[Evgeny Stambulchik]

Ctrl+t to reset the timer. Re: "Home", this is the intended behavior.
Please read the man page, 4.3 has quite some backward-incompatibility
changes.

** Changed in: pdf-presenter-console (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/1844623

Title:
  pdf presenter console not resetting timer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pdf-presenter-console/+bug/1844623/+subscriptions

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

[Bug 1875245] [NEW] gnome-shell monitors.xml config validator fails adjacent check for screens saved with 'Fractional Scaling'

[Evgeny Vakhteev]

Public bug reported:


### Affected version

Distributor ID: Ubuntu

Description:Ubuntu 20.04 LTS

GNOME Shell 3.36.1

### Bug summary

Gome-shell monitors.xml config validator fails to validate config saved
by Gnome settings with Fractional Scaling on:

```
Apr 25 13:28:28 xxx systemd[1798]: Starting GNOME Shell on X11...
Apr 25 13:28:28 xxx gnome-shell[10304]: Enabling experimental feature 
'x11-randr-fractional-scaling'
Apr 25 13:28:28 xxx /usr/lib/gdm3/gdm-x-session[10123]: (II) AMDGPU(0): EDID 
vendor "GSM", prod id 23305
...
Apr 25 13:28:28 xxx gnome-shell[10304]: Failed to read monitors config file 
'/home/xxx/.config/monitors.xml': Logical monitors not adjacent
```

### Steps to reproduce

* Need multiple displays to reproduce

1. Go to Display Settings
2. Enable Fractional scaling, for one of the screens, and set scaling to a 
different value than the other one.
3. Restart gnome-shell
4. Settings switched to default ones, as gnome-shell can't validate monitors.xml


### What happened

Gnome-shell can't apply monitors.xml config as it can't validate it with
fractional scaling on

### What did you expect to happen

Scaled settings validated, loaded and remain the same across gnome-shell
restarts

### Relevant logs, screenshots, screencasts etc.

Saved 'Scaled' monitors.xml, which not passing validation:

```


  0
  0
  1
  

  HDMI-A-1
  ACI
  ASUS PB278
  D3LMTF056504


  2560
  1440
  59.950550079345703

  


  5120
  0
  1.5
  yes
  

  DisplayPort-1
  ACI
  ASUS PB287Q
  0x0001ecd2


  3840
  2160
  59.996623992919922

  

  
```

As you can see first one resolution is 2560x1440, but the second one by
position starts at x=5120, so 2560x2, as the second one is saved with
1.5 scale. But gnome-shell probably expects them to be adjacent, so
expects x=2560

So, when gnome-shell starts it looks like we are failing to pass the
adjacent check. And that's exactly what it's saying:

Apr 25 13:28:28 xxx gnome-shell[10304]: Failed to read monitors config
file '/home/xxx/.config/monitors.xml': Logical monitors not adjacent

To verify that I made x=2560 in monitors.xml and restarted gnome-shell,
all scaling remained in place as they saved and no errors from gnome-
shell anymore, but the left screen is half overridden by right one
(which is exactly how to position specified now for the scaled screen).

The modified version of monitors.xml, passing validation:

```


  0
  0
  1
  

  HDMI-A-1
  ACI
  ASUS PB278
  D3LMTF056504


  2560
  1440
  59.950550079345703

  


  2560
  0
  1.5
  yes
  

  DisplayPort-1
  ACI
  ASUS PB287Q
  0x0001ecd2


  3840
  2160
  59.996623992919922

  

  
```

So it looks like config validator in gnome-shell needs to be fixed to
behave differently when logical monitors are scaled.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.1-5ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 26 13:53:28 2020
DisplayManager: gdm3
InstallationDate: Installed on 2020-04-23 (3 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/usr/bin/zsh
RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago)

** Affects: gnome-shell (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/1875245

Title:
  gnome-shell monitors.xml config validator fails adjacent check for
  screens saved with 'Fractional Scaling'

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

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

[Bug 1825593] Re: Display: 100% scale not remembered when X11 Fractional Scaling is enabled

[Evgeny Vakhteev]

Bug report for gnome-shell submitted: https://gitlab.gnome.org/GNOME
/gnome-shell/-/issues/2690

** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2690
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2690

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

Title:
  Display: 100% scale not remembered when X11 Fractional Scaling is
  enabled

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

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

[Bug 1825593] Re: Display: 100% scale not remembered when X11 Fractional Scaling is enabled

[Evgeny Vakhteev]

What I found is, when I'm saving my settings in monitors.xml, is have
the following:

 

  0
  0
  1
  

  HDMI-A-1
  ACI
  ASUS PB278
  D3LMTF056504


  2560
  1440
  59.950550079345703

  


  5120
  0
  1.5
  yes
  

  DisplayPort-1
  ACI
  ASUS PB287Q
  0x0001ecd2


  3840
  2160
  59.996623992919922

  

  

As you can see first one resolution is 2560x1440, but the second one by
position starts at x=5120, so 2560x2, as the second one is saved with
1.5 scale. But gnome-shell probably expects them to be adjacent, so
expects x=2560

So, when gnome-shell starts it looks like we are failing to pass the
adjacent check. And that's exactly what it's saying:

Apr 25 13:28:28 xxx gnome-shell[10304]: Failed to read monitors config
file '/home/xxx/.config/monitors.xml': Logical monitors not adjacent

To verify that I made x=2560 in monitors.xml and restarted gnome-shell,
all scaling remained in place as they saved and no errors from gnome-
shell anymore, but the right screen is half overridden by left one
(which is exactly how to position specified now for the scaled screen).

So it looks like config validator in gnome-shell needs to be fixed to
behave differently when logical monitors are scaled.

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

Title:
  Display: 100% scale not remembered when X11 Fractional Scaling is
  enabled

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

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

[Bug 1864386] [NEW] Capturing Audio (Dubbing). "Make sure you have audio plugins installed on your system"

[Evgeny]

Public bug reported:

SUMMARY

STEPS TO REPRODUCE
1. Install Kdenlive under Ubuntu 19.10.
2. Try to Capturing Audio (Dubbing).

OBSERVED RESULT
Found that list of capturing device is empty with remark: "Make sure you have 
audio plugins installed on your system".

EXPECTED RESULT
Other programs like "SimpleScreenRecorder" work perfect with record audio from 
my laptop and microphone. I expected Kdenlive to record sound from the 
microphone without any problems. 

SOFTWARE/OS VERSIONS
Ubuntu Linux: 19.10;
KDE Frameworks 5.62.0;
Qt 5.12.4.

https://bugs.kde.org/show_bug.cgi?id=418103

But it is a packaging issue. "kdenlive-19.12.2-x86_64.appimage" work
fine.

It was necessary to install the package "libqt5multimedia5-plugins". It
is necessary that this package is automatically installed along with
other dependencies, otherwise you can lose a lot of time until find a
solution to the problem.

** Affects: kdenlive (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/1864386

Title:
  Capturing Audio (Dubbing). "Make sure you have audio plugins installed
  on your system"

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

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

[Bug 1794036] Re: Bionic support with repcached

[Evgeny Kuznetsov]

** Also affects: ubuntu
   Importance: Undecided
   Status: New

** No longer affects: ubuntu

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

Title:
  Bionic support with repcached

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-memcached/+bug/1794036/+subscriptions

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

[Bug 1503310] Re: window content doesn't refresh, only if window is moved

[Evgeny Petrov]

In my current setup (Ubuntu 18.04, nvidia-driver-430) I experience this
issue when using Gnome-Calculator or gedit.

Most of the other applications are not affected.

Changing the gnome theme through the "GNOME-Tweaks" app helped to solve
the problem. Affected themes are Ambiance and Radiance, all others seem
to work

** Attachment added: "Gedit is not repainted"
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1503310/+attachment/5309923/+files/Screenshot%20from%202019-12-05%2006-15-43.png

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

Title:
  window content doesn't refresh, only if window is moved

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

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

[Bug 1812223] Re: gir test fail on ppc64el

[Evgeny Vereshchagin]

Today on GitHub a ppc64el webhook was turned on for the systemd project. The 
fuzzers (built with ASan) crashed there as soon as they started with something 
like
```
757/758 fuzz-varlink:oss-fuzz-14708:address FAIL 0.02 s (exit status 1)

--- command ---
/usr/bin/env 
/tmp/autopkgtest.vdKhS9/build.g6f/systemd/build-deb/fuzz-varlink:address 
/tmp/autopkgtest.vdKhS9/build.g6f/systemd/test/fuzz/fuzz-varlink/oss-fuzz-14708
--- stderr ---
==24171==Shadow memory range interleaves with an existing memory mapping. ASan 
cannot proceed correctly. ABORTING.
==24171==ASan shadow was supposed to be located in the 
[0x01ff-0x11ff] range.
==24171==Process memory map follows:
```
https://github.com/systemd/systemd/pull/13568#issuecomment-545426488

I'm not sure what exactly is going on there but I'm wondering if anyone
runs anything under ASan on ppc64el on a regular basis. Is it even
supported there?

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

Title:
  gir test fail on ppc64el

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

> it looks like @laney is listed there, which is probably appropriate
(he has admin access to the test systems, while I don't)

My understanding is that @laney can help with the infrastructure where
the tests are run. What usually happens on Ubuntu CI for the most part
has nothing to do with the infrastructure. I'd say it's pretty stable
except that for about a month if I recall correctly it failed to report
the statuses of PRs but it was fixed by @laney in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817344.

Regarding TEST-34 on i386, could you open an issue on GitHub? It could
probably be kept on the list as well until it's fixed.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

By the way, @ddstreet would it be OK to mention that you maintain Ubuntu
CI at https://www.freedesktop.org/wiki/Software/systemd/autopkgtest/?
Currently it's almost impossible to figure out who is responsible for
it. At some point I assumed it was @xnox but it doesn't seem the case so
I don't even try to cc @xnox any more.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

Regarding i386, I downloaded the log and took a look at what failed
there. Turns out all the tests except for TEST-34-DYNAMICUSERMIGRATE,
where the global timeout kicked in, passed. Apparently, to judge from
https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/upstream, on Ubuntu CI the tests
are still run one by one whereas on CentOS CI we started to run them in
parallel back in March (https://github.com/systemd/systemd-centos-
ci/pull/78) so it's no wonder the whole test times out sporadically. I
don't expect the script in the Debian package to be fixed any time soon
so could anyone either bump up the timeout or turn the test off?

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

> Opened MR to blacklist TEST-15 and TEST-22

That PR on GitHub hasn't been merged yet so I think it's too soon to
turn those tests off.

> ah, ok - so I did look into this, or at least some failures really
similar to this, a while back, for bug 1831468.

As far as I can tell, several tests failed there because QEMU_TIMEOUT
kicked in. It's different from what is going on on i386 on GitHub where
the whole upstream test fails due to the global timeout.

> Let me know if that sounds familiar or if you have any debugging
suggestions

Depending on where the test is run it could be 300s isn't enough for it
to finish. Given that it's not particularly popular platform I assume
it's run in VMs where the upstream test also launch VMs with QEMU with
no acceleration whatsoever. Could you try bumping up QEMU_TIMEOUT to see
whether it helps?

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

Just to clarify, I think that it would be better to turn off the test
globally because we know it's flaky and unstable and we generally never
roll out globally flaky tests so as not to annoy contributors (I'm not
sure why Ubuntu CI should be different from any other CI system we use
upstream). And then, it should be possible to run the test over and over
again somewhere to see what fails updating the list along the way.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

Regarding the blacklist, we started to work on it in
https://github.com/systemd/systemd/issues/11195 (which was initially
about merging PRs where bugs were caught by Travis CI but ignored
because everybody was used to Ubuntu CI failing more often than not) and
ended up with a list of test I suggested because I more or less knew
what was flaky at the time and kept monitoring Ubuntu CI for a couple of
days. As far as I can tell, it has been abandoned since then. If you're
ready to keep the list up to date by visiting PRs where Ubuntu CI fails
I'm of course all for it.

Other than that, right now the upstream test timeouts on i386, which has
been on for just two days:
https://github.com/systemd/systemd/pull/12901#issuecomment-506646998.
I'm not sure how turning off some tests will help there (because
generally I don't understand why it fails).

Plus, in
https://github.com/systemd/systemd/pull/12861#issuecomment-506556062 the
test is completely broken on Ubuntu CI and I have no idea why.


** Bug watch added: github.com/systemd/systemd/issues #11195
   https://github.com/systemd/systemd/issues/11195

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

I agree ideally the test should be fixed but it's been flaky for a
couple of years and I didn't notice anyone who would be willing to try
to figure it out. I think it's time to admit nobody cares. Even if I'm
totally wrong and someone is interested in getting it to work on Ubuntu
CI, it should be possible to turn it off globally so as not to annoy
contributors with known issues they shouldn't even have to care about
and keep trying to reproduce it "locally" (as we do on CentOS CI, Travis
CI, Azure Pipelines and so on and so forth).

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

In the meantime, I brought arm64 back almost as soon as
https://salsa.debian.org/systemd-team/systemd/merge_requests/34 was
merged. It looks promising except that the "upstream" test is flaky
there as well. It'd be great to turn it off on Ubuntu CI.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

Good to know! Thank you!

Would it also be possible to mark the "upstream" test
(https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/control#L113) "flaky" or turn it
off altogether? We run it on CentOS and Arch anyway so it should be
safe. On Ubuntu CI it's particularly flaky and I don't think it makes
much sense to keep running it there until some stuff like timeouts isn't
adjusted to VMs on the Ubuntu CI infrastructure. I think at this point
it would make sense to make sure that Ubuntu-specific tests are in good
shape.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

> looks like this has been fixed already upstream

Yes. I merged the PR (created by @yuwata) fixing that this morning.

> looks like someone stopped that; it's only running tests for 12888,
12897, and 12899 currently.

In
https://github.com/systemd/systemd/issues/12891#issuecomment-506093934 I
asked Iain Lane to stop that, which I think explains why it's not there
any more.

> I'll take a look at those failures.

Those failures most likely have something to do with that PR and
probably should be fixed upstream. I think it would be better to somehow
address https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824864.
arm64 has been off since December 2018 due to 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/1829829

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1824864] Re: CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

[Evgeny Vereshchagin]

Given that https://github.com/systemd/systemd/issues/11104 is a
variation of this bug and the reason `arm64` has been off since December
2018, I'm wondering how long it will take to fix this on Bionic.

** Bug watch added: github.com/systemd/systemd/issues #11104
   https://github.com/systemd/systemd/issues/11104

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

Title:
  CONFIG_LOG_BUF_SHIFT set to 14 is too low on arm64

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

By the way, judging by http://autopkgtest.ubuntu.com/running#pkg-
systemd-upstream, it seems Ubuntu CI keeps running the tests for PR
12618, which was merged about a month ago.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

Anyway, as I said in
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831296/comments/3,
I don't think Ubuntu CI in its current form is suitable for CI so I'll
just turn it off as soon as it starts failing again. I'm afraid I don't
have time for keeping an eye on it and reporting whatever comes up there
on bugs.launchpad.net.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

I turned on bionic-amd64 and bionic-i386 yesterday. VMs no longer fail
to boot but apparently something else was broken on bionic-i386 while it
was off: https://github.com/systemd/systemd/issues/12891.

In https://github.com/systemd/systemd/pull/12861#issuecomment-506025351
both bionic-amd64 and bionic-s390x failed due to something weird I don't
quite understand. It would be great if someone who is interested in
keeping it afloat could chime in there to help to debug that.

** Bug watch added: github.com/systemd/systemd/issues #12891
   https://github.com/systemd/systemd/issues/12891

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI

[Evgeny Vereshchagin]

I'd add that it seems to me the "upstream" mode of Ubuntu CI doesn't
seem to be actively maintained because unlike the other CI systems used
upstream (which are usually fixed almost immediately), it can be broken
for weeks (or sometimes even months) which isn't suitable for CI. In
principle, if nobody takes care of it, it would probably makes sense to
turn off Ubuntu CI upstream (which I did) and switch to the usual
release cycle where maintainers try to release the package, catch a lot
of bugs (easily preventable by the CI when PRs are opened) and report
them upstream. It's far from ideal, of course, but I don't know what
else to do about it.

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

Title:
  __main__.SeccompTest is failing on Ubuntu CI

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

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

[Bug 1831296] Re: __main__.SeccompTest is failing on Ubuntu CI

[Evgeny Vereshchagin]

That's correct. The assertion is at https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/tests/boot-and-services#L421.

Regarding which release of Ubuntu is affected, I have to say I don't
know. The issue is mostly about "upstream" mode of Ubuntu CI, which can
be detected by checking an environment variable called TEST_UPSTREAM, as
far as I can remember.

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

Title:
  __main__.SeccompTest is failing on Ubuntu CI

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

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

[Bug 1831296] [NEW] __main__.SeccompTest is failing on Ubuntu CI

[Evgeny Vereshchagin]

Public bug reported:

Since https://github.com/systemd/systemd/pull/12430 was merged and
libsecomp was updated the test has been failing on Ubuntu CI:
https://github.com/systemd/systemd/issues/12709. By analogy with
https://github.com/systemd/systemd/pull/12430/commits/c3ab2c389ee60d92fb8d7fe779ae9c4e3c092e4c,
the test should look for either "killed" or "dumped".

** Affects: systemd (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/1831296

Title:
  __main__.SeccompTest is failing on Ubuntu CI

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

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

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

To judge from 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/i386/s/systemd-upstream/20190521_185445_b37c3@/log.gz,
 VMs seems to also be throwing kernel panics:
```
[0.894903] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[0.895921] EDD information not available.
[0.985183] isapnp: No Plug & Play device found
[0.986013] md: Waiting for all devices to be available before autodetect
[0.987166] md: If you don't use raid, use raid=noautodetect
[0.988330] md: Autodetecting RAID arrays.
[0.989038] md: autorun ...
[0.989525] md: ... autorun DONE.
[0.990139] VFS: Cannot open root device 
"UUID=961ce78b-c06e-4632-9aa0-56a8356b081b" or unknown-block(0,0): error -6
[0.991923] Please append a correct "root=" boot option; here are the 
available partitions:
[0.993406] Kernel panic - not syncing: VFS: Unable to mount root fs on 
unknown-block(0,0)
[0.994818] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-50-generic 
#54-Ubuntu
[0.996121] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
[0.997704] Call Trace:
[0.998138]  dump_stack+0x58/0x81
[0.998713]  panic+0x94/0x1e6
[0.999233]  mount_block_root+0x199/0x234
[1.000111]  ? calibrate_delay+0x190/0x4e0
[1.000833]  ? create_dev.constprop.7+0x3a/0x53
[1.001611]  mount_root+0x33/0x35
[1.002182]  prepare_namespace+0x11b/0x167
[1.002885]  kernel_init_freeable+0x1b3/0x1c5
[1.003634]  ? rest_init+0xa0/0xa0
[1.004238]  kernel_init+0xd/0x100
[1.004830]  ret_from_fork+0x1c/0x38
[1.005892] Kernel Offset: 0x1000 from 0xc100 (relocation range: 
0xc000-0xdf5fdfff)
[1.007376] ---[ end Kernel panic - not syncing: VFS: Unable to mount root 
fs on unknown-block(0,0)
```
And there is another one at 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-upstream-systemd-ci-systemd-ci/bionic/i386/s/systemd-upstream/20190521_100015_69099@/log.gz
```
[   41.006515] IP: rollback_registered_many+0x141/0x390
[   41.007872] *pdpt = 1da0b001 *pde =  
[   41.009424] Oops: 0002 [#1] SMP PTI
[   41.010396] Modules linked in: kvm_intel kvm irqbypass crc32_pclmul pcbc 
aesni_intel aes_i586 crypto_simd cryptd joydev input_leds serio_raw mac_hid 
qemu_fw_cfg xt_TCPMSS xt_tcpudp iptable_mangle ip_tables x_tables autofs4 btrfs 
xor zstd_compress raid6_pq psmouse pata_acpi virtio_blk virtio_net i2c_piix4 
floppy
[   41.017754] CPU: 0 PID: 85 Comm: kworker/u2:2 Not tainted 4.15.0-50-generic 
#54-Ubuntu
[   41.019883] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
[   41.022385] Workqueue: netns cleanup_net
[   41.023459] EIP: rollback_registered_many+0x141/0x390
[   41.024825] EFLAGS: 00010202 CPU: 0
[   41.025783] EAX: 0008 EBX: 0008 ECX: 0020 EDX: 
[   41.027477] ESI: dae31ec4 EDI: 00ff EBP: dae31eac ESP: dae31e88
[   41.029162]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
[   41.030641] CR0: 80050033 CR2: dfc746c0 CR3: 1da28000 CR4: 001406f0
[   41.032333] Call Trace:
[   41.033030]  ? netdev_run_todo+0x4a/0x300
[   41.034136]  unregister_netdevice_many.part.104+0x10/0x80
[   41.035603]  default_device_exit_batch+0x13c/0x160
[   41.036933]  ? do_wait_intr_irq+0x80/0x80
[   41.038034]  ops_exit_list.isra.8+0x53/0x60
[   41.039169]  cleanup_net+0x18e/0x260
[   41.040152]  process_one_work+0x1b9/0x3d0
[   41.041246]  worker_thread+0x37/0x420
[   41.042254]  kthread+0xf0/0x110
[   41.043115]  ? process_one_work+0x3d0/0x3d0
[   41.044256]  ? kthread_create_worker_on_cpu+0x20/0x20
[   41.045640]  ret_from_fork+0x2e/0x38
[   41.046629] Code: ce d6 89 d8 03 0c 9d c0 34 bc d6 e8 5a d5 92 ff 89 d8 ba 
a0 e2 ce d6 e8 de de 11 00 3b 05 fc e3 ce d6 89 c3 72 d4 bf ff ff ff 00 <00> 00 
00 00 00 00 00 00 00 01 00 ff ff ff ff ff ff fa 16 3e bb
[   41.051663] EIP: rollback_registered_many+0x141/0x390 SS:ESP: 0068:dae31e88
[   41.053543] CR2: 0008
[   41.054464] ---[ end trace 06d0534c6301b91d ]---
[   41.057078] BUG: unable to handle kernel NULL pointer dereference at 
[   41.059059] IP: flush_backlog+0x3f/0x120
[   41.060132] *pdpt = 1da0b001 *pde =  
[   41.061682] Oops:  [#2] SMP PTI
[   41.062649] Modules linked in: kvm_intel kvm irqbypass crc32_pclmul pcbc 
aesni_intel aes_i586 crypto_simd cryptd joydev input_leds serio_raw mac_hid 
qemu_fw_cfg xt_TCPMSS xt_tcpudp iptable_mangle ip_tables x_tables autofs4 btrfs 
xor zstd_compress raid6_pq psmouse pata_acpi virtio_blk virtio_net i2c_piix4 
floppy
[   41.069990] CPU: 0 PID: 149 Comm: kworker/0:1H Tainted: G  D  
4.15.0-50-generic #54-Ubuntu
[   41.072469] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.1-1ubuntu1~cloud0 04/01/2014
[   41.074954] Workqueue: events_highpri flush_backlo

[Bug 1829829] Re: Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

@pitti would it be possible to temporarily skip the tests where VMs are
rebooted to reduce the blast radius so to speak? I really don't want to
turn Ubuntu CI off completely.

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

Title:
  Ubuntu CI has been flaky for a week

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

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

[Bug 1829829] [NEW] Ubuntu CI has been flaky for a week

[Evgeny Vereshchagin]

Public bug reported:

It was originally reported in 
https://github.com/systemd/systemd/pull/12583#issuecomment-492949206 5 days 
ago. To judge from the logs VMs can't be rebooted there:
```
Ubuntu 18.04.2 LTS autopkgtest ttyS0

autopkgtest login:
---
--- nova show 91e76a78-d05c-412a-b383-55a26010ae69 
(adt-bionic-amd64-systemd-upstream-20190516-051604) --
+--++
| Property | Value  
|
+--++
| OS-DCF:diskConfig| MANUAL 
|
| OS-EXT-AZ:availability_zone  | nova   
|
| OS-EXT-SRV-ATTR:host | euler  
|
| OS-EXT-SRV-ATTR:hypervisor_hostname  | euler.lcy01.scalingstack   
|
| OS-EXT-SRV-ATTR:instance_name| instance-003d216a  
|
| OS-EXT-STS:power_state   | 1  
|
| OS-EXT-STS:task_state| -  
|
| OS-EXT-STS:vm_state  | active 
|
| OS-SRV-USG:launched_at   | 2019-05-16T07:00:42.00 
|
| OS-SRV-USG:terminated_at | -  
|
| accessIPv4   |
|
| accessIPv6   |
|
| config_drive |
|
| created  | 2019-05-16T07:00:33Z   
|
| flavor   | autopkgtest 
(f878e70e-9991-46e0-ba02-8ea159a71656) |
| hostId   | 
1722c5f2face86c3fc9f338ae96835924721512372342f664e6941bd
   |
| id   | 91e76a78-d05c-412a-b383-55a26010ae69   
|
| image| 
adt/ubuntu-bionic-amd64-server-20190516.img 
(d00bf12c-467e-433f-a4f5-15720f13bff1) |
| key_name | 
testbed-juju-prod-ues-proposed-migration-machine-11 
   |
| metadata | {} 
|
| name | 
adt-bionic-amd64-systemd-upstream-20190516-051604   
   |
| net_ues_proposed_migration network   | 10.42.40.13
|
| os-extended-volumes:volumes_attached | [] 
|
| progress | 0  
|
| security_groups  | autopkgtest@lcy01-27.secgroup  
|
| status   | ACTIVE 
|
| tenant_id| afaef86b96dd4828a1ed5ee395ea1421   
|
| updated  | 2019-05-16T07:00:42Z   
|
| user_id  | 8524250971084851b3792a68fbc398dd   
|
+--++
---
: failure: Timed out on waiting for ssh connection
autopkgtest [07:07:45]: ERROR: testbed failure: cannot send to testbed: [Errno 
32] Broken pipe
```

Though judging by https://github.com/systemd/systemd/pull/12626, it
appears that sometimes the tests pass.

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

--

[Bug 1828927] Re: RabbitVCS compare revisions in SVN doesn't work

[Evgeny Erlihman]

Just wanted to add more information on this. It does not look like the
root cause of this issue is the same as before.

It looks like when Meld is showing the diff, it shows the head revision
of the wanted file and the version from previous revision of the
repository, not the file. SO if the file was not modified in the
previous commit, it would show as identical.

It should be comparing head revision of the file with previous revision
of the file and not the previous commit.

I used same vesrion of rabbitvcs on 16.04, and it worked fine. The
problem started happening when i upgraded to 18.04.

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

Title:
  RabbitVCS compare revisions in SVN doesn't work

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

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

[Bug 1819589] [NEW] Ubuntu CI is broken

[Evgeny Vereshchagin]

Public bug reported:

Since 
https://salsa.debian.org/systemd-team/systemd/commit/8d810fda9a640a932d6e7b32afd958fe75e36f5b
 was merged Ubuntu CI has been failing with
```
Investigating (0) udev:amd64 < 237-3ubuntu10.13 -> 241-608-gfd541a5f08-0 @ii 
pumU Ib >
Broken udev:amd64 Depends on dpkg:amd64 < 1.19.0.5ubuntu2.1 @ii mK > (>= 1.19.3)
Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 udev : Depends: dpkg (>= 1.19.3) but 1.19.0.5ubuntu2.1 is to be installed
W: --force-yes is deprecated, use one of the options starting with --allow 
instead.
E: Unable to correct problems, you have held broken packages.
blame: https://salsa.debian.org/systemd-team/systemd.git
badpkg: installation of basic binaries failed, exit code 100
autopkgtest [18:37:50]: ERROR: erroneous package: installation of basic 
binaries failed, exit code 100
Exit request sent.^M
Creating nova instance adt-bionic-amd64-systemd-upstream-20190311-180219 from 
image adt/ubuntu-bionic-amd64-server-20190311.img (UUID 
2bf5f055-214b-4fcf-aadc-dd60a3a1a9d1)...
Creating nova instance adt-bionic-amd64-systemd-upstream-20190311-180219 from 
image adt/ubuntu-bionic-amd64-server-20190311.img (UUID 
2bf5f055-214b-4fcf-aadc-dd60a3a1a9d1)...
```

It's also being discussed in
https://github.com/systemd/systemd/pull/11963.

** Affects: systemd (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/1819589

Title:
  Ubuntu CI is broken

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

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

[Bug 1817344] Re: Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

[Evgeny Vereshchagin]

** Also affects: systemd (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/1817344

Title:
  Ubuntu CI that runs tests via autopkgtest for systemd on GitHub
  reports the wrong results

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

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

[Bug 1817344] [NEW] Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the wrong results

[Evgeny Vereshchagin]

Public bug reported:

I'm not sure this is the right place to report this, but apparently it's
the best way to reach out to Dimitri John Ledkov
(https://github.com/xnox) and Iain Lane (https://github.com/iainlane),
who I believe at least know who maintains Ubuntu CI there.

I'm copying the following verbatim from
https://github.com/systemd/systemd/pull/11531#issuecomment-464731263
(where we are kind of discussing the issue):

> The two PRs you referenced to fail in the `make check` unit tests
(test-path).

That's correct that test-path failed but it failed in
https://github.com/systemd/systemd/pull/11685 while Ubuntu CI reported
it in https://github.com/systemd/systemd/pull/11686 (that is, in
https://github.com/systemd/systemd/pull/11686 in the logs for some
reason UPSTREAM_PULL_REQUEST is 11685 instead of 11686 and something
like that has happened often lately).

In https://github.com/systemd/systemd/pull/11743#issuecomment-464637797,
the issue is that Ubuntu CI showed the results for the first version of
the PR (where there was a bug) and it didn't run the tests against the
latest version. But in that case it's hard to tell because there is no
way to figure out what exactly Ubuntu CI tested. That's why I asked
@xnox to add `git describe` to https://salsa.debian.org/systemd-
team/systemd/blob/master/debian/extra/checkout-upstream so that by
looking at UPSTREAM_PULL_REQUEST and the output of `git describe` it
would be possible to find out what Ubuntu CI reports.

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

** Summary changed:

- Ubuntu CI that runs test via autopkgtest for systemd on GitHub reports the 
wrong results
+ Ubuntu CI that runs tests via autopkgtest for systemd on GitHub reports the 
wrong results

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

Title:
  Ubuntu CI that runs tests via autopkgtest for systemd on GitHub
  reports the wrong results

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

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

[Bug 1743872] Re: "0BDA:A811" - Not work 802.11ac WLAN Adapter

[Evgeny]

I have the same bug with same vendor/product id.

Is it useful, about patch under os_dep/linux/usb_intf.c, struct usb_device_id 
rtw_usb_id_tbl[].
for 0bda:a811?

At the line 320:

{USB_DEVICE(0x0BDA, 0xA811),.driver_info = RTL8821}, /* OUTLINK - Edimax
*/

This line was added 3 years ago, why doesnt work from box? May be is it
wrong patch?

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

Title:
  "0BDA:A811" - Not work 802.11ac WLAN Adapter

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

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

[Bug 1743872] Re: "0BDA:A811" - Not work 802.11ac WLAN Adapter

[Evgeny]

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

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

Title:
  "0BDA:A811" - Not work 802.11ac WLAN Adapter

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

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

[Bug 1781425] Re: videos only play sound but no image

[Evgeny Stambulchik]

Probably the same as #1790389; try installing gstreamer1.0-gtk3.

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

Title:
  videos only play sound but no image

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pdf-presenter-console/+bug/1781425/+subscriptions

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

[Bug 1790389] [NEW] gstreamer1.0-gtk3 should be the "rec" dependency

[Evgeny Stambulchik]

Public bug reported:

Just like in Debian; without gstreamer1.0-gtk3 (providing the "gtksink"
capability to gstreamer), embedded video playback would not work in
pdfpc.

See 

** Affects: pdf-presenter-console (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/1790389

Title:
  gstreamer1.0-gtk3 should be the "rec" dependency

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pdf-presenter-console/+bug/1790389/+subscriptions

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

[Bug 1763994] Re: LG Gram sound issues after rebooting Ubuntu

[Evgeny Brazgin]

I can confirm the problem with loud beeping sound at bios booting time.
In my case it can be interrupted by long-pressing power button until the
laptop switches off, the next boot works well.

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

Title:
  LG Gram sound issues after rebooting Ubuntu

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

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

[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Evgeny Brazgin]

Hi Mark,
The problem is a little more complex.

For example, let's take package virtualbox-5.2 from official virtualbox repo 
(https://download.virtualbox.org/virtualbox/debian/).
1. Deb package depends on libcurl3.
2. Its binary is linked to library with name 'libcurl.so.4'.
3. Its binary requires existence of versioned symbols with names like 
'curl_version_info@@CURL_OPENSSL_3'.

2 and 3 together don't allow simply solve the problem, because there are
apps, which read library of version 4 and use API of version 3.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

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

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

[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Evgeny Brazgin]

I think Canonical should implement some solution like in #47 to support
both ABIs and keep it supported for some time, because all other apps
need some time to upgrade to libcurl4 (18.04 is LTS, so it looks like it
shouldn't have been upgraded to libcurl4 until 18.10).

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

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

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

[Bug 1772339] [NEW] libx86emu1 package doesn't contain libx86emu1.so in cosmic

[Evgeny Brazgin]

Public bug reported:

Appears for cosmic in the latest version 1.14:
https://packages.ubuntu.com/cosmic/libs/libx86emu1

$ dpkg -c libx86emu1_1.14-1_amd64.deb | grep so
lrwxrwxrwx root/root 0 2018-05-19 06:20 
./usr/lib/x86_64-linux-gnu/libx86emu.so. -> libx86emu.so.


Looks like packaging problem.

This prevents the app `hwinfo` from working.

** Affects: libx86emu (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/1772339

Title:
  libx86emu1 package doesn't contain libx86emu1.so in cosmic

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

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

[Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Evgeny Brazgin]

Hello César Bento Freire,
This is not related to libcurl.

But I would suggest you to download libxerces-c3.1 from ubuntu 17.10
repository and try to install it:
https://packages.ubuntu.com/artful/libxerces-c3.1

amd64: 
http://mirrors.kernel.org/ubuntu/pool/universe/x/xerces-c/libxerces-c3.1_3.1.4+debian-2_amd64.deb
i386: 
http://mirrors.kernel.org/ubuntu/pool/universe/x/xerces-c/libxerces-c3.1_3.1.4+debian-2_i386.deb

This may require you to install further additional dependencies from
ubuntu 17.10, or it may just work.

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

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

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

[Bug 1752075] [NEW] xubuntu install via ubiquity input/output error

[Evgeny Litvinenko]

Public bug reported:

try to run ubiquity -d --automatic  fails with input/output error

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Tue Feb 27 16:32:08 2018
InstallCmdLine: file=/cdrom/preseed/xubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
LiveMediaBuild: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.63.4 xenial xubuntu

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

Title:
  xubuntu install via ubiquity input/output error

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

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

[Bug 1473555] Re: package linux-firmware-nonfree (not installed) failed to install / upgrade: attempt "to override /lib/firmware/bcm70015fw.bin", which is also in package firmware CrystalHD 0.0 ~ git2

[Evgeny]

** Changed in: linux-firmware-nonfree (Ubuntu)
 Assignee: (unassigned) => Evgeny (pipik)

** Changed in: linux-firmware-nonfree (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  package linux-firmware-nonfree (not installed) failed to install /
  upgrade: attempt "to override /lib/firmware/bcm70015fw.bin", which is
  also in package firmware CrystalHD 0.0 ~ git20120110.fdd2f19-1

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

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

[Bug 1326776] Re: linux-firmware-nonfree: Copyright infringement of Broadcom b43 firmware

[Evgeny]

** Changed in: linux-firmware-nonfree (Ubuntu)
 Assignee: Tim Gardner (timg-tpi) => Evgeny (pipik)

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

Title:
  linux-firmware-nonfree: Copyright infringement of Broadcom b43
  firmware

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

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

[Bug 1738479] [NEW] libimobile device doesn't see device and device reboots when I'm disconnecting it from computer device doesn't see device, device reboots when I'm disconnecting it from computer

[Evgeny]

Public bug reported:

Hi.

My computer: 
(Lubuntu):
evg@evg-Parallels-Virtual-Platform:$ uname -a
Linux evg-Parallels-Virtual-Platform 4.10.0-42-generic #46~16.04.1-Ubuntu SMP 
Mon Dec 4 15:57:59 UTC 2017 i686 i686 i686 GNU/Linux
(Ubuntu):
Linux ubuntu 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 
2017 i686 i686 i686 GNU/Linux

lsb_release -rd
Description:Ubuntu 16.04.3 LTS
Release:16.04

Device: iPad Air (1st generation), iOS 10.3.3 no jailbroken

I've successfully installed all libs from this document
https://gist.github.com/samrocketman/70dff6ebb18004fc37dc5e33c259a0fc .
And device isn't visible when I'm trying to pair it using idevicepair
pair command, but it appears in all connected device list.

evg@evg-Parallels-Virtual-Platform:$ lsusb
Bus 001 Device 006: ID 05ac:12ab Apple, Inc. iPad 4/Mini1
Bus 001 Device 002: ID 203a:fff9
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
evg@evg-Parallels-Virtual-Platform:$ idevicepair pair
No device found, is it plugged in?
I've tried on Lubuntu (16.0.4 LTS) both 32bit and 64 bit systems and on Ubuntu 
(16.0.4 LTS and 17.10) both 32 and 64 bit systems. Also on Ubuntu my ipad 
reboots when I disconnecting it from computer.

video with reboot (Reboot appears only on Ubuntu, not Lubuntu):
https://youtu.be/8expDYVAW4o

** Affects: libimobiledevice (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/1738479

Title:
  libimobile device doesn't see device and device reboots when I'm
  disconnecting it from computer device doesn't see device, device
  reboots when I'm disconnecting it from computer

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

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

[Bug 1722179] [NEW] Second x-screen hangs in multiple-head configuration

[Evgeny S Maksimov]

Public bug reported:

On a machine with two Radeon R7 240 video adapters and four monitors (two 
monitors on each), when Qt 5 app actively uses OpenGL to draw the interface 
starts, a hanging second x-screen appears after a while. At this point, the 
mouse cursor over the hanging x-screen moves freely.
The problem is also typical for Kubuntu 17.04 but in the case of Kubuntu 17.10 
(beta) it periodically leads to a full freezing of the X-server.

P.S.
When the DVI cable is physically disconnected from the fourth monitor the 
problem does not appear.
P.P.S.
The hardware of the system unit is absolutely new.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-video-amdgpu 1.4.0-1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
BootLog: /dev/sda1: clean, 699983/122101760 files, 286086386/488378368 blocks
Date: Mon Oct  9 09:36:33 2017
DistUpgraded: 2017-10-05 19:03:53,942 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: artful
DistroVariant: kubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 
[1002:6613] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Oland PRO [Radeon R7 240/340] [1043:04c5]
 Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340] 
[1002:6613] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Oland PRO [Radeon R7 240/340] [1043:04c5]
InstallationDate: Installed on 2017-09-18 (20 days ago)
InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=b3726d8c-94d8-41b5-b20f-e2369c18ec8c ro quiet splash vt.handoff=7
SourcePackage: xserver-xorg-video-amdgpu
UpgradeStatus: Upgraded to artful on 2017-10-05 (3 days ago)
dmi.bios.date: 06/26/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xserver-xorg-video-amdgpu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful kubuntu

** Attachment added: "demo.jpg"
   https://bugs.launchpad.net/bugs/1722179/+attachment/4965559/+files/demo.jpg

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

Title:
  Second x-screen hangs in multiple-head configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1722179/+subscriptions

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

[Bug 1665695] [NEW] OpenSSH PKCS#11 interface does not support ECC.

[Evgeny Khorkin]

Public bug reported:

OpenSSH client doesn't support Eliptics Curve keys on PKCS11 smartcard

ssh-keygen -v -D /usr/lib/libeTPkcs11.so 
debug1: manufacturerID  cryptokiVersion 2.20 libraryDescription 
 libraryVersion 9.1
debug1: label  manufacturerID  model  
serial <> flags 0x60d
C_GetAttributeValue failed: 18
debug1: X509_get_pubkey failed or no rsa
debug1: X509_get_pubkey failed or no rsa
debug1: X509_get_pubkey failed or no rsa
no keys
cannot read public key from pkcs11

pkcs11-tool --module /usr/lib/libeTPkcs11.so -O
...
Public Key Object; EC  EC_POINT 256 bits
  EC_POINT:   
04410474c5423bd0aa44b7825b3e79cd839e06736b18466b131d0884dbf8d946fbdc7f3297e73b998acf56550c303dc972a4dec51b9a3b746d3fe9fb4a44bd84b080fc
  EC_PARAMS:  06082a8648ce3d030107
  label:  TestECCpair
  Usage:  encrypt, verify, wrap


There is upstream bug: https://bugzilla.mindrot.org/show_bug.cgi?id=2474
Suggested patch: https://bugzilla.mindrot.org/attachment.cgi?id=2728

release: Ubuntu 16.04.2 LTS
openssh version: 7.2p2-4ubuntu2.1

** Affects: openssh (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/1665695

Title:
  OpenSSH PKCS#11 interface does not support ECC.

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

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

[Bug 1636573] Re: xinit flooding syslog

[Evgeny]

I have the same problem & don't know what to do.
Linux Mint 18.1
Kodi version: 2:17.0~git20170210.1529-final-0xenial

Trying to get in third-party repo. Kodi's flooding into file /var/log/syslog 
>30gb of two strings:
extern "Python": function Cryptography_rand_bytes() called, but 
@ffi.def_extern() was not called in the current subinterpreter. Returning 0.
extern "Python": function Cryptography_rand_status() called, but 
@ffi.def_extern() was not called in the current subinterpreter. Returning 0.

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

Title:
  xinit flooding syslog

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

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

[Bug 771272] Re: gnome-keyring doesn't support ecdsa or ed25519 keys

[Evgeny Markov]

Almost six years have passed, but bug still not closed.

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

Title:
  gnome-keyring doesn't support ecdsa or ed25519 keys

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

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

[Bug 1393531] Re: cannot add ed25519 or ecdsa keys to the keyring

[Evgeny Markov]

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

Still not fixed... nice.

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

Title:
  cannot add ed25519 or ecdsa  keys to the keyring

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

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

[Bug 1648733] Re: Segmentation fault on 4.3-1

[Evgeny Li.]

** Description changed:

  joe 4.3-1 crashes with Segmentation fault(core dumped)
  on string containing \\ and UTF-8 chars
- (look at file supplied)
+ (to reproduce, open supplied 'crash.rb' file)
+ 
+ NOTE: joe 4.2 haven't this bug!
+ 
+ gdb output:
+ 
+ GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
+ ...
+ Program terminated with signal SIGSEGV, Segmentation fault.
+ #0  0x080963e9 in parse (syntax=0x445, line=0x82a5f58, h_state=...,
+ charmap=0x82a0fb8) at syntax.c:162
+ 162 h = (stack ? stack->syntax : syntax)->states[h_state.state];
+ (gdb) where
+ #0  0x080963e9 in parse (syntax=0x445, line=0x82a5f58, h_state=...,
+ charmap=0x82a0fb8) at syntax.c:162
+ #1  0x0809d2ea in lattr_get (db=0x87085b0, y=0x445, p=0x82a5e68, line=8)
+ at lattr.c:303
+ #2  0x080728b1 in get_context (bw=0x835a508, bw=0x835a508) at tw.c:72
+ #3  stagen (stalin=0x835d9a8 "\\i^[  I A  ~/dev/i/crash.rb (ruby)  ",
+ bw=0x835a508, s=0x829476b "x", fill=32 ' ') at tw.c:231
+ #4  0x08072c82 in disptw (w=0x8916928, flg=1) at tw.c:599
+ #5  0x0805d79e in edupd (flg=1) at main.c:67
+ #6  0x0805d91e in edloop (flg=0) at main.c:134
+ #7  0x0804a898 in main (argc=2, real_argv=0xbfbc1fb4, envv=0xbfbc1fc0)
+ at main.c:678

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

Title:
  Segmentation fault on 4.3-1

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

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

[Bug 1648706] Re: search with regexp range bug

[Evgeny Li.]

** Summary changed:

- search with regexp diapason bug
+ search with regexp range bug

** Description changed:

- regexp diapason doesn't work. 
- To reproduce, try to search some regexp diapason on appropriate file. 
+ regexp range doesn't work at all.
+ To reproduce, try to search some regexp range on appropriate file.
  E.g. search for
  
  \[1-9]
  \[a-z]
  
  and so on.
  
  Note: latest joe version 4.3, compiled on xenial, works fine.

** Description changed:

- regexp range doesn't work at all.
+ joe 4.1
+ Search by regexp range doesn't work at all.
  To reproduce, try to search some regexp range on appropriate file.
  E.g. search for
  
  \[1-9]
  \[a-z]
  
  and so on.
  
- Note: latest joe version 4.3, compiled on xenial, works fine.
+ Note: latest joe version (4.3), compiled on xenial, works.

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

Title:
  search with regexp range bug

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

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

[Bug 1648733] [NEW] Segmentation fault on 4.3-1

[Evgeny Li.]

Public bug reported:

joe 4.3-1 crashes with Segmentation fault(core dumped)
on string containing \\ and UTF-8 chars
(look at file supplied)

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

** Attachment added: "crash.rb"
   https://bugs.launchpad.net/bugs/1648733/+attachment/4789415/+files/crash.rb

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

Title:
  Segmentation fault on 4.3-1

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

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

[Bug 1648706] [NEW] search with regexp diapason bug

[Evgeny Lineytsev]

Public bug reported:

regexp diapason doesn't work. 
To reproduce, try to search some regexp diapason on appropriate file. 
E.g. search for

\[1-9]
\[a-z]

and so on.

Note: latest joe version 4.3, compiled on xenial, works fine.

** Affects: joe (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/1648706

Title:
  search with regexp diapason bug

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

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

[Bug 1638640] Re: Goldendict tray icon error on screen lock

[Evgeny Frolov]

This problem doesn't exist form me at ubuntu 16.04 fresh install.

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

Title:
  Goldendict tray icon error on screen lock

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

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

[Bug 1638640] Re: Goldendict tray icon error on screen lock

[Evgeny Frolov]

Additional information.
The same touches skype icon in the system tray (ubuntu 16.10).

Skype icon changes to error sign on screen lock or suspend and resume.

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

Title:
  Goldendict tray icon error on screen lock

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

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

[Bug 1491249] Re: Regression: Visual new email notification no longer working in 38.2.0

[Evgeny Frolov]

The fully updated ubuntu 16.10 install. There is no osd-notifications
too! Only sound + Unity panel showing the number of unread + messaging
applet changing color.

But where is the notification text-bubble??

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

Title:
  Regression: Visual new email notification no longer working in 38.2.0

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

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

[Bug 1638640] [NEW] Goldendict tray icon error on screen lock

[Evgeny Frolov]

Public bug reported:

On ubuntu 16.10 launching Goldendict (v. 1.5.0~git20160508.g92b5485-1.1) 
creates a tray icon in the ubuntu panel tray area.
The icon is unexpectedly changed to a crossed red circle on black background on 
screen lock.

Steps to reproduce:
1) launch goldendict
2) lock your screen
3) unlock your screen

Expected behavior:
The goldendict icon that's appeared after step 1) should be there unchanged 
after screen unlocking.

What happened insted:
The goldendict trayicon is changed to an error sign (crossed red circle on 
black background) after screen unlocking.

PS I believe, one can catch the fact that the icon changes right before the 
lock.
PPS DropBox and Telegram icons are not affected.
PPPS Restarting goldendict fixes the problem.
S what can I do to help with dealing with the bug?

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

** Attachment added: "Screenshot of the error-looking-like goldendict tray icon"
   
https://bugs.launchpad.net/bugs/1638640/+attachment/4771229/+files/Screenshot%20from%202016-11-02%2020-10-52.png

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

Title:
  Goldendict tray icon error on screen lock

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

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

[Bug 1534541] Re: Dash doesn't accept input (appears frozen) after youtube scope auth

[Evgeny]

I have simmilar bug when exiting fullscreen mode on youtube. Everything
freezes, but I still can move mouse and do ctrl+alt+f1.

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

Title:
  Dash doesn't accept input (appears frozen) after youtube scope auth

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1534541/+subscriptions

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

[Bug 1039998] Re: perf top (linux-tools) cannot find debug info for some gstreamer plugins

[Evgeny Vereshchagin]

Looks like `perf` doesn't understand a path /usr/lib/debug/.build-id/

See: https://gist.github.com/evverx/bd0a6748f3c6254d2021#perf-probe
Environment: https://gist.github.com/evverx/bd0a6748f3c6254d2021#environment

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

Title:
  perf top (linux-tools) cannot find debug info for some gstreamer
  plugins

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

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

[Bug 1518713] [NEW] package mysql-server-5.6 5.6.27-0ubuntu0.15.04.1 failed to install/upgrade: подпроцесс установлен сценарий post-installation returned error code 1 during upgrade, possibly due to c

[Evgeny]

Public bug reported:

Bug happened during update Ubuntu 14.10 Release:14.10: >
Ubuntu 15.04 Release:   15.04

apt-cache policy mysql-server*
mysql-server-core-5.1:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
mysql-server-core-5.5:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
mysql-server-core-5.6:
  Установлен: 5.6.27-0ubuntu0.15.04.1
  Кандидат:   5.6.27-0ubuntu1
  Таблица версий:
 5.6.27-0ubuntu1 0
500 http://ru.archive.ubuntu.com/ubuntu/ wily-security/main amd64 
Packages
500 http://ru.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
 *** 5.6.27-0ubuntu0.15.04.1 0
100 /var/lib/dpkg/status
 5.6.25-0ubuntu1 0
500 http://ru.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
mysql-server-5.0:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
mysql-server-5.1:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
mysql-server-5.5:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
 5.5.44-0ubuntu0.14.10.1 0
100 /var/lib/dpkg/status
mysql-server-5.6:
  Установлен: 5.6.27-0ubuntu0.15.04.1
  Кандидат:   5.6.27-0ubuntu1
  Таблица версий:
 5.6.27-0ubuntu1 0
500 http://ru.archive.ubuntu.com/ubuntu/ wily-security/main amd64 
Packages
500 http://ru.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
 *** 5.6.27-0ubuntu0.15.04.1 0
100 /var/lib/dpkg/status
 5.6.25-0ubuntu1 0
500 http://ru.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
virtual-mysql-server-core:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
mysql-server:
  Установлен: 5.6.27-0ubuntu0.15.04.1
  Кандидат:   5.6.27-0ubuntu1
  Таблица версий:
 5.6.27-0ubuntu1 0
500 http://ru.archive.ubuntu.com/ubuntu/ wily-security/main amd64 
Packages
500 http://ru.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 
Packages
 *** 5.6.27-0ubuntu0.15.04.1 0
100 /var/lib/dpkg/status
 5.6.25-0ubuntu1 0
500 http://ru.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages
virtual-mysql-server:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: mysql-server-5.6 5.6.27-0ubuntu0.15.04.1
ProcVersionSignature: Ubuntu 3.16.0-44.59-lowlatency 3.16.7-ckt14
Uname: Linux 3.16.0-44-lowlatency x86_64
ApportVersion: 2.17.2-0ubuntu1.8
Architecture: amd64
Date: Sun Nov 22 15:44:48 2015
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2014-10-23 (394 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.mysql.conf.d.mysqld.safe.syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['debian-5.5.flag', 'mysql', 'ib_logfile0', 
'ib_logfile1', 'ibdata1']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-lowlatency 
root=UUID=44166d85-2743-49d1-ab34-a01a280cb4ce ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.2
SourcePackage: mysql-5.6
Title: package mysql-server-5.6 5.6.27-0ubuntu0.15.04.1 failed to 
install/upgrade: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
UpgradeStatus: Upgraded to vivid on 2015-11-22 (0 days ago)

** Affects: mysql-5.6 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package third-party-packages vivid

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

Title:
  package mysql-server-5.6 5.6.27-0ubuntu0.15.04.1 failed to
  install/upgrade: подпроцесс установлен сценарий post-installation
  returned error code 1 during upgrade, possibly due to choosing the
  option to create a new configuration file non existent before

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1518713/+subscriptions

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

[Bug 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus

[Evseev Evgeny]

Bug still exists in 15.10.  It is extremelly annoying.

Possible workaround:

* Install autokey, add to Startup applications. It handles shortcuts using X 
Window System instead of Gnome.
* Add custom scripts to autokey and set shortcuts for them

Keyboard First Layout:
   from subprocess import check_output
   check_output(['gsettings', 'set', 'org.gnome.desktop.input-sources', 
'current', '0'])

Keyboard Second Layout:
  from subprocess import check_output
  check_output(['gsettings', 'set', 'org.gnome.desktop.input-sources', 
'current', '1'])

Works well with XMind. Gedit search input still lose focus on layout
switch.

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

Title:
  Pressing any global keyboard shortcut causes temporary loss of focus

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

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

[Bug 1482990] Re: ld -lpython3.4 failed

[Evgeny Lensky]

** Changed in: python3.4 (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/python3.4/+question/270210

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

Title:
  ld -lpython3.4 failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1482990/+subscriptions

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

[Bug 1482990] Re: ld -lpython3.4 failed

[Evgeny Lensky]

libboost compilation failed because of a lack of libpython3.4.so

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

Title:
  ld -lpython3.4 failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1482990/+subscriptions

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

[Bug 1482990] [NEW] ld -lpython3.4 failed

[Evgeny Lensky]

Public bug reported:

#ld -lpython3.4 --verbose
attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.so failed
attempt to open /usr/i686-linux-gnu/lib32/libpython3.4.a failed
attempt to open //usr/local/lib32/libpython3.4.so failed
attempt to open //usr/local/lib32/libpython3.4.a failed
attempt to open //lib32/libpython3.4.so failed
attempt to open //lib32/libpython3.4.a failed
attempt to open //usr/lib32/libpython3.4.so failed
attempt to open //usr/lib32/libpython3.4.a failed
attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.so failed
attempt to open //usr/local/lib/i386-linux-gnu/libpython3.4.a failed
attempt to open //usr/local/lib/libpython3.4.so failed
attempt to open //usr/local/lib/libpython3.4.a failed
attempt to open //lib/i386-linux-gnu/libpython3.4.so failed
attempt to open //lib/i386-linux-gnu/libpython3.4.a failed
attempt to open //lib/libpython3.4.so failed
attempt to open //lib/libpython3.4.a failed
attempt to open //usr/lib/i386-linux-gnu/libpython3.4.so failed

** Affects: python3.4 (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/1482990

Title:
  ld -lpython3.4 failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3.4/+bug/1482990/+subscriptions

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

[Bug 1482808] [NEW] timedatectl status prints old timezone

[Evgeny Vereshchagin]

Public bug reported:

# lsb_release -rd
Description:Ubuntu 14.04.3 LTS
Release:14.04

# apt-cache policy systemd-services
systemd-services:
  Installed: 204-5ubuntu20.13
  Candidate: 204-5ubuntu20.13
  Version table:
 *** 204-5ubuntu20.13 0
500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
100 /var/lib/dpkg/status


# timedatectl status
  Local time: Sat 2015-08-08 01:09:36 UTC
  Universal time: Sat 2015-08-08 01:09:36 UTC
Timezone: Etc/UTC (UTC, +)

# echo 'Europe/Moscow' >/etc/timezone
# dpkg-reconfigure -f noninteractive tzdata

Current default time zone: 'Europe/Moscow'

# timedatectl status
  Local time: Sat 2015-08-08 04:10:58 MSK
  Universal time: Sat 2015-08-08 01:10:58 UTC
RTC time: Sat 2015-08-08 01:10:57
Timezone: Etc/UTC (MSK, +0300)

# cat /etc/timezone
Europe/Moscow

Should be "Timezone: Europe/Moscow (MSK, +0300)"

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

** Summary changed:

- timedatectl status prints timezone
+ timedatectl status prints old timezone

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

Title:
  timedatectl status prints old timezone

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

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

[Bug 1481871] [NEW] apt-key del doesn't understand fingerprint

[Evgeny Vereshchagin]

Public bug reported:

Description:Ubuntu 14.04.3 LTS
Release:14.04

apt:
  Installed: 1.0.1ubuntu2.10

apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
7A82B743B9B8E46F12C733FA4759FA960E27C0A6

apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here

apt-key del  7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key

apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still
here

# Works fine with IDs

apt-key del  0E27C0A6

apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing
exported

# Works fine with fingerprint on Precise

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

** Description changed:

  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  
  apt:
-   Installed: 1.0.1ubuntu2.10
+   Installed: 1.0.1ubuntu2.10
  
- 
- apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80 
+ apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
+ 7A82B743B9B8E46F12C733FA4759FA960E27C0A6
  
  apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 #
  key is here
  
  apt-key del  7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key
  
  apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 #
  key is still here
  
  # Works fine with IDs
  
  apt-key del  0E27C0A6
  
  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing
  exported
  
  # Works fine with fingerprint on Precise

** Description changed:

  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  
  apt:
    Installed: 1.0.1ubuntu2.10
  
  apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
  7A82B743B9B8E46F12C733FA4759FA960E27C0A6
  
- apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 #
- key is here
+ apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here
  
  apt-key del  7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key
  
  apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 #
  key is still here
  
  # Works fine with IDs
  
  apt-key del  0E27C0A6
  
  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing
  exported
  
  # Works fine with fingerprint on Precise

** Description changed:

  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  
  apt:
    Installed: 1.0.1ubuntu2.10
  
  apt-key adv --recv-keys --keyserver hkp://keyserver.ubuntu.com:80
  7A82B743B9B8E46F12C733FA4759FA960E27C0A6
  
  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is here
  
  apt-key del  7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # delete key
  
- apt-key export apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 #
- key is still here
+ apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # key is still
+ here
  
  # Works fine with IDs
  
  apt-key del  0E27C0A6
  
  apt-key export 7A82B743B9B8E46F12C733FA4759FA960E27C0A6 # nothing
  exported
  
  # Works fine with fingerprint on Precise

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

Title:
  apt-key del doesn't understand fingerprint

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

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

[Bug 1478907] [NEW] Nvidia-related error during an update involving the kernel

[Evgeny Makarov]

Public bug reported:

After a regular update that involved kernel 3.13.0-59 (currently using
3.13.0-58), I got an error message, I believe, about the nvidia-331
package. Unfortunately, I after I clicked the button to submit the bug,
I don't have the error message anymore. I also got an error about the
nvidia-331-uvm package. The latter may be related to bug #1268257, and
I've kept getting it with every kernel update for several months. But
the error about the nvidia-331 package is new.

$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04

$ apt-cache policy nvidia-331
nvidia-331:
  Installed: 331.113-0ubuntu0.0.4
  Candidate: 331.113-0ubuntu0.0.4
  Version table:
 *** 331.113-0ubuntu0.0.4 0
500 http://mirror.corbina.net/ubuntu/ trusty-updates/restricted amd64 
Packages
500 http://mirror.corbina.net/ubuntu/ trusty-security/restricted amd64 
Packages
100 /var/lib/dpkg/status
 331.38-0ubuntu7 0
500 http://mirror.corbina.net/ubuntu/ trusty/restricted amd64 Packages

$ apt-cache policy nvidia-331-uvm
nvidia-331-uvm:
  Installed: 331.113-0ubuntu0.0.4
  Candidate: 331.113-0ubuntu0.0.4
  Version table:
 *** 331.113-0ubuntu0.0.4 0
500 http://mirror.corbina.net/ubuntu/ trusty-updates/restricted amd64 
Packages
500 http://mirror.corbina.net/ubuntu/ trusty-security/restricted amd64 
Packages
100 /var/lib/dpkg/status
 331.38-0ubuntu7 0
500 http://mirror.corbina.net/ubuntu/ trusty/restricted amd64 Packages

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: nvidia-331 331.113-0ubuntu0.0.4
ProcVersionSignature: Ubuntu 3.13.0-58.97-generic 3.13.11-ckt22
Uname: Linux 3.13.0-58-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
DKMSKernelVersion: 3.13.0-59-generic
Date: Tue Jul 28 13:42:16 2015
InstallationDate: Installed on 2014-08-09 (352 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageVersion: 331.113-0ubuntu0.0.4
SourcePackage: nvidia-graphics-drivers-331
Title: nvidia-331 331.113-0ubuntu0.0.4: nvidia-331 kernel module failed to build
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia.331.hybrid.conf: [deleted]

** Affects: nvidia-graphics-drivers-331 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  Nvidia-related error during an update involving the kernel

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

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

[Bug 1322872] Re: Docky software crashes almost every time I suspend the machin Linux Mint 17 RC mate 64 bit Laptop Asus N56VZ

[Evgeny Shpilevsky]

Have the same problem on Linux Mint 17 Dell Latitude E6330

$ uname
Linux laptop 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 
x86_64 x86_64 x86_64 GNU/Linux

$ mono --version
Mono JIT compiler version 3.2.8 (Debian 3.2.8+dfsg-4ubuntu1.1)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. 
www.mono-project.com
TLS:   __thread
SIGSEGV:   altstack
Notifications: epoll
Architecture:  amd64
Disabled:  none
Misc:  softdebug 
LLVM:  supported, not enabled.
GC:sgen


Stack trace for help:

$ docky
[Info  20:45:35.725] Docky version: 2.2.0 Release
[Info  20:45:35.731] Kernel version: 3.13.0.24
[Info  20:45:35.733] CLR version: 4.0.30319.17020
[Error 20:45:36.029] [SystemService] Could not initialize power manager dbus: 
'org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on 
interface "org.freedesktop.UPower" doesn't exist
'
[Info  20:45:36.035] [SystemService]   at 
Docky.Services.SystemService+IUPowerProxy.Get (System.String interface, 
System.String propname) [0x0] in :0 
  at Docky.Services.SystemService.HandleUPowerChanged () [0x0] in :0 
  at Docky.Services.SystemService.InitializeBattery () [0x0] in :0 
[Info  20:45:36.053] [ThemeService] Setting theme: Classic
[Warn  20:45:36.080] [DesktopItemService] Could not find remap file 
'/home/ftdebugger/.local/share/docky/remaps.ini'!
[Info  20:45:36.280] [DockServices] Dock services initialized.
[Fatal 20:45:36.825] [GLib] Source ID 63 was not found when attempting to 
remove it
Cairo.Surface is leaking, programmer is missing a call to Dispose
Set MONO_CAIRO_DEBUG_DISPOSE to track allocation traces

Unhandled Exception:
System.Reflection.TargetInvocationException: Exception has been thrown by the 
target of an invocation. ---> System.Exception: 
org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on 
interface "org.freedesktop.UPower" doesn't exist

  at Docky.Services.SystemService+IUPowerProxy.Get (System.String interface, 
System.String propname) [0x0] in :0 
  at Docky.Services.SystemService.HandleUPowerChanged () [0x0] in :0 
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke 
(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags 
invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, 
System.Globalization.CultureInfo culture) [0x0] in :0 
  --- End of inner exception stack trace ---
at System.Reflection.MonoMethod.Invoke 
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
 <0x00137>
at System.Reflection.MethodBase.Invoke (object,object[]) <0x00032>
at System.Delegate.DynamicInvokeImpl (object[]) <0x00203>
at System.MulticastDelegate.DynamicInvokeImpl (object[]) <0x0003b>
at System.Delegate.DynamicInvoke (object[]) <0x00020>
at DBus.Connection.HandleSignal (DBus.Protocol.Message) <0x0031f>
at DBus.Connection.DispatchSignals () <0x00067>
at DBus.Connection.Iterate () <0x0002f>
at DBus.BusG/c__AnonStorey0.<>m__0 (intptr,DBus.GLib.IOCondition,intptr) 
<0x0003b>
at (wrapper native-to-managed) DBus.BusG/c__AnonStorey0.<>m__0 
(intptr,DBus.GLib.IOCondition,intptr) <0x0008a>
at (wrapper managed-to-native) Gtk.Application.gtk_main () <0x00054>
at Gtk.Application.Run () <0xb>
at Docky.Docky.Main (string[]) <0x005cb>

[ERROR] FATAL UNHANDLED EXCEPTION:
System.Reflection.TargetInvocationException: Exception has been thrown
by the target of an invocation. ---> System.Exception:
org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature
"ss" on interface "org.freedesktop.UPower" doesn't exist

  at Docky.Services.SystemService+IUPowerProxy.Get (System.String interface, 
System.String propname) [0x0] in :0 
  at Docky.Services.SystemService.HandleUPowerChanged () [0x0] in :0 
  at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke 
(System.Reflection.MonoMethod,object,object[],System.Exception&)
  at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags 
invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, 
System.Globalization.CultureInfo culture) [0x0] in :0 
  --- End of inner exception stack trace ---
at System.Reflection.MonoMethod.Invoke 
(object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
 <0x00137>
at System.Reflection.MethodBase.Invoke (object,object[]) <0x00032>
at System.Delegate.DynamicInvokeImpl (object[]) <0x00203>
at System.MulticastDelegate.DynamicInvokeImpl (object[]) <0x0003b>
at System.Delegate.DynamicInvoke (object[]) <0x00020>
at DBus.Connection.HandleSignal (DBus.Protocol.Message) <0x0031f>
at DBus.Connection.DispatchSignals () <0x00067>
at DBus.Connection.Iterate () <0x0002f>
at DBus.BusG/c__AnonStorey0.<>m__0 (intptr,DBus.GL

[Bug 1357804] Re: Ubuntu 14.04 does not support 2560x1080 resolution.

[Evgeny]

Do you have any solution for ATI graphics card?

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

Title:
  Ubuntu 14.04 does not support 2560x1080 resolution.

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

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