from:"walter"

[Bug 2079836] Re: nvme list shows wrong drive sizes in in Noble

2024-09-06 Thread Walter

** Bug watch added: github.com/linux-nvme/nvme-cli/issues #2260
   https://github.com/linux-nvme/nvme-cli/issues/2260

** Also affects: nvme-utils via
   https://github.com/linux-nvme/nvme-cli/issues/2260
   Importance: Unknown
   Status: Unknown

** Also affects: libnvme (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/2079836

Title:
  nvme list shows wrong drive sizes in in Noble

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvme-utils/+bug/2079836/+subscriptions


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

[Bug 2079836] [NEW] nvme list shows wrong drive sizes in in Noble

2024-09-06 Thread Walter

Public bug reported:

nvme-cli 2.8-1build2 (in Ubuntu/Noble) shows wrong drive sizes. Compare
the following two.

1.16.3 (Ubuntu/Jammy) output:

# nvme list
Node  SN   Model
Namespace Usage  Format   FW Rev  
-  
 - -- 
 
/dev/nvme0n1  82xx Kxxx1T92 
1   0.00   B /   1.92  TB  4 KiB +  0 B   0106
/dev/nvme1n1  23xx Micron_7xxx_Mxx960TFR
1   3.60  GB / 960.20  GB  4 KiB +  0 B   E2MU200 


2.8.2 (Ubuntu/Noble) output:

# nvme list   
Node  Generic   SN   Model  
  Namespace  Usage  Format  
 FW Rev··
- -  
 -- -- 
 
/dev/nvme0n1  /dev/ng0n182xx Kxxx1T92   
  0x1  0.00   B /  15.36  TB  4 KiB +  0 B  
 0106
/dev/nvme1n1  /dev/ng1n123xx 
Micron_7xxx_Mxx960TFR0x1  3.54  GB /   7.68  TB 
 4 KiB +  0 B   E2MU200


The difference is this: 1.92  TB vs 15.36  TB, and 960.20  GB vs 7.68  TB.

The drives did not suddenly get bigger, but the problem is described here:
https://github.com/linux-nvme/nvme-cli/issues/2260
And fixed here:
https://github.com/linux-nvme/libnvme/pull/803/commits/00efe8364b0a

This fix is included in:
https://github.com/linux-nvme/libnvme/releases/tag/v1.9

That is not available in the 2.8 version:

  # nvme --version
  nvme version 2.8 (git 2.8)
  libnvme version 1.8 (git 1.8)

But it should be in the Oracular 2.10 one:

  nvme-cli (2.10-1) sid; urgency=medium
  [...]
* Bumping libnvme build-depends to 1.10.

Suggested patch fixes things, as can be seen here:

  # nvme list -o json | grep -vE 'ModelNumber|SerialNumber' >old
  (switch to 0osso0 patched build)
  # nvme list -o json | grep -vE 'ModelNumber|SerialNumber' >new

  # apt-cache policy libnvme1t64
  libnvme1t64:
Installed: 1.8-3build1+0osso0
Candidate: 1.8-3build1+0osso0
Version table:
   *** 1.8-3build1+0osso0 500
  500 http://ppa.osso.nl/ubuntu noble/osso amd64 Packages
  100 /var/lib/dpkg/status
   1.8-3build1 500
  500 http://apt.osso.nl/ubuntu noble/main amd64 Packages

  # diff -U1000 old new 
  --- old   2024-09-06 14:03:36.981330913 +
  +++ new   2024-09-06 14:03:10.680072465 +
  @@ -1,24 +1,24 @@
   {
 "Devices":[
   {
 "NameSpace":1,
 "DevicePath":"/dev/nvme1n1",
 "GenericPath":"/dev/ng1n1",
 "Firmware":"E2MU200",
 "UsedBytes":3596890112,
  -  "MaximumLBA":1875385008,
  -  "PhysicalSize":7681576992768,
  +  "MaximumLBA":234423126,
  +  "PhysicalSize":960197124096,
 "SectorSize":4096
   },
   {
 "NameSpace":1,
 "DevicePath":"/dev/nvme0n1",
 "GenericPath":"/dev/ng0n1",
 "Firmware":"0106",
 "UsedBytes":0,
  -  "MaximumLBA":3750748848,
  -  "PhysicalSize":15363067281408,
  +  "MaximumLBA":468843606,
  +  "PhysicalSize":1920383410176,
 "SectorSize":4096
   }
 ]
   }

Patch 00efe8364b0.patch is attached.

Summarizing:

ubuntu/jammy - not affected
ubuntu/noble - affected but fixed by 00efe8364b0.patch
ubuntu/oracular - not affected

Cheers,
Walter Doekes
OSSO B.V.

** Affects: nvme-cli (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "00efe8364b0.patch"
   
https://bugs.launchpad.net/bugs/2079836/+attachment/5813992/+files/00efe8364b0.patch

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

Title:
  nvme list shows wrong drive sizes in in Noble

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


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

[Bug 2078813] Re: ipmitool lan print in Noble truncated output

2024-09-05 Thread Walter

Oracular has 1.8.19-7build2:
https://launchpad.net/ubuntu/oracular/+source/ipmitool

So, we have these versions:

- ipmitool_1.8.18-11ubuntu2.1_amd64.deb - from Jammy
- ipmitool_1.8.19-7build1_amd64.deb - from older Noble
- ipmitool_1.8.19-7build2_amd64.deb - current Noble _and_ Oracular
- ipmitool_1.8.19-7build2+0osso0_amd64.deb - OSSO patch
- ipmitool_1.8.19-7ubuntu0.24.04.1~ppa1_amd64.deb - Sergio patch

Let's see what they do:

# echo; for x in ipmitool_1.8.18-11ubuntu2.1_amd64.deb
ipmitool_1.8.19-7build1_amd64.deb ipmitool_1.8.19-7build2_amd64.deb
ipmitool_1.8.19-7build2+0osso0_amd64.deb
ipmitool_1.8.19-7ubuntu0.24.04.1~ppa1_amd64.deb; do dpkg -i $x
>/dev/null 2>&1; echo "[$x]"; ipmitool lan print | wc -l; done

[ipmitool_1.8.18-11ubuntu2.1_amd64.deb]
32
[ipmitool_1.8.19-7build1_amd64.deb]
14
[ipmitool_1.8.19-7build2_amd64.deb]
14
[ipmitool_1.8.19-7build2+0osso0_amd64.deb]
32
[ipmitool_1.8.19-7ubuntu0.24.04.1~ppa1_amd64.deb]
32

14 = bad
32 = good


LGTM.

Walter

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

Title:
  ipmitool lan print in Noble truncated output

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


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

[Bug 2078813] [NEW] ipmitool lan print in Noble truncated output

2024-09-03 Thread Walter

Public bug reported:

ipmitool 1.8.19 (in Ubuntu/Noble) shows a truncated output when doing
'ipmitool lan print'.

This means we're missing fields like "Default Gateway IP".

A diff between the 1.8.18 and 1.8.19 output is as follows:

  --- 1.8.18.txt2024-09-03 15:17:18.280191476 +
  +++ 1.8.19.txt2024-09-03 15:17:23.684191153 +
  @@ -1,32 +1,14 @@
   Set in Progress : Set Complete
   Auth Type Support   : NONE MD2 MD5 PASSWORD 
   Auth Type Enable: Callback : MD2 MD5 PASSWORD 
   : User : MD2 MD5 PASSWORD 
   : Operator : MD2 MD5 PASSWORD 
   : Admin: MD2 MD5 PASSWORD 
   : OEM  : MD2 MD5 PASSWORD 
   IP Address Source   : DHCP Address
   IP Address  : 10.xx.xx.xx
   Subnet Mask : 255.255.255.0
   MAC Address : 3c:xx:xx:xx:xx:22
   SNMP Community String   : public
   IP Header   : TTL=0x00 Flags=0x00 Precedence=0x00 TOS=0x00
   BMC ARP Control : ARP Responses Enabled, Gratuitous ARP Disabled
  -Default Gateway IP  : 10.xx.xx.1
  -Default Gateway MAC : 00:00:00:00:00:00
  -Backup Gateway IP   : 0.0.0.0
  -Backup Gateway MAC  : 00:00:00:00:00:00
  -802.1q VLAN ID  : Disabled
  -802.1q VLAN Priority: 0
  -RMCP+ Cipher Suites : 1,2,3,6,7,8,11,12
  -Cipher Suite Priv Max   : XaaaXXaaaXXaaXX
  -: X=Cipher Suite Unused
  -: c=CALLBACK
  -: u=USER
  -: o=OPERATOR
  -: a=ADMIN
  -: O=OEM
  -Bad Password Threshold  : 3
  -Invalid password disable: yes
  -Attempt Count Reset Int.: 300
  -User Lockout Interval   : 300

The cause is this (seen when adding verbosity with -vvv):

`Get LAN Parameter 'Gratituous ARP Intrvl' command failed: Unknown
(0x80)`

In 1.8.18, that would just return false and continue.

In 1.8.19, we get:

`Get LAN Parameter 'Gratituous ARP Intrvl' command failed: Unsupported
parameter`

And then the output stops.

The breakage is caused by:
https://codeberg.org/IPMITool/ipmitool/commit/351dad24a26f ( lib/ipmi_lanp.c 
line 240 ).

The fix is:
https://codeberg.org/IPMITool/ipmitool/pulls/25
https://codeberg.org/IPMITool/ipmitool/commit/137aeb64cbb4

This fix has not landed in a tagged version yet.

Also reported in debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061770

Cheers,
Walter Doekes
OSSO B.V.

( attached
https://codeberg.org/IPMITool/ipmitool/commit/137aeb64cbb4.patch )

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

** Patch added: "137aeb64cbb4.patch"
   
https://bugs.launchpad.net/bugs/2078813/+attachment/5812878/+files/137aeb64cbb4.patch

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

Title:
  ipmitool lan print in Noble truncated output

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


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

[Bug 2060615] Re: [noble] two versions of perl-modules are published, breaking pbuilder/debootstrap

2024-09-02 Thread Walter

Hi!

I have issues with my debootstrap now:


  debootstrap --arch=amd64 --components='main,restricted,universe' \
  --include="linux-image-generic casper initramfs-tools grub-pc bzip2 
ca-certificates curl ipmitool iputils-ping lsof man-db netcat-openbsd nmap 
patch rsync ssh tcpdump vim ethtool lshw pciutils debootstrap efibootmgr fdisk 
gdisk parted nvme-cli smartmontools cryptsetup dosfstools e2fsprogs hdparm lvm2 
mdadm zfsutils-linux jq python3-pip python3-setuptools python-is-python3 
coreutils pwgen smartmontools nvme-cli hdparm sdparm sg3-utils lldpd" noble 
./build-noble/rootfs

Ends with:

  Errors were encountered while processing:
   libsnmp40t64:amd64
   lldpd
  dpkg: dependency problems prevent configuration of libsnmp40t64:amd64:
   libsnmp40t64:amd64 depends on libperl5.38 (>= 5.38.2); however:
Package libperl5.38 is not installed.

If I add:

 libperl5.38t64

Which provides libperl5.38, then I can bootstrap succesfully.

Is this the same problem? Or something different?

In my case debootstrap seems unable to find something that provides
libperl5.38 at all.

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

Title:
  [noble] two versions of perl-modules are published, breaking
  pbuilder/debootstrap

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


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

[Bug 2078418] [NEW] can't upgrade from 22.04 to 24.04

2024-08-30 Thread Walter Wahl

Public bug reported:

I start the upgrade prozess.
I got a message (in german): It was not possible to install a required package

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.19
ProcVersionSignature: Ubuntu 5.15.0-119.129-generic 5.15.160
Uname: Linux 5.15.0-119-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CrashReports: 640:0:124:175018:2024-08-30 08:25:21.635458659 +0200:2024-08-30 
08:25:21.635458659 +0200:/var/crash/_usr_bin_do-release-upgrade.0.crash
CurrentDesktop: KDE
Date: Fri Aug 30 08:56:50 2024
InstallationDate: Installed on 2022-09-11 (719 days ago)
InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to jammy on 2024-08-30 (0 days ago)
VarLogDistupgradeAptHistorylog:
 Start-Date: 2024-08-30  08:49:54
 Requested-By: walter (1000)
 End-Date: 2024-08-30  08:49:54
VarLogDistupgradeApttermlog:
 Log started: 2024-08-30  08:49:54
 Log ended: 2024-08-30  08:49:54
VarLogDistupgradeTermlog:

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


** Tags: amd64 apport-bug dist-upgrade jammy

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

Title:
  can't upgrade from 22.04 to 24.04

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


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

[Bug 2077938] [NEW] ps SIGABRT with -o something -p 1,2,

2024-08-27 Thread Walter

Public bug reported:

## PROBLEM ##

$ ps -p 1,2,
error: improper list

$ ps -o anything -p 1,2,
free(): invalid pointer
Signal 6 (ABRT) caught by ps (3.3.17).
ps:ps/display.c:70: please report this bug
Aborted (core dumped)


## VERSION ##

$ dpkg -l procps | grep ^ii
ii  procps 2:3.3.17-6ubuntu2.1 amd64/proc file system utilities

$ ps --version
ps from procps-ng 3.3.17


## CAUSE ##

(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737347729344) 
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=140737347729344) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=140737347729344, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
#3  0x77d7c476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#4  0x77d627f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x77dc3676 in __libc_message (action=action@entry=do_abort, 
fmt=fmt@entry=0x77f15b77 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#6  0x77ddacfc in malloc_printerr (str=str@entry=0x77f13744 
"free(): invalid pointer") at ./malloc/malloc.c:5664
#7  0x77ddca44 in _int_free (av=, p=, 
have_lock=0) at ./malloc/malloc.c:4439
#8  0x77ddf453 in __GI___libc_free (mem=) at 
./malloc/malloc.c:3391
#9  0x55565d07 in parse_list (arg=, 
parse_fn=parse_fn@entry=0x555657f0 ) at ps/parser.c:222
#10 0x55566d94 in parse_bsd_option () at ps/parser.c:682
#11 parse_all_options () at ps/parser.c:1122
#12 0xf38d in arg_parse (argv=0x7fffdd58, argc=5) at 
ps/parser.c:1196
#13 main (argc=5, argv=0x7fffdd58) at ps/display.c:682

That's here in ps/parser.c:

parse_error:
  free(buf);
  free(node->u); /* <-- uninitialized memory */
  free(node);
  return err;
}


## FIX ##

Index: procps-3.3.17/ps/parser.c
===
--- procps-3.3.17.orig/ps/parser.c
+++ procps-3.3.17/ps/parser.c
@@ -185,6 +185,7 @@ static const char *parse_list(const char
   /*** prepare to operate ***/
   node = malloc(sizeof(selection_node));
   node->n = 0;
+  node->u = NULL;
   buf = strdup(arg);
   /*** sanity check and count items ***/
   need_item = 1; /* true */


## FIX IN UPSTREAM ##

$ git show f5f843e257daeceaac2504b8957e84f4bf87a8f2
commit f5f843e257daeceaac2504b8957e84f4bf87a8f2
Author: Roman Žilka 
Date:   Thu Aug 10 21:56:00 2023 +0200

ps/parser: parse_list(): int overflow for large arg, free() of
uninit. ptr

$ git describe f5f843e257daeceaac2504b8957e84f4bf87a8f2
v4.0.3-62-gf5f843e2


Patch attached.

Cheers,
Walter Doekes
OSSO B.V.

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

** Patch added: "fix-sigabrt-on-improper-list.patch"
   
https://bugs.launchpad.net/bugs/2077938/+attachment/5809707/+files/fix-sigabrt-on-improper-list.patch

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

Title:
  ps SIGABRT with -o something -p 1,2,

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


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

[Bug 2077795] Re: After a weekly update the nvidia-driver-545 that I used because it was the most reliable stopped working and reverted back to nouveau drivers that barely work

2024-08-26 Thread Walter Tautz

To add to this, I run 22.04 and the kernel as indicated above does indeed NOT 
load the nvidia module
from the version above. Had to revert back to 6.5 kernal.

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

Title:
  After a weekly update the nvidia-driver-545 that I used because it was
  the most reliable stopped working and reverted back to nouveau drivers
  that barely work

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


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

[Bug 2070064] Re: Failed to fetch - Download hangs at 40% and does not finish

2024-08-07 Thread Dylan Walter

Issue is no longer present, not obvious that a change was made.

** Changed in: openjdk-lts (Ubuntu)
   Status: New => Invalid

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

Title:
  Failed to fetch - Download hangs at 40% and does not finish

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


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

[Bug 2070064] Re: Failed to fetch - Download hangs at 40% and does not finish

2024-08-07 Thread Dylan Walter

This appears to have cleared.

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

Title:
  Failed to fetch - Download hangs at 40% and does not finish

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


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

[Bug 1987190] Re: ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

2024-07-19 Thread Walter

Note, the patch also helps if didn't experience issues, but are now
running into old snapshots (created by the ZFS module on Ubuntu kernel
5.4) that are seemingly empty (in .zfs/snapshot/xxx).

I still can't believe Ubuntu hasn't added this trivial patch..

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

Title:
  ZFS unrecoverable error after upgrading from 20.04 to 22.04.1

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


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

[Bug 2064716] Re: gnome-terminal darkened by visual bell during screensaver

2024-07-10 Thread Walter

Should be fixed by:
https://gitlab.gnome.org/GNOME/mutter/-/commit/906920cb333486fd9ecd553cc819e2cd9799da6c

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

Title:
  gnome-terminal darkened by visual bell during screensaver

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


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

[Bug 2064716] Re: gnome-terminal darkened by visual bell during screensaver

2024-07-05 Thread Walter

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

** Also affects: gnome-terminal via
   https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7760
   Importance: Unknown
   Status: Unknown

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

Title:
  gnome-terminal darkened by visual bell during screensaver

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


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

[Bug 2064716] Re: gnome-terminal darkened by visual bell during screensaver

2024-07-04 Thread Walter

** Description changed:

+ Problem: visual bell during screensaver turns terminal very dark with no
+ remedy.
+
+ Reproducing:
+
+ - Settings -> Accessibility -> Hearing -> Visual Alerts -> On
+ (Flash the entire Window)
+
+ - Open a gnome-terminal
+
+ - type: xdg-screensaver activate; printf '\a'
+
+ - Wake up the screensaver, and notice that the window in which there was
+ a bell, is darker.
+
+ Tested and reproduced on:
+
+ - Jammy (2024-06-15)
+ - Noble (2024-07-04)
+
+ -
+ Original ticket below
+ v
+

Symptoms

Sometimes, when coming back to my laptop, and unlocking an existing
GNOME session, I find that my gnome-terminal has turned very dark. I
have found no triggers (other than session unlock) and no fixes to undo
the darkness.

It looks like this:

https://junk.devs.nu/2024/lp2064716-gnome-terminal-turned-dark/gnome-terminal-very-dark-on-the-right.png
(
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+attachment/5774287/+files/gnome-terminal-very-dark-on-the-right.png
)

The window on the right is the one I found after unlocking my GNOME
session. The window on the left was a second terminal I started, which
has the normal brightness.

Using some color picking, I can say that the brightness has been reduced
by 70%-85%.

Here's an animation of the window:

https://junk.devs.nu/2024/lp2064716-gnome-terminal-turned-dark/gnome-terminal-turned-very-dark.webm
(
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+attachment/5774288/+files/gnome-terminal-turned-very-dark.webm
)

The video shows:
- The dark window in a smaller state;
- settings are opened, and switched to bright colors;
- both the good and the bad terminals get lighter, but the bad terminal is
still way too dark;
- moving the window to the right shows a glitch in the glitch where the
bottom-most row has normal colors.

Versions

- Ubuntu Jammy 22.04 (many versions)
- gnome-terminal 3.44.0-1ubuntu1
- libmutter 42.9-0ubuntu7

I thought it might be a Wayland thing, but I switched back to Xorg
recently and the problem wasn't gone. I've not seen this bug with Focal.
And my colleagues haven't seen the bug either.

Followup

I have no idea where to look further. I did some probing with xprop on
the window, that gave me no useful info, and may likely not be relevant
as Wayland is also affected.

Any suggestions to get to the bottom of this is appreciated.

Unfortunately, I don't know how to trigger the bug. I always have
terminals open, and only 1% of the time (ball park) when unlocking does
this occur.

Let me know. Cheers!
Walter Doekes

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

Title:
gnome-terminal darkened by visual bell during screensaver

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

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

[Bug 2070064] [NEW] Failed to fetch - Download hangs at 40% and does not finish

2024-06-21 Thread Dylan Walter

Public bug reported:

It looks like there's an issue of some sort with the openjdk-11-jre-
headless package.  I've tested on 2 Ubuntu 22.04 servers and WSL.  Apt
Update goes through just fine, shows 4 jre-headless updates.  When
installing the get fails with:

Get:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1 [42.5 MB]
Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1
Get:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1 [42.5 MB]
Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1
Get:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1 [42.5 MB]
Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1
Get:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1 [42.5 MB]
Ign:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1
Get:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1 [42.5 MB]
Err:1 http://azure.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
openjdk-11-jre-headless amd64 11.0.23+9-1ubuntu1~22.04.1
  Connection timed out [IP: 52.147.219.192 80]
E: Failed to fetch 
http://azure.archive.ubuntu.com/ubuntu/pool/main/o/openjdk-lts/openjdk-11-jre-headless_11.0.23%2b9-1ubuntu1%7e22.04.1_amd64.deb
  Connection timed out [IP: 52.147.219.192 80]
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

I tried downloading the .deb manually from multiple machines and
browsers, I also attempted to download from archive.ubuntu.com instead
of the azure repo and got the same result.  Downloads about 1/2 and
fails.  If I hold the package the rest of the updates go through fine.

** Affects: openjdk-lts (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/2070064

Title:
  Failed to fetch - Download hangs at 40% and does not finish

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


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

[Bug 2064716] Re: gnome-terminal darkened by visual bell during screensaver

2024-06-16 Thread Walter

** Summary changed:

- gnome-terminal sometimes very dark after gnome unlock
+ gnome-terminal darkened by visual bell during screensaver

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

Title:
  gnome-terminal darkened by visual bell during screensaver

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


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

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-06-15 Thread Walter

Okay. Finally found the reproducer: it's the visual bell during
screensaver.

Attaching a screenshot.

Reproducing:

- Settings -> Accessibility -> Hearing -> Visual Alerts -> On
  (Flash the entire Window)

- Open a gnome-terminal

- type: xdg-screensaver activate; printf '\a'

- Wake up the screensaver, and notice that the window in which there was
a bell, is darker.

Note that changing the Visual Alert to "Flash the entire screen" fixes
the issue.

It tried this just now on a different Ubuntu/Jammy, and the results are
the same; 100% reproducible.


** Attachment added: "Screenshot from 2024-06-15 21-47-11.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+attachment/5789927/+files/Screenshot%20from%202024-06-15%2021-47-11.png

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

Title:
  gnome-terminal sometimes very dark after gnome unlock

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


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

[Bug 2069498] [NEW] (jammy) gdm3 login impossible with fprintd but no libpam-fprintd

2024-06-15 Thread Walter

Public bug reported:

(Note that I'm not using the fingerprint reader.)

If you have:
- fprintd

but not:
- libpam-fprintd

gdm3/pam refuses login.

The following logs are observed at boot:

  dbus-daemon[1928]: [system] Activating via systemd: service 
name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.45' 
(uid=128 pid=2541 comm="/usr/bin/gnome-shell " label="unconfined")
  fprintd[2799]: libusb: error [udev_hotplug_event] ignoring udev action change
  fprintd[2799]: libusb: error [udev_hotplug_event] ignoring udev action change
  dbus-daemon[1928]: [system] Successfully activated service 
'net.reactivated.Fprint'
  systemd[1]: Started Fingerprint Authentication Daemon.

This is seen when a gdm login is attempted:

  gdm-fingerprint][3012]: PAM unable to dlopen(pam_fprintd.so): 
/lib/security/pam_fprintd.so: cannot open shared object file: No such file or 
directory
  gdm-fingerprint][3012]: PAM adding faulty module: pam_fprintd.so
  gdm-fingerprint][3012]: gkr-pam: no password is available for user

Either removing fprintd or installing libpam-fprintd fixes so you can
log in again.


Versions:
- ubuntu 22.04
- gdm3 42.0-1ubuntu7.22.04.4
- fprintd 1.94.2-1ubuntu0.22.04.1
- libpam-fprintd 1.94.2-1ubuntu0.22.04.1

Cheers,
Walter Doekes

** Affects: gdm3 (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/2069498

Title:
  (jammy) gdm3 login impossible with fprintd but no libpam-fprintd

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


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

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-06-11 Thread Walter

Egmont, thanks for your replies.

I've been running this for a few days:

```
gnome-terminal (3.44.0-1ubuntu1wjd0+ubu22.04) jammy; urgency=medium

  * Disable transparency patches:
- 0001-Restore-transparency.patch
- 0001-screen-window-Extra-padding-around-transparent-termi.patch
- scrollbar-background-theming.patch
An attempt to figure out how/why the terminal goes dark sometimes:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716
(LP: #2064716)
```
That is, the Jammy gnome-terminal, but without three patches which seemed to 
relate to transparency.

It hasn't improved things. The darkness bug still exists.

I also haven't found any clues of applications (mis)behaving in the same
timeframe. The CLUTTER_IS_TIMELINE assertions still look most related to
the issue at hand.

Trying to see if I can remove/disable some daemons that I don't need
that are active at the same time...

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

Title:
  gnome-terminal sometimes very dark after gnome unlock

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


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

[Bug 2068737] [NEW] GIMP Crashed on closing while discarding changes

2024-06-07 Thread Walter Perdigao

Public bug reported:

Closed an image I was working on after exporting it as jpeg, closed with
discarding changes and it crashed.

Ubuntu 24.04 LTS
Cinnamon Version 6.0.4
Linux Kernel 6.8.0-31-generic




```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
13.2.0-23ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-13/README.Bugs 
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++,m2 --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-13 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/libexec --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-libstdcxx-backtrace --enable-gnu-unique-object --disable-vtable-verify 
--enable-plugin --enable-default-pie --with-system-zlib 
--enable-libphobos-checking=release --with-target-system-zlib=auto 
--enable-objc-gc=auto --enable-multiarch --disable-werror --enable-cet 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none=/build/gcc-13-uJ7kn6/gcc-13-13.2.0/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-13-uJ7kn6/gcc-13-13.2.0/debian/tmp-gcn/usr
 --enable-offload-defaulted --without-cuda-driver --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) 

# Libraries #
using babl version 0.1.108 (compiled against version 0.1.108)
using GEGL version 0.4.48 (compiled against version 0.4.48)
using GLib version 2.80.0 (compiled against version 2.80.0)
using GdkPixbuf version 2.42.10 (compiled against version 2.42.10)
using GTK+ version 2.24.33 (compiled against version 2.24.33)
using Pango version 1.52.1 (compiled against version 1.52.1)
using Fontconfig version 2.15.0 (compiled against version 2.15.0)
using Cairo version 1.18.0 (compiled against version 1.18.0)

```
> fatal error: Segmentation fault

Stack trace:
```

# Stack traces obtained from PID 11312 - Thread 11312 #


This GDB supports auto-downloading debuginfo from the following URLs:
  
Enable debuginfod for this session? (y or [n]) [answered N; input not from 
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[New LWP 12014]
[New LWP 11899]
[New LWP 11744]
[New LWP 11448]
[New LWP 11359]
[New LWP 11358]
[New LWP 11357]
[New LWP 11327]
[New LWP 11326]
[New LWP 11325]
[New LWP 11324]
[New LWP 11323]
[New LWP 11322]
[New LWP 11321]
[New LWP 11320]
[New LWP 11319]
[New LWP 11318]
[New LWP 11317]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x7d658c91ba9a in __GI___libc_read (nbytes=256, buf=0x7ffe7ac81bb0, fd=15) 
at ../sysdeps/unix/sysv/linux/read.c:26
  Id   Target IdFrame 
* 1Thread 0x7d658c2f9640 (LWP 11312) "gimp-2.10"0x7d658c91ba9a in 
__GI___libc_read (nbytes=256, buf=0x7ffe7ac81bb0, fd=15) at 
../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7d655fe006c0 (LWP 12014) "swap writer"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7d655da006c0 (LWP 11899) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  4Thread 0x7d655f4006c0 (LWP 11744) "gimp-2.10"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  5Thread 0x7d65690006c0 (LWP 11448) "async"syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7d6575a006c0 (LWP 11359) "gdbus"0x7d658c91b4cd in 
__GI___poll (fds=0x7d6538000b90, nfds=3, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  7Thread 0x7d65764006c0 (LWP 11358) "gmain"0x7d658c91b4cd in 
__GI___poll (fds=0x5d14bee8df70, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  8Thread 0x7d6576e006c0 (LWP 11357) "pool-spawner" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  9Thread 0x7d6577e006c0 (LWP 11327) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  10   Thread 0x7d6580c006c0 (LWP 11326) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  11   Thread 0x7d65816006c0 (LWP 11325) "worker"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  12   Thread 0x7d65820006c0 (

[Bug 2067078] [NEW] Translation: Presence of % in strings confuses Launchpad

2024-05-24 Thread Walter Garcia-Fontes

Public bug reported:

There are some "%" in the strings to be translated that are confused as
macros, generating an error when the translation is saved. Check for
instance the following string:

https://translations.launchpad.net/ubuntu/noble/+source/snapd/+pots/snappy/ca/+translate?batch=10&show=all&search=%25+o

In the sixth paragraph, there is:

...
it to 50% means that the quota group...
...

and "% m" is interpreted as a macro, if it is not translated with a word
starting with "m" after this %, the string is not saved and Launchpad
says that the macros don't coincide.

Something should be done because it is not always possible to find a
matching word starting with "m" in another language, and this is not
actually a macro.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: snapd 2.62+24.04build1
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 16:17:53 2024
InstallationDate: Installed on 2015-10-17 (3142 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: snapd
UpgradeStatus: Upgraded to noble on 2024-04-15 (39 days ago)

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


** Tags: amd64 apport-bug noble

** Description changed:

- There are some "%" in the string to be translated that are confused as
+ There are some "%" in the strings to be translated that are confused as
  macros, generating an error when the translation is saved. Check for
  instance the following string:
  
  
https://translations.launchpad.net/ubuntu/noble/+source/snapd/+pots/snappy/ca/+translate?batch=10&show=all&search=%25+o
  
  In the sixth paragraph, there is:
  
  ...
  it to 50% means that the quota group...
  ...
  
  and "% m" is interpreted as a macro, if it is not translated with a word
  starting with "m" after this %, the string is not saved and Launchpad
  says that the macros don't coincide.
  
  Something should be done because it is no always possible to find a
  matching word starting with "m" in another language, and this is not
  actually a macro.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: snapd 2.62+24.04build1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 24 16:17:53 2024
  InstallationDate: Installed on 2015-10-17 (3142 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to noble on 2024-04-15 (39 days ago)

** Description changed:

  There are some "%" in the strings to be translated that are confused as
  macros, generating an error when the translation is saved. Check for
  instance the following string:
  
  
https://translations.launchpad.net/ubuntu/noble/+source/snapd/+pots/snappy/ca/+translate?batch=10&show=all&search=%25+o
  
  In the sixth paragraph, there is:
  
  ...
  it to 50% means that the quota group...
  ...
  
  and "% m" is interpreted as a macro, if it is not translated with a word
  starting with "m" after this %, the string is not saved and Launchpad
  says that the macros don't coincide.
  
- Something should be done because it is no always possible to find a
+ Something should be done because it is not always possible to find a
  matching word starting with "m" in another language, and this is not
  actually a macro.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: snapd 2.62+24.04build1
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 24 16:17:53 2024
  InstallationDate: Installed on 2015-10-17 (3142 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to noble on 2024-04-15 (39 days ago)

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

Title:
  Translation: Presence of % in strings confuses Launchpad

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


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

[Bug 2057687] Re: systemctl hibernate error: "Call to Hibernate failed: Invalid argument"

2024-05-03 Thread Steven Walter

The issue seems to be that /sys/power/resume contains 0:0, rather than
the major:minor of the hibernate device.  If I manually populate
/sys/power/resume, then I can "systemctl hibernate" successfully and
successfully resume.

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

Title:
  systemctl hibernate error: "Call to Hibernate failed: Invalid
  argument"

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


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

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-05-03 Thread Walter

Well. I got some luck in reproducing. Got it twice today (23:14:03 and
23:40:51), and these log messages were seen right around when the screen
locked:

$ journalctl --user  -S '-2 days' | grep CLUTTER -A2

mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: invalid (NULL) pointer instance
mei 02 19:10:18 wortel.kiwi gnome-shell[21305]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
--
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: invalid (NULL) pointer instance
mei 03 23:14:03 wortel.kiwi gnome-shell[21305]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
--
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: invalid (NULL) pointer instance
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed

In fact, I know what I was doing:

2024-05-03 23:40:45 sleep 5; start-vpn
2024-05-03 23:42:44 history | tail -n10


Somewhere around 23:40:48 I locked the screen, and at 23:40:50+ code started 
running that triggers a (maybe) GUI notification popup.

Full disclosure, that VPN notification popup is mine:
https://github.com/ossobv/openvpn-u2f-setup/blob/main/openvpn-u2f-ask-password


I'm not entirely sure what the sequence of events is here, but those dbus/glib 
interactions around the time when things break are too much of a coincidence. 
This also explains why I'm the only one having this issue.


mei 03 23:40:51 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG: Got 
pyinotify event
mei 03 23:40:51 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. 
is_in_screensaver org.gnome.ScreenSaver True
mei 03 23:40:51 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. Ignoring 
ask-password request because in screensaver mode
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_auto_reverse: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: 
clutter_timeline_set_repeat_count: assertion 'CLUTTER_IS_TIMELINE (timeline)' 
failed
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: invalid (NULL) pointer instance
mei 03 23:40:51 wortel.kiwi gnome-shell[362660]: g_signal_connect_data: 
assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
mei 03 23:42:18 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG: Re-reading 
/run/systemd/ask-password
mei 03 23:42:18 wortel.kiwi dbus-daemon[362531]: [session uid=1000 pid=362531] 
Activating service name='org.freedesktop.FileManager1' requested by ':1.28' 
(uid=1000 pid=362660 comm="/usr/bin/gnome-shell " label="unconfined")
mei 03 23:42:18 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. 
is_in_screensaver org.gnome.ScreenSaver True
mei 03 23:42:18 wortel.kiwi openvpn-u2f-ask-password[364589]: DEBUG. Ignoring 
ask-password request because in screensaver mode
mei 03 23:42:18 wortel.kiwi ubuntu-appindicat...@ubuntu.com[362660]: unable to 
update icon for software-update-available
mei 03 23:42:18 wortel.kiwi ubuntu-appindicat...@ubuntu.com[362660]: unable to 
update icon for livepatch
mei 03 23:42:18 wortel.kiwi dbus-daemon[362531]: [session uid=1000 pid=362531] 
Successfully activated service 'org.freedesktop.FileManager1'
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Can't update stage views actor 
[:0x57eecffe8350] is on because it needs an 
allocation.
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Can't update stage views actor 
[:0x57eed23232f0] is on because it needs an 
allocation.
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Can't update stage views actor 
[:0x57eed2324db0] is on because it needs an 
allocation.
mei 03 23:42:18 wortel.kiwi dbus-daemon[362531]: [session uid=1000 pid=362531] 
Activating service name='org.gnome.ArchiveManager1' requested by ':1.97' 
(uid=1000 pid=364706 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" 
label="un>
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
mei 03 23:42:18 wortel.kiwi gnome-shell[362660]:

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-05-03 Thread Walter

Good question. I did in fact try that:

- In Unnamed profile -> Colors;
- the "Use transparency from system theme" was ticked, but there is no 
transparency.
- I unticked it, and and clicked "Use transparent background", and then it was 
transparent -- still dark though.

I also tried:

xprop -f _NET_WM_WINDOW_OPACITY 32c -set _NET_WM_WINDOW_OPACITY
0x7fff

Which made it 50% transparent. And then 0x0 which hid the window
entirely and then 0x to make it opaque again.

Alas, no change in darkness.

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

Title:
  gnome-terminal sometimes very dark after gnome unlock

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


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

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-05-03 Thread Walter

** Description changed:

Symptoms

It looks like this:

- https://junk.devs.nu/2024/lp0-gnome-terminal-turned-dark/gnome-terminal-
- very-dark-on-the-right.png
+
https://junk.devs.nu/2024/lp2064716-gnome-terminal-turned-dark/gnome-terminal-very-dark-on-the-right.png
+ (
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+attachment/5774287/+files/gnome-terminal-very-dark-on-the-right.png
)

The window on the right is the one I found after unlocking my GNOME
session. The window on the left was a second terminal I started, which
has the normal brightness.

Using some color picking, I can say that the brightness has been reduced
by 70%-85%.

Here's an animation of the window:

- https://junk.devs.nu/2024/lp0-gnome-terminal-turned-dark/gnome-terminal-
- turned-very-dark.webm
+
https://junk.devs.nu/2024/lp2064716-gnome-terminal-turned-dark/gnome-terminal-turned-very-dark.webm
+ (
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+attachment/5774288/+files/gnome-terminal-turned-very-dark.webm
)

Versions

- Ubuntu Jammy 22.04 (many versions)
- gnome-terminal 3.44.0-1ubuntu1
- libmutter 42.9-0ubuntu7

I thought it might be a Wayland thing, but I switched back to Xorg
recently and the problem wasn't gone. I've not seen this bug with Focal.
And my colleagues haven't seen the bug either.
-

Followup

I have no idea where to look further. I did some probing with xprop on
the window, that gave me no useful info, and may likely not be relevant
as Wayland is also affected.

Any suggestions to get to the bottom of this is appreciated.

Unfortunately, I don't know how to trigger the bug. I always have
terminals open, and only 1% of the time (ball park) when unlocking does
this occur.

Let me know. Cheers!
Walter Doekes

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

Title:
gnome-terminal sometimes very dark after gnome unlock

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

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

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-05-03 Thread Walter

** Attachment added: 
"https://junk.devs.nu/2024/lp0-gnome-terminal-turned-dark/gnome-terminal-turned-very-dark.webm";
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+attachment/5774288/+files/gnome-terminal-turned-very-dark.webm

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

Title:
  gnome-terminal sometimes very dark after gnome unlock

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


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

[Bug 2064716] [NEW] gnome-terminal sometimes very dark after gnome unlock

2024-05-03 Thread Walter

Public bug reported:


Symptoms


Sometimes, when coming back to my laptop, and unlocking an existing
GNOME session, I find that my gnome-terminal has turned very dark. I
have found no triggers (other than session unlock) and no fixes to undo
the darkness.

It looks like this:

https://junk.devs.nu/2024/lp0-gnome-terminal-turned-dark/gnome-terminal-
very-dark-on-the-right.png

The window on the right is the one I found after unlocking my GNOME
session. The window on the left was a second terminal I started, which
has the normal brightness.

Using some color picking, I can say that the brightness has been reduced
by 70%-85%.

Here's an animation of the window:

https://junk.devs.nu/2024/lp0-gnome-terminal-turned-dark/gnome-terminal-
turned-very-dark.webm

The video shows:
- The dark window in a smaller state;
- settings are opened, and switched to bright colors;
- both the good and the bad terminals get lighter, but the bad terminal is 
still way too dark;
- moving the window to the right shows a glitch in the glitch where the 
bottom-most row has normal colors.



Versions


- Ubuntu Jammy 22.04 (many versions)
- gnome-terminal 3.44.0-1ubuntu1
- libmutter 42.9-0ubuntu7

I thought it might be a Wayland thing, but I switched back to Xorg
recently and the problem wasn't gone. I've not seen this bug with Focal.
And my colleagues haven't seen the bug either.



Followup


I have no idea where to look further. I did some probing with xprop on
the window, that gave me no useful info, and may likely not be relevant
as Wayland is also affected.

Any suggestions to get to the bottom of this is appreciated.

Unfortunately, I don't know how to trigger the bug. I always have
terminals open, and only 1% of the time (ball park) when unlocking does
this occur.

Let me know. Cheers!
Walter Doekes

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

Title:
  gnome-terminal sometimes very dark after gnome unlock

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


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

[Bug 2064716] Re: gnome-terminal sometimes very dark after gnome unlock

2024-05-03 Thread Walter

** Attachment added: 
"https://junk.devs.nu/2024/lp0-gnome-terminal-turned-dark/gnome-terminal-very-dark-on-the-right.png";
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2064716/+attachment/5774287/+files/gnome-terminal-very-dark-on-the-right.png

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

Title:
  gnome-terminal sometimes very dark after gnome unlock

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


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

[Bug 2056205] Re: Noble: Nautilus does't show available network shared folders

2024-03-05 Thread Walter Ribeiro

** Summary changed:

- Noble: Nautilus does't show available resources in network
+ Noble: Nautilus does't show available network shared folders

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

Title:
  Noble: Nautilus does't show available network shared folders

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


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

[Bug 2056205] [NEW] Noble: Nautilus does't show available resources in network

2024-03-05 Thread Walter Ribeiro

Public bug reported:

I have 3 Ubuntu machines on my home network. Two of them with 22.04 and this 
one with Noble.
On both computers with 22.04, Nautilus shows network shared folders, which I 
can access, read and write, according to the permission settings. But in Noble, 
network shared folders are not shown.
I try to access using "Connect to server" in the bottom panel, when I type 
"smb:" the text turns red and it doesn't work either.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: nautilus 1:46~beta-0ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  5 14:07:32 2024
GsettingsChanges: b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' 
b'true'
InstallationDate: Installed on 2024-02-20 (14 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240116)
ProcEnviron:
 LANG=pt_BR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:
 file-roller   43.1-1
 nautilus-extension-gnome-terminal 3.51.90-1ubuntu1

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


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

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

Title:
  Noble: Nautilus does't show available resources in network

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


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

Re: [Bug 2055162] Re: linux-headers package not being pulled in with linux-image-generic

2024-02-28 Thread Walter Tautz

I had removed the linux-generic package in the past since, presumably, it
is "optional". I have made a point of reinstalling it. Hopefully this will
correct the issue where
I had to install the correct header package AFTER the kernel package had
been updated. Unfortunately this causes the nvidia kernel module to be not
available which,
of course, prevents gnome from launching. I would suggest that you find a
way to force the linux-generic package to be required and warn people that
removing it
will remove it's dependencies also. As soon as the header package was
installed dkms immediately started building and the desktop started.

==
apt show linux-generic
Package: linux-generic
Version: 5.15.0.97.92
Priority: optional
Section: kernel
Source: linux-meta
Origin: Ubuntu
Maintainer: Ubuntu Kernel Team 
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 21.5 kB
Provides: kernel-testing--linux--full--generic,
kernel-testing--linux--full--preferred
Depends: linux-image-generic (= 5.15.0.97.92), linux-headers-generic (=
5.15.0.97.92)
Download-Size: 1,696 B
APT-Manual-Installed: yes
APT-Sources: http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64
Packages
Description: Complete Generic Linux kernel and headers
 This package will always depend on the latest complete generic Linux kernel
 and headers.

--
 Roger Federer Fanatic Extraordinaire :-)

On Wed, 28 Feb 2024 at 03:35, Juerg Haefliger <2055...@bugs.launchpad.net>
wrote:

> > does not pull in the correct linux-header package
>
> What is installed that you think is wrong? Can you post the relevant apt
> logs (/var/log/apt/{history,term}.log*)?
>
>
> ** Changed in: linux (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2055162
>
> Title:
>   linux-headers package not being pulled in with linux-image-generic
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   linux-image-5.15.0-97-generic definitely exists in Ubuntu and it does
>   not pull in the correct linux-header package which is required to
>   rebuilt nvidia kernel modules.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 22.04
>   Package: ubiquity (not installed)
>   ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136
>   Uname: Linux 5.15.0-97-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp
> zcommon znvpair
>   ApportVersion: 2.20.11-0ubuntu82.5
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: GNOME
>   Date: Tue Feb 27 08:29:48 2024
>   InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz
> file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
>   InstallationDate: Installed on 2023-06-16 (256 days ago)
>   InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64
> (20230223)
>   ProcEnviron:
>LANGUAGE=en_CA:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: ubiquity
>   Symptom: installation
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055162/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=linux; component=main;
> status=Incomplete; importance=Undecided; assignee=None;
> Launchpad-Bug-Tags: amd64 apport-bug jammy ubiquity-22.04.19
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: juergh vorlon wtautz
> Launchpad-Bug-Reporter: Walter Tautz (wtautz)
> Launchpad-Bug-Modifier: Juerg Haefliger (juergh)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: wtautz
>
>

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

Title:
  linux-headers package not being pulled in with linux-image-generic

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

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

[Bug 2055270] [NEW] Buy Tramadol Online At Lowest Prices

2024-02-28 Thread Alex Walter

*** This bug is a security vulnerability ***

Public security bug reported:

Buy Tramadol Online 100mg USA Overnight

➤Order here: https://t.ly/N0hN9

➤Shop Here: https://t.ly/N0hN9


Tramadol 100mg may interact with other medications, including certain 
antidepressants, antipsychotics, and medications that affect serotonin levels. 
It's important to inform your healthcare provider about all medications you are 
taking, including prescription, over-the-counter, and herbal supplements, to 
avoid potential interactions.

Tramadol should not be used in combination with alcohol or other
substances that depress the central nervous system, as this can increase
the risk of respiratory depression and other serious side effects.

People with a history of substance abuse or addiction should use
tramadol with caution, as it has the potential for misuse, dependence,
and addiction.

Tramadol is not recommended for use in children under the age of 12, as
its safety and efficacy in this population have not been established.

Older adults may be more sensitive to the side effects of tramadol,
particularly dizziness and drowsiness, and may require lower doses or
closer monitoring.

It's essential to follow your healthcare provider's instructions
carefully when taking tramadol 100mg and to report any side effects or
concerns promptly. Additionally, do not stop taking tramadol suddenly
without consulting your doctor, as this can lead to withdrawal symptoms.
If you have any questions or uncertainties about tramadol or its use,
don't hesitate to discuss them with your healthcare provider.

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

** Information type changed from Public to Public Security

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

Title:
  Buy Tramadol Online At Lowest Prices

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


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

[Bug 2055162] [NEW] linux-headers package not being pulled in with linux-image-generic

2024-02-27 Thread Walter Tautz

Public bug reported:

linux-image-5.15.0-97-generic definitely exists in Ubuntu and it does
not pull in the correct linux-header package which is required to
rebuilt nvidia kernel modules.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity (not installed)
ProcVersionSignature: Ubuntu 5.15.0-97.107-generic 5.15.136
Uname: Linux 5.15.0-97-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Tue Feb 27 08:29:48 2024
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
InstallationDate: Installed on 2023-06-16 (256 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
Symptom: installation
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


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

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

Title:
  linux-headers package not being pulled in with linux-image-generic

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


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

[Bug 1977715] Re: thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from INBOX

2022-06-06 Thread Walter

ADDITIONAL INFO
---

I now started thunderbird using:

$ XDG_SESSION_TYPE=x11 WAYLAND_DISPLAY= thunderbird


(I don't think those envvars do _exactly_ what I was looking for. For instance, 
I notice that ossobv/xpaste still doesn't get access to the send_event: 
https://github.com/ossobv/xpaste/blob/ea8b2ff9f839f9ecc345fd9d04014b99def5b112/xpaste#L182
 )

It _does_ look like it changes things for the better because I haven't
had it deadlock on me yet. And I've been moving mails for 45 minutes
now.

The stdout/stderr definitely reports a change:


$ diff before after -U30
--- before  2022-06-06 13:23:30.137659175 +0200
+++ after   2022-06-06 13:23:13.921604292 +0200
@@ -1,40 +1,58 @@
-$ thunderbird 
+$ XDG_SESSION_TYPE=x11 WAYLAND_DISPLAY= thunderbird 
 [calBackendLoader] Using Thunderbird's libical backend
 [LDAPModuleLoader] Using LDAPDirectory.jsm
 [MsgSendModuleLoader] Using MessageSend.jsm
 [SmtpModuleLoader] Using SmtpService.jsm
+[GFX1-]: glxtest: Could not connect to wayland socket
 console.debug: "Trying to load /usr/lib/thunderbird/libotr.so"
 console.debug: "Trying to load libotr.so from system's standard library 
locations"
 console.debug: "Trying to load libotr.so.5 from system's standard library 
locations"
 console.debug: "Trying to load libotr.so from system's standard library 
locations"
 console.log: (new Error("Cannot load required OTR library", 
"resource:///modules/OTRLib.jsm", 109))
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
 console.debug: "Successfully loaded OpenPGP library librnp.so version 
0.16+git20220124.f06439f7.MZLA from /usr/lib/thunderbird/librnp.so"
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
 console.debug: "Found 0 public keys and 0 secret keys (0 protected, 0 
unprotected)"
 console.debug: "Successfully loaded optional OpenPGP library libgpgme.so.11 
from system's standard library locations"
 console.debug: "gpgme version: 1.16.0-unknown"
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
 console.warn: services.settings: thunderbird/hijack-blocklists has signature 
disabled
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
-Unsupported modifier, resource creation failed.
-XXX: resource creation failed
+console.error: gloda.datastore: "got error in 
_asyncTrackerListener.handleError(): 19: constraint failed"
 IPDL protocol error: Handler returned error code!
 
 ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ExpectFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)
 
 IPDL protocol error: Handler returned error code!
 
 ###!!! [Parent][DispatchAsyncMessage] Error: 
PClientManager::Msg_ForgetFutureClientSource Processing error: message was 
deserialized, but the handler returned false (indicating failure)


Hope this helps!

Cheers,
Walter

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

Title:
  thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from
  INBOX

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


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

[Bug 1934243] Re: thunderbird drag-n-drop move messages fails on Wayland

2022-06-06 Thread Walter

You say "drag-n-drop sometimes fails to work when moving messages. I
attempt to drag a message (or a collection of messages) from one folder
to another, but the attempt to drag fails and nothing happens".

In https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1977715 I
also report that it sometimes fails. But in my case Thunderbird becomes
completely unresponsive.

Could be related.

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

Title:
  thunderbird drag-n-drop move messages fails on Wayland

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


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

[Bug 1977715] [NEW] thunderbird 91.9.1 (jammy) sometimes deadlocks when moving mails from INBOX

2022-06-06 Thread Walter

ot;\372", 1) = 1
[pid 549265] 11:04:12.124299 recvmsg(3, {msg_namelen=0}, MSG_DONTWAIT) = -1 
EAGAIN (Resource temporarily unavailable)
[pid 549263] 11:04:12.124966 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.125697 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.125982 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.126254 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="0\0\0\0\24\0\0\0\5\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2723\377\377"...,
 iov_len=64}, {iov_base="\372\";9F\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=20}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT 

[pid 549263] 11:04:12.126395 write(9, "\372", 1 
[pid 549265] 11:04:12.126515 <... sendmsg resumed>) = 84
[pid 549263] 11:04:12.126603 <... write resumed>) = 1
[pid 549263] 11:04:12.127199 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.127536 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.127668 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.127872 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2713\377\377"...,
 iov_len=64}, 
{iov_base="\10\223\2\351\0\230\264f\372\";9G\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=28}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT) = 92
[pid 549265] 11:04:12.128305 recvmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\1\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377%f\0\0"...,
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT) = 
92
[pid 549265] 11:04:12.128533 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.128705 read(8,  
[pid 549265] 11:04:12.128777 recvmsg(3,  
[pid 549263] 11:04:12.128836 <... read resumed>"\372", 1) = 1
[pid 549265] 11:04:12.128892 <... recvmsg resumed>{msg_namelen=0}, 
MSG_DONTWAIT) = -1 EAGAIN (Resource temporarily unavailable)
[pid 549263] 11:04:12.128950 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.129162 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.129571 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.129852 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.130217 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.130361 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.130489 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="0\0\0\0\24\0\0\0\5\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2703\377\377"...,
 iov_len=64}, {iov_base="\372\";9H\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=20}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT) = 84
[pid 549277] 11:04:12.142977 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.143281 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.143697 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.143971 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.144125 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.144319 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\4\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2673\377\377"...,
 iov_len=64}, 
{iov_base="\10\223\2\351\0\230\264f\372\";9I\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=28}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT 

[pid 549263] 11:04:12.144456 read(8,  
[pid 549265] 11:04:12.144512 <... sendmsg resumed>) = 92
[pid 549263] 11:04:12.144727 <... read resumed>"\372", 1) = 1
[pid 549265] 11:04:12.144830 recvmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="8\0\0\0\24\0\0\0\1\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377&f\0\0"...,
 iov_len=4096}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT) = 
92
[pid 549265] 11:04:12.145078 write(9, "\372", 1) = 1
[pid 549265] 11:04:12.145403 recvmsg(3, {msg_namelen=0}, MSG_DONTWAIT) = -1 
EAGAIN (Resource temporarily unavailable)
[pid 549263] 11:04:12.145643 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.146242 write(9, "\372", 1) = 1
[pid 549263] 11:04:12.146523 read(8, "\372", 1) = 1
[pid 549263] 11:04:12.146888 write(13, "\0", 1) = 1
[pid 549265] 11:04:12.147055 read(12, "\0", 1) = 1
[pid 549265] 11:04:12.147295 sendmsg(3, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="0\0\0\0\24\0\0\0\5\0^\0\1\0\0\0\0\0\0\0\377\377\377\377\377\377\377\377\2663\377\377"...,
 iov_len=64}, {iov_base="\372\";9J\314\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 
iov_len=20}], msg_iovlen=2, msg_controllen=0, msg_flags=0}, MSG_DONTWAIT) = 84


CHILD 2 STRACE
--

(the following keeps repeating every 60 seconds)

$ sudo strace -tt -fp 549304 -e'!futex,poll,epoll_wait,restart_syscall'
strace: Process 549304 attached with 22 threads
[pid 549

[Bug 1955704] Re: systemd/plymouth preventing reboot/shutdown

2022-06-04 Thread Walter

Hi [~phm2f1alcw69]

is this possibly related to #1977652 ?

Depends on:

- your version of systemd / ubuntu (I don't see any versions in this
report)

- whether you also saw items looped in the logs (journald -b -1 | tail)


Cheers,
Walter

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

Title:
  systemd/plymouth preventing reboot/shutdown

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


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

[Bug 1977652] [NEW] systemd loops trying to start systemd-ask-password-plymouth

2022-06-04 Thread Walter

Public bug reported:

Short story:
- after boot
- when a systemd service wants a password
- systemd-ask-password is invoked
- systemd-ask-password-plymouth.path is reached
- systemd-ask-password-plymouth.service is started

Except:
- the conditions for the latter are (apparently) not met

End result:
- 40.000x "Condition check resulted in Forward Password Requests to Plymouth 
being skipped."
- 1.5 minutes of 100% cpu usage


AFFECTED VERSION


systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04


HOW TO REPRODUCE


If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled and
reboot. OpenVPN (calling systemd-ask-password) will trigger the
condition.

This causes high CPU usage for 1.5 minutes.

It looks like /run/plymouth/pid exists (for the .path file) at first,
when that is invoked, but then the resultant target (the .service file)
checks again, and finds that it is gone.

Manually reproducing:

# ls /run/systemd/ask-password
ask.5hW6rb  sck.79cfe1203518610

# mkdir /run/plymouth/pid
# systemctl start systemd-ask-password-plymouth.service 
systemd-ask-password-plymouth.path

# systemctl show --value --property=MainPID 
systemd-ask-password-plymouth.service
24777

# rmdir /run/plymouth/pid ; kill 24777

Result: systemd going into a loop.

Stop the loop with:

# systemctl stop systemd-ask-password-plymouth.path



ANALYSIS


It looks like this:
https://github.com/systemd/systemd/issues/21025

which is fixed by:
https://github.com/systemd/systemd/pull/21030

Alternative bug reports:
https://bugzilla.redhat.com/show_bug.cgi?id=1919538

Systemd's own analysis of the situation:

# systemd-analyze critical-chain systemd-ask-password-plymouth.service
...
systemd-ask-password-plymouth.service @1min 35.823s
└─systemd-ask-password-plymouth.path @593ms
  └─plymouth-start.service @571ms +21ms
└─systemd-udevd.service @450ms +119ms
  └─systemd-tmpfiles-setup-dev.service @429ms +18ms
└─systemd-sysusers.service @382ms +46ms
  └─systemd-remount-fs.service @353ms +22ms
└─systemd-journald.socket @318ms
  └─system.slice @264ms
└─-.slice @264ms

---
WORKAROUNDS
---

This works as long as you don't need the plymouth-ask-password:

# systemctl disable systemd-ask-password-plymouth.path
# systemctl mask systemd-ask-password-plymouth.path


Could you get the relevant patches from upstream sorted in Jammy?

Thanks!

Walter Doekes
OSSO B.V.

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

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

Title:
  systemd loops trying to start systemd-ask-password-plymouth

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


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

[Bug 1977645] Re: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail

2022-06-04 Thread Walter

Created PR at Debian:
https://salsa.debian.org/debian/gpgme/-/merge_requests/4

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

Title:
  python3-gpg "1.16.0-unknown" version is incomparable -> dependencies
  always fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions


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

[Bug 1977645] [NEW] python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail

2022-06-04 Thread Walter

Public bug reported:

The python version of the gpgme version contains "unknown" and is
therefore not PEP440 order compatible.

See this example:

  # pip3 freeze | grep gpg
  gpg===1.16.0-unknown

  # pip3 install pstore
  ...
  Successfully installed gpg-1.10.0
  Successfully installed pstore-2.0.0

  # pip3 freeze | grep gpg
  gpg==1.10.0


Key takeways from that example:

- pstore depends on gpg>=1.10

- 1.16 SHOULD be higher than 1.10

- pip installs 1.10 even though 1.16 exists

- the triple-= (gpg===1.16.0-unknown) means that the version exists, but
cannot be version compared: https://peps.python.org/pep-0440/#arbitrary-
equality


Suggested fix:

- replace the '-' from `gpgme-config --version` "1.16.0-unknown" with a
'+'; that will compare as expected;

- fix so "-unknown" isn't appended.


Apparently, this is caused by insufficient fixes in 
0001-avoid-identifying-as-beta.patch

I've attached a FIXED version, which should fix things.

Before:

  $ autoreconf -ivf

  $ grep Generated.*gpgme configure
  # Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown.

After:

  $ quilt push 
  Applying patch 0001-avoid-identifying-as-beta-FIXED.patch

  $ autoreconf -ivf

  $ grep Generated.*gpgme configure
  # Generated by GNU Autoconf 2.71 for gpgme 1.16.0.


Versions:

$ lsb_release -a 2>/dev/null| grep Codename
Codename:   jammy

$ apt-cache policy python3-gpg  | grep Installed
  Installed: 1.16.0-1.2ubuntu4


Cheers,
Walter Doekes
OSSO B.V.

** Affects: gpgme1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: patch

** Patch added: "0001-avoid-identifying-as-beta-FIXED.patch"
   
https://bugs.launchpad.net/bugs/1977645/+attachment/5594802/+files/0001-avoid-identifying-as-beta-FIXED.patch

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

Title:
  python3-gpg "1.16.0-unknown" version is incomparable -> dependencies
  always fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+subscriptions


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

[Bug 1967741] Re: Crash while using MS teams in webbrowser Google Chrome

2022-04-04 Thread Walter

Hallo,

Did run sudo ubuntu-bug /var/crash/_usr_sbin_gdm3.0.crash
and send the file
Is that ok?

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

Title:
  Crash while using MS teams in webbrowser Google Chrome

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


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

[Bug 1967741] [NEW] Crash while using MS teams in webbrowser Google Chrome

2022-04-04 Thread Walter

Public bug reported:

The problem regularly occurs in combination with MS teams in Google
Chrome.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gdm3 41~rc-0ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-39.44-lowlatency 5.13.19
Uname: Linux 5.13.0-39-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Mon Apr  4 10:55:07 2022
InstallationDate: Installed on 2020-07-21 (621 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug impish 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/1967741

Title:
  Crash while using MS teams in webbrowser Google Chrome

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


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

[Bug 1966502] Re: gjs-console crashed with SIGSEGV

2022-03-28 Thread Walter Garcia-Fontes

In my case Gnome Extensions works under Wayland but it crashes under
Xorg.

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

Title:
  gjs-console crashed with SIGSEGV

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


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

[Bug 1966660] Re: gjs-console crashed with SIGSEGV

2022-03-28 Thread Walter Garcia-Fontes

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

** This bug has been marked a duplicate of bug 1966502
   gjs-console crashed with SIGSEGV

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

Title:
  gjs-console crashed with SIGSEGV

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


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

[Bug 1966660] [NEW] gjs-console crashed with SIGSEGV

2022-03-28 Thread Walter Garcia-Fontes

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

Public bug reported:

I get this crash when trying to execute gnome-extensions-app.

ProblemType: Crash
DistroRelease: Ubuntu 22.04
Package: gjs 1.72.0-1
ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21
Uname: Linux 5.14.0-1024-oem x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 28 11:14:44 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
ExecutablePath: /usr/bin/gjs-console
InstallationDate: Installed on 2022-02-20 (35 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
ProcCmdline: /usr/bin/gjs /usr/share/gnome-shell/org.gnome.Extensions
SegvAnalysis:
 Segfault happened at: 0x7f5903655feb:  mov(%rdi),%edi
 PC (0x7f5903655feb) ok
 source "(%rdi)" (0x02a0) not located in a known VMA region (needed 
readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gjs
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
 () at /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
Title: gjs-console crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
separator:

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


** Tags: amd64 apport-crash jammy

** Information type changed from Private to Public

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

Title:
  gjs-console crashed with SIGSEGV

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


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

[Bug 1966656] [NEW] do-release-upgrade crashed with FileNotFoundError in getListFromFile(): [Errno 2] El fitxer o directori no existeix: '/usr/share/ubuntu-release-upgrader/removal_blacklist.cfg'

2022-03-28 Thread Walter Garcia-Fontes

Public bug reported:

I got this error and the upgrade from Ubuntu 21.10 to 22.04 aborted with
a black screen. I could recover from the boot recovery menu and the dpkg
reconstruct option.

ProblemType: Crash
DistroRelease: Ubuntu 21.10
Package: ubuntu-release-upgrader-core 1:22.04.7
ProcVersionSignature: Ubuntu 5.14.0-1024.26-oem 5.14.21
Uname: Linux 5.14.0-1024-oem x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CrashDB: ubuntu
Date: Mon Mar 28 10:34:59 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-focal-amd64-20200502-85
ExecutablePath: /usr/bin/do-release-upgrade
InstallationDate: Installed on 2022-02-20 (35 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58
InterpreterPath: /usr/bin/python3.10
PackageArchitecture: all
ProcCmdline: python3 /usr/lib/python3/dist-packages/DistUpgrade/dist-upgrade.py 
--partial --frontend DistUpgradeViewText --datadir 
/usr/share/ubuntu-release-upgrader
Python3Details: /usr/bin/python3.10, Python 3.10.3, python3-minimal, 
3.10.1-0ubuntu2
PythonArgs: ['/usr/bin/do-release-upgrade', '--partial', '--frontend', 
'DistUpgradeViewText', '--datadir', '/usr/share/ubuntu-release-upgrader']
PythonDetails: N/A
SourcePackage: ubuntu-release-upgrader
Title: do-release-upgrade crashed with FileNotFoundError in getListFromFile(): 
[Errno 2] El fitxer o directori no existeix: 
'/usr/share/ubuntu-release-upgrader/removal_blacklist.cfg'
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
mtime.conffile..etc.update-manager.release-upgrades: 2022-03-01T12:10:17.845607

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


** Tags: amd64 apport-crash dist-upgrade jammy need-duplicate-check

** Information type changed from Private to Public

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

Title:
  do-release-upgrade crashed with FileNotFoundError in
  getListFromFile(): [Errno 2] El fitxer o directori no existeix:
  '/usr/share/ubuntu-release-upgrader/removal_blacklist.cfg'

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


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

[Bug 1910273] Re: Upgrade to groovy breaks DNS resolution

2022-02-28 Thread Walter Schneider

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

I am getting DOMAINS in /etc/resolve.conf:

DOMAINS is initialized with "DOMAINS" in `/etc/network/if-up.d/resolved`
and set in /run/systemd/resolve/netif/*

```bash
$ cat /run/systemd/resolve/netif/3
# This is private data. Do not parse.
LLMNR=yes
MDNS=no
SERVERS=DNS
DOMAINS=DOMAINS
```

systemd-resolved adds DOMAINS to domains-searchlist:
```bash
cat /etc/resolv.conf 
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 127.0.0.1
nameserver 192.168.2.1
search DOMAINS lan
```

DOMAINS=$DOMAINS would have no effect and could be omitted,

As there are further errors form the if-down script (resolved: 12:
mystatedir: not found),

i've removed both `/etc/network/if-up.d/resolved` and `/etc/network/if-
down.d/resolved`.

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

Title:
  Upgrade to groovy breaks DNS resolution

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


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

[Bug 1960712] Re: package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess was killed by signal (Terminated)

2022-02-14 Thread Walter Hachmann

Hello, Mr. Grant Orndorff,

It looks like it was installed normally after all. When I do the command
"sudo apt install ubuntu-advantage-tools", the response is:

"Reading state information... Done
ubuntu-advantage-tools is already the newest version (27.6~20.04.1).
ubuntu-advantage-tools set to manually installed.nks
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded."

Thanks and Best Regards,

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

Title:
  package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade:
  installed ubuntu-advantage-tools package post-installation script
  subprocess was killed by signal (Terminated)

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


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

Re: [Bug 1960712] Re: package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess was killed by signal (Terminat

2022-02-14 Thread Walter Hachmann

Hello, Mr. Grant Orndorff,

It looks like it was installed normally after all. When I do the command
"sudo apt install ubuntu-advantage-tools", the response is:

"Reading state information... Done
ubuntu-advantage-tools is already the newest version (27.6~20.04.1).
ubuntu-advantage-tools set to manually installed.nks
0 upgraded, 0 newly installed, 0 to remove and 8 not upgraded."

Thanks and Best Regards,

* Walter R. G. Hachmann *



On Mon, Feb 14, 2022 at 4:15 PM Grant Orndorff <1960...@bugs.launchpad.net>
wrote:

> Hello Walter Hachmann, thank you for taking the time to file a bug!
>
> debconf can wait forever if it is expecting some sort of input but not
> getting any. That may be what is happening here. A common scenario that
> can trigger this is if the config file /etc/ubuntu-
> advantage/uaclient.conf is edited and the new version of ubuntu-
> advantage-tools wants to deliver a new default uaclient.conf. However, I
> do see that it appears you used `--force-confdef --force-confold` which
> I would've expected to handle this situation.
>
> It looks like this upgrade was triggered via aptdaemon. Can you try
> manually running:
>
> sudo apt install ubuntu-advantage-tools
>
> and let us know how it goes? Particularly what does debconf prompt for
> in this situation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1960712
>
> Title:
>   package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade:
>   installed ubuntu-advantage-tools package post-installation script
>   subprocess was killed by signal (Terminated)
>
> Status in ubuntu-advantage-tools package in Ubuntu:
>   New
>
> Bug description:
>   /usr/bin/dpkg --status-fd 75 --configure -a --force-confdef
> --force-confold
> 23002 pts/0SN+0:00 /usr/bin/perl -w
> /usr/share/debconf/frontend
> /var/lib/dpkg/info/ubuntu-advantage-tools.postinst configure 27.5~20.04.1
>   This debconf procedure is taking forever!
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 20.04
>   Package: ubuntu-advantage-tools 27.6~20.04.1
>   ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
>   Uname: Linux 5.4.0-99-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.21
>   Architecture: amd64
>   CasperMD5CheckResult: skip
>   Date: Sat Feb 12 13:22:04 2022
>   DuplicateSignature:
>package:ubuntu-advantage-tools:27.6~20.04.1
>Setting up ubuntu-advantage-tools (27.6~20.04.1) ...
>dpkg: error processing package ubuntu-advantage-tools (--configure):
> installed ubuntu-advantage-tools package post-installation script
> subprocess was killed by signal (Terminated)
>   ErrorMessage: installed ubuntu-advantage-tools package post-installation
> script subprocess was killed by signal (Terminated)
>   InstallationDate: Installed on 2018-03-24 (1420 days ago)
>   InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64
> (20180228)
>   Python3Details: /usr/bin/python3.8, Python 3.8.10, 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.6
>   SourcePackage: ubuntu-advantage-tools
>   Title: package ubuntu-advantage-tools 27.6~20.04.1 failed to
> install/upgrade: installed ubuntu-advantage-tools package post-installation
> script subprocess was killed by signal (Terminated)
>   UpgradeStatus: Upgraded to focal on 2021-09-03 (162 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1960712/+subscriptions
>
>

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

Title:
  package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade:
  installed ubuntu-advantage-tools package post-installation script
  subprocess was killed by signal (Terminated)

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


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

[Bug 1960712] [NEW] package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade: installed ubuntu-advantage-tools package post-installation script subprocess was killed by signal (Terminated

2022-02-12 Thread Walter Hachmann

Public bug reported:

/usr/bin/dpkg --status-fd 75 --configure -a --force-confdef --force-confold
  23002 pts/0SN+0:00 /usr/bin/perl -w /usr/share/debconf/frontend 
/var/lib/dpkg/info/ubuntu-advantage-tools.postinst configure 27.5~20.04.1
This debconf procedure is taking forever!

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ubuntu-advantage-tools 27.6~20.04.1
ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
Uname: Linux 5.4.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Feb 12 13:22:04 2022
DuplicateSignature:
 package:ubuntu-advantage-tools:27.6~20.04.1
 Setting up ubuntu-advantage-tools (27.6~20.04.1) ...
 dpkg: error processing package ubuntu-advantage-tools (--configure):
  installed ubuntu-advantage-tools package post-installation script subprocess 
was killed by signal (Terminated)
ErrorMessage: installed ubuntu-advantage-tools package post-installation script 
subprocess was killed by signal (Terminated)
InstallationDate: Installed on 2018-03-24 (1420 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
Python3Details: /usr/bin/python3.8, Python 3.8.10, 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.6
SourcePackage: ubuntu-advantage-tools
Title: package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade: 
installed ubuntu-advantage-tools package post-installation script subprocess 
was killed by signal (Terminated)
UpgradeStatus: Upgraded to focal on 2021-09-03 (162 days ago)

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


** Tags: amd64 apport-package focal need-duplicate-check

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

Title:
  package ubuntu-advantage-tools 27.6~20.04.1 failed to install/upgrade:
  installed ubuntu-advantage-tools package post-installation script
  subprocess was killed by signal (Terminated)

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


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

[Bug 1928954] Re: sssd not using offline credentials even no network available

2021-12-20 Thread Walter Kovacs

This problem still exists. Why is it cloesed?

** Changed in: sssd (Ubuntu)
   Status: Expired => In Progress

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

Title:
  sssd not using offline credentials even no network available

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


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

[Bug 1928954] Re: sssd not using offline credentials even no network available

2021-10-20 Thread Walter Kovacs

Hello,

today I was able to play around some more. I installed a new VM with
Ubuntu 20.04. The domain join is done by our install script. I changed
it to set log level to 6.

I logged in with a user, disconnected the LAN connection and logged out.

Then I was not able to login for a few minutes. Without doing anything
but wait a login was possible. I guess it took a while to discover that
the offline credentials needed to be used.


** Attachment added: "sssd.logs.tar"
   
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1928954/+attachment/5534625/+files/sssd.logs.tar

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

Title:
  sssd not using offline credentials even no network available

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


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

Re: [Bug 1931041] Re: weird browser-on-the-right side issue

2021-09-12 Thread walter wu

Chrome and firefox. It is nothing to do with PDF.

Sent from my iPhone

> On Sep 11, 2021, at 11:35 AM, Paul White <1931...@bugs.launchpad.net> wrote:
> 
> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner.
> 
> You refer to a browser but which one? Firefox, Chromium or another?
> 
> You attempted to submit this report against 'evince' which is a document
> viewer used mainly to view PDFs. Does this issue also affect evince?
> 
> If you still see a problem related to the one that you reported this bug
> report needs filing against the correct package as per
> https://wiki.ubuntu.com/Bugs/FindRightPackage to ensure that the right
> developers are made aware of the problem.
> 
> 
> ** Changed in: ubuntu
>   Status: New => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1931041
> 
> Title:
>  weird  browser-on-the-right side issue
> 
> Status in Ubuntu:
>  Incomplete
> 
> Bug description:
>  I have a DELL inspiron 14 5000 laptop. Dual boot with windows and
>  Ubuntu. I have a large external curved monitor (32 inch DELL). Here is
>  a weird issue:
> 
>  If I position the  browser on right half of the external monitor, it
>  is not responsive. It is very slow even just to scroll up and down.
> 
>  The interesting thing is 1) as soon as I move the browser over the
>  middle line to the left side , the problem disappear. 2) it does not
>  happen on my laptop screen.
> 
>  I have not tried using other external monitors.
> 
>  Any idea ?
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 20.04
>  Package: evince 3.36.7-0ubuntu1
>  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
>  Uname: Linux 5.8.0-55-generic x86_64
>  ApportVersion: 2.20.11-0ubuntu27.18
>  Architecture: amd64
>  CasperMD5CheckResult: skip
>  CurrentDesktop: ubuntu:GNOME
>  Date: Sun Jun  6 16:40:50 2021
>  InstallationDate: Installed on 2021-02-22 (104 days ago)
>  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
> (20200731)
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no user)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: evince
>  UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+bug/1931041/+subscriptions
>

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

Title:
  weird  browser-on-the-right side issue

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


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

[Bug 1928954] Re: sssd not using offline credentials even no network available

2021-08-18 Thread Walter Kovacs

Today I installed another laptop. I logged in with one user and entered
a few commands (mokutil). After that I logged out, disconnected the LAN
cable and was able to log in.

Then I connected the LAn cable again. Logged in with a different user
immediately logged out and during that disconnected the LAN cable. With
the new user I was not able to log in while disconnected.

Is there a delay between login and creating the offline credentials?

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

Title:
  sssd not using offline credentials even no network available

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


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

[Bug 1928954] Re: sssd not using offline credentials even no network available

2021-08-18 Thread Walter Kovacs

Hello,

today I installed 7 laptops with Ubuntu 20.04 LTS directly from ubuntu
repo. Afterwards I set up our domain and all of these  laptops have
above problem.

As far as I can tell the sssd demon does not enter offline state even
when the LAN cable is disconnected.

We have a "normal" Windows Server as domain controller I am not sure
which informations will help you there.

Here is our sssd.conf

[sssd]
services = nss, pam, ssh
config_file_version = 2
domains = REALM.LO
debug_level = 1

[domain/REALM.LO]
debug_level = 1
id_provider = ad
access_provider = ad
auth_provider = ad
krb5_store_password_if_offline = True 
enumerate = False
ignore_group_members = True
use_fully_qualified_names = False

auto_private_groups = True
cache_credentials = True

ad_gpo_access_control = permissive

krb5_server = realm.lo
krb5_realm = realm.lo

# SSH Key Login
ldap_user_extra_attrs = altSecurityIdentities:altSecurityIdentities
ldap_user_ssh_public_key = altSecurityIdentities
ldap_use_tokengroups = True

# home directory
override_homedir = /home/%d/%u
default_shell = /bin/bash


-
and our krb5.conf

[libdefaults]
default_realm = REALM.LO
ticket_lifetime = 24h
renew_lifetime = 7d
forwardable = true
dns_lookup_realm = true
dns_lookup_kdc = true
rdn = true

[realms]
REALM.LO = {
kdc = realm.lo
admin_server =  realm.lo
}

[domain_realms]
.realm.lo = REALM.LO



I would gladly provide more informations if needed

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

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

Title:
  sssd not using offline credentials even no network available

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


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

[Bug 1930982]

2021-06-16 Thread Walter ZAMBOTTI

(In reply to Lee Salzman [:lsalzman] from comment #25)
> The circumstantial evidence "seems like" something in the function here 
> (https://searchfox.org/mozilla-central/source/gfx/wr/swgl/src/composite.h#534)
>  is underflowing. But I would need someone who can reliably reproduce the 
> issue to find out where in those math equations are actually doing so. I 
> tried testing in my patch if the additions were the culprit, but that seems 
> unlikely.
> 
> It's possible the multiplications "rbCoeffs * uv" or "gCoeffs * uv" are 
> underflowing based on whatever values the ARM video codecs seem to be 
> supplying. However, this is not happening on x86 at all, which is strange, 
> and it is also happening on ARM across platform, which is further strange, 
> since there isn't really much in the way of platform specific code here.
> 
> Sotaro, might you be able to investigate this?

Taking a step back.  If a certain function is suspected what are the
diff's with this code between the working 88.0 and non working 89.0
version?

Since the issue affects all ARM regardless of platform the only culprit
not eliminated is Firefox.

If you have a downloaded executable for me to test I'm happy to do so.
My platforms are :

aarch64 Ubuntu 18.04 LTS
aarch64 Ubuntu 20.10

I can only test on one of these platforms!

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

Title:
  Firefox 89: webrender breaks videos on Raspberry Pi

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

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

[Bug 1931041] [NEW] weird browser-on-the-right side issue

2021-06-07 Thread walter wu

Public bug reported:

I have a DELL inspiron 14 5000 laptop. Dual boot with windows and
Ubuntu. I have a large external curved monitor (32 inch DELL). Here is a
weird issue:

If I position the  browser on right half of the external monitor, it is
not responsive. It is very slow even just to scroll up and down.

The interesting thing is 1) as soon as I move the browser over the
middle line to the left side , the problem disappear. 2) it does not
happen on my laptop screen.

I have not tried using other external monitors.

Any idea ?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: evince 3.36.7-0ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun  6 16:40:50 2021
InstallationDate: Installed on 2021-02-22 (104 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  weird  browser-on-the-right side issue

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

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

[Bug 1928954] [NEW] sssd not using offline credentials even no network available

2021-05-19 Thread Walter Kovacs

Public bug reported:

I installed a new Ubuntu 20.04 with a new image from ubuntu.org

After the installation I joined our domain and logged in with domain
users credentials. Then I logged out and disconnected LAN cable. I could
not log in with my offline credentials.

If you wait long enough sometimes 15 minutes sometimes hours sssd will
finally enter offline mode while not connected to LAN.


The only solution so far was to add our domain controller to /etc/hosts
but this is not a permanent solution.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: sssd 2.2.3-3ubuntu0.4
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed May 19 16:38:47 2021
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sssd
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  sssd not using offline credentials even no network available

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

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

[Bug 1875220] Re: Applet does not update VPN DNS server's IP - Also OTP option when enabled is not persisted on configuration file

2021-04-15 Thread Walter Garcia-Fontes

** Bug watch added: gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/issues 
#36
   https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/issues/36

** Also affects: network-manager-fortisslvpn (Fedora) via
   https://gitlab.gnome.org/GNOME/NetworkManager-fortisslvpn/-/issues/36
   Importance: Unknown
   Status: Unknown

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

Title:
  Applet does not update VPN DNS server's IP - Also OTP option when
  enabled is not persisted on configuration file

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

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

[Bug 1923881] Re: Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity installer

2021-04-14 Thread Walter Lapchynski

@xnox that's a very good question. What I can say is that Calamares does
look for locales (/usr/share/i18n/SUPPORTED, locale.gen, `locale -a`, in
that order) and certainly does include its own functionality for
choosing through those options. That said, I don't *think* it needs it.
We did take today's image and removed all the ubiquity-* packages, ran
Calamares, and it seemed like everything worked just fine. So I guess
you could make the depend calamares | ubiquity but that seems rather
bizarre to me. I mean, after all, the issue here is that the installer
requires this, right? So why not have casper depend on no installer and
make the installer have the dependency?

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

Title:
  Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity
  installer

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

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

[Bug 1923881] Re: Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity installer

2021-04-14 Thread Walter Lapchynski

Looks like the real culprit here is having casper depend upon ubiquity. I 
suspect before the removal of udeb packages (including localechooser-data which 
was the alternative to the depend otherwise satisfied by ubiquity), we never 
ran into this problem simply because of localechooser-data:
https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1923833

** Package changed: calamares (Ubuntu) => casper (Ubuntu)

** Changed in: casper (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Lubuntu and Ubuntu Studio Hirsute incorrectly launch Ubiquity
  installer

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

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

[Bug 1923856] [NEW] package minidlna (not installed) failed to install/upgrade: »installiertes minidlna-Skript des Paketes post-removal«-Unterprozess gab den Fehlerwert 1 zurück

2021-04-14 Thread Walter

Public bug reported:

n.a.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: minidlna (not installed)
ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Apr 14 16:06:47 2021
ErrorMessage: »installiertes minidlna-Skript des Paketes 
post-removal«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2019-12-27 (473 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.3
SourcePackage: minidlna
Title: package minidlna (not installed) failed to install/upgrade: 
»installiertes minidlna-Skript des Paketes post-removal«-Unterprozess gab den 
Fehlerwert 1 zurück
UpgradeStatus: Upgraded to groovy on 2021-04-14 (0 days ago)

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


** Tags: amd64 apport-package groovy

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

Title:
  package minidlna (not installed) failed to install/upgrade:
  »installiertes minidlna-Skript des Paketes post-removal«-Unterprozess
  gab den Fehlerwert 1 zurück

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

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

[Bug 1919371] [NEW] picom needs a sane default configuration

2021-03-16 Thread Walter Lapchynski

Public bug reported:

With bug 1919370 we will be changing from compton to picom. It doesn't
come with a default configuration and though picom can load a
compton.conf, it doesn't support all of its options, so we need to adapt
it accordingly.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: lubuntu-default-settings 21.04.3
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 19:23:23 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
PackageArchitecture: all
SourcePackage: lubuntu-default-settings
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lubuntu-default-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  picom needs a sane default configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lubuntu-default-settings/+bug/1919371/+subscriptions

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

[Bug 1919370] [NEW] use picom instead of compton

2021-03-16 Thread Walter Lapchynski

Public bug reported:

compton is dead and with the new rewrite/fork picom being packaged, we
should seed this instead.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: lubuntu-desktop 21.04.1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 19:27:02 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
SourcePackage: lubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: lubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  use picom instead of compton

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

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

[Bug 1919367] [NEW] compton recommends picom

2021-03-16 Thread Walter Lapchynski

Public bug reported:

compton's been pretty much abandoned and as such someone took it upon
themselves to fork/rewrite it and that is what has resulted in picom.
picom is partially compatible with compton but it does not support all
of its options. Since Recommends are installed by default, installing
compton results in having two compositors (picom and compton) and since
picom doesn't come with a default config all set up, it will use
compton.conf and it will likely fail silently. This is just bad. If
anything, picom should be a suggest, or just simply not mentioned at
all.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: compton 1-1
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 19:12:15 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
SourcePackage: compton
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug hirsute

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

Title:
  compton recommends picom

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

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

[Bug 1798071] Re: Suspension fails and re-login screen is black

2021-03-16 Thread Walter Lapchynski

Suspension is handled by the kernel, not by artwork (and it's buggy
depending on the hardware). Similarly, my guess is that any graphical
issues you had are related to the kernel modules, as well. Either way,
it doesn't seem like this is going anywhere, so Incomplete it is.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: lubuntu-artwork

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

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

Title:
  Suspension fails and re-login screen is black

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

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

[Bug 1919363] [NEW] provide warning to user about bad media when running installer

2021-03-16 Thread Walter Lapchynski

Public bug reported:

Right now, we have this great check running at boot that tests the
integrity of various files contained on the ISO. Previously, it
interrupted the boot process but would report to the user whether or not
a failure occurred. Recent changes have made this test silently run in
the background. It's plausible it can still be running *after* the GUI
loads. That's neat stuff, but there's no feedback to the user.

A file by the name of casper-md5check.json is in /run in the live
environment with the results. In turn, that will be dropped into
/var/log/installer on the installed system. This JSON file will report
which files did not match and what the overall result is (which can be
unknown, fail, success, or skip). Example:

{
  "checksum_missmatch": [ 
"./casper/filesystem.manifest"
],
  "result": "fail"
}

In turn, the results are reported by apport in any bugs filed.

Bug 1918733 was created to resolve this issue, but was marked Won't Fix,
at least for casper. In that bug, it was suggested that the various
installers would implement this in some way. Therefore, this bug exists
to resolve it in Calamares.

My proposed fix is a simple shell script or a small Python program. It
would be run before Calamares via the customized Desktop Entry (i.e. the
one that's on the desktop). I'm thinking of this instead of doing it in
Calamares as it will not allow us to create random dialogs. kdialog
would, though, so we should add that to the live seed and use that. I
would suggest that we run this with ; and not && because we don't want a
minor logic failure or something to prevent installation altogether.
Also, I don't think we want to get heavy handed. There may be a reason
one may want to continue with bad media (e.g. for testing).

The logic would be something like this:

 1. Check the status of the systemd casper-md5check.service
 2. If the service is still running, wait for a given timeout
 3. If the timeout is reached and the service is still running, exit gracefully 
(maybe submit a bug? or record the problem somewhere?)
 4. Parse the results
 5. Warn the user but do not prevent them from continuing

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: calamares-settings-lubuntu 1:21.04.2
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Tue Mar 16 18:33:36 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
PackageArchitecture: all
SourcePackage: calamares-settings-ubuntu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: calamares-settings-ubuntu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug hirsute

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

Title:
  provide warning to user about bad media when running installer

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

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

[Bug 1886561] Re: network manager applet for authentication is not working

2021-03-15 Thread Walter Lapchynski

nm-tray is light and based in Qt, which is great. Its VPN support,
however, is lacking, as you have discovered.

Incidentially, the workaround is discussed in the Lubuntu manual:
https://manual.lubuntu.me/stable/G/AdvancedNetworking.html

** Changed in: nm-tray (Ubuntu)
   Status: New => Triaged

** Changed in: nm-tray (Ubuntu)
   Importance: Undecided => Medium

** Bug watch added: github.com/palinek/nm-tray/issues #44
   https://github.com/palinek/nm-tray/issues/44

** Also affects: nm-tray via
   https://github.com/palinek/nm-tray/issues/44
   Importance: Unknown
   Status: Unknown

** Summary changed:

- network manager applet for authentication is not working 
+ nm-tray does not prompt for password with VPN connections

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

Title:
  nm-tray does not prompt for password with VPN connections

To manage notifications about this bug go to:
https://bugs.launchpad.net/nm-tray/+bug/1886561/+subscriptions

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

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-11 Thread Walter Lapchynski

I filed a separate report (bug 1918733) about the lack of feedback.

Technically, I would consider this bug fixed unless I'm missing
something.

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

Title:
  File integrity check at boot of install media  no longer functional

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

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

[Bug 1918733] [NEW] file integrity check provides no feedback to the user

2021-03-11 Thread Walter Lapchynski

Public bug reported:

As of 1.460, it seems the file integrity check is now running silently,
which is great. It wasn't working correctly (bug 1917590) but that's now
resolved. Unfortunately, a failed result provides no feedback at any
time to the user.

Additionally, the installer can be run despite the bad media. That's
probably a separate bug for the installer.

Either way, the software shouldn't let a user continue to waste their
time on something that's broken.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: casper 1.460
ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
Uname: Linux 5.10.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu60
Architecture: amd64
CasperMD5CheckMismatches: ./casper/filesystem.manifest
CasperMD5CheckResult: fail
CasperVersion: 1.460
CurrentDesktop: LXQt
Date: Thu Mar 11 21:10:01 2021
LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210311)
SourcePackage: casper
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.casper.conf: 2021-03-11T21:09:00.584000

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


** Tags: amd64 apport-bug hirsute

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

Title:
  file integrity check provides no feedback to the user

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

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

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-11 Thread Walter Lapchynski

It seems that 1.460 got the file check up and running again. However, a
failure doesn't result in any feedback to the user. I'm not sure that's
by design or not?

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

Title:
  File integrity check at boot of install media  no longer functional

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

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

[Bug 1918564] Re: Multiple archiver applications appear in Lubuntu 21.04 (Hirsute Hippo)

2021-03-10 Thread Walter Lapchynski

Gee, Thomas, great thinking! I'll get this resolved shortly. :)

** Changed in: lxqt-metapackages (Ubuntu)
   Status: New => Confirmed

** Changed in: lxqt-metapackages (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: lxqt-metapackages (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Multiple archiver applications appear in Lubuntu 21.04 (Hirsute Hippo)

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

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

[Bug 1887530] Re: Dragging icon from start menu to desktop changes the way it works

2021-03-04 Thread Walter Lapchynski

Actually, this is intended behavior.

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => Invalid

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

Title:
  Dragging icon from start menu to desktop changes the way it works

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

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

[Bug 1887532] Re: virtualbox-guest-additions-iso package does not work (works in Ubuntu)

2021-03-04 Thread Walter Lapchynski

Same with the other bug you filed with VBox and Lubuntu: no Windows, but
can't reproduce.

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  virtualbox-guest-additions-iso package does not work (works in Ubuntu)

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

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

[Bug 1917724] Re: lubuntu hirsute install fail mkfs.xfs

2021-03-04 Thread Walter Lapchynski

Ok so now I'm less concerned, let's try to figure out how to actually
reproduce this. Clearly an existing partition table is necessary.

** Changed in: calamares (Ubuntu)
   Importance: Critical => Undecided

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

Title:
  lubuntu hirsute install fail mkfs.xfs

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

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

[Bug 1887681] Re: Monitor settings dialog does not open when Lubuntu runs in virtualbox

2021-03-04 Thread Walter Lapchynski

I don't have Windows 10, but I can't reproduce.

** Changed in: lubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  Monitor settings dialog does not open when Lubuntu runs in virtualbox

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

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

[Bug 1917724] Re: lubuntu hirsute install fail mkfs.xfs

2021-03-04 Thread Walter Lapchynski

I have a wee bit of a concern that the kpmcore patch we added to get EFI
installs working in Calamares may have had an impact here. I hope not,
but I'm concerned. If that's the case, we may have to throw the latest
Git master of kpmcore in a PPA and rebuild Calamares against it and try
with that. In which case we may have to either drop that patch and issue
release notes with a workaround for the label issue or ship Git master
(probably not).

To reduce noise, can we just forget about reusing and extra partitions
and stuff and simply do a fresh partition table with either xfs,
reiserfs, or btrfs (i.e. 3 separate tests) and see if it fails
similarly? In other words, I want to test just whether or not creating
the file system on a fresh table works. This should just work. It
certainly should just work in kpm, as it has in the past. If those fail
and especially if they all fail, that's trouble.

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

** Changed in: calamares (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  lubuntu hirsute install fail mkfs.xfs

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

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

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-03 Thread Walter Lapchynski

Michael, I did notice that systemd was complaining in the logs about the
lack of a service file so I think you're on to something.

I'll also add I love the idea of this happening transparently. If we can
actually get that working, even better. That will reduce the skips
significantly.

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

Title:
  File integrity check at boot of install media  no longer functional

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

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

[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Walter Lapchynski

Thanks a lot, Heather! Experience tells me the likelihood that patch
will easily apply to older major versions is extremely small. That said,
I'm looking towards the future. Having this report "live" will help us
keep track of things until that time comes. Thanks again!

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

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

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

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-03 Thread Walter Lapchynski

Also /run/casper-md5check.json is missing in the live system, as is
/var/log/installer/casper-md5check.json in the installed system.

Since this is a relatively new problem, I did see this commit, which sounds 
like it attempts to continue to boot while the check is running. I wonder if 
the problem doesn't lie here somewhere:
https://git.launchpad.net/ubuntu/+source/casper/commit/?id=8415b4102e5c59064a5acff878aa2c3c8aa10e96

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

Title:
  File integrity check at boot of install media  no longer functional

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

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

[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-03 Thread Walter Lapchynski

Of course making it Won't Fix will render this bug all but invisible,
though, and there are future release versions to consider. I don't want
to get into a status war especially given I'm not in the LibreOffice
team, but I'm sure this won't ever come up on my radar again given that
status. Even just setting it as Triaged or Confirmed would be
sufficient.

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

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

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

[Bug 1917590] Re: File integrity check at boot of install media no longer functional

2021-03-03 Thread Walter Lapchynski

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

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

Title:
  File integrity check at boot of install media  no longer functional

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

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

[Bug 1917590] Re: File integrity check at boot of install media no longer visible

2021-03-03 Thread Walter Lapchynski

I note here that CasperMD5CheckResult is unknown, which is to say that
no skip or fail has been recorded. In that sense, it would seem that the
check didn't even run. We certainly can't use it to verify ISO integrity
in bugs, and in that sense, I'd call this a pretty problematic
regression.

** Changed in: casper (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- File integrity check at boot of install media  no longer visible
+ File integrity check at boot of install media  no longer functional

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

Title:
  File integrity check at boot of install media  no longer functional

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

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

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski

So our script for installing the EFI signed packages could use a
refactor. If it was properly constructed, **assuming Internet was
available**, one could have gotten around this issue. Right now, it
forces the assumption that there is no Internet, so some small blame can
be placed there.

One can resolve this by removing the following lines from
/etc/calamares/modules/before_bootloader_context.conf:

-command: sed -i '/deb http/d' /etc/apt/sources.list
 timeout: 10

There's a task to fix up the script here:
https://phab.lubuntu.me/T200

However, this is still not the cause of our problems.

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

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

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

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

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski

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

** Changed in: calamares (Ubuntu)
   Importance: Undecided => Critical

** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-21.04

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

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

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

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

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski

It seems that 1ubuntu37 comes from the ship-live seed (i.e. on the ISO)
while 1ubuntu40 is from the repos. Oddly, it seems to want to prefer the
former? Still, I don't know why we have an outdated package.

** Summary changed:

- Lubuntu Hirsute daily install failed -external command finished w/errors 
+ Lubuntu Hirsute daily install failed due to grub packaging errors

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

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

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

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

[Bug 1917292] Re: Lubuntu Hirsute daily install failed due to grub packaging errors

2021-03-01 Thread Walter Lapchynski

Sorry for all the comments. Anyways, this is probably not a Calamares
bug. Calamares may be contributing but a stale package on the ISO is a
much bigger problem. Unfortunately, I'm not sure where the problem lies
so I'm not entirely sure where to file it against. I've asked at
#ubuntu-release and no response so far.

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

Title:
  Lubuntu Hirsute daily install failed due to grub packaging errors

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

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

[Bug 1917360] [NEW] where have the logs gone?

2021-03-01 Thread Walter Lapchynski

Public bug reported:

Look at https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1917292
and you'll see the session.log is nearly devoid of information.

It seems that somewhere along the way (probably
https://github.com/calamares/calamares/commit/631923abf8c06289139895dbae96b07a547b550e)
default logging behavior changed.

We could call with `-d` but that includes the debug button which has
potential to freak out users, so better would be to set our preferred
log level with e.g. `-D6` in the call to the installer in the Desktop
Entry.

** Affects: calamares-settings-ubuntu (Ubuntu)
 Importance: Medium
 Assignee: Dan Simmons (kc2bez)
 Status: Triaged

** Package changed: calamares (Ubuntu) => calamares-settings-ubuntu
(Ubuntu)

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Importance: Undecided => Medium

** Changed in: calamares-settings-ubuntu (Ubuntu)
   Status: New => Triaged

** Changed in: calamares-settings-ubuntu (Ubuntu)
Milestone: None => ubuntu-21.04

** Changed in: calamares-settings-ubuntu (Ubuntu)
 Assignee: (unassigned) => Dan Simmons (kc2bez)

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

Title:
  where have the logs gone?

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

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

[Bug 1917292] Re: Lubuntu Hirsute daily install failed -external command finished w/errors

2021-03-01 Thread Walter Lapchynski

Not sure what's up with the Calamares logs, but the full error is:

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 grub-efi-amd64-bin : Depends: grub-common (= 2.04-1ubuntu37) but 
2.04-1ubuntu40 is to be installed
  Recommends: efibootmgr but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

This is the result of trying to install grub-efi-amd64-signed. src:grub2
and src:grub2-signed have been released (as 1ubuntu40) as of the 25th
and efibootmgr hasn't changed in forever. Something is weird here with
regards to packages.

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

Title:
  Lubuntu Hirsute daily install failed -external command finished
  w/errors

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

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

[Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-02-28 Thread Walter Lapchynski

Flipped to Fix Committed from Fix Released for libreoffice in Ubuntu
since even Hirsute is still stuck on 7.0.4 and I'm not sure even +1 will
have 7.1.x, let alone 7.2.x.

** Changed in: libreoffice (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

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

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

[Bug 1916260] Re: PCManFM-Qt opens files with a single click only

2021-02-26 Thread Walter Lapchynski

That's the default setting and I can't reproduce it.

** Changed in: pcmanfm-qt (Ubuntu)
   Status: New => Incomplete

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

Title:
  PCManFM-Qt opens files with a single click only

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

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

[Bug 1910934] Re: lxqt loses natural scrolling

2021-02-26 Thread Walter Lapchynski

I could imagine that a failure in the bus could result in similar
behavior since the settings are device-based and not general. In other
words, if you had 5 touchpads, you'd really have 5 different natural
scrolling options to select. So if you have deviceX and the bus has a
hiccup, causing the device to be re-enumerated, you may then have
deviceX+1, which has its own setting. At some point, I would imagine
that trying to connect to deviceX would time out and it would get
dropped. Logging out and back in again would likely force LXQt to re-
read the devices, leaving only deviceX+1.

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

Title:
  lxqt loses natural scrolling

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

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

[Bug 1916897] Re: Option has no effect and reset itself

2021-02-25 Thread Walter Lapchynski

Something is really weird here, even outside of what problem there MAY
be with obconf-qt.

The setting for this in the Openbox config is
`yes` which is a default part of
the Lubuntu configuration (and technically Debian and upstream Openbox,
too).

The option is relatively new as previous centering solutions were buggy, as 
evidenced by this bug:
https://bugzilla.icculus.org/show_bug.cgi?id=5946

However, as you can see there, it was resolved with a new commit:
https://github.com/danakj/openbox/commit/f866c034bf6e954791442ff029d5ae51ab0bd616

Despite all that, I can't get it to work no way, no how.

That said, I'm going to add Openbox and investigate a bit further.

** Bug watch added: bugzilla.icculus.org/ #5946
   http://bugzilla.icculus.org/show_bug.cgi?id=5946

** Also affects: openbox (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Option has no effect and reset itself

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

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

[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot

2021-02-23 Thread Walter Lapchynski

Excellent. Thanks for the confirmation.

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

Title:
  lubuntu hirsute: display configuration doesn't survive logout/reboot

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

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

[Bug 1905947] Re: lubuntu hirsute: display configuration doesn't survive logout/reboot

2021-02-23 Thread Walter Lapchynski

Sounds like this is fixed. Thanks Chris!

** Changed in: lxqt-config (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/1905947

Title:
  lubuntu hirsute: display configuration doesn't survive logout/reboot

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

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

[Bug 1916356] Re: The installer failed to create partition on disk with EFI (not BIOS)

2021-02-23 Thread Walter Lapchynski

Nevermind that test I mentioned; leok already figured it out. ;)

** Description changed:

  See attached bugs for longer explanation but basically due to some
  changes in core software (dosfstools) EFI installs fail to create
  partitions because a null label is no longer acceptable. There is now a
  fix in kpmcore, which is what Calamares uses to do this work, that
  essentially sets "NO_LABEL" instead of a null ("") label.
+ 
+ Workaround: manual partitioning expressly setting labels on all
+ partitions.
  
  ---
  
  Testing Lubuntu Hirsute ISO 20210220 -
  Test machine Lenovo V14 IIL - booting in UEFI+secure boot mode
  
  Connected to WiFi network and ran the installer -
  
  I selected "Erase disk with swap file" and then Calamares crashed with
  the error: "the installer failed to create partition on disk "WDC PC
  SN20 ..." see attached screenshot and files.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.35-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.shellprocess_logs.conf:
   ---
   dontChroot: true
   timeout: 30
   script:
   - calamares-logs-helper @@ROOT@@
  .etc.calamares.modules.unpackfs.conf:
   ---
   unpack:
   -   source: "/cdrom/casper/filesystem.squashfs"
   sourcefs: "squashfs"
   destination: ""
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  CurrentDesktop: LXQt
  Date: Sat Feb 20 20:23:48 2021
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210220)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.1
   calamares-settings-lubuntu   1:21.04.1
   xfsprogs 5.6.0-1ubuntu4
   btrfs-progs  5.10.1-1
  SourcePackage: calamares
  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/1916356

Title:
  The installer failed to create partition on disk with EFI (not BIOS)

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

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

[Bug 1916497] Re: PCManFM-Qt does not respect systemw-wide Qt widget style

2021-02-23 Thread Walter Lapchynski

If it "fixed itself" perhaps a little log out/on was all that's needed.
Marking as incomplete unless we have clear steps to reproduce.

** Changed in: pcmanfm-qt (Ubuntu)
   Status: New => Incomplete

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

Title:
  PCManFM-Qt does not respect systemw-wide Qt widget style

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

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

[Bug 1916356] Re: The installer failed to create partition on disk with EFI

2021-02-23 Thread Walter Lapchynski

It should be apparent that this affects EFI only. I wouldn't expect
secure boot or not to make a difference. Either way, let's hold off on
reporting any results on this for a bit.

The only one thing I'm thinking that might be worth testing is whether
or not manual partitioning with labels set on all partitions makes a
difference. If it does, we at least have a workaround.

Meanwhile kc2bez is testing the fix. Applying to kpmcore alone wasn't
sufficient, so we'll rebuild Calamares against that and see how it goes.

** Summary changed:

- The installer failed to create partition on disk
+ The installer failed to create partition on disk with EFI

** Changed in: calamares (Ubuntu)
   Status: Confirmed => Triaged

** Bug watch added: Calamares Issues #1637
   https://github.com/calamares/calamares/issues/1637

** Also affects: calamares via
   https://github.com/calamares/calamares/issues/1637
   Importance: Unknown
   Status: Unknown

** Also affects: kpmcore (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: KDE Bug Tracking System #432941
   https://bugs.kde.org/show_bug.cgi?id=432941

** Also affects: kpmcore via
   https://bugs.kde.org/show_bug.cgi?id=432941
   Importance: Unknown
   Status: Unknown

** Changed in: kpmcore (Ubuntu)
   Status: New => Triaged

** Changed in: calamares (Ubuntu)
   Importance: Undecided => Critical

** Changed in: kpmcore (Ubuntu)
   Importance: Undecided => Critical

** Summary changed:

- The installer failed to create partition on disk with EFI
+ The installer failed to create partition on disk with EFI (not BIOS)

** Description changed:

+ See attached bugs for longer explanation but basically due to some
+ changes in core software (dosfstools) EFI installs fail to create
+ partitions because a null label is no longer acceptable. There is now a
+ fix in kpmcore, which is what Calamares uses to do this work, that
+ essentially sets "NO_LABEL" instead of a null ("") label.
+ 
+ ---
+ 
  Testing Lubuntu Hirsute ISO 20210220 -
  Test machine Lenovo V14 IIL - booting in UEFI+secure boot mode
  
  Connected to WiFi network and ran the installer -
  
  I selected "Erase disk with swap file" and then Calamares crashed with
  the error: "the installer failed to create partition on disk "WDC PC
  SN20 ..." see attached screenshot and files.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: calamares 3.2.35-0ubuntu2
  ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11
  Uname: Linux 5.10.0-14-generic x86_64
  .etc.calamares.modules.finished.conf:
   ---
   restartNowMode: user-checked
   restartNowCommand: "systemctl -i reboot"
  .etc.calamares.modules.shellprocess_logs.conf:
   ---
   dontChroot: true
   timeout: 30
   script:
   - calamares-logs-helper @@ROOT@@
  .etc.calamares.modules.unpackfs.conf:
   ---
   unpack:
   -   source: "/cdrom/casper/filesystem.squashfs"
   sourcefs: "squashfs"
   destination: ""
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.456
  CurrentDesktop: LXQt
  Date: Sat Feb 20 20:23:48 2021
  LiveMediaBuild: Lubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210220)
  RelatedPackageVersions:
   calamares-settings-ubuntu-common 1:21.04.1
   calamares-settings-lubuntu   1:21.04.1
   xfsprogs 5.6.0-1ubuntu4
   btrfs-progs  5.10.1-1
  SourcePackage: calamares
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: calamares (Ubuntu)
 Assignee: (unassigned) => Dan Simmons (kc2bez)

** Changed in: kpmcore (Ubuntu)
 Assignee: (unassigned) => Dan Simmons (kc2bez)

** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-21.04

** Changed in: kpmcore (Ubuntu)
Milestone: None => ubuntu-21.04

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

Title:
  The installer failed to create partition on disk with EFI (not BIOS)

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

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

[Bug 1916481] Re: qterminal: undefined symbol

2021-02-23 Thread Walter Lapchynski

You're looking at it all too much like a human :) There's a lot of stuff
going on under the hood that you may not realize is apparently a
necessary part of making your software work.

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

Title:
  qterminal: undefined symbol

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

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

[Bug 1916481] Re: qterminal: undefined symbol

2021-02-22 Thread Walter Lapchynski

It's on the development branch, so I wouldn't be surprised you have bugs
in general with any software.

Also, speaking with my Community Council hat on, the goal for the
community is to be inclusive and welcoming to all, so using language
that no one would consider offensive would be great.

Thanks!

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

Title:
  qterminal: undefined symbol

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qterminal/+bug/1916481/+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 >

1 - 100 of 4973 matches

Mail list logo