Re: [Bug 1975557] Re: blank screen does not turn off display backlight

2022-05-25 Thread Robert Blair
** Reply to message from Daniel van Vugt <1975...@bugs.launchpad.net> on Wed,
25 May 2022 06:15:35 -

I get an error running apport-collect.  I am beginning to think that the last
update to this system went wrong.  There are other problems comming up which I
did not have before.

I have now tried the display with another 22.04 install and that works
OK.

So I think this problem report should be closed.

bob1@Juptier:~$ apport-collect 1975557
ERROR: connecting to Launchpad failed: Unable to find the server at
launchpad.net
You can reset the credentials by removing the file
"/home/bob1/.cache/apport/launchpad.credentials"
bob1@Juptier:~$ 


> The difference between 21.10 and 22.04 might just be that we now default
> to Wayland instead of Xorg. So the display subsystems are different.
> 
> Please run this command to gather more information:
> 
>   apport-collect 1975557
> 
> And to save time in future please use the 'ubuntu-bug' command to report
> new bugs.
> 
> ** Tags added: jammy
> 
> ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
> 
> ** Changed in: gnome-shell (Ubuntu)
>Status: New => Incomplete
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1975557
> 
> Title:
>   blank screen does not turn off display backlight
> 
> Status in gnome-shell package in Ubuntu:
>   Incomplete
> 
> Bug description:
>   I updated a system from 21.10 to 22.04 and noticed that when the
>   screen is blanked by no keyboard or mouse activity that the backlight
>   in the VGA monitor is still on.  The "settings->Displays" has "Unknown
>   Display" which I assume means the system does not know what commands
>   to send to the monitor to shut it off.  I booted a live DVD of 21.10
>   and the settings has the VGA display as 'AOC 22" ' which is correct
>   and the screen blanking works correctly.  So it seems that the
>   definition for the AOC displays have been removed from 22.04.
> 
>   This behavior is different on Ubuntu 21.10, the VGA display is blank and the
> backlight is off.  A minor nit is on 21.10 the "settings->Displays" shows the
> VGA display manufacture name, on 22.04 the
>   VGA display manufacture name is "Unknown Display".
> 
>   I have discovered that the settings have the following options
> 
>   "settings->Power->Screen Blank" with a time value to be selected and the
>   following text on the next line "Turns the screen off after a period of
>   inactivity"
> 
>   "settings->Privacy->Screen->Blank Screen Display" with a time value to be
>   selected and the following text on the next line "Period of inactivity after
>   which the screen will go blank"
> 
>   The two options have different actions but seem to be connected because
>   changing the time on one changes the time on the other.
> 
>   My guess is that the update changed the action for Ubuntu 22.04.  I
>   would like the 21.10 behavior, that is to turn off the VGA display not
>   just blank the display when selecting the "settings->Power->Screen
>   Blank" for 22.04.
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1975557/+subscriptions

-- 
Robert Blair


Tell me and I forget. Teach me and I remember. Involve me and I learn.  -- Xun 
Kuang (Confucian philosopher)

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

Title:
  blank screen does not turn off display backlight

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


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

[Bug 1975557] [NEW] blank screen does not turn off display backlight

2022-05-23 Thread Robert Blair
Public bug reported:

I updated a system from 21.10 to 22.04 and noticed that when the screen
is blanked by no keyboard or mouse activity that the backlight in the
VGA monitor is still on.  The "settings->Displays" has "Unknown Display"
which I assume means the system does not know what commands to send to
the monitor to shut it off.  I booted a live DVD of 21.10 and the
settings has the VGA display as 'AOC 22" ' which is correct and the
screen blanking works correctly.  So it seems that the definition for
the AOC displays have been removed from 22.04.

This behavior is different on Ubuntu 21.10, the VGA display is blank and the 
backlight is off.  A minor nit is on 21.10 the "settings->Displays" shows the 
VGA display manufacture name, on 22.04 the
VGA display manufacture name is "Unknown Display".

I have discovered that the settings have the following options

"settings->Power->Screen Blank" with a time value to be selected and the
following text on the next line "Turns the screen off after a period of
inactivity"

"settings->Privacy->Screen->Blank Screen Display" with a time value to be
selected and the following text on the next line "Period of inactivity after
which the screen will go blank"

The two options have different actions but seem to be connected because
changing the time on one changes the time on the other.

My guess is that the update changed the action for Ubuntu 22.04.  I
would like the 21.10 behavior, that is to turn off the VGA display not
just blank the display when selecting the "settings->Power->Screen
Blank" for 22.04.

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

Title:
  blank screen does not turn off display backlight

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


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

[Bug 1579469] [NEW] package samba 2:4.3.9+dfsg-0ubuntu0.15.10.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-05-07 Thread Robert Blair
Public bug reported:

This fails when the system tries to do an automatic update.

ProblemType: Package
DistroRelease: Ubuntu 15.10
Package: samba 2:4.3.9+dfsg-0ubuntu0.15.10.1
ProcVersionSignature: Ubuntu 4.2.0-35.40-generic 4.2.8-ckt5
Uname: Linux 4.2.0-35-generic i686
ApportVersion: 2.19.1-0ubuntu5
Architecture: i386
Date: Sat May  7 23:33:34 2016
DuplicateSignature: package:samba:2:4.3.9+dfsg-0ubuntu0.15.10.1:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2013-01-09 (1214 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
RelatedPackageVersions:
 nautilus 1:3.14.2-0ubuntu13
 gvfs 1.24.2-0ubuntu4
SambaClientRegression: Yes
SourcePackage: samba
Title: package samba 2:4.3.9+dfsg-0ubuntu0.15.10.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to wily on 2015-11-05 (185 days ago)

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


** Tags: apport-package i386 wily

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

Title:
  package samba 2:4.3.9+dfsg-0ubuntu0.15.10.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

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

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


[Bug 1459817] [NEW] Ubuntu 15.04 slow boot related to networking probably WIFI

2015-05-28 Thread Robert Blair
Public bug reported:

Ubuntu 15.04 boots slowly, this did not happen on version 14.10.  The
problem appears to be in the networking code, possibly WIFI.  I have
attached a bootchart file.

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Attachment added: "bootchart"
   https://bugs.launchpad.net/bugs/1459817/+attachment/4406287/+files/plot4.svg

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

Title:
  Ubuntu 15.04 slow boot related to networking probably WIFI

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

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


[Bug 812907] Re: Unallocated free space after creating parititons

2013-12-07 Thread Robert Blair
This looks the same as the problem I have.

I had another OS installed on the disk before I installed Ubuntu using
the 12.10 live CD.  There was a small primary partition, the rest of the
disk was an extended partition.  There were two partitions at the front
of the extended space so I installed Ubuntu at the end of the extended
space.  It seemed that everything was normal (for a few months) until I
tried to change the swap partition size.  When I started gparted it
listed all of the disk as free space.  The last time any changes were
made to the partition tables was the Ubuntu install.

As I see the problem the install changed the end of the extended
partition to an incorrect value.

During the install I used whatever partitioning program the install
uses.  The first partition defined was /home then swap then root, all at
the end of the free space.  The following is the output of fdisk.

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xdf5ee111

   Device Boot  Start End  Blocks   Id  System
/dev/sda1   *  63   160648001a  OS/2 Boot Manager
Partition 1 does not start on physical sector boundary.
/dev/sda4   16065   703309823   351646879+   5  Extended
Partition 4 does not start on physical sector boundary.
/dev/sda5   1612810265534 5124703+   7  HPFS/NTFS/exFAT
/dev/sda6102655983074840910241406b  W95 FAT32
Partition 6 does not start on physical sector boundary.
/dev/sda7   781461504   97677107197654784   83  Linux
/dev/sda8   703324160   78144921539062528   82  Linux swap / Solaris
/dev/sda9   625184768   70330982339062528   83  Linux

The Ubuntu partitions are listed backwards.  Notice that the end of sda4
is the same as sda9, this is wrong.

Why would any program change the end of the extended partition end
unless you were purposely changing the size of the extended partition?

I changed the end of sda4 to 976773166 which I think is correct (if not
what should it be?) and now gparted can display all the partitions on
the disk and I could change the size of the swap partition.

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

Title:
  Unallocated free space after creating parititons

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

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