Bug#952690: timeshift: Bad URL for "Homepage" at packages.debian.org

[Richard Owlett]

Package: timeshift
Severity: normal

Dear Maintainer,


A recent post suggested use of timeshift. I went to packages.debian.org and
the online version of the man page for descriptive information without
finding the information desired.

On https://packages.debian.org/buster/timeshift I clicked on
"Homepage [teejeetech.blogspot.in]" and received the message:
> You're about to be redirected
>
> The blog that used to be here is now at http://www.teejeetech.in/.
>
> Do you wish to be redirected?

The entry for "Homepage" should be updated to
   https://teejeetech.in/timeshift/

See also: https://lists.debian.org/debian-www/2020/02/msg00060.html

-- System Information:
Debian Release: 9.8
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-8-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#919634: wiki.debian.org: https://wiki.debian.org/ down

[Richard Owlett]

As of the time of this post the wiki seems to be working fine.
I browse with SeaMonkey on Debian Stretch (i386)
[User agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 
Firefox/52.0 SeaMonkey/2.49.4

Build identifier: 20180711182954]


On 01/18/2019 12:01 AM, Howard Johnson wrote:

Package: wiki.debian.org
Severity: grave
Justification: renders package unusable

wiki web server is mis-configured.

When I browse to:

 https://wiki.debian.org/

The web page returned says:

 Forbidden

 You are not allowed to access this!"


OR when viewed as source, I see this:


 
 403 Forbidden
 Forbidden
 pYou are not allowed to access this!/p



-- System Information:
Debian Release: 9.6
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#852323: debian-installer: grub-installer not convert root= entry to UUID

[Richard Owlett]

On 01/23/2017 10:03 AM, Steve McIntyre wrote:

On Mon, Jan 23, 2017 at 06:43:27PM +0300, Andrey Jr. Melnikov wrote:

Package: debian-installer
Severity: important
Tags: d-i


Installation procedure of grub2 dont't transform root= entry from /dev/sd?? to 
UUID notation.
This lead to unbootable system after install.


Hmmm. It normally does this reliably in my experience. What version of
d-i did you use, and did you follow through the menus as normal? Is
there anything special about your setup?



I suspect I have a symptom of the same, or very similar, bug.

My environment is unusual:
  1. I'm interested in extremely minimal installs.
  2. I have minimal internet connectivity thus I purchase DVD sets.

While waiting for the latest DVD set to arrive, I decided to download 
debian-9.1.0-i386-netinst.iso and write it to a USB flash drive. I then 
used it to install a very minimal system to another USB flash drive 
plugged into the *SAME USB expander*. I specified that Grub be installed 
to the MBR of the destination flash drive.


My hardware, on power on, will repeatably recognize multiple devices 
attached to the expander in a specific order {based on the physical 
location}. The install went normally and it would boot as expected *as 
long as* the source drive was present -- independent of the bios seeing 
the primary hard drive or the flash drive as the boot device. [1]


If only the destination device was present at boot time there were 
multiple scenarios.


If the bios saw the flash device as the boot device *and only if* its 
grub.cfg had had all references to /dev/sdd changed to /dev/sdb, it 
would boot successfully. [2]


The situation is more complicated if the active grub is in the MBR of 
the permanently installed HDD (/dev/sda). I had noticed that running 
update-grub did not always yield a workable menu entry. It's a 
pathological corner case and I did not record the circumstances.


I see the need to perform multiple installs to document exactly what 
factors trigger a failure. Before I run them I need to know what log 
files I should preserve for each case.


I also suspect that Bug#876866 is related.


[1]  What happens is dependent on whether or not my WiFi hub is attached 
to the USB3 port having priority over the USB2 port into which the port 
expander was attached.


[2]  My WiFi was plugged into the USB3 port during install.

Bug#865535: arandr: Does not use applied settings on reboot

[Richard Owlett]

Package: arandr
Version: 0.1.9-2
Severity: normal

Dear Maintainer,

   * What led up to the situation?
I had chosen settings to be:
  laptop as1366 x 768  and normal orientation
  vga monitor as   1280 x 1024 and normal orientation
  the vga monitor was selected as "Active"
I the applied the settings by clicking the the green checkmark.
In my trouble shooting I used the "Layout -> Save As" menu item to save 
the settings in  .

I expected the settings be maintained across a reboot.
The resolution & orientation were.
The vga as Active *WAS NOT*.
The desktop environment is MATE.
Running the saved script manually had the desired effect.

I noticed 3 other things of unknown relevance:
  1. The MATE desktop appears properly on both screens after a reboot.
  2. The problem occurs for applications independent of how launched.
  3. The "Layout -> Properties" menu item displays
 >
 >> #!/bin/sh
 >> %(xrandr)s
 >
  It is neither editable nor apparently proper syntax.

-- Package-specific info:
Output of /usr/share/bug/arandr:
$ xrandr --version
xrandr program version   1.5.0
Server reports RandR version 1.5
$ xrandr --query --current
Screen 0: minimum 320 x 200, current 1366 x 1024, maximum 8192 x 8192
LVDS-1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 
345mm x 194mm
VGA-1 connected primary 1280x1024+0+0 (normal left inverted right x axis 
y axis) 338mm x 270mm


-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-3-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages arandr depends on:
ii  python 2.7.13-2
ii  python-gtk22.24.0-5.1
ii  x11-xserver-utils  7.7+7+b1

arandr recommends no packages.

arandr suggests no packages.

-- no debconf information

Bug#313303: Should this bug be closed?

[Richard Owlett]

I have verified this bug does not appear in Debian Testing which has 
Tomboy 1.14.1 .


Upstream  reports 
it as not seen in Linux as of Feb 2013.

Bug#693464: installation-reports: Root password not recognized when requested and can run in rescue mode wo password

[Richard Owlett]

Holger Wansing wrote:

Hi,

Richard Owlett rowl...@cloud85.net wrote:

Package: installation-reports
Severity: important

*** Please type your report below this line ***

_PROBLEM HISTORY_
I've been doing a series of Debian installs over the last
several months.
Purpose:Evolve a install meeting a personal minimal and
Functional.
Constraint: NO network physically available. Install from
purchased set of DVDs.

I have a history of problems with the root password not
being recognized.


It would be useful, if you could try to reproduce that bug with
the current daily build for Wheezy:
http://www.debian.org/devel/debian-installer/


thanks
Holger




Got an unexpected chance to go to local library yesterday 
(11/17), but only had time to download first CD from page 
you referenced.
I think, from just rereading page, it's a weekly rather than 
daily build. Identifying info 
debian-wheezy-DI-b3-i386-CD-1.iso, size 678428672 bytes, 
MD5: 3ffcca4aaa228260ac8799134cf8533c.


I did the install twice.
When shadow password was *NOT* enabled the problem 
occurred as in my original report.
When shadow password was  enabled the problem did *NOT* 
occur.


I launched only from 1st line in GRUB menu - did not test in 
'rescue mode'.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#693464: installation-reports: Root password not recognized when requested and can run in rescue mode wo password

[Richard Owlett]

Holger Wansing wrote:

Hi,

Richard Owlett rowl...@cloud85.net wrote:

Package: installation-reports
Severity: important

*** Please type your report below this line ***

_PROBLEM HISTORY_
I've been doing a series of Debian installs over the last
several months.
Purpose:Evolve a install meeting a personal minimal and
Functional.
Constraint: NO network physically available. Install from
purchased set of DVDs.

I have a history of problems with the root password not
being recognized.


It would be useful, if you could try to reproduce that bug with
the current daily build for Wheezy:
http://www.debian.org/devel/debian-installer/


thanks
Holger



I only have occasional acces to a high speed internet 
connection. Normal connection is dial-up :(



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#693464: installation-reports: Root password not recognized when requested and can run in rescue mode wo password

[Richard Owlett]

Package: installation-reports
Severity: important

*** Please type your report below this line ***

_PROBLEM HISTORY_
I've been doing a series of Debian installs over the last 
several months.
Purpose:Evolve a install meeting a personal minimal and 
Functional.
Constraint: NO network physically available. Install from 
purchased set of DVDs.


I have a history of problems with the root password not 
being recognized.


If the problem *DOES* occur on a  individual install 
iteration , it *WILL* occur
on *EVERY* cold boot and *EVERY* time a root password is 
required.
If the problem *DOESN'T* occur on a  individual install 
iteration , it *WILL NEVER* occur on *ANY* cold boot and

*ANY* time a root password is required.

The problem is independent of:
   a.   install media- downloaded LiveCD or purchased 8 
DVD set
   b.   install mode- whether or not graphical is in 
menu line chosen

   b.   target machine - Lenovo ThinkPad or Lenovo desktop

For history of my investigation see thread beginning at 
http://lists.debian.org/507ee968.2000...@cloud85.net .


_TEST PROCEDURE USED TO DEMONSTRATE PROBLEM_
Power off the machine
Power up and chose DVD as boot device
With Debian 6.0.5 DVD 1 of 8 in drive, select Graphical 
Expert Install


from here on only entries when default entry NOT 
chosen


1. after network configuration failed due *NO* network existing
   chose Do not configure network at this time
2. Did not enable shadow passwords
3. Did not chose set clock using NTP
4. Set time zone to Central
5. Partitioning choices made
   Manual
   Delete *ALL* existing partitions
   Create a 20 GB primary partition at beginning of drive, 
format as Ext3,  mount point /

   Create a 5 GB logical partition at end of drive for swap
6. Driver selection - Generic [I usually choose targeted]
7. Software selection - Chose ONLY Standard system utilities
8. Finish the installation - said clock not set to UTC


First boot after install
1. User name and password accepted
2. Attempted sudo apt-get install gdm3
   Received error message -bash: sudo: command not found
3. Attempted su, neither root nor user password accepted
4. Rebooted with CNTRL-ALT-DEL
5. Chose rescue mode
6. System appeared to start as expected

   The last three lines displayed on monitor are:

Setting up console font and keymap...done.CRLF
sulogin: root account is locked, starting shellCRLF
root@debian:~# [9.683173] IBM TrackPoint firmware: 0x0e, 
buttons: 3/3
[9.892571] input: TPPS/2 IBM TrackPoint as 
/devices/platform/i8042serio1/serio2/input/input10


I then hit ENTER receiving a new prompt of root@debian~#

7. Entered apt-get install gdm3, received a prompt of Do 
you want to continue [Y/n]? to which I responded with ENTER


*NOTE BENE* NO PASSWORD(s) were requested or given after I 
started Rescue mode.


8. That process appeared to run to a normal finish.
9. Then entered apt-get install gedit gparted which also 
seemed to conclude normally.

10. Rebooted by typing exit
11. Received an apparently normal Gnome request for password 
which was accepted.
12. Attempted to run both root terminal and gparted, 
neither would recognize the root password.



Re-did the above installation except chose Install when 
DVD booted.
Every thing was the same through Step 2 under 1st boot 
after install.


When entering su in step 3, the root password *WAS* accepted.
Doing apt-get install gdm3 and apt-get install gedit 
gparted both proceeded to apparently normal finish. Typing 
exit returned me to the user prompt. I then rebooted using 
CNTRL-ALT-DEL.


Attempting to run Root Terminal proceeded normally thru 
prompting and accepting the root password. The terminal did 
not appear - I've had that happen before, apparently 
although the icon for Root Terminal appears in the 
Applications sub-menu, the underlying program is not installed.


Gparted started without asking for a password while 
displaying the screen titled Granted permissions without 
asking for password. Confirmed my suspicion by powering 
down and rebooting. This time I started Gparted first [it 
did ask for root password] and then attempting to star Root 
Terminal. I received the screen titled Granted permissions 
without asking for password. The Root Terminal again DID 
NOT appear. Installing gnome-terminal with Synaptic caused 
Terminal to appear in Applications menu. Now both Root 
Terminal and Terminal are functional.



-- Package-specific info:

Boot method: CD
Image version: Debian GNU/Linux 6.0.5 Squeeze - Official 
i386 DVD Binary-1  20120512-13:45



Machine: Lenovo R61 ThinkPad


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't 
try it


Initial boot:   [O]
Detect network card:[O]
Configure network:  [E]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Install base system:[O]

Bug#687804: installation-reports: users are not able to review external documentation while stuck in the installer

[Richard Owlett]

Christian PERRIER wrote:

Quoting lee (l...@yun.yagibdah.de):

Package: installation-reports
Severity: wishlist

Dear Maintainer,

this is a feature request:  It would be nice if users would have at
least a web browser like lynx and an irc client available while they
are using the installer.  There has been/currently is a lengthy
discussion about this on the debian-user mailing list starting with



Frankly speaking, I would very much prefer seeing people working on
current issues of the installer (I mean, not only during 3 months
before the release) rather than adding more bells, whistles and shiny
new features. It would be great if existing features were kept working
during the entire release process.

This is of course not targeted at you who reported this bug (don't
shoot the messenger)but more at all these people who have great ideas
on debian-user but never show up in development teams.

If you want a web browser, an IRC client, games, etc. in D-I, then
please come and first fix issues related to GRUB and encrypted
partitions, partitions sizes, preseeding, documentation, etc. *Then*
we'll see if we add a web browser.




As I tried to say elsewhere in this thread, I suspect the 
solution already exists in the liveCD. [and as an aside to 
Mr. Thibault  the reason I believe so is having used the CD 
and followed several discussions on several Debian groups]


There are icons in lower right for several workspaces.
I've seen comments about switching consoles with function 
key combinations.


Should one not be able to switch out of the installation 
process and into a browser (2 are already included) to 
search out answers? Although launching a browser internally 
and loading a specific link may be a significant effort, if 
my idea is technically feasible it would apparently only 
require a page of instructional text.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#687804: installation-reports: users are not able to review external documentation while stuck in the installer

[Richard Owlett]

Samuel Thibault wrote:

lee, le Sun 16 Sep 2012 04:29:21 +0200, a écrit :

The goal would be to give users a working system included on the
installer CD/DVD that provides them at least with a (graphical) web
browser, software to burn installation CDs/DVDs/bluerays, an irc
client and other useful tools so that they can communicate and read
web pages and are able to overcome problems that they may have during
the installation.


Mmm, this just seems like the liveCD that we already have, doesn't it?

Samuel



No, not really.
Although I suspect all the tools exist on the liveCD such 
that a Linux *EXPERT* could accomplish the op's goal.


Consider the flowing sequence of events.

1. Your grandmother has been been using a proprietary OS and 
its associated
   browser/email program. IOW, computer literate enough to 
be comfortable

   being a _user_.
2. You talk up the advantages of Linux and give her a 
liveCD, demonstrating

   how to boot and do her favorite three tasks.
3. One morning, while you are at work, she decides she will 
install Debian.
   After all that inviting 'install icon' is on screen and 
she has liked her

   experience.
4. She clicks install.
5. She is asked a question and does not know what a key 
word/idea means.

   She knows she could Google it.
   But no connection to WEB.
6. Linux declared uninstallable :

[I'm tempted to paraphrase the nursery rhyme starting For 
want of ...]



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#280348: #280348: d-i manual: how to burn the bootable cd-rom

[Richard Owlett]

Holger Wansing wrote:

In this old bugreport it is requested, to describe in the
manual how to burn a bootable CD.

But in the relevant chapter 4.1 there is a link to
http://www.debian.org/CD/ which has a prominent link to
the FAQ about Debian CDs.
And that FAQ describes several methods to create a bootable
CD, on different OSses.

Since there is no need to have such info existing several
times, this bug can be closed IMHO.

Comments?

Holger



As a relatively new user, I would replace the link to 
http://www.debian.org/CD/ with a link directly to the FAQ 
http://www.debian.org/CD/faq/. This would imply moving 
what little information is not already in the FAQ there.



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org