[Bug 2070453] [NEW] package snapd (not installed) failed to install/upgrade: el subproceso instalado paquete snapd script post-removal devolvió el código de salida de error 1

2024-06-26 Thread Angel Alexander
Public bug reported:

dpkg: error al procesar el paquete snapd (--purge):
 el subproceso instalado paquete snapd script post-removal devolvió el código 
de salida de error 1
Purgando ficheros de configuración de firefox (1:1snap1-0ubuntu5) ...
Purgando ficheros de configuración de thunderbird (2:1snap1-0ubuntu3) ...
Se encontraron errores al procesar:
 snapd
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: snapd (not installed)
ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
Uname: Linux 6.8.0-36-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jun 26 10:09:21 2024
ErrorMessage: el subproceso instalado paquete snapd script post-removal 
devolvió el código de salida de error 1
InstallationDate: Installed on 2024-06-04 (22 days ago)
InstallationMedia: Ubuntu 24.04.0 2024.05.03 LTS "Custom Noble Numbat" 
(20240503)
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6
 apt  2.7.14build2
SourcePackage: snapd
Title: package snapd (not installed) failed to install/upgrade: el subproceso 
instalado paquete snapd script post-removal devolvió el código de salida de 
error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package noble

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

Title:
  package snapd (not installed) failed to install/upgrade: el subproceso
  instalado paquete snapd script post-removal devolvió el código de
  salida de error 1

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


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

[Bug 2069361] Re: Google Chrome does not tile correctly

2024-06-25 Thread Angel D. Segarra
Unfortunately it happens even with enhanced tiling disabled.

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

Title:
  Google Chrome does not tile correctly

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


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

Re: [Bug 2069361] Re: Google Chrome does not tile correctly

2024-06-25 Thread Angel D. Segarra
Unfortunately it happens even with the tiling extension disabled.

On Mon, Jun 24, 2024 at 11:20 PM Daniel van Vugt <2069...@bugs.launchpad.net>
wrote:

> Ubuntu uses a different tiling extension. You can disable it with:
>
>   gnome-extensions disable tiling-assist...@ubuntu.com
>
>
> ** Package changed: mutter (Ubuntu) =>
> gnome-shell-extension-tiling-assistant (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2069361
>
> Title:
>   Google Chrome does not tile correctly
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2069361/+subscriptions
>
>

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

Title:
  Google Chrome does not tile correctly

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


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

[Bug 2069361] Re: Google Chrome does not tile correctly

2024-06-24 Thread Angel D. Segarra
Just to add, this may be a Ubuntu specific bug. I tried replicating this
in Fedora with Gnome 46.0 and 46.2 and can't reproduce.

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

Title:
  Google Chrome does not tile correctly

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


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

[Bug 2069361] Re: Google Chrome does not tile correctly

2024-06-19 Thread Angel D. Segarra
scaling is 100%. Changing chrome ozone to wayland doesn’t fix it.

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

Title:
  Google Chrome does not tile correctly

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


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

[Bug 2069361] Re: Chrome does not tile correctly after disabling enhanced tiling

2024-06-18 Thread Angel D. Segarra
I also enabled enhanced tiling and seeing the same behavior.

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

Title:
  Chrome does not tile correctly after disabling enhanced tiling

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


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

[Bug 2069361] Re: Chrome does not tile correctly after disabling enhanced tiling

2024-06-18 Thread Angel D. Segarra
No text scaling in my case.

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

Title:
  Chrome does not tile correctly after disabling enhanced tiling

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


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

[Bug 2069361] [NEW] Chrome does not tile correctly after disabling enhanced tiling

2024-06-13 Thread Angel D. Segarra
Public bug reported:

Not sure under what package to file this under but I've disabled
enhanced tiling due to issues I was having with it but now with it
disabled for some reason Google Chrome does not tile correctly. When
tiled using super+left/right, parts of the app end up behind the top
panel and outside of the edge of the screen or the ubuntu dock.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: mutter (not installed)
ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
Uname: Linux 6.8.0-35-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 13 17:00:17 2024
InstallationDate: Installed on 2024-06-04 (9 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

** Description changed:

  Not sure under what package to file this under but I've disabled
  enhanced tiling due to issues I was having with it but now with it
  disabled for some reason Google Chrome does not tile correctly. When
  tiled using super+left/right, parts of the app end up behind the top
- panel and if tiled to where the ubuntu dock is, a part of the app is
- behind the dock.
+ panel and outside of the edge of the screen or the ubuntu dock.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
  Uname: Linux 6.8.0-35-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 13 17:00:17 2024
  InstallationDate: Installed on 2024-06-04 (9 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
-  LANG=en_US.UTF-8
-  PATH=(custom, no user)
-  SHELL=/bin/bash
-  TERM=xterm-256color
-  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Chrome does not tile correctly after disabling enhanced tiling

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


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

[Bug 2051595] Re: Reapplying a layout with mapped applications makes the app unresponsive

2024-04-28 Thread Angel D. Segarra
I can reproduce this much more easily and consistently when tiling
chrome and vscode both running under xwayland.

e.g.
1. Tile vscode to the right (super+right)
2. Tile chrome to the left (super+left)
3. both apps are unresponsive to input, chrome can be seen flickering as in OPs 
video with gnome-text.

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

Title:
  Reapplying a layout with mapped applications makes the app
  unresponsive

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


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

[Bug 1942361] Re: Wrong terminus font-size

2024-03-19 Thread Miguel Angel Noguera
Removing /etc/fonts/conf.d/70-no-bitmaps.conf fix the problem in every
version.

IMHO, to fix it dpkg-reconfigure fontconfig should ask "Do you want to
disable bitmap fonts?"

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

Title:
  Wrong terminus font-size

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


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

[Bug 2058375] [NEW] Kubuntu noble Try/Install main screen

2024-03-19 Thread Miguel Angel Noguera
Public bug reported:

Launching kubuntu's daily image, in the main screen I select "Español de
España" as language, then "try kubuntu"

When desktop is loaded, translations seem ok but keyboard "es" is not
loaded

(Ubuntu Noble Numbat (development branch), Release 24.04)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: kubuntu noble

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

Title:
  Kubuntu noble Try/Install main screen

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


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

[Bug 2058367] [NEW] Kubuntu noble daily installer broken

2024-03-19 Thread Miguel Angel Noguera
Public bug reported:

For more than a month it has been impossible to install the kubuntu-
daily image, the installer always crashes and the installation is not
completed (Ubuntu Noble Numbat (development branch), Release 24.04)

In every daily version, always is the same error: "El archivo de
secuencia de comandos principal /usr/lib/x86_64-linux-
gnu/calamares/modules/networkcfg/main.py para el trabajo de Python
networckg generó una excepción"

This bug has ben solved in calamares 3.3.5 so it seems a good idea
update to this version.

Comparing with the KDE NEON version I have discovered that editing line
158 in .../calamares/modules/networkcfg/main.py from "os.chmod(f,
0o0600" to "os.chmod(f.fileno(), 0o600)" also solves the problem and
allows the installation to be completed successfully.

** 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/2058367

Title:
  Kubuntu noble daily installer broken

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


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

[Bug 1976191] [NEW] package libfaudio0 20.04-2 [modified: usr/share/doc/libfaudio0/changelog.Debian.gz usr/share/doc/libfaudio0/copyright] failed to install/upgrade: intentando sobreescribir el compar

2022-05-29 Thread miguel angel castro bejar
Public bug reported:

mac@macb:~$ sudo dpkg --configure -a
dpkg: error al procesar el paquete libfaudio0:amd64 (--configure):
 el paquete libfaudio0:amd64 20.04-2 no se puede configurar porque 
libfaudio0:i386 está en una versión diferente (19.07-0~bionic)
dpkg: error al procesar el paquete libfaudio0:i386 (--configure):
 el paquete libfaudio0:i386 19.07-0~bionic no se puede configurar porque 
libfaudio0:amd64 está en una versión diferente (20.04-2)
Se encontraron errores al procesar:
 libfaudio0:amd64
 libfaudio0:i386
mac@macb:~$ sudo apt -f install
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias   
Leyendo la información de estado... Hecho
Corrigiendo dependencias... Listo
Los paquetes indicados a continuación se instalaron de forma automática y ya no 
son necesarios.
  gir1.2-handy-1 libhandy-1-0 python3-bs4 python3-html5lib python3-lxml 
python3-soupsieve
  python3-webencodings
Utilice «sudo apt autoremove» para eliminarlos.
Se instalarán los siguientes paquetes adicionales:
  libfaudio0:i386
Se actualizarán los siguientes paquetes:
  libfaudio0:i386
1 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados.
2 no instalados del todo o eliminados.
Se necesita descargar 0 B/142 kB de archivos.
Se utilizarán 123 kB de espacio de disco adicional después de esta operación.
¿Desea continuar? [S/n] s
(Leyendo la base de datos ... 194780 ficheros o directorios instalados 
actualmente.)
Preparando para desempaquetar .../libfaudio0_20.04-2_i386.deb ...
Desempaquetando libfaudio0:i386 (20.04-2) sobre (19.07-0~bionic) ...
dpkg: error al procesar el archivo 
/var/cache/apt/archives/libfaudio0_20.04-2_i386.deb (--unpack):
 intentando sobreescribir el compartido 
`/usr/share/doc/libfaudio0/changelog.Debian.gz', que es dis
tinto de otras instancias del paquetes libfaudio0:i386
Se encontraron errores al procesar:
 /var/cache/apt/archives/libfaudio0_20.04-2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
mac@macb:~$

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libfaudio0 20.04-2 [modified: 
usr/share/doc/libfaudio0/changelog.Debian.gz usr/share/doc/libfaudio0/copyright]
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
AptOrdering:
 libfaudio0:i386: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun May 29 16:48:10 2022
DpkgTerminalLog:
 Preparando para desempaquetar .../libfaudio0_20.04-2_i386.deb ...
 Desempaquetando libfaudio0:i386 (20.04-2) sobre (19.07-0~bionic) ...
 dpkg: error al procesar el archivo 
/var/cache/apt/archives/libfaudio0_20.04-2_i386.deb (--unpack):
  intentando sobreescribir el compartido 
`/usr/share/doc/libfaudio0/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libfaudio0:i386
ErrorMessage: intentando sobreescribir el compartido 
`/usr/share/doc/libfaudio0/changelog.Debian.gz', que es distinto de otras 
instancias del paquetes libfaudio0:i386
InstallationDate: Installed on 2022-05-03 (26 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.8
SourcePackage: faudio
Title: package libfaudio0 20.04-2 [modified: 
usr/share/doc/libfaudio0/changelog.Debian.gz 
usr/share/doc/libfaudio0/copyright] failed to install/upgrade: intentando 
sobreescribir el compartido `/usr/share/doc/libfaudio0/changelog.Debian.gz', 
que es distinto de otras instancias del paquetes libfaudio0:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: faudio (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/1976191

Title:
  package libfaudio0 20.04-2 [modified:
  usr/share/doc/libfaudio0/changelog.Debian.gz
  usr/share/doc/libfaudio0/copyright] failed to install/upgrade:
  intentando sobreescribir el compartido
  `/usr/share/doc/libfaudio0/changelog.Debian.gz', que es distinto de
  otras instancias del paquetes libfaudio0:i386

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


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

[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2022-04-21 Thread Angel D. Segarra
Updated and now I can't reproduce. Looks like some update made it go
away.

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions


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

[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2022-04-20 Thread Angel D. Segarra
fwiw I've checked Ubuntu 21.10/22.04, Fedora 35/36 and Arch. This only
happens in Ubuntu.

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions


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

[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b

2022-04-09 Thread Angel D. Segarra
** Description changed:

  Ubuntu 22.04 development fully updated as of time of this report.
  
  On a fresh boot, as soon as you open some applications and do the up
  touchpad gesture to enter the application grid and then back down to
- return to the desktop, journal spits out js stacktrace and animations
- become choppy.
+ return to the desktop, journal spits out js stacktrace. If you don't
+ trigger the crash then try opening and closing an app and trying again.
  
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10)
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36)
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77)
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object 
.Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed 
— impossible to get any property from it. This might be caused by the object 
having been destroyed from C code using something such as destroy(), dispose(), 
or remove() vfuncs.

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

Title:
  Touchpad gesture animations trigger Object St.Button (0x56439bd53160),
  has been already disposed — impossible to get any property from it.
  This might be caused by the object having been destroyed from C code
  using something such as destroy(), dispose(), or remove() vfuncs.

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


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

[Bug 1968390] Re: JS ERROR: TypeError: this.window_container is null

2022-04-09 Thread Angel D. Segarra
** Description changed:

  Ubuntu 22.04 Development
  
- 
- A 3 finger touchpad swipe up/down gesture with 1 application open outputs a 
lot of JS errors and stacks to the journal. This issue may be the same or 
related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 
but the output is somewhat different when you have more than 1 app open.
+ A 3 finger touchpad swipe up/down gesture with 1 application open
+ outputs a lot of JS errors and stacks to the journal. This issue may be
+ the same or related to https://bugs.launchpad.net/ubuntu/+source/gnome-
+ shell/+bug/1968383 but the output is somewhat different when you have
+ more than 1 app open.
  
  This also happens with all extensions disabled, does not happen in
  Fedora 36.
  
  To reproduce
  
  1. login and open terminal and watch the journal
  2. perform the 3 finger swipe up gesture until the app grid displays then 
swipe down to go back to the desktop.
  3. See journal
+ 4. If nothing happens try opening an app, closing it and try again.
  
  Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), 
has been already disposed — impossible to get any property from it. This might 
be caused by the object having been destroyed from C code using something such 
as destroy(), dispose(), or remove() vfuncs.
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10)
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36)
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77)
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #1   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #1   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0aa640 I   self-hosted:205 
(330c4e3bed80 @ 272)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #3   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   7ffc4c0a99a0 b   
resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0a9a70 b   
resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #3   7ffc4c0aa640 I   self-hosted:205 
(330c4e3bed80 @ 272)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #4   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #5   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
  Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
  Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Apr 08 21:18:49 x1c gnome-shell[21675]: #0   7ffc4c0a98b0 b   
resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43)
  Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0a99a0 b   
resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91)
  Apr 08 21:18:49 x1c 

[Bug 1968383] Re: Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having b

2022-04-09 Thread Angel D. Segarra
** Description changed:

  Ubuntu 22.04 development fully updated as of time of this report.
  
  On a fresh boot, as soon as you open some applications and do the up
  touchpad gesture to enter the application grid and then back down to
- return to the desktop, journal spits out js stacktrace.
+ return to the desktop, journal spits out js stacktrace and animations
+ become choppy.
  
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10)
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36)
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77)
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object 
.Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed 
— impossible to get any property from it. This might be caused by the object 
having been destroyed from C code using something such as destroy(), dispose(), 
or remove() vfuncs.

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

Title:
  Touchpad gesture animations trigger Object St.Button (0x56439bd53160),
  has been already disposed — impossible to get any property from it.
  This might be caused by the object having been destroyed from C code
  using something such as destroy(), dispose(), or remove() vfuncs.

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


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

[Bug 1968390] [NEW] JS ERROR: TypeError: this.window_container is null

2022-04-08 Thread Angel D. Segarra
Public bug reported:

Ubuntu 22.04 Development


A 3 finger touchpad swipe up/down gesture with 1 application open outputs a lot 
of JS errors and stacks to the journal. This issue may be the same or related 
to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1968383 but the 
output is somewhat different when you have more than 1 app open.

This also happens with all extensions disabled, does not happen in
Fedora 36.

To reproduce

1. login and open terminal and watch the journal
2. perform the 3 finger swipe up gesture until the app grid displays then swipe 
down to go back to the desktop.
3. See journal

Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Button (0x56219f5b8060), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:566 (4ce0bb0ac40 @ 10)
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:567 (4ce0bb0ac40 @ 36)
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:570 (4ce0bb0ac40 @ 77)
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:638 (4ce0bb0ae20 @ 23)
Apr 08 21:18:49 x1c gnome-shell[21675]: #1   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:353 (4ce0bb0a5b0 @ 62)
Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:357 (4ce0bb0a5b0 @ 87)
Apr 08 21:18:49 x1c gnome-shell[21675]: #1   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:364 (4ce0bb0a600 @ 8)
Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0aa640 I   self-hosted:205 
(330c4e3bed80 @ 272)
Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222)
Apr 08 21:18:49 x1c gnome-shell[21675]: #3   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   7ffc4c0a99a0 b   
resource:///org/gnome/shell/ui/environment.js:160 (330c4e3cc560 @ 43)
Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0a9a70 b   
resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23)
Apr 08 21:18:49 x1c gnome-shell[21675]: #2   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109)
Apr 08 21:18:49 x1c gnome-shell[21675]: #3   7ffc4c0aa640 I   self-hosted:205 
(330c4e3bed80 @ 272)
Apr 08 21:18:49 x1c gnome-shell[21675]: #4   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222)
Apr 08 21:18:49 x1c gnome-shell[21675]: #5   56219e7256c8 i   
resource:///org/gnome/shell/ui/windowPreview.js:571 (4ce0bb0ac40 @ 105)
Apr 08 21:18:49 x1c gnome-shell[21675]: == Stack trace for context 
0x56219d5b9180 ==
Apr 08 21:18:49 x1c gnome-shell[21675]: Object St.Label (0x56219f5a8440), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Apr 08 21:18:49 x1c gnome-shell[21675]: #0   7ffc4c0a98b0 b   
resource:///org/gnome/shell/ui/environment.js:361 (330c4e3ccc90 @ 43)
Apr 08 21:18:49 x1c gnome-shell[21675]: #1   7ffc4c0a99a0 b   
resource:///org/gnome/shell/ui/environment.js:163 (330c4e3cc560 @ 91)
Apr 08 21:18:49 x1c gnome-shell[21675]: #2   7ffc4c0a9a70 b   
resource:///org/gnome/shell/ui/environment.js:369 (330c4e3ccd30 @ 23)
Apr 08 21:18:49 x1c gnome-shell[21675]: #3   56219e7257f0 i   
resource:///org/gnome/shell/ui/windowPreview.js:365 (4ce0bb0a600 @ 109)
Apr 08 21:18:49 x1c gnome-shell[21675]: #4   7ffc4c0aa640 I   self-hosted:205 
(330c4e3bed80 @ 272)
Apr 08 21:18:49 x1c gnome-shell[21675]: #5   56219e725750 i   
resource:///org/gnome/shell/ui/windowPreview.js:363 (4ce0bb0a5b0 @ 222)
Apr 08 

[Bug 1968383] Re: Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having been

2022-04-08 Thread Angel D. Segarra
** Description changed:

  Ubuntu 22.04 development fully updated as of time of this report.
  
  On a fresh boot, as soon as you open some applications and do the up
- touch gesture to enter the application grid and then back down to return
- to the desktop, journal spits out js stacktrace.
+ touchpad gesture to enter the application grid and then back down to
+ return to the desktop, journal spits out js stacktrace.
  
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10)
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36)
  Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
  Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77)
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
  Apr 08 18:46:18 x1c gnome-shell[1782]: Object 
.Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed 
— impossible to get any property from it. This might be caused by the object 
having been destroyed from C code using something such as destroy(), dispose(), 
or remove() vfuncs.

** Summary changed:

- Touch gesture animations trigger Object St.Button (0x56439bd53160), has been 
already disposed — impossible to get any property from it. This might be caused 
by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
+ Touchpad gesture animations trigger Object St.Button (0x56439bd53160), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.

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

Title:
  Touchpad gesture animations trigger Object St.Button (0x56439bd53160),
  has been already disposed — impossible to get any property from it.
  This might be caused by the object having been destroyed from C code
  using something such as destroy(), dispose(), or remove() vfuncs.

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


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

[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2022-04-08 Thread Angel D. Segarra
I am seeing this in 22.04 and an easy way for me to reproduce is on a
fresh login, open a terminal and watch the log, open Brave/Chrome, for
some reason the first time you open the browser it has a GTK title bar
which goes away on closing/reopening the app, now right clicking in the
terminal window or opening the hamburger menu and bringing up the menu
triggers this message in the logs.

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions


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

[Bug 1968383] [NEW] Touch gesture animations trigger Object St.Button (0x56439bd53160), has been already disposed — impossible to get any property from it. This might be caused by the object having be

2022-04-08 Thread Angel D. Segarra
Public bug reported:

Ubuntu 22.04 development fully updated as of time of this report.

On a fresh boot, as soon as you open some applications and do the up
touch gesture to enter the application grid and then back down to return
to the desktop, journal spits out js stacktrace.

Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Button (0x56439a2fd220), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:566 (3be09010ac40 @ 10)
Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:567 (3be09010ac40 @ 36)
Apr 08 18:46:18 x1c gnome-shell[1782]: == Stack trace for context 
0x564398f2e170 ==
Apr 08 18:46:18 x1c gnome-shell[1782]: #0   56439bea4058 i   
resource:///org/gnome/shell/ui/windowPreview.js:570 (3be09010ac40 @ 77)
Apr 08 18:46:18 x1c gnome-shell[1782]: Object St.Label (0x56439a2e4c80), has 
been already disposed — impossible to get any property from it. This might be 
caused by the object having been destroyed from C code using something such as 
destroy(), dispose(), or remove() vfuncs.
Apr 08 18:46:18 x1c gnome-shell[1782]: Object 
.Gjs_ui_windowPreview_WindowPreview (0x56439a324ef0), has been already disposed 
— impossible to get any property from it. This might be caused by the object 
having been destroyed from C code using something such as destroy(), dispose(), 
or remove() vfuncs.

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


** Tags: jammy

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

Title:
  Touch gesture animations trigger Object St.Button (0x56439bd53160),
  has been already disposed — impossible to get any property from it.
  This might be caused by the object having been destroyed from C code
  using something such as destroy(), dispose(), or remove() vfuncs.

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


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

[Bug 1833281]

2022-03-27 Thread hi-angel
Modern kernels handle SWAPPING situations much better.

Also, these days the Multi-LRU patchset should pretty much resolve the
problem. It is not yet upstream, but is used in downstream kernels such
as linux-zen and liquorix-kernel. There is hope it will be merged by
5.19¹

1: https://www.phoronix.com/scan.php?page=news_item=MGLRU-Not-
For-5.18

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

Title:
  System freeze when memory is put on SWAP in Linux >4.10.x

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


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

[Bug 1956508] Re: Impish update: upstream stable patchset 2022-01-05

2022-03-24 Thread Angel Parrales
This update fixed my rtl8192e disconnecting bug, after a regression in
previous update.

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

Title:
  Impish update: upstream stable patchset 2022-01-05

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


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

[Bug 1949352] Re: Removable drives are not auto-mounted after screen lock/unlock

2022-02-05 Thread Angel D. Segarra
Fixed here as well, tested same steps as #17. Just wanted to add tested
version is 70~ubuntu3.21.10.1

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

Title:
  Removable drives are not auto-mounted after screen lock/unlock

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


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

[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2022-02-05 Thread Angel D. Segarra
Hi Daniel, sorry for the late reply, it does look very similar to bug
1863416, the only difference is it's happening in wayland for me.
Contrary to what I said above I can't consistently reproduce the problem
but I do still see these messages in the journal, but no idea how to
reproduce them.

I ran that apport command but got this message:

Package gtk+3.0 not installed and no hook available, ignoring

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1951878/+subscriptions


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

[Bug 1859592] Re: Bluetooth unavailable after updates - Reading Intel version information failed (-110)

2022-02-02 Thread Angel Parrales
Power cable unplug as comment #2
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592/comments/2
did the trick

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

Title:
  Bluetooth unavailable after updates - Reading Intel version
  information failed (-110)

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


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

[Bug 1870597] Re: libinput says "your system is too slow"

2022-01-28 Thread Angel D. Segarra
I'm getting spammed by libinput messages about the system being slow. A
couple of patches in libinput were merged to master about  month ago
that rate limits some messages that previously were not, and should at
least stop the spamming of messages, if you use a wireless mouse for
example the journal gets flooded if you're doing a lot of mouse
movements.

Please consider backporting these.

https://gitlab.freedesktop.org/libinput/libinput/-/commit/a1e9150210abda0d3dd41127330cd7985d29957d
https://gitlab.freedesktop.org/libinput/libinput/-/commit/64a49d18b948a5b8ac88da9207689af356a081cf

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

Title:
  libinput says "your system is too slow"

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


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

[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2022-01-07 Thread Angel D. Segarra
** Package changed: gnome-terminal (Ubuntu) => mutter (Ubuntu)

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

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


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

[Bug 1953176] [NEW] package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package post-installation script subprocess returned error exit status 1

2021-12-03 Thread Angel Guevara
Public bug reported:

Trying to install XRDP on Ubuntu 20.04 VM on Hyper V

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: xrdp 0.9.12-1
ProcVersionSignature: Ubuntu 5.11.0-41.45~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 xrdp:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Dec  3 10:33:59 2021
ErrorMessage: installed xrdp package post-installation script subprocess 
returned error exit status 1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: xrdp
Title: package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xrdp (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/1953176

Title:
  package xrdp 0.9.12-1 failed to install/upgrade: installed xrdp
  package post-installation script subprocess returned error exit status
  1

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


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

[Bug 1951878] Re: "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2021-11-22 Thread Angel D. Segarra
* I found out how to repro.

Ubuntu 21.10 on Wayland session
mutter 40.5-1ubuntu3~21.10.1

If I leave any gtk apps open e.g. gnome-terminal, evince, Files open,
and then open Google Chrome with the flags to enable wayland support

--enable-features=UseOzonePlatform --ozone-platform=wayland

Then any gtk app that was open outputs the following message to journal
after any UI interaction, like switching tabs, opening context menu,
etc.

gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
drawable is not a native X11 window

evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
not a native X11 window

This persists until each individual app is restarted.

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

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

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


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

[Bug 1951878] [NEW] "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in Wayland session

2021-11-22 Thread Angel D. Segarra
Public bug reported:

Ubuntu 21.10 on Wayland session
mutter 40.5-1ubuntu3~21.10.1

My apologies if this does not belong in mutter but because it happens in
multiple applications, it's my best guess.

This is a weird bug because I don't know what causes it but it happens
consistently after normal usage which for me means several times leaving
the laptop idle and unlocking.

If I leave gnome-terminal and/or evince open, eventually any UI action
like switching from multiple tabs, opening context menu etc will output
the following to journal

gnome-terminal-[2393]: ../../../../../gdk/x11/gdkwindow-x11.c:5653
drawable is not a native X11 window

evince[3213]: ../../../../../gdk/x11/gdkwindow-x11.c:5653 drawable is
not a native X11 window

I suspect this may happen with other gtk apps as well. This persists
until each individual app is restarted.

** Affects: gnome-terminal (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/1951878

Title:
  "gdk/x11/gdkwindow-x11.c:5653 drawable is not a native X11 window" in
  Wayland session

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


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

[Bug 1951786] Re: Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated

2021-11-22 Thread Angel D. Segarra
Can confirm, does not happen with dock disabled. Thanks!

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

Title:
  Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already
  deallocated

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


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

[Bug 1951786] [NEW] Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already deallocated

2021-11-21 Thread Angel D. Segarra
Public bug reported:

on Ubuntu 21.10
gnome-shell 40.5-1ubuntu2

Locking desktop and then unlocking it makes gnome-shell spit out a stack
trace.

v 22 02:00:49 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to access it. This 
might be caused by the>
Nov 22 02:00:49 saturn gnome-shell[33781]: == Stack trace for context 
0x5572c18e3130 ==
Nov 22 02:00:49 saturn gnome-shell[33781]: #0   7ffcbc579470 b   
resource:///org/gnome/gjs/modules/core/overrides/GObject.js:567 (22c5be1b1d80 @ 
25)
Nov 22 02:00:49 saturn gnome-shell[33781]: #1   5572c8ea2dc0 i   
resource:///org/gnome/shell/ui/components/autorunManager.js:159 (374b9f3380 @ 
31)
Nov 22 02:00:49 saturn gnome-shell[33781]: #2   7ffcbc57a1d0 b   
resource:///org/gnome/shell/ui/components/__init__.js:56 (374b9d7650 @ 66)
Nov 22 02:00:49 saturn gnome-shell[33781]: #3   7ffcbc57a960 b   
resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d7790 @ 15)
Nov 22 02:00:49 saturn gnome-shell[33781]: #4   7ffcbc57b030 b   
self-hosted:225 (374b92ab50 @ 273)
Nov 22 02:00:49 saturn gnome-shell[33781]: #5   5572c8ea2d30 i   
resource:///org/gnome/shell/ui/components/__init__.js:22 (374b9d78d0 @ 110)
...skipping...
Nov 22 02:04:21 saturn gnome-shell[33781]: #7   7ffcbc578a80 b   
resource:///org/gnome/shell/ui/sessionMode.js:200 (25da4d8e6d30 @ 284)
Nov 22 02:04:21 saturn gnome-shell[33781]: #8   7ffcbc579630 b   
resource:///org/gnome/shell/ui/sessionMode.js:168 (25da4d8e6e20 @ 116)
Nov 22 02:04:21 saturn gnome-shell[33781]: #9   7ffcbc579dc0 b   
resource:///org/gnome/shell/ui/screenShield.js:574 (25da4d8d4a60 @ 79)
Nov 22 02:04:21 saturn gnome-shell[33781]: #10   7ffcbc57a550 b   
resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4ab0 @ 17)
Nov 22 02:04:21 saturn gnome-shell[33781]: #11   7ffcbc57acd0 b   
resource:///org/gnome/shell/gdm/authPrompt.js:604 (25da4d8f24c0 @ 65)
Nov 22 02:04:21 saturn gnome-shell[33781]: #12   7ffcbc57b460 b   
resource:///org/gnome/shell/ui/unlockDialog.js:871 (374b9053d0 @ 40)
Nov 22 02:04:21 saturn gnome-shell[33781]: #13   7ffcbc57bbf0 b   
resource:///org/gnome/shell/ui/screenShield.js:565 (25da4d8d4b00 @ 50)
Nov 22 02:04:21 saturn gnome-shell[33781]: #14   7ffcbc57c380 b   
resource:///org/gnome/shell/ui/screenShield.js:116 (25da4d8dc6f0 @ 13)
Nov 22 02:04:21 saturn gnome-shell[33781]: #15   7ffcbc57ca50 b   
resource:///org/gnome/gjs/modules/core/_signals.js:114 (22c5be1b1330 @ 439)
Nov 22 02:04:21 saturn gnome-shell[33781]: #16   5572c39ba218 i   
resource:///org/gnome/gjs/modules/core/overrides/Gio.js:152 (22c5be1a5b50 @ 39)
Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to connect to any 
signal on it. This migh>
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Nov 22 02:04:21 saturn dbus-daemon[33727]: [session uid=1000 pid=33727] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.20' 
(uid=1000 pid=33781 comm>
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed
Nov 22 02:04:21 saturn gnome-shell[33781]: Object .GUnionVolumeMonitor 
(0x5572c2e0f8a0), has been already deallocated — impossible to access it. This 
might be caused by the>
Nov 22 02:04:21 saturn gnome-shell[33781]: g_volume_monitor_get_volumes: 
assertion 'G_IS_VOLUME_MONITOR (volume_monitor)' failed
Nov 22 02:04:21 saturn gnome-shell[33781]: == Stack trace for context 
0x5572c18e3130 ==
Nov 22 02:04:21 saturn gnome-shell[33781]: #0   5572c39ba218 i   
resource:///org/gnome/shell/ui/components/automountManager.js:66 (374b9f3e20 @ 
30)
Nov 22 02:04:21 saturn gnome-shell[33781]: #1   7ffcbc57d550 b   
self-hosted:850 (374b92a650 @ 398)
Nov 22 02:04:21 saturn NetworkManager[1054]:   [1637564661.8704] 
agent-manager: 
agent[70e63220a742bb64,:1.631/org.gnome.Shell.NetworkAgent/1000]: agent 
registered
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_parser_new_from_buf: assertion 
'a_buf && a_len' failed
Nov 22 02:04:21 saturn gnome-shell[33781]: cr_declaration_parse_list_from_buf: 
assertion 'parser' failed

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

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

Title:
  Object .GUnionVolumeMonitor (0x5572c2e0f8a0), has been already
  deallocated

To manage notifications about this bug go 

[Bug 1896772] Re: systemd-resolved configures no Current Scopes on start

2021-10-22 Thread Freddy Angel
I have the same issue:

   systemd-resolved: Failed to save link data
/run/systemd/resolve/netif/3: Permission denied

The netif folder is indeed owned by root. If I change the ownership to
systemd-resolved and restart the service, there is no error but as soon
as I reboot the system, the ownership is reverted to root and the error
is back.

Also, I searched the log for other resolved messages and found the error
below as well:

nm-dispatcher[4641]: /etc/network/if-up.d/resolved: 12: mystatedir:
not found

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

Title:
  systemd-resolved configures no Current Scopes on start

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


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

[Bug 1942361] [NEW] Wrong terminus font-size

2021-09-01 Thread Miguel Angel Noguera
Public bug reported:

1) Kubuntu Impish Indri (development branch) / Release: 21.10 / konsole 21.07.90
2) xfonts-terminus 4.48-3

3) font size must be selectable between from 9 to 24 px

4) only 9 px is available, wich is too small in most cases.

Same bug in debian 11.0 / ubuntu 21.04

PCLinuxOS (version 4.48) and openSUSE tumbleweed (version 4.49.1)
performs the right way

Downgrading to 4.40-2 (focal package) also fixes the problem.

Switching from xorg to wayland doesnt affect.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xfonts-terminus 4.40-2
ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
Uname: Linux 5.13.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu68
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Sep  1 20:08:46 2021
InstallationDate: Installed on 2021-08-21 (10 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Alpha amd64 (20210821)
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=es
 LANG=es_ES.UTF-8
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: xfonts-terminus
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: xfonts-terminus (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

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

Title:
  Wrong terminus font-size

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


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

[Bug 1942079] [NEW] unable to install

2021-08-30 Thread Angel López
Public bug reported:

Error trying to boot a 64bits computer, it says a file is currupt

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: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Mon Aug 30 08:15:36 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (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/1942079

Title:
  unable to install

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


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

[Bug 1940721] [NEW] Primero me mostro un error 10 al inicio y despues se en el final de la instalacion me aparecio error

2021-08-20 Thread Miguel Angel
Public bug reported:

En la instalacion me mostro error descargando lo ultimo del sistema
operativo y me salio una ventana que pedia reiniciar y tampoco funciona,
no sabria que mas describir soy nuevo en este sistema

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.10
ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-43-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.445.1
CurrentDesktop: ubuntu:GNOME
Date: Fri Aug 20 17:43:27 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
ProcEnviron:
 LANGUAGE=es_CO.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_CO.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Primero me mostro un error 10 al inicio y despues se en el final de la
  instalacion me aparecio error

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


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

[Bug 1917831] [NEW] package dbus 1.12.16-2ubuntu2.1 failed to install/upgrade: installed dbus package post-installation script subprocess returned error exit status 2

2021-03-04 Thread angel garcia
Public bug reported:

fdgdfgdfg

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: dbus 1.12.16-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Mar  4 22:38:06 2021
DuplicateSignature:
 package:dbus:1.12.16-2ubuntu2.1
 Installing new version of config file /etc/init.d/dbus ...
 dpkg-statoverride: error: group 'messagebus' does not exist
 dpkg: error processing package dbus (--configure):
  installed dbus package post-installation script subprocess returned error 
exit status 2
ErrorMessage: installed dbus package post-installation script subprocess 
returned error exit status 2
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: dbus
Title: package dbus 1.12.16-2ubuntu2.1 failed to install/upgrade: installed 
dbus package post-installation script subprocess returned error exit status 2
UpgradeStatus: Upgraded to focal on 2021-03-05 (0 days ago)

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


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

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

Title:
  package dbus 1.12.16-2ubuntu2.1 failed to install/upgrade: installed
  dbus package post-installation script subprocess returned error exit
  status 2

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

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

[Bug 1886608] Re: package grub-pc 2.04-1ubuntu26 failed to install/upgrade: el subproceso instalado paquete grub-pc script post-installation devolvió el código de salida de error 1

2020-10-02 Thread Angel Duran
Hola Jesús.

He actualizado un equipo con Ubuntu 18.04 a Ubuntu 20.04 y se me ha reproducido 
el error.
He podido subsanarlo. Aquí te dejo lo que he hecho

Eliminamos versiones anteriores del kernel
En este ejemplo eliminamos la versión 4.15.0-118, pero podemos eliminar la que 
deseeemos. Podemos ejecutar

   # ls -la /boot

para saber que versiones, o restos de ellas, tenemos.

   # cd /boot
   # mkdir kk
   # mv *4.15.0-118* kk
   # update-grub
   # reboot


https://itsfoss.com/dpkg-returned-an-error-code-1/

# ls -l /var/lib/dpkg/info | grep i grub-pc
# mkdir kk
# mv /var/lib/dpkg/info/grub-pc.* kk


Para estar seguros, antes de reiniciar, podemos ejecutar una reparación

https://slimbook.es/tutoriales/linux/164-3-maneras-de-como-reinstalar-o-reparar-grub-boot-repair-archlinux-o-antergos
# add-apt-repository ppa:yannubuntu/boot-repair
# apt-get update
# apt-get install -y boot-repair
# boot-repair


Las URL es el lugar de dónde he obtenido la información.

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

Title:
  package grub-pc 2.04-1ubuntu26 failed to install/upgrade: el
  subproceso instalado paquete grub-pc script post-installation devolvió
  el código de salida de error 1

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

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

[Bug 1896803] [NEW] ninguno

2020-09-23 Thread angel jose andrades lopez
Public bug reported:

no hay ningun problema

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.9timbuktu1
ProcVersionSignature: Ubuntu 4.15.0-1028.33-oem 4.15.18
Uname: Linux 4.15.0-1028-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Sep 23 11:25:45 2020
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 canonical-oem-stella-bionic-amd64-47
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz boot=casper automatic-ubiquity 
noprompt quiet splash --
InstallationDate: Installed on 2020-07-20 (65 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20181213-08:48
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic oem-config third-party-packages 
ubiquity-18.04.14.9timbuktu1

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

Title:
  ninguno

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

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

[Bug 1888969] Re: Please merge ddclient 3.9.1-5 (universe) from Debian unstable (main)

2020-08-22 Thread Angel Abad
This bug was fixed in the package ddclient - 3.9.1-5

---
ddclient (3.9.1-5) unstable; urgency=medium

  * Add line continuations to /etc/ddclient.conf
  * Update Japanese debconf translation.
Thanks to Takuma Yamada (Closes: #815388)
  * Update Portuguese debconf translation.
Thanks to Rui Branco (Closes: #871402)
  * Add new device built-ins (`fw=`)
Thanks to Geoff Simmons (Closes: #589980)
  * Fix `usev6` processing (Closes: #832395, #832396)
  * debian/control: Set `Rules-Requires-Root: no`

 -- Richard Hansen   Tue, 28 Jul 2020 01:46:01
-0400

ddclient (3.9.1-4) unstable; urgency=medium

  * Delete superseded debian/salsa-ci.yml file.

 -- Richard Hansen   Wed, 22 Jul 2020 16:26:52
-0400

ddclient (3.9.1-3) unstable; urgency=medium

  * Use dh_systemd_{enable,start} instead of dh_installsystemd
  * Upgrade to debhelper-compat 12

 -- Richard Hansen   Tue, 14 Jul 2020 19:08:32
-0400

ddclient (3.9.1-2) unstable; urgency=medium

  [ Andreas Henriksson ]
  * debian/skeleton: drop leftover example file
  * Add debian/salsa-ci.yml with default pipelines

  [ Richard Hansen ]
  * Silence lintian false positive (duplicate-updaterc.d-calls-in-postinst)

 -- Richard Hansen   Sun, 12 Jul 2020 18:34:05
+

ddclient (3.9.1-1) unstable; urgency=medium

  [ Richard Hansen ]
  * Refresh patches via 'gbp pq'
  * New upstream version 3.9.0
  * Refresh patches
  * Add dependency on libdata-validate-ip-perl
  * Bump Standards-Version to 4.0.0
  * debian/copyright: Fix year
  * Switch upstream to GitHub
  * Add gbp.conf
  * Merge tag 'v3.9.0'
  * Merge tag 'v3.9.1' (Closes: #913308)
  * Refresh patches
  * Bump debhelper compat to 9 (no changes) (Closes: #965481)
  * Change priority from extra to optional
  * Set shebang as required by Debian policy >= 4.1.2
  * Install RELEASENOTE as NEWS.gz
  * Use dh to build
  * Remove irrelevant examples
  * Install new relevant examples
  * Bump Standards-Version to 4.4.1
  * Update the Vcs-Git, Vcs-Browser URLs to the new home on salsa
  * Take over maintainership
  * Remove support for upgrading from ancient ddclient
  * Simplify debian/config and debian/postinst
  * Fail postinst if debconf's `db_get` fails
  * Fix quoting in shell scripts (Closes: #729960)
  * Unconditionally source debconf/confmodule in postinst
  * Recommend additional Perl modules for full protocol support
  * Ask for the protocol before asking for the server
  * Interpret an empty server as "use the default"
  * Update service and protocol choices (Closes: #745217, #625715)
  * Change default debconf check interval from 300 to 5m
  * Support `postinst reconfigure` (recommended by debconf-devel(7))
  * Remove the `run_daemon` control from the init script
  * Bump debhelper compat to 10
  * Add a systemd service node config.
Thanks to Andreas Henriksson (Closes: #950246)
  * Change the default for "Run as a daemon?" to true
  * Bump Standards-Version to 4.5.0
  * Apply upstream fix for boolean "true" parsing
  * Apply upstream fix for use=ip when ip=
  * debian/copyright: Untabify, style fixes.

  [ Debian Janitor ]
  * debian/changelog: Trim trailing whitespace.
  * Set upstream metadata fields.

 -- Richard Hansen   Sun, 12 Jul 2020 15:58:55
+

** Changed in: ddclient (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ddclient (Ubuntu)
   Status: New => Confirmed

** Changed in: ddclient (Ubuntu)
 Assignee: (unassigned) => Angel Abad (angelabad)

** Changed in: ddclient (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Please merge ddclient 3.9.1-5 (universe) from Debian unstable (main)

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

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

[Bug 1851573] Re: configuration file //.config/debconf-kde-helperrc not writable

2020-08-11 Thread Angel Rodriguez
First time it happened to me. Created text file "~/.config/debconf-kde-
helperrc" Problem solved.

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

Title:
  configuration file //.config/debconf-kde-helperrc not writable

To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-runtime/+bug/1851573/+subscriptions

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

[Bug 1884033] [NEW] initramfs-tools

2020-06-18 Thread JOSE ANGEL FERMOSELL
Public bug reported:

2020-06-18 09:52:28,921 ERROR got an error from dpkg for pkg: 
'initramfs-tools': 'installed initramfs-tools package post-installation script 
subprocess returned error exit status 1'
2020-06-18 09:52:28,921 DEBUG running apport_pkgfailure() initramfs-tools: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
2020-06-18 09:52:32,418 ERROR Exception during pm.DoInstall()
Traceback (most recent call last):
  File "/tmp/ubuntu-release-upgrader-6xnl7bxz/DistUpgrade/DistUpgradeView.py", 
line 220, in run
res = pm.do_install(self.writefd)
apt_pkg.Error: E:Sub-process /usr/bin/dpkg returned an error code (1)
2020-06-18 09:52:32,461 ERROR SystemError from cache.commit(): 
installArchives() failed
2020-06-18 09:52:32,462 ERROR found exception: 'E:Sub-process /usr/bin/dpkg 
returned an error code (1)'

# lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04

# apt-cache policy
 500 http://security.ubuntu.com/ubuntu focal-security/universe i386 Packages
 release 
v=20.04,o=Ubuntu,a=focal-security,n=focal,l=Ubuntu,c=universe,b=i386
 origin security.ubuntu.com

** Affects: ubuntu-release-upgrader (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/1884033

Title:
  initramfs-tools

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

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

[Bug 1812680] Re: gre tunnels are down after netplan apply

2020-02-05 Thread Angel Abad
I have the same issue on my gre tunnels.

Thanks!

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

** Changed in: netplan.io (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  gre tunnels are down after netplan apply

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

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

[Bug 1824874] Re: undismissable, unclickable authentication dialog left on screen (top-left corner) after policykit authentication [pushModal: invocation of begin_modal failed]

2020-01-02 Thread Angel D. Segarra
I get this all the time after resuming from sleep, unfortunately with
wayland it's not possible to reload gnome-shell so I have to log out/in
to get rid of it.

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

Title:
  undismissable, unclickable authentication dialog left on screen (top-
  left corner) after policykit authentication [pushModal: invocation of
  begin_modal failed]

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

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

[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]

2019-11-12 Thread Angel D. Segarra
3.34.1+git20191107-1ubuntu1~19.10.1

Confirmed fixed here too.

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview: Object St.Button (0x55aeadeca4a0), has been already
  deallocated ... [workspace.js:695]

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

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

[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview

2019-10-14 Thread Angel D. Segarra
I also reported this upstream https://gitlab.gnome.org/GNOME/gnome-
shell/issues/1791

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview

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

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

[Bug 1848119] Re: gnome-shell infinite error loop when closing app in activities overview

2019-10-14 Thread Angel D. Segarra
There's nothing in /var/crash related to this. I guess I associated
stack traces with crashes, perhaps error is the appropriate description
here. I've edited the title and description to reflect this.

** Summary changed:

- gnome-shell infinite crash loop when closing app in activities overview
+ gnome-shell infinite error loop when closing app in activities overview

** Description changed:

  Ubuntu 19.10 on Xorg
  gnome-shell 3.34.1-1ubuntu1
  
  How to reproduce:
  1) Open terminal and watch journalct -f
  2) Open Files
  3) Close Files in the activities overview
- 4) gnome-shell loop crashes non stop.
- 
+ 4) gnome-shell errors in journal non stop.
  
  Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), 
has been already deallocated — impossible to get any property from it. This 
might be caused by the object having been destroyed from C code using something 
such as destroy(), dispose(), or remove() vfuncs.
  Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
  Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
  Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   
self-hosted:975 (7f438c12dee0 @ 392)

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

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

Title:
  gnome-shell infinite error loop when closing app in activities
  overview

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

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

[Bug 1848119] [NEW] gnome-shell infinite crash loop when closing app in activities overview

2019-10-14 Thread Angel D. Segarra
Public bug reported:

Ubuntu 19.10 on Xorg
gnome-shell 3.34.1-1ubuntu1

How to reproduce:
1) Open terminal and watch journalct -f
2) Open Files
3) Close Files in the activities overview
4) gnome-shell loop crashes non stop.


Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has 
been already deallocated — impossible to get any property from it. This might 
be caused by the object having been destroyed from C code using something such 
as destroy(), dispose(), or remove() vfuncs.
Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 
0x55aead0b5360 ==
Oct 14 23:25:38 titan gnome-shell[9919]: #0   55aeae6f3910 i   
resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15)
Oct 14 23:25:38 titan gnome-shell[9919]: #1   7ffd96c5e360 b   self-hosted:975 
(7f438c12dee0 @ 392)

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

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

Title:
  gnome-shell infinite crash loop when closing app in activities
  overview

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

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

[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

2019-09-16 Thread Angel D. Segarra
Getting this on 19.04

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

Title:
  Unrecoverable failure in required component
  org.gnome.SettingsDaemon.Color.desktop

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

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

[Bug 1820617] Re: subiquity install fails: kernel modules not found

2019-06-28 Thread Angel Cervera Claudio
Working: ubuntu-18.04.2-server-amd64.iso
BUG: ubuntu-18.04.2-live-server-amd64.iso

So looks like the problem is the "live" installer. I suppose that the
same scenery with 19.04

How to reopen the BUG?

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

Title:
  subiquity install fails: kernel modules not found

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

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

[Bug 1820617] Re: subiquity install fails: kernel modules not found

2019-06-27 Thread Angel Cervera Claudio
I understand that the bug has been fixed and released, but the problem
is still present in 19.04-live-server-amd64 and 18.04.2-live-server-
amd64

Is this bug really fixed?

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

Title:
  subiquity install fails: kernel modules not found

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

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

[Bug 1820617] Re: subiquity install fails: kernel modules not found

2019-06-27 Thread Angel Cervera Claudio
Workaround to be able to install in the meantime?

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

Title:
  subiquity install fails: kernel modules not found

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

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

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

2019-05-02 Thread Angel Vargas
Currently trying to get charm ceph-radosgw  rev 268, Ubuntu Bionic,
OpenStack Stein (base bundle like)

I'm having the issue where the service seems running, then after few
minutes the unit change to blocked and report the service is not
running, this is in a baremetal deployment with multiples network spaces
(handled by maas).

For this charm I deployed using single commands per unit required:


juju deploy --to lxd:0 --config ceph-radosgw.yaml ceph-radosgw --bind="public 
admin=admin cluster=cluster internal=internal public=public"

then the config file looks like:
---
ceph-radosgw:
  ceph-osd-replication-count: 2
  cache-size: 1200
  os-admin-network: 10.101.0.0/24
  os-internal-network: 10.50.0.0/24
  os-public-network: 10.100.0.0/24
  vip: 10.100.0.210 10.101.0.210 10.50.0.210
  pool-prefix: sc
  source: 'cloud:bionic-stein'

juju shows this:

ceph-radosgw/0*   blocked   idle   0/lxd/0  10.100.0.64 80/tcp  
Services not running that should be: 
ceph-rado...@rgw.juju-a2d93a-0-lxd-0
  ha-radosgw/0*   activeexecuting   10.100.0.64 
Unit is ready and clustered
ceph-radosgw/1blocked   executing  6/lxd/0  10.100.0.77 80/tcp  
Services not running that should be: 
ceph-rado...@rgw.juju-a2d93a-6-lxd-0
  ha-radosgw/1activeidle10.100.0.77 
Unit is ready and clustered
ceph-radosgw/2blocked   executing  1/lxd/3  10.100.0.78 80/tcp  
Services not running that should be: 
ceph-rado...@rgw.juju-a2d93a-1-lxd-3


then going to each LXD container and checking the service I got this output in 
every unit:


ubuntu@juju-a2d93a-0-lxd-0:~$ sudo service jujud-unit-ceph-radosgw-0 status
● jujud-unit-ceph-radosgw-0.service - juju unit agent for ceph-radosgw/0
   Loaded: loaded 
(/lib/systemd/system/jujud-unit-ceph-radosgw-0/jujud-unit-ceph-radosgw-0.service;
 enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-05-02 19:59:07 UTC; 2h 2min ago
 Main PID: 3820 (bash)
Tasks: 67 (limit: 7372)
   CGroup: /system.slice/jujud-unit-ceph-radosgw-0.service
   ├─3820 bash 
/lib/systemd/system/jujud-unit-ceph-radosgw-0/exec-start.sh
   └─3824 /var/lib/juju/tools/unit-ceph-radosgw-0/jujud unit --data-dir 
/var/lib/juju --unit-name ceph-radosgw/0 --debug

May 02 21:57:27 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:14 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:15 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:15 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:15 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:15 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:15 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:24 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:27 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted
May 02 22:00:27 juju-a2d93a-0-lxd-0 systemd[1]: 
jujud-unit-ceph-radosgw-0.service: Failed to reset devices.list: Operation not 
permitted


then run this command: 


ubuntu@juju-a2d93a-0-lxd-0:~$ sudo service ceph-rado...@rgw.juju-a2d93a-6-lxd-0 
status
● ceph-rado...@rgw.juju-a2d93a-6-lxd-0.service - Ceph rados gateway
   Loaded: loaded (/lib/systemd/system/ceph-radosgw@.service; indirect; vendor 
preset: enabled)
   Active: inactive (dead)


Is there some workaround for this issue? 

juju unit log: /var/log/juju/unit-ceph-radosgw-0.log

https://paste.ubuntu.com/p/RhFcHSmx3B/


Thanks guys

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

Title:
  systemd issues with bionic-rocky causing nagios alert and can't
  restart daemon

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions

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

[Bug 1734095] Re: Software & Updates not showing authorization popup [gnome-shell[N]: pushModal: invocation of begin_modal failed]

2019-04-23 Thread Angel D. Segarra
I can also reproduce this reliably in Disco. I tried to enable Canonical
Partner packages so I think it's easy to trigger.

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

Title:
  Software & Updates not showing authorization popup [gnome-shell[N]:
  pushModal: invocation of begin_modal failed]

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

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

[Bug 1825623] Re: [AppIndicatorSupport-FATAL] unable to update overlay icon

2019-04-23 Thread Angel D. Segarra
I see this error in the logs.

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

Title:
  [AppIndicatorSupport-FATAL] unable to update overlay icon

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

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

[Bug 1825585] Re: Application / Document search does not close when the "Put Windows" extension is installed

2019-04-23 Thread Angel Aguilera
I had the same issue without the "Put Windows" extension.

Anyway, I had the "Workspace Grid" extension, and it seems the same
workaround (disable/enable the extension) applies:
https://askubuntu.com/questions/1135465/unable-to-close-applications-
after-update-to-19-04

I have not been able to check if this works, because finally I
reinstalled the system from scratch (previously I had release-upgraded
from 18.10 to 19.04), and the issue has not affected me since then.

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

Title:
  Application / Document search does not close when the "Put Windows"
  extension is installed

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

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

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

2019-04-23 Thread Angel Vargas
@james-page

In my case, after the upgrade the charm unit showed running, but the
openstack api/horizon wasn't able to talk to the service, we went to the
logs and there wasn't obvious information telling why the service wasn't
up, only from the juju controller logs we saw for some reason the
radosgw was going to failed state, after reboot the container, the
service wasn't starting, so we decide to deploy a lean openstack-base
r59 (bionic-stein) bundle as usual, so the charm was showing the exact
same problem/behavior. Not sure what is wrong with the update we did, to
get back radosgw working we have to downgrade to (bionic-rocky):

ceph-mon   13.2.4+dfsg1  active   3  ceph-mon   
jujucharms   32  ubuntu
ceph-osd   13.2.4+dfsg1  active   3  ceph-osd   
jujucharms  275  ubuntu
ceph-radosgw   13.2.4+dfsg1  active   1  ceph-radosgw   
jujucharms  263  ubuntu


And we got the services up again. We are currently working to fix the 
production environment. 


When I wrote first time, I thought the initial way how the bug affect us was 
related to the current report.

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

Title:
  systemd issues with bionic-rocky causing nagios alert and can't
  restart daemon

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions

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

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

2019-04-22 Thread Angel Vargas
We upgraded the charms and radosgw got broken, ceph-radosgw release 267.


After hours of debugging, We decided to test a fresh 4 node deployment to 
investigate the problem and try to revert, deploying a fresh openstack base 
juju is showing:


ceph-radosgw/0*   blocked   idle   0/lxd/0  10.100.0.61 80/tcp  
Services not running that should be: 
ceph-rado...@rgw.juju-168b18-0-lxd-0

if we do a restart to the lxd container, when we execute:

sudo service radosgw status

we get:


Apr 23 00:18:05 juju-168b18-0-lxd-0 radosgw[36885]: Starting 
client.rgw.juju-168b18-0-lxd-0...
Apr 23 00:18:05 juju-168b18-0-lxd-0 systemd[1]: Started LSB: radosgw RESTful 
rados gateway.
Apr 23 00:19:22 juju-168b18-0-lxd-0 systemd[1]: Stopping LSB: radosgw RESTful 
rados gateway...
Apr 23 00:19:22 juju-168b18-0-lxd-0 systemd[1]: Stopped LSB: radosgw RESTful 
rados gateway.
Apr 23 00:19:26 juju-168b18-0-lxd-0 systemd[1]: radosgw.service: Failed to 
reset devices.list: Operation not permitted
Apr 23 00:19:26 juju-168b18-0-lxd-0 systemd[1]: Starting LSB: radosgw RESTful 
rados gateway...
Apr 23 00:19:26 juju-168b18-0-lxd-0 radosgw[37618]: Starting 
client.rgw.juju-168b18-0-lxd-0...
Apr 23 00:19:26 juju-168b18-0-lxd-0 systemd[1]: Started LSB: radosgw RESTful 
rados gateway.
Apr 23 00:21:48 juju-168b18-0-lxd-0 systemd[1]: Stopping LSB: radosgw RESTful 
rados gateway...
Apr 23 00:21:49 juju-168b18-0-lxd-0 systemd[1]: Stopped LSB: radosgw RESTful 
rados gateway.


that's the output after a fresh boot, then if we do:

sudo service radosgw start

we get the service running:

● radosgw.service - LSB: radosgw RESTful rados gateway
   Loaded: loaded (/etc/init.d/radosgw; generated)
   Active: active (running) since Tue 2019-04-23 00:22:47 UTC; 17min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 811 ExecStart=/etc/init.d/radosgw start (code=exited, 
status=0/SUCCESS)
Tasks: 582 (limit: 7372)
   CGroup: /system.slice/radosgw.service
   └─850 /usr/bin/radosgw -n client.rgw.juju-168b18-0-lxd-0

Apr 23 00:22:46 juju-168b18-0-lxd-0 systemd[1]: Starting LSB: radosgw RESTful 
rados gateway...
Apr 23 00:22:46 juju-168b18-0-lxd-0 radosgw[811]: Starting 
client.rgw.juju-168b18-0-lxd-0...
Apr 23 00:22:47 juju-168b18-0-lxd-0 systemd[1]: Started LSB: radosgw RESTful 
rados gateway.


but juju still keep showing the unit blocked.


This is the juju log for ceph-radosgw:

https://paste.ubuntu.com/p/kb3g9XZ7nb/

We are getting the same behaviour in our production and test
environment. Even if we get the service running, the unit doesn't seem
to work from the openstack perspective, e.g. try to create a bucket the
api doesn't connect.

How can I help?

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

Title:
  systemd issues with bionic-rocky causing nagios alert and can't
  restart daemon

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions

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

[Bug 1821545] [NEW] package bash 4.3-14ubuntu1 failed to install/upgrade: package bash is already installed and configured

2019-03-24 Thread Francisco Angel Javier Prieto
Public bug reported:

when install ever fatal error with idle-python3.5
I have Raspberry pi 3

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bash 4.3-14ubuntu1
Uname: Linux 4.1.19-v7+ armv7l
ApportVersion: 2.20.1-0ubuntu2
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: armhf
Date: Sun Mar 24 19:14:22 2019
ErrorMessage: package bash is already installed and configured
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.10ubuntu1
SourcePackage: dpkg
Title: package bash 4.3-14ubuntu1 failed to install/upgrade: package bash is 
already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package bash 4.3-14ubuntu1 failed to install/upgrade: package bash is
  already installed and configured

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

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

Re: [Bug 1817072] Re: WiFi connnectivity loses

2019-03-06 Thread Raul Angel Gaggioli
Hi Kai, i have not knowledge to prove new kernels on my notebook, sorry.
In my case, was a "dirty solutions" this:On my router:1) Change security to 
WPA2-AES 2) Not any mixed mode, i.e. only "N" mode3) Not auto-channel but set 
to a fixed channelOn my notebook:1) options iwlwifi 11n_disable=8
With this, connection is stable in my home and office but when i am in any 
public place, it depends...
 If this issue is not resolved my next upgrade wil be made with other linux 
distributions. This problem is very upset for the final users, not programmers, 
like me. Sorry again.

Raúl 
El miércoles, 6 de marzo de 2019 08:20:52 ART, Kai-Heng Feng 
 escribió:  
 
 Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v5.0 kernel [0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.0/

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1817072

Title:
  WiFi connnectivity loses

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since I installed ubuntu 18.04 mate, randomly loses wifi connectivity and I 
must constantly disconnect from the wifi network and reconnect to have 
connectivity. From the same machine but booting windows that situation does not 
happen, only when booting Ubuntu.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC0:  raul      2081 F pulseaudio
  /dev/snd/controlC1:  raul      2081 F pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=7f36c93c-4e2b-440d-9a3a-2eab7c53e1e2
  InstallationDate: Installed on 2016-11-18 (825 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX305LA
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a157b67f-c2dc-4d6b-a870-7e3f1d9e5659 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
  linux-restricted-modules-4.15.0-45-generic N/A
  linux-backports-modules-4.15.0-45-generic  N/A
  linux-firmware                            1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-25 (118 days ago)
  UserGroups: adm admin audio cdrom dip fax lp lpadmin netdev plugdev 
sambashare scanner shadow sudo video
  _MarkForUpload: True
  dmi.bios.date: 08/03/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX305LA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX305LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.206:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX305LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

2019-02-28 Thread Angel
Hello, I followed all the instructions and apparently I could install fprint 
correctly. However when I run sudo ./img_capture I got an error message. Also 
is not possible to enroll and fprint_demo cannot fing any device.
I tried to look for the error 903 but the github page is no longer available
I'm running it in ubuntu 18.10 if that helps.
I hope anyone can help me out
The error message is:

(process:3360): libfprint-DEBUG: 20:49:10.427: 161437947: 
../libfprint/fpi-core.c:743
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver upekts
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver upektc
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver upeksonly
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver vcom5s
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver uru4000
(process:3360): libfprint-DEBUG: 20:49:10.432: registered driver aes1610
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes1660
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes2501
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes2550
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes2660
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes3500
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver aes4000
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs101
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs301
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs5011
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver upektc_img
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver etes603
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver vfs0050
(process:3360): libfprint-DEBUG: 20:49:10.433: registered driver elan
(process:3360): libfprint-DEBUG: 20:49:10.433: driver elan supports USB device 
04f3:0c10
(process:3360): libfprint-DEBUG: 20:49:10.433: selected driver elan supports 
USB device 04f3:0c10
Found device claimed by ElanTech Fingerprint Sensor driver
(process:3360): libfprint-sync-DEBUG: 20:49:10.433: 161443813: 
../libfprint/fpi-sync.c:57
(process:3360): libfprint-async-DEBUG: 20:49:10.433: 161443841: 
../libfprint/fpi-async.c:77
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161556427: 
../libfprint/drivers/elan.c:801
(process:3360): libfprint-async-DEBUG: 20:49:10.546: status 0
(process:3360): libfprint-sync-DEBUG: 20:49:10.546: status 0
Opened device. It's now time to scan your finger.

(process:3360): libfprint-sync-DEBUG: 20:49:10.546: to be handled by elan
(process:3360): libfprint-async-DEBUG: 20:49:10.546: 161556723: 
../libfprint/fpi-async.c:577
(process:3360): libfprint-DEBUG: 20:49:10.546: action 4
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161556774: 
../libfprint/drivers/elan.c:849
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161556801: 
../libfprint/drivers/elan.c:788
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161556825: 
../libfprint/drivers/elan.c:101
(process:3360): libfprint-drv-DEBUG: 20:49:10.546: 0x55677d4c12f0 entering 
state 0
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161556880: 
../libfprint/drivers/elan.c:732
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 4019
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161557110: 
../libfprint/drivers/elan.c:332
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161557187: 
../libfprint/drivers/elan.c:357
(process:3360): libfprint-elan-DEBUG: 20:49:10.546: 161557218: 
../libfprint/drivers/elan.c:378
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161557410: 
../libfprint/drivers/elan.c:332
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 0138
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161557524: 
../libfprint/drivers/elan.c:320
(process:3360): libfprint-drv-DEBUG: 20:49:10.547: 0x55677d4c12f0 entering 
state 1
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161557584: 
../libfprint/drivers/elan.c:732
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: FW ver 0x0138
(process:3360): libfprint-drv-DEBUG: 20:49:10.547: 0x55677d4c12f0 entering 
state 2
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161557659: 
../libfprint/drivers/elan.c:732
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 000c
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161557796: 
../libfprint/drivers/elan.c:332
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161557847: 
../libfprint/drivers/elan.c:357
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161557874: 
../libfprint/drivers/elan.c:378
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161558036: 
../libfprint/drivers/elan.c:332
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 6000... (4 bytes)
(process:3360): libfprint-elan-DEBUG: 20:49:10.547: 161558145: 
../libfprint/drivers/elan.c:320
(process:3360): libfprint-drv-DEBUG: 20:49:10.547: 0x55677d4c12f0 entering 
state 3
(process:3360): 

[Bug 1812095] Re: console login loop after entering username followed by RETURN

2019-02-28 Thread Miguel Angel Blanco Muñpz
*** This bug is a duplicate of bug 1813873 ***
https://bugs.launchpad.net/bugs/1813873

Bug confirmed in Ubuntu 18.04.2 LTS with 4.15.0-45-generic kernel

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

Title:
  console login loop after entering username followed by RETURN

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

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

[Bug 1817072] ProcCpuinfoMinimal.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240702/+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/1817072

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] WifiSyslog.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240709/+files/WifiSyslog.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] PulseList.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240706/+files/PulseList.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] ProcInterrupts.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240704/+files/ProcInterrupts.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] RfKill.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1817072/+attachment/5240707/+files/RfKill.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] ProcCpuinfo.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240701/+files/ProcCpuinfo.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] ProcEnviron.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240703/+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/1817072

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] CRDA.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1817072/+attachment/5240697/+files/CRDA.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] UdevDb.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1817072/+attachment/5240708/+files/UdevDb.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] ProcModules.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240705/+files/ProcModules.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] Lspci.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1817072/+attachment/5240700/+files/Lspci.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] IwConfig.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240699/+files/IwConfig.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] CurrentDmesg.txt

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240698/+files/CurrentDmesg.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] Re: WiFi connnectivity loses

2019-02-21 Thread Raul Angel Gaggioli
apport information

** Tags added: apport-collected bionic

** Description changed:

- Since I installed ubuntu 18.04 mate, randomly loses wifi connectivity
- and I must constantly disconnect from the wifi network and reconnect to
- have connectivity. From the same machine but booting windows that
- situation does not happen, only when booting Ubuntu.
+ Since I installed ubuntu 18.04 mate, randomly loses wifi connectivity and I 
must constantly disconnect from the wifi network and reconnect to have 
connectivity. From the same machine but booting windows that situation does not 
happen, only when booting Ubuntu.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  raul   2081 F pulseaudio
+  /dev/snd/controlC1:  raul   2081 F pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=7f36c93c-4e2b-440d-9a3a-2eab7c53e1e2
+ InstallationDate: Installed on 2016-11-18 (825 days ago)
+ InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 064e:9700 Suyin Corp. Asus Integrated Webcam
+  Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
+  Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. UX305LA
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=a157b67f-c2dc-4d6b-a870-7e3f1d9e5659 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-45-generic N/A
+  linux-backports-modules-4.15.0-45-generic  N/A
+  linux-firmware 1.173.3
+ Tags:  bionic
+ Uname: Linux 4.15.0-45-generic x86_64
+ UpgradeStatus: Upgraded to bionic on 2018-10-25 (118 days ago)
+ UserGroups: adm admin audio cdrom dip fax lp lpadmin netdev plugdev 
sambashare scanner shadow sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 08/03/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: UX305LA.206
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: UX305LA
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX305LA.206:bd08/03/2015:svnASUSTeKCOMPUTERINC.:pnUX305LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: UX
+ dmi.product.name: UX305LA
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1817072/+attachment/5240696/+files/AlsaInfo.txt

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

Title:
  WiFi connnectivity loses

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

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

[Bug 1817072] [NEW] WiFi connnectivity loses

2019-02-21 Thread Raul Angel Gaggioli
Public bug reported:

Since I installed ubuntu 18.04 mate, randomly loses wifi connectivity
and I must constantly disconnect from the wifi network and reconnect to
have connectivity. From the same machine but booting windows that
situation does not happen, only when booting Ubuntu.

** Affects: shim-signed (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/1817072

Title:
  WiFi connnectivity loses

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

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

[Bug 1816691] [NEW] Cannot start Compiz Config Settings Manager

2019-02-19 Thread angel
Public bug reported:

When i try to launch CCSM, i get this error:

x@xx ~]$ccsm
compizconfig - Info: Backend : ini
compizconfig - Info: Integration : true
compizconfig - Info: Profile : default
Traceback (most recent call last):
  File "/usr/bin/ccsm", line 122, in 
mainWin = ccm.MainWin(context, plugin, category)
  File "/usr/lib/python3.7/site-packages/ccm/Window.py", line 55, in __init__
self.MainPage = MainPage(self, self.Context)
  File "/usr/lib/python3.7/site-packages/ccm/Pages.py", line 1209, in __init__
pluginWindow = PluginWindow(self.Context)
  File "/usr/lib/python3.7/site-packages/ccm/Widgets.py", line 1642, in __init__
category_box = CategoryBox(context, category, plugins, i)
  File "/usr/lib/python3.7/site-packages/ccm/Widgets.py", line 1506, in __init__
self._plugins.sort(key=PluginKeyFunc)
  File "src/compizconfig.pyx", line 943, in 
compizconfig.Plugin.ShortDesc.__get__
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 27: 
ordinal not in range(128)

** Affects: compiz (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/1816691

Title:
  Cannot start Compiz Config Settings Manager

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

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

[Bug 1814491] [NEW] i don't know, im new at linux

2019-02-03 Thread Angel
Public bug reported:

i don't  know

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb  4 04:38:36 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=es_ES.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu

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

Title:
  i don't know, im new at linux

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

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

Re: [Bug 1773859] Re: upgrades to 18.04 fail

2019-01-30 Thread juan angel Mora
¡Gracias!

El mié., 30 ene. 2019 a las 12:21, José Enrique (<1773...@bugs.launchpad.net>)
escribió:

> Una cosa.
> Chequea el hardware en ocasiones equipos antiguos rinden mal o no rinden
> con el 18
> Si es un equipo moderno sin problemas.
> También puedes valorar en utilizar escritorios más ligeros con equipos
> antiguos XCFE Xubuntu o LXDE Lubuntu.
> Yo con un equipo de 2007 y 2 GB ejecuto Xubuntu 18-04 sin problemas. Y en
> un Netbook con 1 Giga Lubuntu.
> Recuerda que Lubuntu ya no va a crear versiones de 32 bit a partir de la 18
> 04.
> Saludos
>
> El mar., 29 ene. 2019 22:50, juan angel Mora <1773...@bugs.launchpad.net>
> escribió:
>
> > La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5
> > LTS.
> > Vale la pena actualizarla?
> > Graacias
> >
> >
> > El mar., 29 ene. 2019 a las 22:30, José Enrique (<
> > 1773...@bugs.launchpad.net>)
> > escribió:
> >
> > > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que
> no
> > > quieras perder y actualizarla a 18-04.
> > > Funcionar funciona pero estás a punto de que no se actualice más, y
> > puedes
> > > tener problemas de seguridad, ojo se trata de una actualización
> > importante,
> > > que debes realizar, seguramente en dos pasos, dos actualizaciones
> > > parciales. Primero a 16 y luego a 18-04.
> > > Configura el gestor de actualizaciones a versiones LTS, no obstante la
> > > 18-04 tiene soporte para 10 años.
> > > Saludos
> > >
> > > El mar., 29 ene. 2019 22:15, juan angel Mora <
> 1773...@bugs.launchpad.net
> > >
> > > escribió:
> > >
> > > > Muchas gracias por la información.
> > > > Si no es mucho consultarte, a veces cuando me pide actualizaciones
> las
> > > hago
> > > > y luego me dice que tengo el Ubuntu 14.   , que si lo quiero
> > actualizar a
> > > > la ultima versión 16.   y no lo hago por miedo a que se me desbarate
> > todo
> > > > de nuevo, cual es tu consejo?
> > > > Un saludo
> > > >
> > > >
> > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray ()
> > > > escribió:
> > > >
> > > > > The upload of systemd that was purported to fix this bug report was
> > > > > superseded by a security update of systemd so the fix is no longer
> > > > > available.
> > > > >
> > > > > ** Changed in: systemd (Ubuntu Bionic)
> > > > >Status: Fix Committed => Triaged
> > > > >
> > > > > --
> > > > > You received this bug notification because you are subscribed to a
> > > > > duplicate bug report (1787843).
> > > > > https://bugs.launchpad.net/bugs/1773859
> > > > >
> > > > > Title:
> > > > >   upgrades to 18.04 fail
> > > > >
> > > > > Status in systemd package in Ubuntu:
> > > > >   Fix Released
> > > > > Status in systemd-shim package in Ubuntu:
> > > > >   Won't Fix
> > > > > Status in systemd source package in Bionic:
> > > > >   Triaged
> > > > > Status in systemd-shim source package in Bionic:
> > > > >   Won't Fix
> > > > > Status in systemd source package in Cosmic:
> > > > >   Fix Released
> > > > > Status in systemd-shim source package in Cosmic:
> > > > >   Won't Fix
> > > > >
> > > > > Bug description:
> > > > >   [Impact]
> > > > >
> > > > >* Some systems fail to upgrade due to conflicts between systemd
> > and
> > > > >   the (now removed from the archive) systemd-shim / upstart.
> > > > >
> > > > >* Instead of trying to work out what's the problem in ordering /
> > > > >   removal of diverts, ensure that systemd is never unpacked whilst
> > > > >   systemd-shim/upstart are still on disk. Thus declare conflicts
> > > against
> > > > >   systemd-shim/upstart packages in systemd package.
> > > > >
> > > > >   [Test Case]
> > > > >
> > > > >* monitor drop-off of upgrades with below reported problem
> > > > >
> > > > >* Check that it is possible to upgrade to bionic's
> libpam-systemd
> > > > >   from xenial with systemd-shim installed on xenial, ie.
> > > > >
>

Re: [Bug 1773859] Re: upgrades to 18.04 fail

2019-01-29 Thread juan angel Mora
La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5
LTS.
Vale la pena actualizarla?
Graacias


El mar., 29 ene. 2019 a las 22:30, José Enrique (<1773...@bugs.launchpad.net>)
escribió:

> Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no
> quieras perder y actualizarla a 18-04.
> Funcionar funciona pero estás a punto de que no se actualice más, y puedes
> tener problemas de seguridad, ojo se trata de una actualización importante,
> que debes realizar, seguramente en dos pasos, dos actualizaciones
> parciales. Primero a 16 y luego a 18-04.
> Configura el gestor de actualizaciones a versiones LTS, no obstante la
> 18-04 tiene soporte para 10 años.
> Saludos
>
> El mar., 29 ene. 2019 22:15, juan angel Mora <1773...@bugs.launchpad.net>
> escribió:
>
> > Muchas gracias por la información.
> > Si no es mucho consultarte, a veces cuando me pide actualizaciones las
> hago
> > y luego me dice que tengo el Ubuntu 14.   , que si lo quiero actualizar a
> > la ultima versión 16.   y no lo hago por miedo a que se me desbarate todo
> > de nuevo, cual es tu consejo?
> > Un saludo
> >
> >
> > El lun., 28 ene. 2019 a las 19:35, Brian Murray ()
> > escribió:
> >
> > > The upload of systemd that was purported to fix this bug report was
> > > superseded by a security update of systemd so the fix is no longer
> > > available.
> > >
> > > ** Changed in: systemd (Ubuntu Bionic)
> > >Status: Fix Committed => Triaged
> > >
> > > --
> > > You received this bug notification because you are subscribed to a
> > > duplicate bug report (1787843).
> > > https://bugs.launchpad.net/bugs/1773859
> > >
> > > Title:
> > >   upgrades to 18.04 fail
> > >
> > > Status in systemd package in Ubuntu:
> > >   Fix Released
> > > Status in systemd-shim package in Ubuntu:
> > >   Won't Fix
> > > Status in systemd source package in Bionic:
> > >   Triaged
> > > Status in systemd-shim source package in Bionic:
> > >   Won't Fix
> > > Status in systemd source package in Cosmic:
> > >   Fix Released
> > > Status in systemd-shim source package in Cosmic:
> > >   Won't Fix
> > >
> > > Bug description:
> > >   [Impact]
> > >
> > >* Some systems fail to upgrade due to conflicts between systemd and
> > >   the (now removed from the archive) systemd-shim / upstart.
> > >
> > >* Instead of trying to work out what's the problem in ordering /
> > >   removal of diverts, ensure that systemd is never unpacked whilst
> > >   systemd-shim/upstart are still on disk. Thus declare conflicts
> against
> > >   systemd-shim/upstart packages in systemd package.
> > >
> > >   [Test Case]
> > >
> > >* monitor drop-off of upgrades with below reported problem
> > >
> > >* Check that it is possible to upgrade to bionic's libpam-systemd
> > >   from xenial with systemd-shim installed on xenial, ie.
> > >
> > >   lxc launch ubuntu-daily:xenial test-shim-upgrade
> > >   lxc exec test-shim-upgrade
> > >   apt update
> > >   apt install systemd-shim
> > >   wget
> > >
> >
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
> > >   apt install ./systemd-shim_10-3_amd64.deb
> > >   sed 's/xenial/bionic/' -i /etc/apt/sources.list
> > >   apt update
> > >   apt install systemd
> > >
> > >   this currently passes, however, systemd-shim remains installed. It
> > >   should be removed instead. Apt install systemd should have lines like
> > >   this:
> > >
> > >   The following packages will be REMOVED:
> > > systemd-shim
> > >   ...
> > >   Removing 'diversion of
> > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> > >
> >
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> > > by systemd-shim'
> > >   ...
> > >
> > >
> > >   [Regression Potential]
> > >
> > >* systemd-shim/upstart are both removed and not supported in bionic,
> > >   thus forcing their removal via conflicts should bring the system into
> > >   an expected state.
> > >
> > >   [Other Info]
> > >
> > >* original bug report
> > >
> > >   $ sudo apt upgrade
> > >   Reading package lists

Re: [Bug 1773859] Re: upgrades to 18.04 fail

2019-01-29 Thread juan angel Mora
Muchas gracias por la información.
Si no es mucho consultarte, a veces cuando me pide actualizaciones las hago
y luego me dice que tengo el Ubuntu 14.   , que si lo quiero actualizar a
la ultima versión 16.   y no lo hago por miedo a que se me desbarate todo
de nuevo, cual es tu consejo?
Un saludo


El lun., 28 ene. 2019 a las 19:35, Brian Murray ()
escribió:

> The upload of systemd that was purported to fix this bug report was
> superseded by a security update of systemd so the fix is no longer
> available.
>
> ** Changed in: systemd (Ubuntu Bionic)
>Status: Fix Committed => Triaged
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1787843).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>   upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>   Fix Released
> Status in systemd-shim package in Ubuntu:
>   Won't Fix
> Status in systemd source package in Bionic:
>   Triaged
> Status in systemd-shim source package in Bionic:
>   Won't Fix
> Status in systemd source package in Cosmic:
>   Fix Released
> Status in systemd-shim source package in Cosmic:
>   Won't Fix
>
> Bug description:
>   [Impact]
>
>* Some systems fail to upgrade due to conflicts between systemd and
>   the (now removed from the archive) systemd-shim / upstart.
>
>* Instead of trying to work out what's the problem in ordering /
>   removal of diverts, ensure that systemd is never unpacked whilst
>   systemd-shim/upstart are still on disk. Thus declare conflicts against
>   systemd-shim/upstart packages in systemd package.
>
>   [Test Case]
>
>* monitor drop-off of upgrades with below reported problem
>
>* Check that it is possible to upgrade to bionic's libpam-systemd
>   from xenial with systemd-shim installed on xenial, ie.
>
>   lxc launch ubuntu-daily:xenial test-shim-upgrade
>   lxc exec test-shim-upgrade
>   apt update
>   apt install systemd-shim
>   wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
>   apt install ./systemd-shim_10-3_amd64.deb
>   sed 's/xenial/bionic/' -i /etc/apt/sources.list
>   apt update
>   apt install systemd
>
>   this currently passes, however, systemd-shim remains installed. It
>   should be removed instead. Apt install systemd should have lines like
>   this:
>
>   The following packages will be REMOVED:
> systemd-shim
>   ...
>   Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>   ...
>
>
>   [Regression Potential]
>
>* systemd-shim/upstart are both removed and not supported in bionic,
>   thus forcing their removal via conflicts should bring the system into
>   an expected state.
>
>   [Other Info]
>
>* original bug report
>
>   $ sudo apt upgrade
>   Reading package lists... Done
>   Building dependency tree
>   Reading state information... Done
>   Calculating upgrade... Done
>   The following packages will be REMOVED:
> systemd-shim
>   0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>   1 not fully installed or removed.
>   After this operation, 71.7 kB disk space will be freed.
>   Do you want to continue? [Y/n] y
>   (Reading database ... 63 files and directories currently installed.)
>   Removing systemd-shim (9-1bzr4ubuntu1) ...
>   Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>   dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
> different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
>   dpkg: error processing package systemd-shim (--remove):
>subprocess installed post-removal script returned error exit status 2
>   Errors were encountered while processing:
>systemd-shim
>   E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>   Commenting out the dpkg-divert in systemd-shim's postrm solved this
>   for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
>

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

Title:
  upgrades to 18.04 fail

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

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

[Bug 1809874] Re: multiple server delete produce multiple new lines

2019-01-16 Thread Noam Angel
thanks for correcting indeed it is with flag --wait

fix merged:
https://review.openstack.org/#/c/627493/

** Description changed:

  multiple server delete produce multiple new lines
  
  example:
- openstack server delete fced7819-4d82-400d-bb87-479c5deb854a 
7cadbd07-990d-4525-9ecf-1ec80fc57e92 1f4a75d4-d75e-4c36-a068-df5f1e190256
- 
+ openstack server delete --wait fced7819-4d82-400d-bb87-479c5deb854a 
7cadbd07-990d-4525-9ecf-1ec80fc57e92 1f4a75d4-d75e-4c36-a068-df5f1e190256
  
  #output end#
  
- 
- 
https://github.com/openstack/python-openstackclient/blob/master/openstackclient/compute/v2/server.py#L1007
+ https://github.com/openstack/python-
+ openstackclient/blob/master/openstackclient/compute/v2/server.py#L1007

** Changed in: python-openstackclient
   Status: New => Fix Released

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

Title:
  multiple server delete produce multiple new lines

To manage notifications about this bug go to:
https://bugs.launchpad.net/python-openstackclient/+bug/1809874/+subscriptions

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

[Bug 1809874] [NEW] multiple server delete produce multiple new lines

2018-12-27 Thread Noam Angel
Public bug reported:

multiple server delete produce multiple new lines

example:
openstack server delete fced7819-4d82-400d-bb87-479c5deb854a 
7cadbd07-990d-4525-9ecf-1ec80fc57e92 1f4a75d4-d75e-4c36-a068-df5f1e190256


#output end#


https://github.com/openstack/python-openstackclient/blob/master/openstackclient/compute/v2/server.py#L1007

** Affects: python-openstackclient (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/1809874

Title:
  multiple server delete produce multiple new lines

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

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

[Bug 1809669] [NEW] error unknow-package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar

2018-12-24 Thread Luis Angel Muñoz
Public bug reported:

i can not upgrade ubuntu, it has an error in kernel secure efi boot or
something like that.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1
Uname: Linux 4.19.1-041901-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No existe el archivo o 
el directorio: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 linux-libc-dev:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Dec 23 10:13:27 2018
ErrorMessage: problemas de dependencias - se deja sin configurar
GrubDiff: Los archivos binarios /boot/efi/EFI/ubuntu/grubx64.efi y 
/usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed son distintos
InstallationDate: Installed on 2018-10-02 (83 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SecureBoot: 6   0   0   0   1
SourcePackage: shim-signed
Title: package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed 
to install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to bionic on 2018-11-12 (41 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  error unknow-package shim-signed
  1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

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

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

[Bug 1807437] [NEW] package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status 1

2018-12-07 Thread Angel Delight
Public bug reported:

On startuo I got an error message,three consecutive times now, saying
system failed to load package. Weirdly, another message appears saying
my software is up to date. When I 'x' it. I'm left with the option of
reporting the bug failure, which I'm doing now.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: openssh-server 1:7.6p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
AptOrdering:
 usbmuxd:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Dec  7 19:01:57 2018
ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2016-07-29 (861 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SSHDConfig:
 Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config line 13: Deprecated option UsePrivilegeSeparation
 /etc/ssh/sshd_config line 16: Deprecated option KeyRegenerationInterval
 /etc/ssh/sshd_config line 17: Deprecated option ServerKeyBits
 /etc/ssh/sshd_config line 30: Bad SSH2 mac spec 
'hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-ripemd160-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160,umac-...@openssh.com'.
SourcePackage: openssh
Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-15 (205 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

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

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

[Bug 1805092] [NEW] dbus error running svn

2018-11-26 Thread Angel L. Mateo
Public bug reported:

Whenever I try to run a svn command that needs authentication (a commit
or a clone), I get the error:

amateo@joshua:/tmp$ svn co https://x.um.es/svn/
Authentication realm:  Usuario/contrase?\F1a
Username: XX
Password for 'XX': **

dbus[10163]: arguments to dbus_message_iter_append_basic() were incorrect, 
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file 
../../../dbus/dbus-message.c line 2754.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Abortado (`core' generado)

I'm running ubuntu bionic with subversion 1.9.7-4ubuntu1.

amateo@joshua:/tmp$ lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

** Affects: subversion (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/1805092

Title:
  dbus error running svn

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

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

[Bug 1690085]

2018-11-07 Thread hi-angel
> Has anyone run *BSD or FreeDOS or something else which would allow a Ryzen to
> get bored for hours/days?

Yes, FreeBSD is affected too
https://www.phoronix.com/scan.php?page=news_item=Ryzen-BSD-Lock-
Ups-2018

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

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

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

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

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)

2018-10-29 Thread Angel D. Segarra
I'm sorry, I no longer use Ubuntu on my machines. But I can confirm this
happened to me when the lockscreen is active.

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

Title:
  gnome-shell filling up syslog with thousands of entries with stack
  traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224
  in cosmic)

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

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

[Bug 1799331] [NEW] package phpmyadmin 4:4.6.6-5 failed to install/upgrade: instalado phpmyadmin paquete post-installation guión el subproceso devolvió un error con estado de salida 1

2018-10-22 Thread jose angel alvarado gonzalez
Public bug reported:

al instalar phpmyadmin no me empezo a salir este problema, ya lo
desinstalé pero me sigue apareciendo este mismo error... saludos desde
mexico xd

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: phpmyadmin 4:4.6.6-5
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 mysql-client:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat Oct 20 20:28:39 2018
ErrorMessage: instalado phpmyadmin paquete post-installation guión el 
subproceso devolvió un error con estado de salida 1
InstallationDate: Installed on 2018-10-05 (17 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: phpmyadmin
Title: package phpmyadmin 4:4.6.6-5 failed to install/upgrade: instalado 
phpmyadmin paquete post-installation guión el subproceso devolvió un error con 
estado de salida 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

Title:
  package phpmyadmin 4:4.6.6-5 failed to install/upgrade: instalado
  phpmyadmin paquete post-installation guión el subproceso devolvió un
  error con estado de salida 1

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

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

[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-17 Thread Angel D. Segarra
Apologies, this is indeed still happening in 18.10.

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

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

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

Re: [Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries (stack traces ending in osdWindow.js:206/207)

2018-10-13 Thread Angel D. Segarra
It's been removed from 18.10.

On Thu, Oct 11, 2018 at 9:51 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> Is anyone seeing this bug in Ubuntu 18.10 or is it already fixed there?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1772677
>
> Title:
>   gnome-shell filling up syslog with thousands of entries (stack traces
>   ending in osdWindow.js:206/207)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions
>

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

Title:
  gnome-shell filling up syslog with thousands of entries (stack traces
  ending in osdWindow.js:206/207)

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

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

[Bug 1792702] Re: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it."

2018-10-06 Thread Angel D. Segarra
Same behavior in Gnome 3.30.1 in 18.10 Beta.

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

Title:
  gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout
  (...), has been already finalized. Impossible to set any property to
  it."

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

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

[Bug 1792702] Re: gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout (...), has been already finalized. Impossible to set any property to it."

2018-10-06 Thread Angel D. Segarra
Same behavior, happens when screen is locked, log grew close to 1 GB in
less then 1 hour locked.

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

Title:
  gnome-shell filling /var/log/syslog with "Object St.Icon|BoxLayout
  (...), has been already finalized. Impossible to set any property to
  it."

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

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

[Bug 1579580] Re: ureadahead reports relative path errors in journalctl output

2018-09-10 Thread Angel D. Segarra
I would just remove ureadahead using apt. It's just another canonical
project that nobody has looked at in years and not a priority. I see no
difference whatsoever without it and maybe you won't either.

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

Title:
  ureadahead reports relative path errors in journalctl output

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

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

[Bug 1739468] Re: Repeated [AppIndicatorSupport-WARN] Item :1.51/org/ayatana/NotificationItem/multiload is already registered

2018-09-04 Thread Angel D. Segarra
This problem is compounded by the fact that rsyslog is duplicating
journal logging. Getting huge log files.

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

Title:
  Repeated [AppIndicatorSupport-WARN] Item
  :1.51/org/ayatana/NotificationItem/multiload is already registered

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

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

[Bug 1787843] [NEW] tengo un problema de arranque de equipo, despues de instalar la ultima version de ubuntu

2018-08-19 Thread juan angel Mora
Public bug reported:

Instale la nueva version de Ubuntu, pero al reiniciarse se me quedaba 
ploqueado, lo intente a traves del BIOS pidiendole que me reparase lo que podia 
haber mal y en apariencias fue bien (eso fue ayer), hoy lo vuelvo a encender y 
me vuelve a pasar lo mismo le pido que me identifique el problema y me dice que 
es un problema al instalar el software y que esta en el paquete : systemd-shim 
9-1bzr4ubuntu1 y hasta ahi se, me podrian ayudar?
Agracias

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic i686
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
Date: Fri Aug 17 02:50:45 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2015-09-11 (1073 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-package bionic i386 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/1787843

Title:
  tengo un problema de arranque de equipo, despues de instalar la ultima
  version de ubuntu

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

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

[Bug 1784355] [NEW] Installer crashes installing grub uefi

2018-07-30 Thread Angel L. Mateo
Public bug reported:

While trying to install Ubuntu 18.04 on my system, the installer crashes
trying to install uefi grub.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 30 12:40:24 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=es_ES.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.6 ubuntu

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

Title:
  Installer crashes installing grub uefi

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

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

  1   2   3   4   5   6   7   8   9   10   >