[Bug 1963671] Re: Snap refresh timer stuck

[Marek Stasiak]

I have a problem with some snaps not being auto-updated (Firefox).
Ubuntu 22.04 here. There is something fishy about refresh schedule. Snap
refresh --time shows past date for "next" refresh.


marek@marek-pc:~$ snap refresh --time
timer: 00:00~24:00/4
last: 2 days ago, at 00:01 CEST
next: 2 days ago, at 10:20 CEST



marek@marek-pc:~$ snap changes
ID   Status  Spawn  Ready  Summary
503  Done2 days ago, at 00:01 CEST  2 days ago, at 00:01 CEST  Auto-refresh 
snap "bitwarden"


marek@marek-pc:~$ snap version
snap2.62
snapd   2.62
series  16
ubuntu  22.04
kernel  6.5.0-28-generic

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

Title:
  Snap refresh timer stuck

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


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

[Bug 2063158] [NEW] Tuxedo: ubuntu-minimal not found

[Marek]

Public bug reported:

i'm using tuxedo repos and upgrade to 24.04 fails due to missing
repository entries?

$ more /etc/apt/sources.list
# tuxedo-tomte commented out all entries at installation, any TUXEDO 
repositories will be automatically deleted
# 
#

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19
ProcVersionSignature: Ubuntu 6.5.0-10031.35-tuxedo 6.5.13
Uname: Linux 6.5.0-10031-tuxedo x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 00:00:01 2024
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to jammy on 2024-04-22 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2024-04-22 23:59:42.780607
 Log time: 2024-04-22 23:59:45.025504
 Log time: 2024-04-23 00:00:01.286514
 Log time: 2024-04-23 00:00:02.433200
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2022-11-27T18:21:54.872000

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


** Tags: amd64 apport-bug dist-upgrade jammy 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/2063158

Title:
  Tuxedo: ubuntu-minimal not found

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


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

[Bug 2059847] Re: Input lag or freezes on Nvidia desktops with X11

[Marek]

To get rid of the terminal slowness, what should I do?

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

Title:
  Input lag or freezes on Nvidia desktops with X11

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


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

[Bug 2059847] Re: Input lag in native terminal

[Marek]

I believe it is related to one of those packages:


** Attachment added: "Screenshot from 2024-03-31 12-13-50.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2059847/+attachment/5760904/+files/Screenshot%20from%202024-03-31%2012-13-50.png

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

Title:
  Input lag in native terminal

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


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

[Bug 2059847] Re: Input lag in native terminal

[Marek]

There is also a recent discussion here:
https://askubuntu.com/questions/1509058/input-delay-on-terminal-ubuntu-22-04-4

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

Title:
  Input lag in native terminal

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


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

Re: [Bug 2059847] Re: Input lag in native terminal

[Marek]

I am deeply sorry - I must have selected the wrong option in 'ubuntu-bug'.
I am referring to the native terminal installed on ubuntu 22.04, which for
the last few days seems to be lagging due to some latest update. There is
an input delay, noticeable, and the deleting of input text comes with a
delay, too.

sob., 30 mar 2024 o 21:25 Steve Langasek <2059...@bugs.launchpad.net>
napisał(a):

> This bug is filed against ubiquity, which is an installer, not a
> terminal.  It is unclear what you mean by a "native terminal".  Please
> elaborate.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2059847
>
> Title:
>   Input lag in native terminal
>
> Status in ubiquity package in Ubuntu:
>   New
>
> Bug description:
>   There is a noticeable delay in input while using the native terminal.
>   I belive it was caused by a recent software update, as this issue is
>   relatively new.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
>   Uname: Linux 6.5.0-26-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia wl
>   ApportVersion: 2.20.11-0ubuntu82.5
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar 30 19:57:13 2024
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>   InstallationDate: Installed on 2024-03-30 (0 days ago)
>   InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64
> (20240220)
>   SourcePackage: ubiquity
>   Symptom: installation
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2059847/+subscriptions
>
>

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

Title:
  Input lag in native terminal

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


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

[Bug 2059847] [NEW] Input lag in native terminal

[Marek]

Public bug reported:

There is a noticeable delay in input while using the native terminal. I
belive it was caused by a recent software update, as this issue is
relatively new.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 30 19:57:13 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2024-03-30 (0 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy ubiquity-22.04.20

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

Title:
  Input lag in native terminal

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


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

[Bug 2011806] Re: [lunar] Snaps don't launch due to cgroup issue

[Marek Stasiak]

So, this won't be fixed until https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/6565 is resolved? Or is it fixed in newer Ubuntu
releases? (On 22.04 I am experiencing the problem quite often, wondering
if there is any point in upgrading)

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

Title:
  [lunar] Snaps don't launch due to cgroup issue

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


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

[Bug 1960024] [NEW] Error while upgrading Ubuntu 18.04 LTS to 20.04 LTS

[Marek]

Public bug reported:

Please report this bug in a browser at
http://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+filebug
and attach the files in /var/log/dist-upgrade/ to the bug report.
E:Sub-process /usr/bin/dpkg returned an error code (1)

Errors during processing: initramfs-tools
Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an error 
code (1)
The update could not be installed

update-initramfs: Generating /boot/initrd.img-5.4.0-97-generic
Error 24 : Write error : cannot write compressed block
E: mkinitramfs failure lz4 -9 -l 24
update-initramfs: failed for /boot/initrd.img-5.4.0-97-generic with 1.

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

** Attachment added: "Upgrade log"
   
https://bugs.launchpad.net/bugs/1960024/+attachment/5559150/+files/dist-upgrade.zip

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

Title:
  Error while upgrading Ubuntu 18.04 LTS to 20.04 LTS

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


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

[Bug 1956844] [NEW] Missing library - libproj.so.19

[Marek ZJ]

Public bug reported:

*** This bug may be related to different package, but it gets visible
with digikam, so I put it here. ***

When starting digikam is trying to access libproj.so.19. This version is
not present in current system, as there is already a newer version
(libproj.so.22). This prevents the application from running.

The workaround is to make a symbolic link like that:

cd /usr/lib/x86_64-linux-gnu
sudo ln -s libproj.so.22.2.1 libproj.so.19

(or sudo ln -s libproj.so.22 libproj.so.19)

Afterwards digikam can be run normally.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: digikam 4:7.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
Uname: Linux 5.13.0-21-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu75
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sat Jan  8 23:42:45 2022
InstallationDate: Installed on 2018-11-13 (1152 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181113)
SourcePackage: digikam
UpgradeStatus: Upgraded to jammy on 2021-11-04 (65 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Missing library - libproj.so.19

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


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

[Bug 1949362] Re: gdalinfo returns undef_symbol

[Marek ZJ]

OK, this one seems to be fixed now. With latest libgdal updates, I have
no more this error.

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

Title:
  gdalinfo returns  undef_symbol

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


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

[Bug 1875642] Re: FSVS - not able to commit changes to remote HTTP SVN repo

[Ph. Marek]

I think I found the problem -- a double-open.

https://github.com/phmarek/fsvs/commit/f39cc00b3200bcd7874faf4de15479dfa3e6762a

No idea how the code got duplicated here, though - and the old (svn)
history is lost...

** Changed in: fsvs (Ubuntu)
   Status: Incomplete => Fix Committed

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

Title:
  FSVS - not able to commit changes to remote HTTP SVN repo

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


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

[Bug 994467] Re: fsvs update command not working

[Ph. Marek]

Sorry, I didn't know about FSVS bugs being sent to Launchpad.

I'm closing this here now; if you still need help, please open a github
issue. Thank you!

** Changed in: fsvs (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/994467

Title:
  fsvs update command not working

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


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

[Bug 1875642] Re: FSVS - not able to commit changes to remote HTTP SVN repo

[Ph. Marek]

Sorry, I only just now stumbled upon the launchpad bugs.

If that still persists, would you please send a debug log? Just run the
same "fsvs" command with "-d", and redirect into a file. Thank you!

** Changed in: fsvs (Ubuntu)
   Status: New => Incomplete

** Changed in: fsvs (Ubuntu)
 Assignee: (unassigned) => Ph. Marek (ph-marek)

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

Title:
  FSVS - not able to commit changes to remote HTTP SVN repo

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


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

[Bug 1949362] Re: gdalinfo returns undef_symbol

[Marek ZJ]

I have downloaded the latest version of the libgdal and I was able ylto
build I'd successfully on my machine. Tha is my current workaround for
running digkam. I can try a clean 21.10 installation, upgrade it to
22.04, then install digikam and confirm steps necessary to build libgdal
from sources.

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

Title:
  gdalinfo returns  undef_symbol

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


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

[Bug 1949362] Re: gdalinfo returns undef_symbol

[Marek ZJ]

The same error drops when starting digikam application, it tries to use
that failing library.

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

Title:
  gdalinfo returns  undef_symbol

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


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

[Bug 1749590] Re: [snap] All open windows are grouped under one single icon in the dock

[Marek Stasiak]

Snap version 7.2.1.2, problem still here. U20.04

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

Title:
  [snap] All open windows are grouped under one single icon in the dock

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


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

[Bug 1945125] [NEW] dss

[Marek]

Public bug reported:

sfsfsdfssdf

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: wl zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: fail
CasperVersion: 1.445.1
Date: Sun Sep 26 21:35:28 2021
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed quiet splash ---
LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu

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

Title:
  dss

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


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

[Bug 1943800] [NEW] the chezscheme-doc package is not working!! (doc in the scheme repl is not recognized. Neither does (import (chez-docs)) work

[Marek Owsikowski]

Public bug reported:

the chezscheme-doc package is not working!!  (doc in the scheme repl is
not recognized. Neither does (import (chez-docs)) work

> (doc "append")
Exception: variable doc is not bound

> doc
Exception: variable doc is not bound

> (import (chez-docs))
Exception: library (chez-docs) not found


But chezscheme9.5-doc is installed. I also don;t get why I can't choose here:
"chezscheme9.5-doc" does not exist in Ubuntu. Please choose a different 
package. If you're unsure, please select "I don't know"

The package name is:
chezscheme9.5-doc/focal,now 9.5+dfsg-6 all [installed]

I did install every chezscheme package

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

** Attachment added: "222.png"
   https://bugs.launchpad.net/bugs/1943800/+attachment/5525574/+files/222.png

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

Title:
  the chezscheme-doc package is not working!!  (doc in the scheme repl
  is not recognized. Neither does (import (chez-docs)) work

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


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

[Bug 1924608] [NEW] package speedtest-cli (not installed) failed to install/upgrade: próba nadpisania "/usr/bin/speedtest", który istnieje także w pakiecie speedtest 1.0.0.2-1.5ae238b

[Marek Andrearczyk]

Public bug reported:

after test, and when i close terminal i get error

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: speedtest-cli (not installed)
ProcVersionSignature: Ubuntu 5.8.0-49.55~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 speedtest-cli:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 15 22:13:33 2021
DpkgTerminalLog:
 Przygotowywanie do rozpakowania pakietu .../speedtest-cli_2.1.2-2_all.deb ...
 Rozpakowywanie pakietu speedtest-cli (2.1.2-2) ...
 dpkg: błąd przetwarzania archiwum 
/var/cache/apt/archives/speedtest-cli_2.1.2-2_all.deb (--unpack):
  próba nadpisania "/usr/bin/speedtest", który istnieje także w pakiecie 
speedtest 1.0.0.2-1.5ae238b
ErrorMessage: próba nadpisania "/usr/bin/speedtest", który istnieje także w 
pakiecie speedtest 1.0.0.2-1.5ae238b
InstallationDate: Installed on 2021-04-15 (0 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: speedtest-cli
Title: package speedtest-cli (not installed) failed to install/upgrade: próba 
nadpisania "/usr/bin/speedtest", który istnieje także w pakiecie speedtest 
1.0.0.2-1.5ae238b
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: speedtest-cli (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/1924608

Title:
  package speedtest-cli (not installed) failed to install/upgrade: próba
  nadpisania "/usr/bin/speedtest", który istnieje także w pakiecie
  speedtest 1.0.0.2-1.5ae238b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/speedtest-cli/+bug/1924608/+subscriptions

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

[Bug 1918849] Re: crash installer, download resources ...

[Marek Kopal]

I can probably just describe the problem, (maybe I'll help at least a
little), or hide or delete the report right away, or ask, it's up to you
and I'm sorry, the first report didn't work with me at all = (

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

Title:
  crash installer, download resources ...

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

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

[Bug 1918849] Re: crash installer, download resources ...

[Marek Kopal]

logs probably aren't there anymore, I won't run the installation again,
I'm glad I deleted ubuntu, there was an error at the end of the
installation, it's Ubuntu version 20.10, drivers were probably being
downloaded or something ...

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

Title:
  crash installer, download resources ...

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

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

[Bug 1918849] Re: crash installer, download resources ...

[Marek Kopal]

I thought logs were sent ...

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

Title:
  crash installer, download resources ...

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

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

[Bug 1914759] [NEW] package mysql-client-core-8.0 8.0.23-0ubuntu0.20.10.1 failed to install/upgrade: nie można skopiować wypakowanych danych "./usr/bin/mysqlcheck" do "/usr/bin/mysqlcheck.dpkg-new": n

[Marek Zientek]

Public bug reported:

Wywala co jaki s czas błąd klienta SQL.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: mysql-client-core-8.0 8.0.23-0ubuntu0.20.10.1
ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18
Uname: Linux 5.8.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
AptOrdering:
 mysql-client-core-8.0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Feb  2 16:00:04 2021
ErrorMessage: nie można skopiować wypakowanych danych "./usr/bin/mysqlcheck" do 
"/usr/bin/mysqlcheck.dpkg-new": niespodziewany koniec pliku lub strumienia
InstallationDate: Installed on 2021-01-30 (5 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLVarLibDirListing: ['#ib_16384_0.dblwr', 'server-key.pem', 
'marek-Ubuntu-dev.pid', 'binlog.04', 'ibtmp1', 'mysql.ibd', 
'binlog.07', 'ib_logfile1', 'mysql', 'undo_002', 'binlog.09', 
'public_key.pem', 'client-key.pem', 'binlog.index', 'ibdata1', 'binlog.01', 
'ib_logfile0', 'binlog.08', '#ib_16384_1.dblwr', 'auto.cnf', 
'private_key.pem', 'performance_schema', 'mysql_upgrade_info', 'binlog.02', 
'ca.pem', 'debian-5.7.flag', 'binlog.05', 'client-cert.pem', 'undo_001', 
'#innodb_temp', 'binlog.06', 'ca-key.pem', 'sys', 'server-cert.pem', 
'binlog.03', 'ib_buffer_pool']
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic 
root=UUID=ce0bdc40-d1c4-4fce-b85d-7095799afcd9 ro quiet splash vt.handoff=7
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.10ubuntu0.2
SourcePackage: mysql-8.0
Title: package mysql-client-core-8.0 8.0.23-0ubuntu0.20.10.1 failed to 
install/upgrade: nie można skopiować wypakowanych danych "./usr/bin/mysqlcheck" 
do "/usr/bin/mysqlcheck.dpkg-new": niespodziewany koniec pliku lub strumienia
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: mysql-8.0 (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/1914759

Title:
  package mysql-client-core-8.0 8.0.23-0ubuntu0.20.10.1 failed to
  install/upgrade: nie można skopiować wypakowanych danych
  "./usr/bin/mysqlcheck" do "/usr/bin/mysqlcheck.dpkg-new":
  niespodziewany koniec pliku lub strumienia

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

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

[Bug 1908223] [NEW] nmap 7.80 crashes with Assertion `htn.toclock_running == true'

[Marek Piechaczek]

Public bug reported:

nmap version 7.80 crashes on Ubuntu 20.04 LTS:

$ sudo nmap -n 192.168.1.223/24

  Starting Nmap 7.80 ( https://nmap.org ) at 2020-12-15 09:18 CET
  nmap: Target.cc:503: void Target::stopTimeOutClock(const timeval*): Assertion 
`htn.toclock_running 
  == true' failed.
  Aborted

Issue was reported in nmap github repository:
- https://github.com/nmap/nmap/issues/1797
- https://github.com/nmap/nmap/issues/1764

Issue is fixed since nmap 7.90 by following commit:
- https://github.com/nmap/nmap/commit/33f421fd6e68fcb8ed50071661d9704717c81b2b

Please integrate aboce change into nmap releaseon Ubuntu 20.04 LTS or
upgrade nmap to newer version

** Affects: nmap
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: github.com/nmap/nmap/issues #1764
   https://github.com/nmap/nmap/issues/1764

** Also affects: nmap via
   https://github.com/nmap/nmap/issues/1764
   Importance: Unknown
   Status: Unknown

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

Title:
  nmap 7.80 crashes with  Assertion `htn.toclock_running == true'

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

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

[Bug 1893857] Re: Dmenu crashes when typig

[Vladimir Marek]

I have downloaded and compiled dmenu 5.0 and that solves the issue. I
believe that the upstream bug is https://bugs.archlinux.org/task/61673.

So kindly please update dmenu .

Thank you

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

Title:
  Dmenu crashes when typig

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

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

[Bug 1897784]

[Jan-Marek Glogowski]

(In reply to Olivier Tilloy from comment #8)
> This bug looks similar to
> https://bugs.documentfoundation.org/show_bug.cgi?id=131083

Nice find. Summary of bug 131083:

Happened reproducible for the user with LO Ubuntu build 6.4.0-0ubuntu7
and LO Tinderbox build 45ca47ac39c03df4de52d627a764f16068b1eab0
(7.0.0.0.alpha0+ is reported for all development builds before branch
off / alpha1 / beta) and just with kf5 in KDE / Plasma 2, not with
Xubuntu (Xfce? which VCL in About? I would assume gtk3). Happens with
the empty / default document.

Bug 131083 comment 13 states: "I'm testing both Kubuntu and Xubuntu in a
VM environment (VirtualBox 6.1.4)."

You can get a comparable (but not equal!) build to the Tinderbox one via
https://bibisect.libreoffice.org/linux-64-7.0 commit
fc089b4dda133f1fd03922b713708e53af6c16fa.

Reproduce:

1. start Calc
2. mark F10/11 vertically
3. exit LO
4. choose not to save

Questions for each point (which might be related or not):

1. How is Calc started? Desktop link, command line (which one?), via start 
center? Does it happen with non-default profile via  
-env:UserInstallation=file:///tmp/test?
2. How are the cells marked? Mouse only, keyboard? Which cell first? Does it 
crash with other cells?
3. Exit crash just happens via window decorations? Or also via menu? Or by 
using Alt+F4 or Ctrl+Q? Or also by closing the Calc document and then the start 
center?
4. Why does Calc think the document was modified?

Point 4 is AFAIK already exposing the real bug.

General question: any additional output in a terminal? New entries in 
~/.xsession-errors?
Is this just happening with the localized KDE (the reporter uses de-DE.UTF-8)?

An other eventually related crash I found (fixed?) is bug 131533 in LO
6.4.4. The implemented fix / patch is just a workaround, as I couldn't
come up with a minimal reproducer without LO. There are some additional
comments (see last ones) with info in
https://gerrit.libreoffice.org/c/core/+/90990.

According to bug 131083 comment 15, an old LO profile doesn't seem to be the 
cause of this, as the crash could be reproduced after deleting the profile. 
Since it didn't crash with the first try, it still might somehow be related. 
Would still be nice to get a known crashing profile for testing / reference, in 
the case there is some setting in it, leading to the crash.
Bug 131083 comment 26 states the problem to reproduce the bug. "Made the 
installed DEB packages identical" I guess just means the package list, like 
"dpkg --get-selections", not the exact versions.

An other bug that just comes to my mind and which was actually fixed for
6.4.0 is bug 104717. That changes the selection / clipboard handling in
Calc. Quoting from my commit message: "Calc also removes the system
selection when clearing the selection. Other applications keep the
primary selection valid, until the application or document closes, so do
the same in Calc." So maybe this introduces some case, where the primary
selection isn't correctly cleared on shutdown. This is not KDE specific,
but the QClipboard handling / API is very different from either Gtk+ or
X11, so there might be some broken case now, where we don't clean the
selection on module shutdown.

Can you see, if the Kubuntu crashes happen on KDE shutdown, AKA session
management related?

> In the errors.ubuntu.com tracker, the earliest version exhibiting the crash
> is 6.4.3, and there are new reports daily with 6.4.6.

The thing we definitely know is that the LO 1:6.4.6-0ubuntu0.20.04.1
build in combination with KDE makes the crash much more likely. It seems
the original bug is older.

Still we don't have any reproducer, just a huge amount of reported
crashes from Kubuntu users.

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions

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

[Bug 1897784]

[Jan-Marek Glogowski]

FWIW: I have installed Ubuntu's LO 6.4.6 in my focal schroot. I'm
running Debian Buster with KDE on the host in X11. I couldn't produce
any crash with the LO in the chroot, doing Calc selections and copy and
paste operations, D'n'D and also some external copy actions.

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions

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

[Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

[Marek Wasenczuk]

Thank you Webmaster4362. However cannot access the cups web interface
"http://localhost:361; !! Any suggestions?

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

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

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

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

[Bug 1881401] Re: HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its package base

[Marek Wasenczuk]

Have recently changed from Ubuntu 18.04 to 20.04. Tried printing on my
HP DeskJet 3630 All in One Series printer and cannot print - keep
getting 'Device communication error'. Running 'hp-doctor'shows missing
dependencies the same as reported by Norbert:

Missing Required Dependencies
-
error: 'libcups2' package is missing or 'cups' service is not running.
error: 'python3-pyqt4' package is missing/incompatible
error: 'gtk2-engines-pixbuf' package is missing/incompatible
Missing Optional Dependencies
-
error: 'python3-dbus.mainloop.qt' package is missing/incompatible

Need help to resolve this. Am NOT an expert in using the terminal. Need
clear instructions PLEASE.

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

Title:
  HPLIP, hp-doctor, hp-check should support Ubuntu 20.04 LTS with its
  package base

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

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

[Bug 1897784]

[Jan-Marek Glogowski]

Created attachment 165976
rhbz#1847031 cleaned crash bt

That whole bt looks broken. RH has no reproducer either, so the fix is
just a guess. Version was libreoffice-6.4.4.2-2.fc32.x86_64, as you can
see in the bt paths.

The bt itself looks "wrong". The user did a right-click on a Calc cell,
that would open the context menu, but at that point, when the Gtk event
is processed, a lot more stuff is already "gone", like all the aGuard
objects have nullptr, so no mutex in them. So I guess this is just for
reference, but won't help.

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions

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

[Bug 1897784]

[Jan-Marek Glogowski]

No. (In reply to Michael Weghorn from comment #2)
> The only relatively recent commit related to QMimeData handling (i.e. mostly
> copy & paste and drag'n'drop) is the fix for tdf#131533, but that fix is in
> 6.4.4 already.
> 
> @jmux: Any ideas?

We know the fix for tdf#131533 is rather fishy and more of a workaround,
then a real fix. But if we have the same backtraces before 6.4.4 (and I
checked that libreoffice_6.3.3-0ubuntu1.debian.tar.xz doesn't carry that
fix), we can - kind of - rule that out. Also all the backtraces just
indicate Calc (ScSelectionTransferObj), not any other LO modules (at
least Writer), which is strange. Maybe an active selection in Calc is
just more common on shutdown, then in other applications? OTOH a copy in
Calc keeps the selection, even if you move the "cursor rectangle". There
is also nothing suspicious new on
https://crashreport.libreoffice.org/stats/version/6.4.6.2

And the only "fix" in vcl/qt5 between 6.4.2 and 6.4.3 is commit
1000169ebca79478a05b4c23e760d99bd77e739e ("Qt5 unify font attribute
conversions"), which I would also rule out as the origin of any bug
(famous last words).

There is also no other fix in vcl/ or sc/ since commit
cbac26c52ccbe59c51c6631cb8c4b0a314a9848a / 6.4.0, which looks suspicious
at all w.r.t. the backtrace at a first glance. And the whole lazy
clipboard stuff was already in 6.3. And your fix for tdf#129809 was
already in 6.4.2.

Still nothing would explain the current peak, I can see in
https://errors.ubuntu.com since
https://errors.ubuntu.com/?release=Ubuntu%2020.04=libreoffice-
core=2020-08-24=2020-09-25, which matches the publishing date
from
https://launchpad.net/ubuntu/+source/libreoffice/1:6.4.6-0ubuntu0.20.04.1
.

So I checked the diff of the 6.4.6 fix range for sc and interestingly it
contains commit 8718d243edc9400b0e0131b096702af8d33df327 (rhbz#1847031
null-deref), which fixes a null-deref in ~ScTransferOb. That should
really just fix a bug, not cause one, but eventually this just papers-
over some real bug in the other fixes, which now hits Qt in some way.
Because ScTransferObj is part of libsclo, which can't exists with
"pScMod == nullptr".

$ git log --pretty=oneline 
f2e448175cee92fc695413e7281223e9f23e30ee~1..origin/libreoffice-6-4-6 | wc -l
123

Now I really would like to have a reproducer, which eventually should
also happen on master... and tdf#130559 is the only additional thing in
sc that looks strange, but that's just 17 out of the 123 patches.

Someone from Kubuntu could "mine" the crash reports, if there is
anything reproducible in it. And I have to get the RHEL bug report from
someone (Caolan, eventually).

So while I first suspected something non-LO, it now smells like a LO
bug, independent of VCL, evetually.

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions

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

[Bug 1897784]

[Jan-Marek Glogowski]

Created attachment 165978
Kubuntu shutdown crash bt

It appears that one can just DL the text with a Launchpad login. So this
is just a copy from the BT as reference. For whatever reason the
clipboard object is still active, while the module is already gone,
which is causing the crash.

An other question is, what other packages were published that day, just
in the case it's eventually no LO bug (I still think it is).

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

Title:
  
/usr/lib/libreoffice/program/soffice.bin:11:ScSelectionTransferObj::~ScSelectionTransferObj:ScSelectionTransferObj::~ScSelectionTransferObj:com::sun::star::uno::Reference:Qt5MimeData::~Qt5MimeData:Qt5MimeData::~Qt5MimeData

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1897784/+subscriptions

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

[Bug 1895299] Re: Wrong scaling factor after reboot

[Marek Frydrysiak]

** Attachment added: "Screenshot after reboot"
   
https://bugs.launchpad.net/ubuntu/+bug/1895299/+attachment/5410121/+files/Screenshot%20after%20reboot.png

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

Title:
  Wrong scaling factor after reboot

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

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

[Bug 1895299] Re: Wrong scaling factor after reboot

[Marek Frydrysiak]

** Attachment added: "Screenshot after rescalling from 1.00 to 0.99 back to 
1.00"
   
https://bugs.launchpad.net/ubuntu/+bug/1895299/+attachment/5410122/+files/Screenshot%20after%20rescalling%201_00-0_99-1_00.png

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Wrong scaling factor after reboot

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

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

[Bug 1895299] [NEW] Wrong scaling factor after reboot

[Marek Frydrysiak]

Public bug reported:

After reboot I can see wrong scaling factor for icons, etc., although
after opening Gnome Tweaks -> Fonts, I can verify that the Scaling
Factor is set to 1,00. Changing it (by '+' or '-') to 1,01 or 0,99 and
back to 1,00 recovers proper scaling.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Sep 11 15:34:09 2020
DistUpgraded: 2020-05-20 22:32:35,149 DEBUG icon theme changed, re-reading
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.4.0-45-generic, x86_64: installed
 nvidia, 435.21, 5.4.0-47-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-45-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-47-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297]
InstallationDate: Installed on 2020-04-02 (162 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: LENOVO 20QNS17N00
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-47-generic 
root=/dev/mapper/ubuntu--vg-root ro psmouse.elantech_smbus=0 nouveau.modeset=0 
quiet splash max_loop=64 vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-05-20 (113 days ago)
dmi.bios.date: 06/04/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2NET38W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QNS17N00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:svnLENOVO:pn20QNS17N00:pvrThinkPadP53:rvnLENOVO:rn20QNS17N00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P53
dmi.product.name: 20QNS17N00
dmi.product.sku: LENOVO_MT_20QN_BU_Think_FM_ThinkPad P53
dmi.product.version: ThinkPad P53
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal fonts ubuntu

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

Title:
  Wrong scaling factor after reboot

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

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

[Bug 1738774]

[Jan-Marek Glogowski]

This is the typical chicken-egg problem: LO's SVG rasterizer / icons
broken => default to PNG. Everybody uses PNG (and some complain about
blocky icons in HiDPI) => nobody fixes the LO's SVG rasterizer / icons.
Some more background info is in bug 133877 comment 11.

And OTOH people can manually select an SVG icon set, so the pressure to
fix this isn't really high.

While the SVG icons easily look better when scaled, the PNG icons
definitely look better in 100% / non-scaled in Linux.

And it also doesn't help that gtk3 always scales the rasterized icons,
so you get the worse 100% SVG icons scaled to HiDPI.

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

Title:
  Pixeled icons with LibreOffice 5.1.6.2 on HiDPI/4K display

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1738774/+subscriptions

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

[Bug 1881882] Re: check_ide_smart failed

[Marek]

You're right, now I see that the suid bit is set not in 
monitoring-plugins-basic package but by my "configuration manager".
Without suid bit icinga reports "Couldn't open device /dev/sda: Acces denied"
Thanks for help

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

Title:
  check_ide_smart failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1881882/+subscriptions

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

[Bug 1881882] [NEW] check_ide_smart failed

[Marek]

Public bug reported:

Sticky bit is missing on the latest version (2.2-3ubuntu3):
ls -l /usr/lib/nagios/plugins/check_ide_smart
-rwxr-xr-x 1 root root 47728 maj  2 08:35 
/usr/lib/nagios/plugins/check_ide_smart

should be:
ls -l /usr/lib/nagios/plugins/check_ide_smart
-rwsr-sr-x 1 root root 47728 lut  6  2018 
/usr/lib/nagios/plugins/check_ide_smart

** Affects: monitoring-plugins (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/1881882

Title:
  check_ide_smart failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/monitoring-plugins/+bug/1881882/+subscriptions

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

[Bug 1879385] Re: Unable to star files and folders in Dropbox folder in Ubuntu 20.04

[Marek Lichtner]

After Dropbox is installed, it creates folder "{homedir}/Dropbox," and
all files are synchronized from your dropbox account. So before it,
there is no Dropbox folder in your home dir. I did not test it before
Dropbox was installed, but I guess there will be no problem to star this
file.

Now I checked my dropbox account; there is also feature to star files.
Maybe there is a conflict between dropbox and nautilus star
functionality.

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

Title:
  Unable to star files and folders in Dropbox folder in Ubuntu 20.04

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

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

[Bug 1879385] ProcCpuinfoMinimal.txt

[Marek Lichtner]

apport information

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

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

Title:
  Unable to star files and folders in Dropbox folder in Ubuntu 20.04

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

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

[Bug 1879385] Re: Unable to star files and folders in Dropbox folder in Ubuntu 20.04

[Marek Lichtner]

apport information

** Tags added: apport-collected third-party-packages

** Description changed:

- It is impossible to star files or folder inside Dropbox folder. There is
- no menu in Nautilus after right click on file. Outside the Dropbox
- folder it works fine. I am not sure if it is bug of Dropbox extension or
- Nautilus.
+ It is impossible to star files or folder inside Dropbox folder. There is no 
menu in Nautilus after right click on file. Outside the Dropbox folder it works 
fine. I am not sure if it is bug of Dropbox extension or Nautilus.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu27
+ Architecture: amd64
+ CasperMD5CheckResult: skip
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 20.04
+ GsettingsChanges:
+  b'org.gnome.nautilus.window-state' b'initial-size' b'(1018, 689)'
+  b'org.gnome.nautilus.preferences' b'click-policy' b"'single'"
+  b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
+  b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
+ InstallationDate: Installed on 2020-04-25 (23 days ago)
+ InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
+ Package: nautilus 1:3.36.1.1-1ubuntu2
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
+ Tags: third-party-packages focal
+ Uname: Linux 5.4.0-29-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ usr_lib_nautilus: dropbox 2020.03.04

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

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

Title:
  Unable to star files and folders in Dropbox folder in Ubuntu 20.04

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

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

[Bug 1879385] ProcEnviron.txt

[Marek Lichtner]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1879385/+attachment/5373953/+files/ProcEnviron.txt

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

Title:
  Unable to star files and folders in Dropbox folder in Ubuntu 20.04

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

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

[Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

[Marek]

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

Same with me, problem showed up after upgrading from 19.04 version.

Uncommenting lines mentioned in #13 did not work for me (ASUS UX301L).

Extremely annoying.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

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

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

[Bug 1847333] [NEW] Installer crashes during installation

[Vladimir Marek]

Public bug reported:

I have tried to install ubuntu on zfs partition. I have enabled
downloading of updates and binary drivers during the installation. I saw
that the installer is setting locales and shortly after that it
disappeared and I got crash notification.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubiquity 19.10.15
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
Date: Tue Oct  8 21:28:12 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
only-ubiquity quiet splash ---
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan ubiquity-19.10.15 ubuntu

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

Title:
  Installer crashes during installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847333/+subscriptions

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

[Bug 1840708] Re: HP Envy with AMD Ryzen 5 2500U processor hangs on boot

[Marek Bajon]

I would try if you explained what the "reverse bisection" is :).
By the way - the signed ubuntu kernel 5.2.0-10 also works correctly with my 
laptop. Will it be provided in ubuntu 18.04.4? If so - maybe there's no point 
in fixing kernel 5.0.0...

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

Title:
  HP Envy with AMD Ryzen 5 2500U processor hangs on boot

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

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

[Bug 1840708] Re: HP Envy with AMD Ryzen 5 2500U processor hangs on boot

[Marek Bajon]

No, not similar. I get no messages on the screen. And the messages
recorded by the other user seem different from messages which I can see
in my syslog file. In my case the computer is not completely dead (there
are messages in the syslog file which confirm that e.g. WiFi connection
is activated), only the display is dead.

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

Title:
  HP Envy with AMD Ryzen 5 2500U processor hangs on boot

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

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

[Bug 1840708] Re: HP Envy with AMD Ryzen 5 2500U processor hangs on boot

[Marek Bajon]

An unsigned kernel 5.2.8 (installed with UKUU) boots correctly, too.

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

Title:
  HP Envy with AMD Ryzen 5 2500U processor hangs on boot

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

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

[Bug 1840708] [NEW] HP Envy with AMD Ryzen 5 2500U processor hangs on boot

[Marek Bajon]

Public bug reported:

Ubuntu 18.04.3, kernel 5.0.0-25-generic
When grub menu disappears, the screen remains blank.

I include a syslog file from a failed boot. The important part is at line 1175:
irq 7: nobody cared (try booting with the "irqpoll" option)

This laptop boots correctly with the 4.18 kernel.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amdgpu

** Attachment added: "syslog file"
   https://bugs.launchpad.net/bugs/1840708/+attachment/5283373/+files/syslog.ERR

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

Title:
  HP Envy with AMD Ryzen 5 2500U processor hangs on boot

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

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

Re: [Bug 1836051] Re: autamatic sleep notification cannot close

[Marek Mikula]

all right guis. I put my pc to sleep mode , not to Turn off. Attachment
,Notification in the middle is not goin to dissapear..

st 10. 7. 2019 o 17:01 Gunnar Hjalmarsson <1836...@bugs.launchpad.net>
napísal(a):

> ** Package changed: ubuntu-docs (Ubuntu) => gnome-control-center
> (Ubuntu)
>
> ** Changed in: gnome-control-center (Ubuntu)
>Status: Invalid => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1836051
>
> Title:
>   autamatic sleep notification cannot close
>
> Status in gnome-control-center package in Ubuntu:
>   New
>
> Bug description:
>   I put my computer to sleep mode. 4 hours set afer no use. Vhen
>   notification appeared, I put comp to sleep. After woke up,
>   notification is still and can not close thru X. ubuntu-bug 18.04.2
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1836051/+subscriptions
>


** Attachment added: "IMG_8952.JPG"
   
https://bugs.launchpad.net/bugs/1836051/+attachment/5276501/+files/IMG_8952.JPG

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

Title:
  autamatic sleep notification cannot close

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

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

Re: [Bug 1836051] Re: autamatic sleep notification cannot close

[Marek Mikula]

wery funny

st 10. 7. 2019 o 13:40 lotuspsychje  napísal(a):

> Please use ubuntu-bug packagename to file a bug against the correct package
> the package you chosen now is ubuntu-docs (the help manual) and is not
> related
> to sleep or suspend.
>
> ** Changed in: ubuntu-docs (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1836051
>
> Title:
>   autamatic sleep notification cannot close
>
> Status in ubuntu-docs package in Ubuntu:
>   Invalid
>
> Bug description:
>   I put my computer to sleep mode. 4 hours set afer no use. Vhen
>   notification appeared, I put comp to sleep. After woke up,
>   notification is still and can not close thru X. ubuntu-bug 18.04.2
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1836051/+subscriptions
>

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

Title:
  autamatic sleep notification cannot close

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

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

[Bug 1836051] [NEW] autamatic sleep notification cannot close

[Marek Mikula]

Public bug reported:

I put my computer to sleep mode. 4 hours set afer no use. Vhen
notification appeared, I put comp to sleep. After woke up, notification
is still and can not close thru X. ubuntu-bug 18.04.2

** Affects: ubuntu-docs (Ubuntu)
 Importance: Undecided
 Status: Invalid

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

Title:
  autamatic sleep notification cannot close

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

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

[Bug 1365296] Re: No 'recent' files shown until a file is opened (due to gmenumodel changes)

[Marek Blahuš]

This bug has been assigned to Lars Karlitski. I don't know him, but he
seems to last have been active here back in 2016. Could that possibly be
blocking the progress in this issue?

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

Title:
  No 'recent' files shown until a file is opened (due to gmenumodel
  changes)

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

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

[Bug 1365296] Re: No 'recent' files shown until a file is opened (due to gmenumodel changes)

[Marek Blahuš]

Evince 3.32.0 in Ubuntu 19.04:

Grid with recent files is shown when opening the viewer.

When already viewing a document, one must choose "New window" from the
single menu to open that "Recent documents" grid (and be able to choose
from there). I had long been unaware of that, because I either press
Ctrl+O for Open…, or I look in the menu for "Recent documents". In my
opinion, the "New window" approach is wrong for several reasons:

1. It is non-standard (new window in GEdit or Firefox is empty until you
open a document in it; new documents are empty; opening an existing
document is called "Open", not "New").

2. It adds an extra step for such a frequent task as Open… (need to
choose "New window", then locate the "Open…" button in that grid window,
navigate to it and click it).

3. It has no keyboard shortcut linked with it. Although I can and do use
Ctrl+O to go to directly to the Open… dialog, there is no shortcut for
"New window", so I can't access recent files by keyboard.

I suggest putting "Open…" and "Open recent" (with a submenu) back into
the application's menu again.

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

Title:
  No 'recent' files shown until a file is opened (due to gmenumodel
  changes)

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

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

[Bug 1815889]

[Marek Olšák]

(In reply to Michel Dänzer from comment #8)
> Mesa doesn't really need explicit thread affinity at all. All it wants is
> that certain sets of threads run on the same CPU module; it doesn't care
> which particular CPU module that is. What's really needed is an API to
> express this affinity between threads, instead of to specific CPU cores.

I think the thread affinity API is a correct way to optimize for CPU
cache topologies. pthread is a basic user API. Security policies
shouldn't disallow pthread functions.

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

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

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

[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Marek Hák]

Oh my god it worked!!! Thank you thank you thank you!!! My laptop has
been like this for a year and it's fixed now! Thank you again so much
for your help :-) I'm so incredibly happy

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

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

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

[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Marek Hák]

The output of 'efibootmgr -v' showed me where the EFI partition is, but
I have no idea where it's mounted or how to get to it.

Boot0004* ubuntuHD(2,GPT,83484852-541d-401e-
84e7-6e6e8549496a,0x1f4800,0x82000)/File(\EFI\ubuntu\shimx64.efi)

Some info that may help:

I do not have the current ubuntu installed on the hard drive itself,
it's installed on a flash drive. My old grub got corrupted or partially
deleted, so now I only have the minimal-bash editing grub. I boot from
the flash drive with:

set prefix=(hd0,msdos2)/boot/grub/
set root=(hd0,msdos2)
insmod normal
normal

After that, I get into a normal grub, that's probably located somewhere
on the flash drive.

The ubuntu on the flash drive was installed on another computer, and
just brought over to the laptop.

Thanks again for any help! I'd really love to sort this out :)

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

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

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

[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Marek Hák]

Thanks for the help Mathieu, however, it sadly did not solve the issue.
There was no /efi direcory in my /boot. I still tried to create the
directories you told me to copy it into, but that didn't work. Is it
possible I have a non-UEFI version of ubuntu?

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

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

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

[Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

[Marek Hák]

Hi, I have this exact issue, and I got to step 5, but secure boot is
preventing me from booting the new kernel, because it is unsigned. Is
there a signed version of it, or can I force it to boot from it somehow?
Thank you.

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

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

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

[Bug 1812101]

[Jan-Marek Glogowski]

FYI KDE4 used to have its own auto-extension checkbox in the file open
dialog, so the LO KDE4 integration used that KDE setting and skipped
LOs' own handling. Probably that setting doesn't exist anymore, as file
dialogs are now Qt5 based and now LO has to handle the file auto-
extension on its own.

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

Title:
  libreoffice-kde5 file dialog/picker doesn't add extension
  automatically

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1812101/+subscriptions

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

[Bug 1798861] Re: Tooltips flicker constantly in GTK3 applications

[Jan-Marek Glogowski]

** Bug watch added: Debian Bug tracker #911148
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148

** Also affects: hash-it via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911148
   Importance: Unknown
   Status: Unknown

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

Title:
  Tooltips flicker constantly in GTK3 applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/hash-it/+bug/1798861/+subscriptions

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

[Bug 1803316] Re: VPN connection is stopped

[Marek Tenus]

It works with 18.04 and does not work with 16.04
It connects with other gates of VPN provider but not with this one I have set.

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

Title:
  VPN connection is stopped

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

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

[Bug 1803316] Re: VPN connection is stopped

[Marek Tenus]

VPN provider wrote to me that everything is ok on their side.

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

Title:
  VPN connection is stopped

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

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

[Bug 1803316] Re: VPN connection is stopped

[Marek Tenus]

Hi,

I install each new update/upgrade. VPN works if my mate uses it using MacOS.
VPN does not work with Ubuntu 18.04 and 16.04 (only this OS I use). I've 
checked it in two different networks.
I used every possible setting using NetworkManager.
I've checked each possible solutions using StackOverflow.

I did not check VPN connection using other VPN.
I wrote the question to VPN's provider if they can check it out this issue.

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

Title:
  VPN connection is stopped

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

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

[Bug 1803316] [NEW] VPN connection is stopped

[Marek Tenus]

Public bug reported:

>From a few days I cannot connect via VPN, It worked from a few months

*sudo apt policy network-manager*

network-manager:
  Installed: 1.2.6-0ubuntu0.16.04.3
  Candidate: 1.2.6-0ubuntu0.16.04.3
  Versions:
 *** 1.2.6-0ubuntu0.16.04.3 500
500 http://ftp.agh.edu.pl/ubuntu xenial-updates/main amd64 Packages
500 http://ftp.agh.edu.pl/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status
 1.1.93-0ubuntu4 500
500 http://ftp.agh.edu.pl/ubuntu xenial/main amd64 Packages


*/var/sys/log*


Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8520] audit: 
op="connection-activate" uuid="3872fc1d-94ce-465e-8d52-7bbeb3eb72fe" name="HS 
VPN" pid=13561 uid=1000 result="success"
Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8706] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: 
Started the VPN service, PID 2396
Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.8815] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: Saw 
the service appear; activating connection
Nov 14 10:46:07 hs NetworkManager[1081]:   [1542188767.9989] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
connection: (ConnectInteractive) reply received
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: pppd started with pid 2405
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0148] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: starting (3)
Nov 14 10:46:08 hs pppd[2405]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Nov 14 10:46:08 hs NetworkManager[1081]: Plugin 
/usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(plugin_init): initializing
Nov 14 10:46:08 hs pppd[2405]: pppd 2.4.7 started by root, uid 0
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 3 / phase 'serial connection'
Nov 14 10:46:08 hs NetworkManager[1081]: nm_device_get_device_type: assertion 
'NM_IS_DEVICE (self)' failed
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0226] manager: 
(ppp0): new Generic device (/org/freedesktop/NetworkManager/Devices/47)
Nov 14 10:46:08 hs pptp[2411]: nm-pptp-service-2396 log[main:pptp.c:350]: The 
synchronous pptp option is NOT activated
Nov 14 10:46:08 hs pppd[2405]: Using interface ppp0
Nov 14 10:46:08 hs NetworkManager[1081]: Using interface ppp0
Nov 14 10:46:08 hs pppd[2405]: Connect: ppp0 <--> /dev/pts/22
Nov 14 10:46:08 hs NetworkManager[1081]: Connect: ppp0 <--> /dev/pts/22
Nov 14 10:46:08 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 5 / phase 'establish'
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0391] devices 
added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Nov 14 10:46:08 hs NetworkManager[1081]:   [1542188768.0392] device added 
(path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration 
found.
Nov 14 10:46:39 hs pppd[2405]: LCP: timeout sending Config-Requests
Nov 14 10:46:39 hs NetworkManager[1081]: LCP: timeout sending Config-Requests
Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 11 / phase 'disconnect'
Nov 14 10:46:39 hs NetworkManager[1081]: Connection terminated.
Nov 14 10:46:39 hs pppd[2405]: Connection terminated.
Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: Terminated ppp daemon with 
PID 2405.
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0566] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: failed: connect-failed (1)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0577] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopping (5)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0579] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state changed: stopped (6)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0680] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
plugin: state change reason: unknown (0)
Nov 14 10:46:39 hs NetworkManager[1081]:   [1542188799.0802] 
vpn-connection[0x134c1c0,3872fc1d-94ce-465e-8d52-7bbeb3eb72fe,"HS VPN",0]: VPN 
service disappeared
Nov 14 10:46:39 hs NetworkManager[1081]: ** Message: nm-pptp-ppp-plugin: 
(nm_phasechange): status 1 / phase 'dead'
Nov 14 10:46:39 hs NetworkManager[1081]: Terminating on signal 15
Nov 14 10:46:39 hs NetworkManager[1081]: Modem hangup
Nov 14 10:46:39 hs pppd[2405]: Terminating on signal 15
Nov 14 10:46:39 hs pppd[2405]: Modem hangup
Nov 14 10:46:39 hs pptp[2291]: nm-pptp-service-2215 
log[pptp_read_some:pptp_ctrl.c:593]: read error: Bad file descriptor
Nov 14 10:46:39 hs kernel: [ 5539.540135] pptpcm[2291]: segfault at 
7f069f3a87b8 ip 00406a87 sp 

[Bug 1772451]

[Jan-Marek Glogowski]

Created attachment 145298
Just an example image from master build

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

Title:
  Diacritical marks become visible only after changing view in Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772451/+subscriptions

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

[Bug 1772451]

[Jan-Marek Glogowski]

That image is from todays master…

And yes - those two selections is just one done with a single cursor.

Probably this should have been a new bug…

Version: 6.2.0.0.alpha0+
Build-ID: b0eab4b2d2761139ecf5191252dfa8005cd29508
CPU-Threads: 64; BS: Linux 3.16; UI-Render: Standard; VCL: x11; 
Gebietsschema: de-DE (de_DE.UTF-8); Calc: threaded

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

Title:
  Diacritical marks become visible only after changing view in Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772451/+subscriptions

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

[Bug 1772451]

[Jan-Marek Glogowski]

Created attachment 145299
The example document used for the screenshot

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

Title:
  Diacritical marks become visible only after changing view in Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772451/+subscriptions

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

[Bug 1773113] Re: nvidia-390 does not show GUI

[Marek Grand]

Oh, I'd like to add it isn't perfect yet, as it gets you to software rendering 
on Cinnamon.
MATE+compiz should work fine. I'll confirm or infirm this later on.

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

Title:
   nvidia-390 does not show GUI

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

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

[Bug 1773113] Re: nvidia-390 does not show GUI

[Marek Grand]

Hi,
I think this helps no matter the OS, I mean, "unices"...
I did that on fedora 29 modular. Delete every xorg.conf-files you can find.
$ sudo rm /etc/X11/xorg.conf
(on fedora there's one in /usr/share/X11 too)
($ sudo rm /usr/share/X11/xorg.conf)
Then restart the login manager (or reboot)
$ sudo service [login-manager here, either gdm, xdm, lightdm, sddm, whatever] 
restart

I assumed this 'cause nvidia-xconfig was said to be deprecated. Thank
you fedora :)

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

Title:
   nvidia-390 does not show GUI

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

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

[Bug 1769654] Re: Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

[Jan-Marek Glogowski]

Just a FYI: I opened https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=907487

That won't result in a different binary package, but from my
interpretation it's a bug in the patch.

** Bug watch added: Debian Bug tracker #907487
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907487

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

Title:
  Ubuntu 18.04 embedded fonts Liberation have corrupted metrics

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-liberation/+bug/1769654/+subscriptions

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

[Bug 1789169] Re: startx doesn't start to blackbox

[Marek Kolacek]

There is a workaround. Don't use startx at all.
Use under root following:
xinit /usr/bin/blackbox
After that X starts.
Under root. And it's possible to sudo su - to
user and then root programs under it.
However under common user command:
xinit /usr/bin/blackbox
won't start.

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

Title:
  startx doesn't start to blackbox

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

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

[Bug 1789170] [NEW] /etc/default/console-setup doesn't affect number of TTY's

[Marek Kolacek]

Public bug reported:

Description: Ubuntu 18.04.1 LTC
Release: Release 18.04

Package: Linux console (tty)

Expected: 
Change in ACTIVE_CONSOLES in /etc/default/console-setup will affect number of 
ttys

Current state:
When I change ACTIVE_CONSOLE="dev/tty[1-4]" it doesn't affect number of tty's 
available.
Still there are tty's 1-6. And the number doesn't change.

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

Title:
  /etc/default/console-setup doesn't affect number of TTY's

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

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

[Bug 1789169] [NEW] startx doesn't start to blackbox

[Marek Kolacek]

Public bug reported:

Description: Ubuntu 18.04.1 LTC
Release: Release 18.04

Package: X11 Org, Blackbox

Expected: When in runlevel 3 the startx starts blackbox

Current state: When in runlevel 3 and changed the
/etc/X11/default-display-manager to /usr/bin/blackbox
The X won't even start. The only solution is to keep
the gdm3 there in then I got the Gnome.

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

Title:
  startx doesn't start to blackbox

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

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

[Bug 1789171] [NEW] upgrade changed my font size in tty

[Marek Kolacek]

Public bug reported:

Description: Ubuntu 18.04.1 LTC
Release: Release 18.04

Package: Linux console (tty)

Expected: Upgrade won't changed my font size in tty

Current state: 
When issued 
apt-get update
apt-get upgrade
The reboot threw me into another font size.
I had set to FONTSIZE="16x32"
The upgrade gave me smaller font.
Couldn't change without reboot.

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

Title:
  upgrade changed my font size in tty

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

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

[Bug 1789168] [NEW] ANSI extended characters doesn't display correctly in console

[Marek Kolacek]

Public bug reported:

Description: Ubuntu 18.04.1 LTC
Release: Release 18.04

Package: Linux console (tty)

Expected: The ANSI extended characters display correctly

Current state: The ANSI extended characters doesn't display correctly
https://theasciicode.com.ar/extended-ascii-code/graphic-character-low-density-dotted-ascii-code-176.html
The extended characters doesn't display on console correctly.
Correctly displayed are only characters DEC 191-197.
The others doesn't display well. Just diamonds instead.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: console

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

Title:
  ANSI extended characters doesn't display correctly in console

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

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

[Bug 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Marek]

I'm on 18.04.01 LTS, and I have this issue. 
I was searching for this shortcut to be disabled.

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

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

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

[Bug 1750384] Re: Cannot Delete Recordset / Zone in ng_dns panels

[Marek Lyčka]

I committed a fix at:

https://review.openstack.org/#/c/588155/2

which review hasn't linked for some reason.

On a side note, this should also fix bug 
https://bugs.launchpad.net/designate-dashboard/+bug/1759717

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

Title:
  Cannot Delete Recordset / Zone in ng_dns panels

To manage notifications about this bug go to:
https://bugs.launchpad.net/designate-dashboard/+bug/1750384/+subscriptions

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

[Bug 1750384] Re: Cannot Delete Recordset / Zone in ng_dns panels

[Marek Lyčka]

** Changed in: designate-dashboard (Ubuntu)
 Assignee: (unassigned) => Marek Lyčka (mareklycka)

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

Title:
  Cannot Delete Recordset / Zone in ng_dns panels

To manage notifications about this bug go to:
https://bugs.launchpad.net/designate-dashboard/+bug/1750384/+subscriptions

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

[Bug 1246272] Re: Keyboard layout changing randomly

[Marek Marczykowski-Górecki]

I have similar problem. I found the only way to set defaults for a new
input device (which also applies to Xorg re-adding the same devices at
some arbitrary times like suspend) at runtime, without restarting Xorg
to pick up modified xorg.conf, is to set xkb* udev properties on a
device (for example by adding new rule and reloading udev).

More details: https://github.com/QubesOS/qubes-
issues/issues/3352#issuecomment-400292279

** Bug watch added: github.com/QubesOS/qubes-issues/issues #3352
   https://github.com/QubesOS/qubes-issues/issues/3352

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

Title:
  Keyboard layout changing randomly

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

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

[Bug 1432949]

[Marek Olšák]

You can try "git am -3 ...". If that doesn't help, then I don't know.

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

Title:
  r300 Mesa driver not loading with KMS enabled

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

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

[Bug 1393624] Re: Lock screen rejects password on Ubuntu 14.04

[Marek Samec]

I have same issue with this configuration:

OS: Ubuntu 18.04 bionic
 Kernel: x86_64 Linux 4.15.0-22-generic
 Shell: bash 4.4.19
 Resolution: 3840x1080
 DE: GNOME 
 WM: GNOME Shell
 WM Theme: Adwaita
 GTK Theme: Flat Remix GTK [GTK2/3]
 Icon Theme: Obsidian-Sand
 Font: Cantarell 11
 CPU: Intel Core i5-7200U @ 4x 3.1GHz [44.0°C]
 GPU: llvmpipe (LLVM 6.0, 256 bits)
 RAM: 3839MiB

I have a laptop and an external screen, running with dual screen setup.
This bug is quite annoying.

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

Title:
  Lock screen rejects password on Ubuntu 14.04

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

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

[Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

[Jan-Marek Glogowski]

I did the same tests as in comment #3 and it works for me.

Thanks.

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

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

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

[Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

[Marek ZJ]

Thanks Timo for explanation. I'm aware of all inconveniences related to
running unstable system, looks that I have just hit one of those... I'll
keep my eye on it. I'd keep the bug open till those dependencies are
fixed, but it is up to you.

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

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

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

[Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

[Marek ZJ]

Ekhm... why do you say "As that package is installed by default"? Maybe 
in experimental Debian, but not in Ubuntu. I had to find this solution, 
manually download two deb files and install them creating a mess in my 
package repository just to make my kubuntu working. Do you call that 
"solution"?
Is anyone even trying to read that report with understanding or 
verifying what is in the repository?!?

On 2018-03-01 15:29, dino99 wrote:
> As you said, and freedesktop concluded:
> 
> Installing libegl-mesa0 package from experimental repository fixes the
> bug.
> 
> As that package is installed by default, that report is now useless.
> 
> 
> ** Changed in: mesa (Ubuntu)
>Status: New => Invalid
> 
> --
> You received this bug notification because you are subscribed to the 
> bug
> report.
> https://bugs.launchpad.net/bugs/1752343
> 
> Title:
>   Problem with DRI2 and GLX - bionic 18.04
> 
> Status in mesa package in Ubuntu:
>   Invalid
> 
> Bug description:
>   I have encountered the problem described below, after some recent
>   updates in my Kubuntu. After asking on "Answers" I was requested to
>   open a bug, so I'm doing it.
> 
>   My problem was, that kwin stopped to show graphical effects. I'm
> using a laptop with Intel graphics - HD5500
>   After some log file search I've found, that probably the cause is
> shown in Xorg.0.log:
> 
>   Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
>   Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering
> 
> 
>   After some googling, I have found article below, explaining possible
> root cause. I have used a solution proposed there, and after
> installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and
> libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared.
> 
>   Link below describes details:
> 
>   https://bugs.freedesktop.org/show_bug.cgi?id=104928
> 
>   Here is some output from my OS diag tools:
> 
>   lshw -C display
> 
> *-display
>  description: VGA compatible controller
>  product: HD Graphics 5500
>  vendor: Intel Corporation
>  physical id: 2
>  bus info: pci@:00:02.0
>  version: 09
>  width: 64 bits
>  clock: 33MHz
>  capabilities: msi pm vga_controller bus_master cap_list rom
>  configuration: driver=i915 latency=0
>  resources: irq:47 memory:c000-c0ff
> memory:b000-bfff ioport:4000(size=64) memory:c-d
> 
>   lsb_release -a
>   No LSB modules are available.
>   Distributor ID: Ubuntu
>   Description: Ubuntu Bionic Beaver (development branch)
>   Release: 18.04
>   Codename: bionic
> 
>   uname -a
>   Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35
> UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> 
>   sudo dmidecode -t 1
>   # dmidecode 3.1
>   Getting SMBIOS data from sysfs.
>   SMBIOS 2.7 present.
> 
>   Handle 0x0001, DMI type 1, 27 bytes
>   System Information
>   Manufacturer: FUJITSU
>   Product Name: LIFEBOOK A555
>   Version:
>   Serial Number: YM3M035369
>   UUID: CF0F380B-2089-E511-8681-742B62ED267C
>   Wake-up Type: Power Switch
>   SKU Number:
>   Family: LIFEBOOK-FTS
> 
>   Best Regards,
> 
>   Marek
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+subscriptions


** Bug watch added: freedesktop.org Bugzilla #104928
   https://bugs.freedesktop.org/show_bug.cgi?id=104928

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

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

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

[Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

[Marek ZJ]

One more - please contact me before setting this again to invalid.
English is not my native, so I'd like to be sure, that misunderstanding
is not the cause for invalidating the report.

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

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

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

[Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

[Marek ZJ]

I hope after 10 years with kubuntu I'm not trying to mix anything...
This is my sources list:

deb http://archive.ubuntu.com/ubuntu/ bionic main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic-updates main restricted
deb http://archive.ubuntu.com/ubuntu/ bionic universe
deb http://archive.ubuntu.com/ubuntu/ bionic-updates universe
deb http://archive.ubuntu.com/ubuntu/ bionic multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-updates multiverse
deb http://archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe 
multiverse
deb http://archive.canonical.com/ubuntu bionic partner
deb http://security.ubuntu.com/ubuntu bionic-security main restricted
deb http://security.ubuntu.com/ubuntu bionic-security universe
deb http://security.ubuntu.com/ubuntu bionic-security multiverse

What I did was just a regular apt update && apt upgrade. 
At some point I have lost my graphical effects in KDE

I suppose you are still supporting apt upgrade, aren't you? :-D

So to summarize - there is a bug in package which is currently in Ubuntu
repository. With following packages:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version   Architecture  Description
+++--=-=-=
ii  libegl1:amd640.2.999+git20 amd64 Vendor neutral GL dispatch 
library --
ii  libegl1-mesa:amd 17.3.3-0ubunt amd64 free implementation of the EGL 
API --
ii  libegl1-mesa-dev 17.3.3-0ubunt amd64 free implementation of the EGL 
API --
un  libegl1-x11  (no description available)


My kubuntu is not using hardware accelerated graphics.

In /var/log/Xorg.0.log file, I can see this:
[ 17324.106] (II) AIGLX: Screen 0 is not DRI2 capable
[ 17324.106] (EE) AIGLX: reverting to software rendering

Using those, I have just googled for some solution and found that when I
install those two .deb files:

libegl-mesa0_18.0.0~rc4-1_amd64.deb  
libgbm1_18.0.0~rc4-1_amd64.deb

Everything goes back to normal.

So something is wrong, but I can't go behind that point to say what
exactly.

** Changed in: mesa (Ubuntu)
   Status: Invalid => New

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

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

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

[Bug 1752343] Re: Problem with DRI2 and GLX - bionic 18.04

[Marek ZJ]

** Package changed: ubuntu => mesa (Ubuntu)

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

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

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

[Bug 1752343] [NEW] Problem with DRI2 and GLX - bionic 18.04

[Marek ZJ]

Public bug reported:

I have encountered the problem described below, after some recent
updates in my Kubuntu. After asking on "Answers" I was requested to open
a bug, so I'm doing it.

My problem was, that kwin stopped to show graphical effects. I'm using a laptop 
with Intel graphics - HD5500 
After some log file search I've found, that probably the cause is shown in 
Xorg.0.log:

Xorg.0.log:[  7073.803] (II) AIGLX: Screen 0 is not DRI2 capable
Xorg.0.log:[  7073.803] (EE) AIGLX: reverting to software rendering


After some googling, I have found article below, explaining possible root 
cause. I have used a solution proposed there, and after installing 
libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my 
problem disappeared. 

Link below describes details:

https://bugs.freedesktop.org/show_bug.cgi?id=104928

Here is some output from my OS diag tools:

lshw -C display

  *-display
   description: VGA compatible controller
   product: HD Graphics 5500
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 09
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:47 memory:c000-c0ff memory:b000-bfff 
ioport:4000(size=64) memory:c-d

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic

uname -a
Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

sudo dmidecode -t 1
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: FUJITSU
Product Name: LIFEBOOK A555
Version:
Serial Number: YM3M035369
UUID: CF0F380B-2089-E511-8681-742B62ED267C
Wake-up Type: Power Switch
SKU Number:
Family: LIFEBOOK-FTS

Best Regards,

Marek

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

Title:
  Problem with DRI2 and GLX - bionic 18.04

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

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

[Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

[Jan-Marek Glogowski]

I can't test this 3.13 kernel, as it has multiple other problems.

What I was talking about was the 4.4 Xenial kernel compiled with the
Trusty config / compiler, so my modules will build against:

Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-
protector-strong not supported by compiler.

So on Trusty with HWE Xenial I get:

$ grep CONFIG_CC_STACKPROTECTOR_STRONG /boot/config-4.4.0-111-generic 
# CONFIG_CC_STACKPROTECTOR_STRONG is not set

while on Xenial I have

$ grep CONFIG_CC_STACKPROTECTOR_STRONG /boot/config-4.4.0-112-generic
CONFIG_CC_STACKPROTECTOR_STRONG=y

Sorry for not being explicit enough.

BTW: I manually compiled the Ubuntu kernel source with my attached
patch, the config from /boot as .config and a make oldconfig etc. and it
worked as expected.

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

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

[Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

[Jan-Marek Glogowski]

Thanks a lot. After apw's comment on IRC I expected something in the
next weeks :-)

I can just tell you it boots and seems to work. When I tried to manually
build my hw-support-dkms against the kernel I got:

LANG=C ./r 
+ pwd
+ make -C /usr/src/linux-headers-4.4.0-112-generic M=/home/glg/mod
make: Entering directory `/usr/src/linux-headers-4.4.0-112-generic'
Makefile:702: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler
  CC [M]  /home/glg/mod/fujitsu-laptop.o
gcc: error: unrecognized command line option '-fstack-protector-strong'
make[1]: *** [/home/glg/mod/fujitsu-laptop.o] Error 1
make: *** [_module_/home/glg/mod] Error 2
make: Leaving directory `/usr/src/linux-headers-4.4.0-112-generic'

So I guess this kernel was build on Xenial, which I don't have
installed. I have Trusty and Bionic, which has the upstream patch
included.

But generally it looks ok'ish, as rfkill-any shows up:

$ cat /sys/class/leds/input2\:\:capslock/trigger 
none rfkill-any kbd-scrolllock kbd-numlock [kbd-capslock] kbd-kanalock 
kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock 
kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full 
CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0 
cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc 
phy0radio

For a test I used the the caspslock led and manually set the soft
rfkill, which triggers the led correctly:

$ echo "rfkill-any" | sudo tee /sys/class/leds/input2\:\:capslock/trigger  
rfkill-any
$ cat /sys/class/leds/input2\:\:capslock/trigger 
none [rfkill-any] kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock 
kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock 
kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock AC-online CMB1-charging-or-full 
CMB1-charging CMB1-full CMB1-charging-blink-full-solid usb-gadget usb-host cpu0 
cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 mmc0 rfkill0 rfkill1 phy0rx phy0tx phy0assoc 
phy0radio 

=> capslock led is on

$ sudo rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

$ sudo rfkill block 0
$ sudo rfkill block 1

=> capslock led is off

I tried all combinations of block and unblock.
No stacks in the dmesg.

So I guess it works as expected.

If you can provide a Trusty based kernel, I'll test it tomorrow.

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

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

[Bug 1745130] [NEW] Support rfkill-any led trigger for Fujitsu u727

[Jan-Marek Glogowski]

Public bug reported:

I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
Author: Michał Kępień 
Date:   Fri Jan 6 07:07:47 2017 +0100

rfkill: Add rfkill-any LED trigger

Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

But the rfkill support is compiled in, so I can't patch it using DKMS.

So my first proposed fix would be to include a backport of this patch.
Alternatively rfkill can be compiled as a module, so I can patch it and
provide an updated module.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
Uname: Linux 4.4.0-111-generic i686
ApportVersion: 2.14.1-0ubuntu3.27
Architecture: i386
Date: Wed Jan 24 10:48:28 2018
SourcePackage: linux-lts-xenial
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug i386 third-party-packages trusty

** Patch added: "Add rfkill-any as led trigger"
   
https://bugs.launchpad.net/bugs/1745130/+attachment/5042221/+files/rfkill-any-4.4.patch

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

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

[Bug 1744011] [NEW] package virtualbox 5.0.40-dfsg-0ubuntu1.16.04.2 failed to install/upgrade: package virtualbox is already installed and configured

[Marek Polak]

Public bug reported:

system just reports a bug to me on start.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: virtualbox 5.0.40-dfsg-0ubuntu1.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
Date: Fri Jan 12 09:35:45 2018
DuplicateSignature:
 package:virtualbox:5.0.40-dfsg-0ubuntu1.16.04.2
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package unattended-upgrades (--configure):
  package unattended-upgrades is already installed and configured
ErrorMessage: package virtualbox is already installed and configured
InstallationDate: Installed on 2017-10-07 (103 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: dpkg
Title: package virtualbox 5.0.40-dfsg-0ubuntu1.16.04.2 failed to 
install/upgrade: package virtualbox is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package virtualbox 5.0.40-dfsg-0ubuntu1.16.04.2 failed to
  install/upgrade: package virtualbox is already installed and
  configured

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

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

[Bug 1742890] [NEW] package virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.2 failed to install/upgrade: package virtualbox-dkms is already installed and configured

[Marek Polak]

Public bug reported:

the problem arose when i wanted to update the kernel.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports:
 600:0:117:178834:2018-01-11 15:21:56.627121806 +0100:2018-01-11 
15:25:26.484114439 +0100:/var/crash/nvidia-384.0.crash
 600:0:117:286419:2018-01-12 09:35:44.730878829 +0100:2018-01-12 
09:35:45.730878829 +0100:/var/crash/virtualbox-dkms.0.crash
 600:0:117:286421:2018-01-12 09:35:45.710880922 +0100:2018-01-12 
09:35:45.478905830 +0100:/var/crash/unattended-upgrades.0.crash
 600:0:117:286409:2018-01-12 09:35:45.746877058 +0100:2018-01-12 
09:35:45.730878775 +0100:/var/crash/virtualbox.0.crash
Date: Fri Jan 12 09:35:45 2018
DuplicateSignature:
 package:virtualbox-dkms:5.0.40-dfsg-0ubuntu1.16.04.2
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package unattended-upgrades (--configure):
  package unattended-upgrades is already installed and configured
ErrorMessage: package virtualbox-dkms is already installed and configured
InstallationDate: Installed on 2017-10-07 (96 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: dpkg
Title: package virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.2 failed to 
install/upgrade: package virtualbox-dkms is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: already-installed amd64 apport-package xenial

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

Title:
  package virtualbox-dkms 5.0.40-dfsg-0ubuntu1.16.04.2 failed to
  install/upgrade: package virtualbox-dkms is already installed and
  configured

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

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

[Bug 1737342] [NEW] package nvidia-384 384.90-0ubuntu3.17.10.1 failed to install/upgrade: pakiet jest w złym stanie - powinien zostać przeinstalowany przed usunięciem

[Marek]

Public bug reported:

It happen direct after login.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: nvidia-384 384.90-0ubuntu3.17.10.1
ProcVersionSignature: Ubuntu 4.13.0-19.22-lowlatency 4.13.13
Uname: Linux 4.13.0-19-lowlatency x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
Date: Sat Dec  2 14:07:50 2017
DpkgTerminalLog:
 Usuwanie pakietu libcuda1-384 (384.90-0ubuntu3.17.10.1) ...
 Usuwanie pakietu nvidia-opencl-icd-384 (384.90-0ubuntu3.17.10.1) ...
 dpkg: błąd przetwarzania pakietu nvidia-384 (--remove):
  pakiet jest w złym stanie - powinien zostać przeinstalowany przed usunięciem
ErrorMessage: pakiet jest w złym stanie - powinien zostać przeinstalowany przed 
usunięciem
InstallationDate: Installed on 2017-04-22 (231 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: nvidia-graphics-drivers-384
Title: package nvidia-384 384.90-0ubuntu3.17.10.1 failed to install/upgrade: 
pakiet jest w złym stanie - powinien zostać przeinstalowany przed usunięciem
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package nvidia-384 384.90-0ubuntu3.17.10.1 failed to install/upgrade:
  pakiet jest w złym stanie - powinien zostać przeinstalowany przed
  usunięciem

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

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

[Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

[Marek]

I would just like to inform you that this bug appear since last CentOS 7.4 
update, 7.3 was ok.
https://bugs.centos.org/view.php?id=13916

Maybe it should be reported to Systemd Issues ?

** Bug watch added: bugs.centos.org/ #13916
   https://bugs.centos.org/view.php?id=13916

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

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

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

[Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec

[Marek]

had somebody tryed sound with kernel 4.12 ??

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

Title:
  No sound on Asus e200ha, intel sst with cx2072x codec

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions

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

[Bug 1641244] Re: Ubuntu 16.04 suspend works only twice or thrice in a row, freezes at next attempt

[Marek Stasiak]

I had too many problems with kernel 4.10 to be able to test this, so I
just let this report expire. Anyway, I kinda gave up with investigation.

One thing I discovered, and this is to people who may be reading this
and looking for a solution, was that suspend with 'sudo acpitool -s'
command was working very good! So I just edited my systemd-
suspend.service file and modified ExecStart line to look like this:

ExecStart=/usr/bin/acpitool -s

and thats it. Suspend is now working as it should be.

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

Title:
  Ubuntu 16.04 suspend works only twice or thrice in a row, freezes at
  next attempt

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

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

[Bug 1684490] [NEW] Crash when a file (or a symlink) ceases to exist

[Marek Parek]

Public bug reported:

Exception in Gtk# callback delegate
  Note: Applications can use GLib.ExceptionManager.UnhandledException to handle 
the exception.
GLib.GException: Chyba při získávání informací pro soubor „/var/www“: Adresář 
nebo soubor neexistuje
  at GLib.FileAdapter.QueryInfo (System.String attributes, FileQueryInfoFlags 
flags, GLib.Cancellable cancellable) <0x415619f0 + 0x00157> in :0 
  at Do.Universe.Linux.FileItem.get_MimeType () <0x4155af30 + 0x00034> in 
:0 
  at Do.Universe.Linux.FileItem.get_Icon () <0x4155a4a0 + 0x00177> in :0 
  at Do.Interface.AnimationBase.BezelDrawingArea.RenderPixbuf (Pane pane, 
Cairo.Context cr) <0x4155a410 + 0x00043> in :0 
  at Do.Interface.AnimationBase.BezelDrawingArea.RenderPane (Pane pane, 
Cairo.Context cr) <0x4154a4e0 + 0x000e7> in :0 
  at Do.Interface.AnimationBase.BezelDrawingArea.Paint () <0x415471d0 + 
0x00387> in :0 
  at Do.Interface.AnimationBase.BezelDrawingArea.OnExposeEvent (Gdk.EventExpose 
evnt) <0x41547090 + 0x00027> in :0 
  at Gtk.Widget.exposeevent_cb (IntPtr widget, IntPtr evnt) <0x41546fd0 + 
0x00082> in :0 
  at GLib.ExceptionManager.RaiseUnhandledException (System.Exception e, Boolean 
is_terminal) [0x0] in :0 
  at Gtk.Widget.exposeevent_cb (IntPtr widget, IntPtr evnt) [0x0] in 
:0 
  at Gtk.Application.gtk_main () [0x0] in :0 
  at Gtk.Application.Run () [0x0] in :0 
  at Do.Do.Main (System.String[] args) [0x0] in :0 

Addittional info:

Happened on a fresh Ubuntu 16.04 intstall - opening Gnome Do and
pressing 'w' causes this error. Reinstating the /var/www symlink to
fixes the error, gnome prings up www directory as a suggestion.

Description:Ubuntu 16.04.2 LTS
Release:16.04
gnome-do  0.95.3-5

** Affects: gnome-do (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/1684490

Title:
  Crash when a file (or a symlink) ceases to exist

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

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

[Bug 1681065] [NEW] package mysql-server-5.7 5.7.17-0ubuntu0.16.04.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Marek]

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

Public bug reported:

insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides 
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql' 
overrides LSB defaults (0 1 6).
mysql_upgrade: Got error: 2002: Can't connect to local MySQL server through 
socket '/var/run/mysqld/mysqld.sock' (2) while connecting to the MySQL server
Upgrade process encountered error and will not continue.
mysql_upgrade failed with exit status 11
dpkg: Fehler beim Bearbeiten des Paketes mysql-server-5.7 (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von mysql-server:
 mysql-server hängt ab von mysql-server-5.7; aber:
  Paket mysql-server-5.7 ist noch nicht konfiguriert.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: mysql-server-5.7 5.7.17-0ubuntu0.16.04.2
Uname: Linux 4.8.3-040803-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Sat Apr  8 12:35:27 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-11 (361 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021)
Logs.var.log.daemon.log:
 
MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql]
MySQLConf.etc.mysql.conf.d.mysqldump.cnf:
 [mysqldump]
 quick
 quote-names
 max_allowed_packet = 16M
MySQLConf.etc.mysql.mysql.conf.d.mysqld_safe_syslog.cnf:
 [mysqld_safe]
 syslog
MySQLVarLibDirListing: ['performance_schema', 'checkpointdigitalsolutions', 
'debian-5.6.flag', 'wordpress_user', 'ks_krappi', 'shopware_demodaten', 
'ib_buffer_pool', 'contaotest', 'ib_logfile0', 'mysql', 'holmvintage', 
'phpmyadmin', 'contao_rocksolid_luxe', 'debian-5.7.flag', 'wordpress_de', 
'auto.cnf', 'ibdata1', 'contao_4_test', 'ib_logfile1', 'iskra_berlin', 
'mytrauringstore', 'eee_ltd', 'sys', 'mysql_upgrade_info']
ProcCmdline: BOOT_IMAGE=/vmlinuz-4.8.3-040803-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro acpi_os_name=Linux acpi_osi= 
acpi_backlight=vendor
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.19
SourcePackage: mysql-5.7
Title: package mysql-server-5.7 5.7.17-0ubuntu0.16.04.2 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.mysql.conf: [modified]
mtime.conffile..etc.init.mysql.conf: 2016-11-18T14:00:06.943578
upstart.mysql.override: manual

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


** Tags: amd64 apparmor apport-package third-party-packages xenial

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

Title:
  package mysql-server-5.7 5.7.17-0ubuntu0.16.04.2 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

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

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