Re: unmet dependencies: libcurl4-openssl-dev
Sivaram Neelakantan wrote: > This is what I have. > > --8<---cut here---start->8--- > cat /etc/apt/sources.list > # > > # deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 > LIVE/INSTALL Binary 20141121-01:55]/ wheezy main > > #deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 > LIVE/INSTALL Binary 20141121-01:55]/ wheezy main The above looks noisy to me. I suggest removing those commented out entries to simplify. > deb http://kartolo.sby.datautama.net.id/debian/ wheezy main > deb-src http://kartolo.sby.datautama.net.id/debian/ wheezy main > > deb http://security.debian.org/ wheezy/updates main > deb-src http://security.debian.org/ wheezy/updates main > > # wheezy-updates, previously known as 'volatile' > deb http://kartolo.sby.datautama.net.id/debian/ wheezy-updates main > deb-src http://kartolo.sby.datautama.net.id/debian/ wheezy-updates main Okay. kartolo.sby.datautama.net.id appears to be an up to date mirror. Looks okay. > #wheezy backports > #deb http://kartolo.sby.datautama.net.id/debian wheezy-backports main Wheezy backports is okay. > #wheezy R packages > deb http://ftp5.gwdg.de/pub/misc/cran/bin/linux/debian wheezy-cran3/ > #deb http://cran.uni-muenster.de/bin/linux/debian wheezy-cran3/ When tracking down installation errors I am always suspicious of third party repositories. They tend to be the problem. I would comment that out while you are debugging the current problem. > The backports line, I added to get emacs24.4 and then commented it out > again. Yay! Backports! :-) > Tried the above, nothing happens. No errors or anything. And the > libcurl4 install still fails What is your output for this? Here is what it should show. $ apt-cache policy libcurl4-openssl-dev librtmp-dev libcurl4-openssl-dev: Installed: (none) Candidate: 7.26.0-1+wheezy11 Version table: 7.26.0-1+wheezy11 0 500 http://security.debian.org/ wheezy/updates/main amd64 Packages 7.26.0-1+wheezy10 0 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages librtmp-dev: Installed: (none) Candidate: 2.4+20111222.git4e06e21-1 Version table: 2.4+20111222.git4e06e21-1 0 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages Your previous error said it could not install librtmp-dev as a dependency. But it should be in the archive right next to it. > >> I've recently started using debian and apart some fiddling to get > >> the latest emacs24.4 on wheezy I have not done anything on the > >> system. > > > > Alarm bells! Alarm bells! Exactly what did you do to install Emacs > > 24 on Wheezy? Wheezy released with Emacs 23 of course. > > After adding the backports to the sources.list, I did a apt-get > install of emacs24.4 and that installed what I wanted. Okay. All good! Backports should be okay. I was worried because people sometimes do really scary things. But emacs from backports should be just fine. Bob signature.asc Description: Digital signature
Re: Write s.o. image with different programm?
On Wed, Feb 04, 2015 at 03:18:50PM +0100, antispammbox-27 wrote: > > Hi all > > It's possible writing an image, build with Macrium Reflect, with another > programm, as: dd, partimage, In theory, yes. Assuming that the image is just that, then you can copy it to a drive however you like. A disk image (be it of a CD/DVD (e.g. .iso), a floppy, or a hard drive partition), is simply a bit-for-bit copy of a file system, stored in a file rather than directly on a partition. If you copy the file to the start of a partition, then that becomes a normal partition. Be certain to check that the image IS only an image. It is perfectly possible for "disk images" or "virtual disks" to contain metadata (headers, footers etc) which shouldn't be written to the disk. If you can do the following without error: # mount -o loop YourDiskImage.file /mnt/somwehere ; umount /mnt/somewhere then you can safely assume that the image may be written out with cat, dd, etc. > > Thanks > > Regards > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject > of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: https://lists.debian.org/ACD68559A06B4E3A9BAB78E3038E941E@rx > signature.asc Description: Digital signature
CRON: Authentication token is no longer valid; new one required
Hello, I am trying to run cron from /etc/cron.d with the root account which has password disabled in order not to be able to login as root but when the cron entry wants to run it simply does not and show the following error message in the log file: CRON[16785]: Authentication token is no longer valid; new one required Any idea how to run a cronjob from /etc/cron.d with the root account disabled? Regards ML -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/951355195.151465.1423133245608.javamail.ya...@mail.yahoo.com
Re: 3rd new wheezy install
On Wed, Feb 04, 2015 at 09:57:50AM -0500, Gene Heskett wrote:
> On Tuesday, February 03, 2015 05:01:46 AM Darac Marjal wrote:
> > On Mon, Feb 02, 2015 at 06:16:34PM -0500, Gene Heskett wrote:
[cut]
>
> My point in all this is that the installer WILL NOT ALLOW you, in any mode,
> to
> just format and label a partition and use it. Try to skip the partitioner and
> go on to the next step it will NOT allow. The only way you can get past that
> is to allow it to write a broken partition table So ATM, I have no clue if
> this drive is partition synchronized so that the 2 partitioms on it, / &
> swap,
> are in fact sector aligned.
OK. For clarity, I'm going to go through this on an existing VM I have
(so already partitioned). I am using the Debian Wheezy 7.8.0 Net Install
CD from here: https://www.debian.org/distrib/netinst
I boot from the CD (ISO) and, at the boot prompt, select "Install"
I walk through the language selection and wait for "Loading Additional
Components".
Networking auto configures and I leave the hostname and domain at
default.
I leave the root password blank and enter details for a new user.
At this point, we get to the dialog marked "Partition disks". My options
here are "Guided - use entire disk", "Guided - use entire disk and set
up LVM", "Guided - use entire disk and set up encrypted LVM" and
"Manual". I choose *"Manual"*.
This takes me into the partitioner itself. There are four menu options
at the top ("Guided partitioning", "Configure software RAID", "Configure
the Logical Volume Manager", "Configure encrypted volumes"), a blank
line and then the layout of my existing disks. In my case, it starts
with a line for the disk "SCSI3 (0,0,0) (sda) - 8.6 GB ATA VBOX
HARDDISK", then a line for each of the partitions "#1 primary
8.2 GB B ext4", "#5 logical 401.6 MB F swap swap" etc. And
finally, there are two "exit" actions: "Undo changes to the partitions"
and "Finish partitioning and write changes to the disk".
At this point, the installer has made no changes to the existing
partitions.
I move the red-bar cursor down to the line starting "#1 primary" and
press enter, as that is the partition where I wish to install Debian.
I now get a dialog starting "You are editing partition #1 of SCSI3 ...".
Here, my options are "Use as: do not use", "Bootable flag: on",
"Resize the partition (currently 8.2GB)" and so on. I move the cursor to
"Use as: do no use" (well, it's already there) and press enter.
I am taken to a selection dialog where I can choose the file system to
put on partition #1. For the sake of argument, I select the top entry
"Ext4 journaling file system".
This takes me back to the previous level, but now I have extra options.
The "Use as:" line now shows the partition will become an Ext4 file
system and below that are the options "Format the partition: no, keep
existing data" (if the installer determines that the partition is blank,
this may read "yes, format it"), "Mount point: none", "Mount options:
defaults" and "Bootable flag: on".
As I am using a single partition, I scroll down to "Mount point: none",
press enter and from the selection dialog, choose "/ - the root file
system".
Finally, I scroll down to "Done setting up the partition" and press
enter.
So, now I'm back at the top level of the partitioner. The layout of my
disk is shown again. This time, the last column of the table of
partitions shows that partition #1 will be used as "/", and partition #5
will be used as "swap".
If I now wanted to proceed with installation I would scroll down to
"Finish partitioning and write changes to disk". This would *NOT ALTER
THE PARTITION TABLE*, it would merely format the partitions (#1 would me
made ext4 and #5 would be re-initialised as swap). Installation would
then proceed.
Now, IF you've been following that procedure AND your installer isn't
behaving in the same manner, then hit a bug in the installer that hasn't
been spotted in about 18 months of regular use by many people.
>
> What is very discouraging in all this is that to a person, you _al_l believe
> the installer can do no wrong, AND its onvious that this list is not in any
> way connected to the people that build the install, so you are not telling
> the
> install image people there is a problem with how it handles these new 4k
> sector disks.
>
> So the problem is not going to get fixed due to a lack of communication. Your
> bug tracker isn't accessible to me as I don't even have incoming mail setup
> such that I could confirm the subscription I'd need to file the bug. Chicken
> v
> egg.
You could always create an account with any of the free webmail
providers (gmail, yahoo, outlook etc) and use that.
>
> Cheers, Gene Heskett
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Archive: https://lists.debian.org/201502040957.50087.
>
signature.asc
Description: Dig
Re: unmet dependencies: libcurl4-openssl-dev
On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote: > Sivaram Neelakantan wrote: > > > deb http://kartolo.sby.datautama.net.id/debian/ wheezy main > > Okay. kartolo.sby.datautama.net.id appears to be an up to date > mirror. Looks okay. Not only does it look okay but it also behaves okay for me. With that as the only line in sources.list I had no problem installing libcurl4-openssl-dev. [Snip] > Your previous error said it could not install librtmp-dev as a > dependency. But it should be in the archive right next to it. Perhaps the OP can have a single line as I did and try apt-get install librtmp-dev If there is any failure we would want to see the complete output of the command. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/05022015115630.907ef3c23...@desktop.copernicus.demon.co.uk
H.264 on Iceweasel
I'm trying to make H.264 encoding work on Iceweasel 35. I'm using Debian testing (Jessie) with Iceweasel from the Mozilla team because many sites complain that the official testing version is too old. I'm trying not to compile Iceweasel myself, I believe there is a simple way to get H.264 working. In the about:buildconfig, I see the --enable-gstreamer=0.10 flag. I have gstreamer0.10-ffmpeg and gstreamer0.10-plugins-base installed. There must be some configuration I'm missing. Can anybody help? -- Bruno Schneider http://www.dcc.ufla.br/~bruno/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP1wdQufN=unncoxQsyX2U3WePSXkR=prtyzyvn0_burczu...@mail.gmail.com
SSL error in (e)links(2) web browers
When I use links2 or elinks web browsers on some websites when https is protocol I get error "Error loading ... SSL error" and page is not loaded. -- http://markorandjelovic.hopto.org One should not be afraid of humans. Well, I am not afraid of humans, but of what is inhuman in them. Ivo Andric, "Signs near the travel-road" -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205134827.4e418...@eunet.rs
Re: 3rd new wheezy install
On Thursday 05 February 2015 11:08:51 Darac Marjal wrote: > Now, IF you've been following that procedure AND your installer isn't > behaving in the same manner, then hit a bug in the installer that hasn't > been spotted in about 18 months of regular use by many people. I think if it were a bug, we would have been given a proper description of it by now. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502051411.31588.lisi.re...@gmail.com
Re: H.264 on Iceweasel
On Thu, Feb 05, 2015 at 10:12:08AM -0200, Bruno Schneider wrote: > I'm trying to make H.264 encoding work on Iceweasel 35. I'm using > Debian testing (Jessie) with Iceweasel from the Mozilla team because > many sites complain that the official testing version is too old. > > In the about:buildconfig, I see the --enable-gstreamer=0.10 flag. I have > gstreamer0.10-ffmpeg and gstreamer0.10-plugins-base installed. There > must be some configuration I'm missing. IIRC gstreamer0.10-plugins-bad and libgstreamer-plugins-bad0.10-0 should bring you the mp4 / H.264 support. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205152842.ga25...@timegate.de
Re: unmet dependencies: libcurl4-openssl-dev
On Thu, Feb 05 2015,Bob Proulx wrote: > Sivaram Neelakantan wrote: [snipped 36 lines] > > When tracking down installation errors I am always suspicious of third > party repositories. They tend to be the problem. I would comment > that out while you are debugging the current problem. > Done. and did an update too. >> Tried the above, nothing happens. No errors or anything. And the >> libcurl4 install still fails > > What is your output for this? Here is what it should show. > > $ apt-cache policy libcurl4-openssl-dev librtmp-dev > libcurl4-openssl-dev: > Installed: (none) > Candidate: 7.26.0-1+wheezy11 > Version table: > 7.26.0-1+wheezy11 0 > 500 http://security.debian.org/ wheezy/updates/main amd64 Packages > 7.26.0-1+wheezy10 0 > 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages > librtmp-dev: > Installed: (none) > Candidate: 2.4+20111222.git4e06e21-1 > Version table: > 2.4+20111222.git4e06e21-1 0 > 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages --8<---cut here---start->8--- apt-cache policy libcurl4-openssl-dev librtmp-dev libcurl4-openssl-dev: Installed: (none) Candidate: 7.26.0-1+wheezy12 Version table: 7.26.0-1+wheezy12 0 500 http://security.debian.org/ wheezy/updates/main amd64 Packages 7.26.0-1+wheezy11 0 500 http://kartolo.sby.datautama.net.id/debian/ wheezy/main amd64 Packages librtmp-dev: Installed: (none) Candidate: 2.4+20111222.git4e06e21-1 Version table: 2.4+20111222.git4e06e21-1 0 500 http://kartolo.sby.datautama.net.id/debian/ wheezy/main amd64 Packages --8<---cut here---end--->8--- I still have the same errors. [snipped 15 lines] sivaram -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87wq3w2svj@gmail.com
Re: unmet dependencies: libcurl4-openssl-dev
On Thu, Feb 05 2015,Brian wrote: > On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote: > >> Sivaram Neelakantan wrote: [snipped 16 lines] > Perhaps the OP can have a single line as I did and try > > apt-get install librtmp-dev > > If there is any failure we would want to see the complete output of the > command. > > Tried that, no cigar. Got more errors. Now what? :) --8<---cut here---start->8--- apt-get install libcurl4-openssl-dev Reading package lists... Done Building dependency tree Reading state information... Done 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: libcurl4-openssl-dev : Depends: libcurl3 (= 7.26.0-1+wheezy11) but 7.26.0-1+wheezy12 is to be installed Depends: libkrb5-dev but it is not going to be installed Depends: librtmp-dev but it is not going to be installed Depends: libssl-dev but it is not going to be installed E: Unable to correct problems, you have held broken packages. --8<---cut here---end--->8--- sivaram -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87siek2smr@gmail.com
Re: 3rd new wheezy install
On Wednesday, February 04, 2015 11:32:07 AM Chris Bannister wrote: > On Wed, Feb 04, 2015 at 09:57:50AM -0500, Gene Heskett wrote: > > convenience. This install is about the 6th I have done, and I am back to > > the only way that works, which it let the SOB use all the disk as it > > sees fit. And this is not a wheezy install as such, that install has > > self destructed within 2 hours of the initial reboot while I was trying > > to recover data that is in some cases 15 years old from the failing > > drive. > > What do you mean here? How can you have 15 yr old data on a newly > installed system? > The failing drive can still be read. Some of this data has now been on 10+ drives in the life of my use of linux, since 1998 TBE. > > What is very discouraging in all this is that to a person, you _al_l > > believe the installer can do no wrong, AND its onvious that this list is > > not in any way connected to the people that build the install, so you > > are not telling the install image people there is a problem with how it > > handles these new 4k sector disks. > > You're going to have provide technical data. You must have worked on > faults where the customer was saying on thing, but you knew you needed > to check certain conditions yourself for diagnostic purposes. > That I have already posted, showing the output reports from other partitioners say that thew partition boundary does NOT start on a sector boundary. The partition boundary is normally considered to begin at any 512 byte sector on the drive. But these new high capacity drives ARE 4096 bytes per sector, so if the partitioner is dumber than a rock, you only get the correct partition vs sector 12.5% of the time. And the partitoner that will not allow one to bypass its fscked up write on partition tables IS DUMBER THAN A ROCK. > > So the problem is not going to get fixed due to a lack of communication. > ene@coyote:~$ sudo fdisk -l /dev/sda > Correct, it's not. Hard data is what's required. You are getting it! Here is an example from this operating drive right now: $> sudo fdisk -l /dev/sda [sudo] password for gene: Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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: 0x000657ed Device Boot Start End Blocks Id System /dev/sda1 *2048 1919977471 959987712 83 Linux /dev/sda2 1919979518 1953523711167720975 Extended Partition 2 does not start on physical sector boundary. /dev/sda5 1919979520 195352371116772096 82 Linux swap / Solaris See that physical sector size? 4096 bytes. And the minimum I/O size? 4096 bytes. Then note carefully what it says about partition 2, which is swap. Because of that miss-alignment, swap will be even slower than it usually is. Linux CAN work around it, but its at the cost of all that read-modify-write math it has to use to compensate that in the swap address scheme, base 0 may be as far as 3584 bytes out of alignment with the beginning of that physical sector. Half or more of the drives speed, plus at least 1 revolution of the platters after the math and buffer modification has been done before it can write valid data back. How hard is that to understand, its a variation on a theme I've been fussing about for a week. Now, I can fix it, but the version of gparted I have, works in cylinder boundaries, or if that is turned off, in mebibyte increments, neither of which will automatically align on a 4096 byte per sector drive unless you start the first partition 8 mebibytes into the start of the drive. I have tried 1, 2 & 4, which does not align. 8 does. > > > bug tracker isn't accessible to me as I don't even have incoming mail > > setup such that I could confirm the subscription I'd need to file the > > bug. Chicken v > > To be honest, a bug report in the manner you've reported here would not > be at all helpful. You need to explain what you did, what you expected > what the actual outcome was so that the person dealing with the bug can > reproduce it using the same tools you used. Thats the other point, I didn't do it, the installer forced me to do it its way, there is no way to bypass it, even in the expert mode. That I tried 6 or 7 times, it simply will not allow you to proceed until it has written a defective partition table, and then spends about an hour doing the mke2fs thing on a miss-aligned drive. Something it should be able to do in 3 or 4 minutes on a terrabyte drive. Now, if I have not explained it well enough for you, please show this message to someone more familiar with the partitioner you use. Just because you don't understand it, doesn't make it "not a problem". It is, and the partitioner writers NEED TO BE TOLD there is a problem, and it needs to be addressed s
Re: 3rd new wheezy install
On Thu, 5 Feb 2015 11:34:18 -0500 Gene Heskett wrote: > > What do you mean here? How can you have 15 yr old data on a newly > > installed system? > The failing drive can still be read. Some of this data has now been on 10+ > drives in the life of my use of linux, since 1998 TBE. This is why , having been bit once, follow the procedure for new installations: - Have the /home directory on a separate physical unit. - Physically disconnect said unit during the install. - Reconnect after the install has been done without problem, adding the relevant line to /etc/fstab. Cheers, Ron. -- Never express yourself more clearly than you are able to think. -- Niels Bohr -- http://www.olgiati-in-paraguay.org -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205144819.50bc4...@ron.cerrocora.org
Re: 3rd new wheezy install
I think we should stop replying to this troll. He has taken up an enormous amount of list time and ignores anything helpful anyone says. (cf Darac Marjal's patient exposition.) He continues to refuse to explain himself properly, and is now resorting to being insulting in his rants. Lisi On Thursday 05 February 2015 16:34:18 Gene Heskett wrote: > On Wednesday, February 04, 2015 11:32:07 AM Chris Bannister wrote: > > On Wed, Feb 04, 2015 at 09:57:50AM -0500, Gene Heskett wrote: > > > convenience. This install is about the 6th I have done, and I am back > > > to the only way that works, which it let the SOB use all the disk as it > > > sees fit. And this is not a wheezy install as such, that install has > > > self destructed within 2 hours of the initial reboot while I was trying > > > to recover data that is in some cases 15 years old from the failing > > > drive. > > > > What do you mean here? How can you have 15 yr old data on a newly > > installed system? > > The failing drive can still be read. Some of this data has now been on 10+ > drives in the life of my use of linux, since 1998 TBE. > > > > What is very discouraging in all this is that to a person, you _al_l > > > believe the installer can do no wrong, AND its onvious that this list > > > is not in any way connected to the people that build the install, so > > > you are not telling the install image people there is a problem with > > > how it handles these new 4k sector disks. > > > > You're going to have provide technical data. You must have worked on > > faults where the customer was saying on thing, but you knew you needed > > to check certain conditions yourself for diagnostic purposes. > > That I have already posted, showing the output reports from other > partitioners say that thew partition boundary does NOT start on a sector > boundary. The partition boundary is normally considered to begin at any > 512 byte sector on the drive. > > But these new high capacity drives ARE 4096 bytes per sector, so if the > partitioner is dumber than a rock, you only get the correct partition vs > sector 12.5% of the time. > > And the partitoner that will not allow one to bypass its fscked up write on > partition tables IS DUMBER THAN A ROCK. > > > > So the problem is not going to get fixed due to a lack of > > > communication. > > > > ene@coyote:~$ sudo fdisk -l /dev/sda > > > > Correct, it's not. Hard data is what's required. > > You are getting it! Here is an example from this operating drive right > now: $> sudo fdisk -l /dev/sda > [sudo] password for gene: > > Disk /dev/sda: 1000.2 GB, 1000204886016 bytes > 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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: 0x000657ed > >Device Boot Start End Blocks Id System > /dev/sda1 *2048 1919977471 959987712 83 Linux > /dev/sda2 1919979518 1953523711167720975 Extended > Partition 2 does not start on physical sector boundary. > /dev/sda5 1919979520 195352371116772096 82 Linux swap / > Solaris > > See that physical sector size? 4096 bytes. And the minimum I/O size? 4096 > bytes. > > Then note carefully what it says about partition 2, which is swap. Because > of that miss-alignment, swap will be even slower than it usually is. Linux > CAN work around it, but its at the cost of all that read-modify-write math > it has to use to compensate that in the swap address scheme, base 0 may be > as far as 3584 bytes out of alignment with the beginning of that physical > sector. Half or more of the drives speed, plus at least 1 revolution of > the platters after the math and buffer modification has been done before it > can write valid data back. > > How hard is that to understand, its a variation on a theme I've been > fussing about for a week. > > Now, I can fix it, but the version of gparted I have, works in cylinder > boundaries, or if that is turned off, in mebibyte increments, neither of > which will automatically align on a 4096 byte per sector drive unless you > start the first partition 8 mebibytes into the start of the drive. I have > tried 1, 2 & 4, which does not align. 8 does. > > > > bug tracker isn't accessible to me as I don't even have incoming mail > > > setup such that I could confirm the subscription I'd need to file the > > > bug. Chicken v > > > > To be honest, a bug report in the manner you've reported here would not > > be at all helpful. You need to explain what you did, what you expected > > what the actual outcome was so that the person dealing with the bug can > > reproduce it using the same tools you used. > > Thats the other point, I didn't do it, the installer forced me to do it its > way, there is no way to bypass it, even in the expert mode. That I tried 6 > or 7 times, it simply will not allow you to proceed until it ha
Re: unmet dependencies: libcurl4-openssl-dev
On Thu 05 Feb 2015 at 22:38:28 +0530, Sivaram Neelakantan wrote: > On Thu, Feb 05 2015,Brian wrote: > > > On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote: > > > >> Sivaram Neelakantan wrote: > > [snipped 16 lines] > > > Perhaps the OP can have a single line as I did and try > > > > apt-get install librtmp-dev > > > > If there is any failure we would want to see the complete output of the > > command. > > > > > > Tried that, no cigar. Got more errors. Now what? :) First we point out the command you were invited to run *and* give the output of was apt-get install librtmp-dev Next we look at the output you did give. > --8<---cut here---start->8--- > apt-get install libcurl4-openssl-dev > Reading package lists... Done > Building dependency tree > Reading state information... Done > 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: > libcurl4-openssl-dev : Depends: libcurl3 (= 7.26.0-1+wheezy11) but > 7.26.0-1+wheezy12 is to be installed The libcurl4-openssl-dev which depends on libcurl3 (= 7.26.0-1+wheezy11) is version 7.26.0-1+wheezy11. So the question becomes: Why does your system want to install this version when 7.26.0-1+wheezy12 is on your mirror and 'apt-cache policy libcurl4-openssl-dev' has it as an installation candidate? If you are becoming desparate you could download 7.26.0-1+wheezy12, install with dpkg -i and run 'apt-get -f install'. This should stand some chance of success. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205180659.ga3...@copernicus.demon.co.uk
Re: H.264 on Iceweasel
On Thu, Feb 5, 2015 at 1:28 PM, Sven Hoexter wrote: > > IIRC gstreamer0.10-plugins-bad and libgstreamer-plugins-bad0.10-0 > should bring you the mp4 / H.264 support. > No, after installation, YouTube still tells me that H.264 is not supported. -- Bruno Schneider http://www.dcc.ufla.br/~bruno/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cap1wdqstm_g_gcoq01eutbpcm7sm+-tevfbnixcjfntqkye...@mail.gmail.com
Re: H.264 on Iceweasel
On 05/02/15 13:12, Bruno Schneider wrote: I'm trying to make H.264 encoding work on Iceweasel 35. I'm using Debian testing (Jessie) with Iceweasel from the Mozilla team because many sites complain that the official testing version is too old. I'm trying not to compile Iceweasel myself, I believe there is a simple way to get H.264 working. In the about:buildconfig, I see the --enable-gstreamer=0.10 flag. I have gstreamer0.10-ffmpeg and gstreamer0.10-plugins-base installed. There must be some configuration I'm missing. Can anybody help? Try purging and reinstalling totem. I just did that (well I actually purged everything gstreamer-related) but I did not get back h.264 support until after I reinstalled totem. Just the 2 plugins Sven mentioned were not enough for me. I am running unstable, but the issue seems the same. Hope that helps, Chris -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d3b255.4080...@cevnet.info.tm
Re: 3rd new wheezy install
On Thursday, February 05, 2015 06:08:51 AM Darac Marjal wrote:
> On Wed, Feb 04, 2015 at 09:57:50AM -0500, Gene Heskett wrote:
> > On Tuesday, February 03, 2015 05:01:46 AM Darac Marjal wrote:
> > > On Mon, Feb 02, 2015 at 06:16:34PM -0500, Gene Heskett wrote:
> [cut]
>
> > My point in all this is that the installer WILL NOT ALLOW you, in any
> > mode, to just format and label a partition and use it. Try to skip the
> > partitioner and go on to the next step it will NOT allow. The only way
> > you can get past that is to allow it to write a broken partition table
> > So ATM, I have no clue if this drive is partition synchronized so that
> > the 2 partitioms on it, / & swap, are in fact sector aligned.
>
> OK. For clarity, I'm going to go through this on an existing VM I have
> (so already partitioned). I am using the Debian Wheezy 7.8.0 Net Install
> CD from here: https://www.debian.org/distrib/netinst
>
> I boot from the CD (ISO) and, at the boot prompt, select "Install"
> I walk through the language selection and wait for "Loading Additional
> Components".
> Networking auto configures and I leave the hostname and domain at
> default.
> I leave the root password blank and enter details for a new user.
>
> At this point, we get to the dialog marked "Partition disks". My options
> here are "Guided - use entire disk", "Guided - use entire disk and set
> up LVM", "Guided - use entire disk and set up encrypted LVM" and
> "Manual". I choose *"Manual"*.
>
> This takes me into the partitioner itself. There are four menu options
> at the top ("Guided partitioning", "Configure software RAID", "Configure
> the Logical Volume Manager", "Configure encrypted volumes"), a blank
> line and then the layout of my existing disks. In my case, it starts
> with a line for the disk "SCSI3 (0,0,0) (sda) - 8.6 GB ATA VBOX
> HARDDISK", then a line for each of the partitions "#1 primary
> 8.2 GB B ext4", "#5 logical 401.6 MB F swap swap" etc. And
> finally, there are two "exit" actions: "Undo changes to the partitions"
> and "Finish partitioning and write changes to the disk".
>
> At this point, the installer has made no changes to the existing
> partitions.
>
> I move the red-bar cursor down to the line starting "#1 primary" and
> press enter, as that is the partition where I wish to install Debian.
>
> I now get a dialog starting "You are editing partition #1 of SCSI3 ...".
> Here, my options are "Use as: do not use", "Bootable flag: on",
> "Resize the partition (currently 8.2GB)" and so on. I move the cursor to
> "Use as: do no use" (well, it's already there) and press enter.
>
> I am taken to a selection dialog where I can choose the file system to
> put on partition #1. For the sake of argument, I select the top entry
> "Ext4 journaling file system".
>
> This takes me back to the previous level, but now I have extra options.
> The "Use as:" line now shows the partition will become an Ext4 file
> system and below that are the options "Format the partition: no, keep
> existing data" (if the installer determines that the partition is blank,
> this may read "yes, format it"), "Mount point: none", "Mount options:
> defaults" and "Bootable flag: on".
>
> As I am using a single partition, I scroll down to "Mount point: none",
> press enter and from the selection dialog, choose "/ - the root file
> system".
>
> Finally, I scroll down to "Done setting up the partition" and press
> enter.
>
> So, now I'm back at the top level of the partitioner. The layout of my
> disk is shown again. This time, the last column of the table of
> partitions shows that partition #1 will be used as "/", and partition #5
> will be used as "swap".
>
> If I now wanted to proceed with installation I would scroll down to
> "Finish partitioning and write changes to disk". This would *NOT ALTER
> THE PARTITION TABLE*, it would merely format the partitions (#1 would me
> made ext4 and #5 would be re-initialised as swap). Installation would
> then proceed.
>
>
> Now, IF you've been following that procedure AND your installer isn't
> behaving in the same manner, then hit a bug in the installer that hasn't
> been spotted in about 18 months of regular use by many people.
I have been down that graden path so many times I think I could do it in my
sleep. I had that drive setup with a hair over a gig for the /boot, and all
that, it did write a new table giving boot only 300 megs, and all the other
partitions were either too small or way too big.
File it, its a bug, a huge one IMO, you may want to take your favorite deer
rifle along in case it attacks you.
But why do I have to repeat what I've said all along? I have even posted the
outputs obtained from other partiotioning utilites after several other
installs, and they all show similar results.
> > What is very discouraging in all this is that to a person, you _al_l
> > believe the installer can do no wrong, AND its onvious that this list is
> > not in any way connected to
Re: 3rd new wheezy install
On Thursday 05 February 2015 18:14:56 Gene Heskett wrote: > I have been down that graden path so many times I think I could do it in my > sleep. You haven't described it once. Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502051819.32877.lisi.re...@gmail.com
Re: H.264 on Iceweasel
On 2015-02-05 16:28 +0100, Sven Hoexter wrote: > On Thu, Feb 05, 2015 at 10:12:08AM -0200, Bruno Schneider wrote: >> I'm trying to make H.264 encoding work on Iceweasel 35. I'm using >> Debian testing (Jessie) with Iceweasel from the Mozilla team because >> many sites complain that the official testing version is too old. >> >> In the about:buildconfig, I see the --enable-gstreamer=0.10 flag. I have >> gstreamer0.10-ffmpeg and gstreamer0.10-plugins-base installed. There >> must be some configuration I'm missing. > > IIRC gstreamer0.10-plugins-bad and libgstreamer-plugins-bad0.10-0 > should bring you the mp4 / H.264 support. I rather think it's gstreamer1.0-libav and gstreamer1.0-plugins-good. At least these are the packages which iceweasel in experimental recommends. Cheers, Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87h9v0ry6i@turtle.gmx.de
Re: H.264 on Iceweasel
On Thu, Feb 5, 2015 at 4:11 PM, Chris wrote: > Try purging and reinstalling totem. I just did that (well I actually purged > everything gstreamer-related) but I did not get back h.264 support until > after I reinstalled totem. Just the 2 plugins Sven mentioned were not enough > for me. I am running unstable, but the issue seems the same. Gnome broke may heart and I now use XFCE. I don't have totem installed. Anyway, that is too much wild guessing for me, because totem uses gstreamer1.0. On Thu, Feb 5, 2015 at 4:49 PM, Sven Joachim wrote: > I rather think it's gstreamer1.0-libav and gstreamer1.0-plugins-good. > At least these are the packages which iceweasel in experimental > recommends. Ok, I can confirm that installing gstreamer1.0-libav on a gstreamer1.0 enabled browser solves the problem. But as I wrote, my iceweasel uses gstreamer0.10. Anyway, after installing gstreamer0.10-plugins-good, the problem seems to be solved. So, one needs gstreamer0.10-ffmpeg and gstreamer0.10-plugins-good. I hope this helps others. -- Bruno Schneider http://www.dcc.ufla.br/~bruno/ -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAP1wdQtAzKmqy3d+S3o4hQSi63KT_K80Y2U=j_xspx_jad4...@mail.gmail.com
Re: H.264 on Iceweasel
On Thu, Feb 05, 2015 at 07:49:25PM +0100, Sven Joachim wrote: > I rather think it's gstreamer1.0-libav and gstreamer1.0-plugins-good. > At least these are the packages which iceweasel in experimental > recommends. Seems to be accurate - I now actually tried it. So one of the later iceweasel builds in jessie picked up the 1.0 gstreamer release. gstreamer1.0-plugins-bad actually lists some video/x-mp4-part support and rtmp. I somehow think I needed it for something in the past but maybe that's also just blurred memory and totally off. ATM I'm running the following selection of gstreamer packages + iceweasel gstreamer1.0-libav:amd64 gstreamer1.0-plugins-base:amd64 gstreamer1.0-plugins-good:amd64 gstreamer1.0-x:amd64 libgstreamer1.0-0:amd64 That at least works out for youtube and vimeo without further quirks. Sven -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205193641.gd30...@timegate.de
Re: 3rd new wheezy install
On Thursday, February 05, 2015 12:48:19 PM Renaud OLGIATI wrote: > On Thu, 5 Feb 2015 11:34:18 -0500 > > Gene Heskett wrote: > > > What do you mean here? How can you have 15 yr old data on a newly > > > installed system? > > > > The failing drive can still be read. Some of this data has now been on > > 10+ drives in the life of my use of linux, since 1998 TBE. > > This is why , having been bit once, follow the procedure for new > installations: > > - Have the /home directory on a separate physical unit The installer WILL NOT ALLOW that. But guess what? The redhat 5.0 installer did allow that in 1998. This is progress? General Electric style, but you all are too young to recall those advertisements. > - Physically disconnect said unit during the install. > - Reconnect after the install has been done without problem, adding the > relevant line to /etc/fstab. > > Cheers, > > Ron. If amd when I get this install running right, I will rsync my /home and /opt trees to another identical drive. And then mount those two partitions over these directories. But I still have moninally 7Gb of old email to be imported into kmail, which I have setup a separate local account called /var/mail/import and by shutting down fetchmail for a while, I can move the old mailfile style files to /var/mail/import, then tell kmail to go check for mail. That worked rather nicely for a 2.5Gb mailfile, and I have 2 others in the 4Gb and nearly 6Gb yet to "import" That /home and /opt drive has been laying on the table cold for a week now. Another identical drive to this one in use now. All prepared and mke2fs'd by gparted by the time I am ready to do that. But I'll have to go get another drive & put a simple install on it so I can boot from it, mount this drive and blow away both the /home and /opt contents just to recover the space. And to fix the /etc/fstab on this drive to mount the 2nd drives two partitions. There are more than 9 ways to skin a cat WHEN you have a working system. But at install time you are 100% at the mercy of the installer. Cheers, Gene -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/201502051338.27625.ghesk...@wdtv.com
Re: 3rd new wheezy install
Gene Heskett wrote: > And the partitoner that will not allow one to bypass its fscked up write on > partition tables IS DUMBER THAN A ROCK. But we keep telling you that the debian-installer will do this. You keep saying it does not work for you. We keep asking for details. >Device Boot Start End Blocks Id System > /dev/sda1 *2048 1919977471 959987712 83 Linux Starts at 2048 which is aligned. Good. > /dev/sda5 1919979520 195352371116772096 82 Linux swap / Solaris 1919979520/2048=937490.0 Starts on an aligned boundary. Good. > Then note carefully what it says about partition 2, which is swap. Wait. Your partition 2 is not swap. Your data shows partition 5 is swap. Your data shows partition 2 is an extended partition. > /dev/sda2 1919979518 1953523711167720975 Extended That isn't swap. That is your extended partition. It holds logical partitions. Your swap partition is properly aligned for 4k Advanced Format drives. I think you have been looking at the wrong partition. :-) Bob signature.asc Description: Digital signature
Re: 3rd new wheezy install
Gene Heskett wrote: > I have been down that graden path so many times I think I could do it in my > sleep. ... Unfortunately being asleep isn't good for doing it correctly. Because everyone keeps showing you how to do it and you never show us that you are following the directions. > File it, its a bug, a huge one IMO, you may want to take your favorite deer > rifle along in case it attacks you. Sorry but this is a phantom bug of your imagination. It doesn't actually exist. > But why do I have to repeat what I've said all along? Because you keep telling us that the world is flat and we know that isn't true. The world is round. Saying that it is flat doesn't make it flat. It really is round. No matter how many times you say it is otherwise. In this case truth wins over rhetoric. > I have even posted the outputs obtained from other partiotioning > utilites after several other installs, and they all show similar > results. Except that you haven't. The only time you posted actual data it came from a different partitioner and not from the debian-installer. I said that here: https://lists.debian.org/20150121234014606439638.noccsple...@bob.proulx.com You have not yet ever posted any details showing the debian-installer not working properly. We keep giving you the benefit of the doubt and asking. You keep talking saying that it doesn't work but never give any details showing this. It works for everyone else. > Your bug tracker isn't accessible to me as I don't even have > incoming mail setup such that I could confirm the subscription I'd > need to file the bug. Chicken v egg. Incorrect. The bug tracker is simply email. It does not require confirmation to submit a bug report. What makes you think it does? It simply requires email. You have proven that you can send email therefore you can send an email to the bug tracker. To submit a bug report simply send off an email. That is all there is to it. https://www.debian.org/Bugs/Reporting See the section "Sending the bug report via e-mail" However if the bug report is like the email messages you have sent to the mailing list saying that the world is flat without details then it wouldn't be useful. They could only be closed saying the world is round. So far you haven't given any details supporting your belief that the debian-installer does not do what we all see it do whenever we use it. Bob signature.asc Description: Digital signature
Re: unmet dependencies: libcurl4-openssl-dev
Brian wrote: > Sivaram Neelakantan wrote: > > libcurl4-openssl-dev : Depends: libcurl3 (= 7.26.0-1+wheezy11) but > > 7.26.0-1+wheezy12 is to be installed > > The libcurl4-openssl-dev which depends on libcurl3 (= 7.26.0-1+wheezy11) > is version 7.26.0-1+wheezy11. So the question becomes: Why does your > system want to install this version when 7.26.0-1+wheezy12 is on your > mirror and 'apt-cache policy libcurl4-openssl-dev' has it as an > installation candidate? Bad pinning? Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/* files? If so what is in it? Remove it and try the apt-get update and apt-get install again. Bob signature.asc Description: Digital signature
Re: SSL error in (e)links(2) web browers
Marko Randjelovic wrote: > When I use links2 or elinks web browsers on some websites when https is > protocol I get error "Error loading ... SSL error" and page is not > loaded. This is probably due to the combination of supported protocols. When negotiating the encryption it may not have an overlapping set that works. For example if the site is old and stale and only offers SSLv3 which has been deprecated then a browser with SSLv3 disabled for security will not be able to connect to it. Do you have an example https page so that we could examine the offered protocols and compare against those supported by those browsers? Bob signature.asc Description: Digital signature
Re: 3rd new wheezy install
Quoting Darac Marjal (mailingl...@darac.org.uk): > On Wed, Feb 04, 2015 at 09:57:50AM -0500, Gene Heskett wrote: > > On Tuesday, February 03, 2015 05:01:46 AM Darac Marjal wrote: > > > On Mon, Feb 02, 2015 at 06:16:34PM -0500, Gene Heskett wrote: > > [cut] > > > > My point in all this is that the installer WILL NOT ALLOW you, in any mode, > > to > > just format and label a partition and use it. Try to skip the partitioner > > and > > go on to the next step it will NOT allow. The only way you can get past > > that > > is to allow it to write a broken partition table So ATM, I have no clue if > > this drive is partition synchronized so that the 2 partitioms on it, / & > > swap, > > are in fact sector aligned. To Gene: you don't "skip the partitioner". What you do is instruct the partitioner to make no changes to the disks in your machine, as described below. [snipped most of this detailed explanation] > So, now I'm back at the top level of the partitioner. The layout of my > disk is shown again. This time, the last column of the table of > partitions shows that partition #1 will be used as "/", and partition #5 > will be used as "swap". I have done much the same just now with my old wheezy netinst CD, with one difference. As my smallest computer has 512MB memory, I usually skip the swap partition too as it save rewriting the label afterwards. (Allowing the partitioner to initialise it clears the label.) So here's the final screen, ready for installation on partition 2: SCSI1 (0,0,0) (sda) - 60.0 GB ATA ...serial number or whatever... #1 primary 20.0 GB B ext4 #2 primary 20.0 GB K ext4/ #3 primary 19.0 GBext4 #4 primary 1.0 GBswap Undo changes to partition Finish partitioning and write changes to disk. (For people who don't use this method of installation, the B is the boot flag that happens to be set on sda1, the K means Keep the data on sda2 (which I emptied, except lost+found), and / means this will be the root partition. sda1/3/4 will be untouched as they were all set to Do Not Use.) > If I now wanted to proceed with installation I would scroll down to > "Finish partitioning and write changes to disk". This would *NOT ALTER > THE PARTITION TABLE*, it would merely format the partitions (#1 would me > made ext4 and #5 would be re-initialised as swap). Installation would > then proceed. After pressing return on the last line, the partitioner raises its eyebrows because there's no swap, and no partition to be formatted. After OKing "Continue with the installation?" I can switch to the log on VC4 and see that no partition table is written, no partition gets formatted, and the log shows it: INFO: Menu item 'partman-base' selected <--- from when you pressed "Partition disks" kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: errors=remount-ro ... stuff while it prepares for the next step ... I have no idea if Gene did this, or else something completely different, but he does seem to be unsable to provide a *precise* narrative of what he did and where it failed. I can only assume (from the statement quoted above) that he tries to skip the "partitioner step" ALTOGTHER, and obviously that's going to fail because the installer has no idea where to copy the installation files to. Cheers, David. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205210958.ga12...@alum.home
Re: CRON: Authentication token is no longer valid; new one required
ML mail wrote: > I am trying to run cron from /etc/cron.d with the root account which > has password disabled in order not to be able to login as root but > when the cron entry wants to run it simply does not and show the > following error message in the log file: > > CRON[16785]: Authentication token is no longer valid; new one required This reads to me that the password for root has expired. It is the state of an expired password that is a problem. When you say that the root password has been disabled what exactly do you mean by that statement? Did you 'passwd -e root'? If so that is the source of the problem. Root should not have an expired password. What does this say? Example from a system of mine. $ passwd --status root root P 05/01/2010 0 9 7 -1 > Any idea how to run a cronjob from /etc/cron.d with the root account > disabled? I didn't have time to test this procedure but I would use 'passwd root' to change the password and to fix the expiration. (Actually *I* would simply edit the /etc/shadow file and fix it but for others I recommend using the tool to avoid a file editing mistake in that very critical file.) After updating the password I think the expiration problem will have been fixed. You don't actually ever have to use that password. Bob signature.asc Description: Digital signature
Re: unmet dependencies: libcurl4-openssl-dev
On 02/05/2015 04:03 PM, Bob Proulx wrote: Brian wrote: Sivaram Neelakantan wrote: libcurl4-openssl-dev : Depends: libcurl3 (= 7.26.0-1+wheezy11) but 7.26.0-1+wheezy12 is to be installed The libcurl4-openssl-dev which depends on libcurl3 (= 7.26.0-1+wheezy11) is version 7.26.0-1+wheezy11. So the question becomes: Why does your system want to install this version when 7.26.0-1+wheezy12 is on your mirror and 'apt-cache policy libcurl4-openssl-dev' has it as an installation candidate? Bad pinning? Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/* files? If so what is in it? Remove it and try the apt-get update and apt-get install again. I thought he used "experimental" to install the package, then removed it from the sources list after. What he REALLY needs is a fresh install to Jessie to get what he wants. That would be the simplest way to go. :) Ric -- My father, Victor Moore (Vic) used to say: "There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome." R.I.P. Dad. http://linuxcounter.net/user/44256.html -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d3deb4.4070...@gmail.com
Debian CPU heating up
Hi, I am trying to create 2 systems (both are portable and works on USB) 1. USB<->SATA bridge SSD with linux kernel 3.19.0 (self compiled). this systems works fine and the operating temperature on the DELL machine I am using is about 54C to 60C 2. USB<->microSD with MicroSD card (sandisk 32GB). this system when it works starts heating up !!! temperatures sore to 80C.(in a matter of 2-3 minutes) BASE CONDITIONS (common for both systems): * Both the systems are jessie * Both are running idential kernel and initrd (infact exact binary copies on both) * top shows very low CPU utilisation * iotop shows occasional R/W but not too much of write/read (less than 0.1 kb/sec) * both are currently text mode only * system is DELL Q15R core-i7-2630QM (see cpuinfo in the end) on SSD: vmstat 0 0 0 7003648 44012 89683200 012 157 583 1 0 99 0 0 0 0 0 7003532 44012 89684000 0 0 136 429 0 0 100 0 0 0 0 0 7003760 44012 89684000 0 0 205 510 0 0 100 0 0 0 0 0 7003904 44012 89684000 0 0 152 513 0 0 100 0 0 (using graphics and so sligtly low in mem but this is on the system which does not heat up) on SDCARD: vmstat 0 0 0 7935012 20884 18481200 0 0 110 313 0 0 100 0 0 0 0 0 7935012 20884 18481200 0 0 97 286 0 0 100 0 0 0 0 0 7935012 20884 18481200 0 0 99 275 0 0 100 0 0 0 0 0 7935012 20884 18481200 0 0 103 280 0 0 100 0 0 0 0 0 7934864 20892 18480400 020 176 470 0 0 100 0 0 I even applied all CPU microcodes and got the message perf_event_intel: PEBS enabled due to microcode update Has someone encountered this before ? I am not sure what is causing the fans to run fast and CPU to heatup when I use the OS on SD card ? I agree SD is slow but that will be IO rather than CPU right ? will that cause heatup ? iotop also shows READ/WRITE only occasionally SSD for I am fully exhausted not kwowing what to do. Can anyone help please ? CPU INFO --- processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz stepping: 7 microcode : 0x29 cpu MHz : 1900.000 cache size : 6144 KB physical id : 0 siblings: 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid xsaveopt bugs: bogomips: 3990.87 clflush size: 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management: -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAPLCSGCA3+NXH3o07Zz9G+=CCVbYMWjnRnLzdWJf44H1xHc=k...@mail.gmail.com
Re: 3rd new wheezy install
On Thu, 5 Feb 2015 13:38:27 -0500 Gene Heskett wrote: > > This is why , having been bit once, follow the procedure for new > > installations: > > > > - Have the /home directory on a separate physical unit > > The installer WILL NOT ALLOW that. The installer will know nothing about it; you install, then once installed connect your home CD, boot a live CD, find and delete the content of the /home created by the installer, add the /dev/sdXXX of your old home drive to fstab, and reboot. The installer never sees your old /home so never gets a chance to bugger it up. Cheers, Ron. -- Work is the curse of the drinking classes. -- Mike Romanoff -- http://www.olgiati-in-paraguay.org -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150205192110.27732...@ron.cerrocora.org
Re: Debian CPU heating up
Hi, Does it happen only when the OS is running on microSD? Have you tried to boot using a live iso either on a CD or on a usb stick? Have you looked thru /var/log/syslog and dmesg to see if there is anything relevant? Regards, Burhan On Fri, Feb 6, 2015 at 12:18 AM, Bhasker C V wrote: > Hi, > > I am trying to create 2 systems (both are portable and works on USB) > > 1. USB<->SATA bridge SSD with linux kernel 3.19.0 (self compiled). >this systems works fine and the operating temperature on the DELL > machine I am using is about 54C to 60C > > 2. USB<->microSD with MicroSD card (sandisk 32GB). >this system when it works starts heating up !!! temperatures sore > to 80C.(in a matter of 2-3 minutes) > > BASE CONDITIONS (common for both systems): > * Both the systems are jessie > * Both are running idential kernel and initrd (infact exact binary > copies on both) > * top shows very low CPU utilisation > * iotop shows occasional R/W but not too much of write/read (less > than 0.1 kb/sec) > * both are currently text mode only > * system is DELL Q15R core-i7-2630QM (see cpuinfo in the end) > > on SSD: vmstat > > 0 0 0 7003648 44012 89683200 012 157 583 1 > 0 99 0 0 > 0 0 0 7003532 44012 89684000 0 0 136 429 0 > 0 100 0 0 > 0 0 0 7003760 44012 89684000 0 0 205 510 0 > 0 100 0 0 > 0 0 0 7003904 44012 89684000 0 0 152 513 0 > 0 100 0 0 > (using graphics and so sligtly low in mem but this is on the system > which does not heat up) > > on SDCARD: vmstat > > 0 0 0 7935012 20884 18481200 0 0 110 313 0 > 0 100 0 0 > 0 0 0 7935012 20884 18481200 0 0 97 286 0 > 0 100 0 0 > 0 0 0 7935012 20884 18481200 0 0 99 275 0 > 0 100 0 0 > 0 0 0 7935012 20884 18481200 0 0 103 280 0 > 0 100 0 0 > 0 0 0 7934864 20892 18480400 020 176 470 0 > 0 100 0 0 > > > I even applied all CPU microcodes and got the message > perf_event_intel: PEBS enabled due to microcode update > > > Has someone encountered this before ? I am not sure what is causing > the fans to run fast and CPU to heatup when I use the OS on SD card ? > I agree SD is slow but that will be IO rather than CPU right ? will > that cause heatup ? > > iotop also shows READ/WRITE only occasionally SSD for > I am fully exhausted not kwowing what to do. Can anyone help please ? > > > CPU INFO --- > processor : 7 > vendor_id : GenuineIntel > cpu family : 6 > model : 42 > model name : Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz > stepping: 7 > microcode : 0x29 > cpu MHz : 1900.000 > cache size : 6144 KB > physical id : 0 > siblings: 8 > core id : 3 > cpu cores : 4 > apicid : 7 > initial apicid : 7 > fdiv_bug: no > f00f_bug: no > coma_bug: no > fpu : yes > fpu_exception : yes > cpuid level : 13 > wp : yes > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm > constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf > eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 > xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes > xsave avx lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi > flexpriority ept vpid xsaveopt > bugs: > bogomips: 3990.87 > clflush size: 64 > cache_alignment : 64 > address sizes : 36 bits physical, 48 bits virtual > power management: > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > https://lists.debian.org/CAPLCSGCA3+NXH3o07Zz9G+=CCVbYMWjnRnLzdWJf44H1xHc=k...@mail.gmail.com > >
missing segfault messages
i'm using testing/unstable, systemd (215-11),
etc. everything up to date, so i'm hoping this is a
transitory thing, but i'm trying to understand the
pathway a message takes from the kernel to where it
should end up in /var/log/{messages,kern,syslog}.
for quite some time the messages would arrive as
desired in one of those files. during recent
testing they no longer do.
there are no changes made to my rsyslog setup and
when looking at systemd journals the messages aren't
there either.
so i'm not sure if the kernel itself isn't noticing
the segfault, or if it is trying to hand the message
to systemd and not getting through or what...
any hints on trying to get this resolved would be
great.
thanks!
in the meantime i'll see if i can revert to previous
systemd and see if that solves the issue...
songbird
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/qr8dqb-529@id-306963.user.uni-berlin.de
Re: Debian CPU heating up
I had a similar problem with certain hardware configs causing a kworker to hog the CPU due to ACPI problems I found the tips here helpful in solving that one https://bbs.archlinux.org/viewtopic.php?id=184913 Sent from iPhone > On 5 Feb 2015, at 22:18, Bhasker C V wrote: > > Hi, > > I am trying to create 2 systems (both are portable and works on USB) > > 1. USB<->SATA bridge SSD with linux kernel 3.19.0 (self compiled). > this systems works fine and the operating temperature on the DELL > machine I am using is about 54C to 60C > > 2. USB<->microSD with MicroSD card (sandisk 32GB). > this system when it works starts heating up !!! temperatures sore > to 80C.(in a matter of 2-3 minutes) > > BASE CONDITIONS (common for both systems): > * Both the systems are jessie > * Both are running idential kernel and initrd (infact exact binary > copies on both) > * top shows very low CPU utilisation > * iotop shows occasional R/W but not too much of write/read (less > than 0.1 kb/sec) > * both are currently text mode only > * system is DELL Q15R core-i7-2630QM (see cpuinfo in the end) > > on SSD: vmstat > > 0 0 0 7003648 44012 89683200 012 157 583 1 > 0 99 0 0 > 0 0 0 7003532 44012 89684000 0 0 136 429 0 > 0 100 0 0 > 0 0 0 7003760 44012 89684000 0 0 205 510 0 > 0 100 0 0 > 0 0 0 7003904 44012 89684000 0 0 152 513 0 > 0 100 0 0 > (using graphics and so sligtly low in mem but this is on the system > which does not heat up) > > on SDCARD: vmstat > > 0 0 0 7935012 20884 18481200 0 0 110 313 0 > 0 100 0 0 > 0 0 0 7935012 20884 18481200 0 0 97 286 0 > 0 100 0 0 > 0 0 0 7935012 20884 18481200 0 0 99 275 0 > 0 100 0 0 > 0 0 0 7935012 20884 18481200 0 0 103 280 0 > 0 100 0 0 > 0 0 0 7934864 20892 18480400 020 176 470 0 > 0 100 0 0 > > > I even applied all CPU microcodes and got the message > perf_event_intel: PEBS enabled due to microcode update > > > Has someone encountered this before ? I am not sure what is causing > the fans to run fast and CPU to heatup when I use the OS on SD card ? > I agree SD is slow but that will be IO rather than CPU right ? will > that cause heatup ? > > iotop also shows READ/WRITE only occasionally SSD for > I am fully exhausted not kwowing what to do. Can anyone help please ? > > > CPU INFO --- > processor: 7 > vendor_id: GenuineIntel > cpu family: 6 > model: 42 > model name: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz > stepping: 7 > microcode: 0x29 > cpu MHz: 1900.000 > cache size: 6144 KB > physical id: 0 > siblings: 8 > core id: 3 > cpu cores: 4 > apicid: 7 > initial apicid: 7 > fdiv_bug: no > f00f_bug: no > coma_bug: no > fpu: yes > fpu_exception: yes > cpuid level: 13 > wp: yes > flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov > pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm > constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf > eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 > xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes > xsave avx lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi > flexpriority ept vpid xsaveopt > bugs: > bogomips: 3990.87 > clflush size: 64 > cache_alignment: 64 > address sizes: 36 bits physical, 48 bits virtual > power management: > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: > https://lists.debian.org/CAPLCSGCA3+NXH3o07Zz9G+=CCVbYMWjnRnLzdWJf44H1xHc=k...@mail.gmail.com > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/9d9f79fa-9f26-482c-b6a4-a54869af7...@perpetualmotion.co.uk
Re: Debian CPU heating up
I do not see anything. top does not show anything in the top list ... it is just that when arranged in high to low CPU usage, the first process it shows is a kernel process and it is using 0% or 0.5% of CPU This really puzzles me Who can take up CPU time without showing up themselves in the 'top' thereby heating the CPU but hiding itself On 2/5/15, Andrew Wood wrote: > I had a similar problem with certain hardware configs causing a kworker to > hog the CPU due to ACPI problems > > I found the tips here helpful in solving that one > > https://bbs.archlinux.org/viewtopic.php?id=184913 > > Sent from iPhone > >> On 5 Feb 2015, at 22:18, Bhasker C V wrote: >> >> Hi, >> >> I am trying to create 2 systems (both are portable and works on USB) >> >> 1. USB<->SATA bridge SSD with linux kernel 3.19.0 (self compiled). >> this systems works fine and the operating temperature on the DELL >> machine I am using is about 54C to 60C >> >> 2. USB<->microSD with MicroSD card (sandisk 32GB). >> this system when it works starts heating up !!! temperatures sore >> to 80C.(in a matter of 2-3 minutes) >> >> BASE CONDITIONS (common for both systems): >> * Both the systems are jessie >> * Both are running idential kernel and initrd (infact exact binary >> copies on both) >> * top shows very low CPU utilisation >> * iotop shows occasional R/W but not too much of write/read (less >> than 0.1 kb/sec) >> * both are currently text mode only >> * system is DELL Q15R core-i7-2630QM (see cpuinfo in the end) >> >> on SSD: vmstat >> >> 0 0 0 7003648 44012 89683200 012 157 583 1 >> 0 99 0 0 >> 0 0 0 7003532 44012 89684000 0 0 136 429 0 >> 0 100 0 0 >> 0 0 0 7003760 44012 89684000 0 0 205 510 0 >> 0 100 0 0 >> 0 0 0 7003904 44012 89684000 0 0 152 513 0 >> 0 100 0 0 >> (using graphics and so sligtly low in mem but this is on the system >> which does not heat up) >> >> on SDCARD: vmstat >> >> 0 0 0 7935012 20884 18481200 0 0 110 313 0 >> 0 100 0 0 >> 0 0 0 7935012 20884 18481200 0 0 97 286 0 >> 0 100 0 0 >> 0 0 0 7935012 20884 18481200 0 0 99 275 0 >> 0 100 0 0 >> 0 0 0 7935012 20884 18481200 0 0 103 280 0 >> 0 100 0 0 >> 0 0 0 7934864 20892 18480400 020 176 470 0 >> 0 100 0 0 >> >> >> I even applied all CPU microcodes and got the message >> perf_event_intel: PEBS enabled due to microcode update >> >> >> Has someone encountered this before ? I am not sure what is causing >> the fans to run fast and CPU to heatup when I use the OS on SD card ? >> I agree SD is slow but that will be IO rather than CPU right ? will >> that cause heatup ? >> >> iotop also shows READ/WRITE only occasionally SSD for >> I am fully exhausted not kwowing what to do. Can anyone help please ? >> >> >> CPU INFO --- >> processor: 7 >> vendor_id: GenuineIntel >> cpu family: 6 >> model: 42 >> model name: Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz >> stepping: 7 >> microcode: 0x29 >> cpu MHz: 1900.000 >> cache size: 6144 KB >> physical id: 0 >> siblings: 8 >> core id: 3 >> cpu cores: 4 >> apicid: 7 >> initial apicid: 7 >> fdiv_bug: no >> f00f_bug: no >> coma_bug: no >> fpu: yes >> fpu_exception: yes >> cpuid level: 13 >> wp: yes >> flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca >> cmov >> pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx rdtscp lm >> constant_tsc arch_perfmon pebs bts xtopology nonstop_tsc aperfmperf >> eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 >> xtpr pdcm pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes >> xsave avx lahf_lm ida arat epb pln pts dtherm tpr_shadow vnmi >> flexpriority ept vpid xsaveopt >> bugs: >> bogomips: 3990.87 >> clflush size: 64 >> cache_alignment: 64 >> address sizes: 36 bits physical, 48 bits virtual >> power management: >> >> >> -- >> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org >> with a subject of "unsubscribe". Trouble? Contact >> listmas...@lists.debian.org >> Archive: >> https://lists.debian.org/CAPLCSGCA3+NXH3o07Zz9G+=CCVbYMWjnRnLzdWJf44H1xHc=k...@mail.gmail.com >> > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAPLCSGCkSD78v-rov-=r758g_ircx0cq2djfxiwnmnz19tw...@mail.gmail.com
Re: Debian CPU heating up
could it be because with USB-SSD the kernel detects it as drive (smart works and also does hdparm) and uses DMA whereas in USB-SD kernel detects and attaches to usbstor but then has to do pio and cpu intensive low efficency transfer methods rather than DMA ? This means that kernel is doing a lot of job to write/read to usb and will not show up in top ... but still since CPU is being used constantly CPU gets heated up just a hypothesis ... someone can comment on this if that is the case how to force UDMA for usb memorystick kind of devices ? tried googling ... no answer On 2/6/15, Bhasker C V wrote: > could it be because with USB-SSD the kernel detects it as drive (smart > works and also does hdparm) and uses DMA whereas in USB-SD kernel > detects and attaches to usbstor but then has to do pio and cpu > intensive low efficency transfer methods rather than DMA ? > This means that kernel is doing a lot of job to write/read to usb and > will not show up in top ... but still since CPU is being used > constantly CPU gets heated up > just a hypothesis ... someone can comment on this > > > > > On 2/6/15, Bhasker C V wrote: >> Hi, >> >> The same system running on the USB-SSD behaves nicely. Less than 60C >> always even when watching videos on youtube. However when I boot from >> USB-SD adapter then CPU starts heating to 80C >> There is no apparent message I can see in dmesg or syslog >> >> >> On 2/5/15, Burhan Hanoglu wrote: >>> Hi, >>> >>> Does it happen only when the OS is running on microSD? Have you tried to >>> boot using a live iso either on a CD or on a usb stick? Have you looked >>> thru /var/log/syslog and dmesg to see if there is anything relevant? >>> >>> Regards, >>> Burhan >>> >>> On Fri, Feb 6, 2015 at 12:18 AM, Bhasker C V >>> wrote: >>> Hi, I am trying to create 2 systems (both are portable and works on USB) 1. USB<->SATA bridge SSD with linux kernel 3.19.0 (self compiled). this systems works fine and the operating temperature on the DELL machine I am using is about 54C to 60C 2. USB<->microSD with MicroSD card (sandisk 32GB). this system when it works starts heating up !!! temperatures sore to 80C.(in a matter of 2-3 minutes) BASE CONDITIONS (common for both systems): * Both the systems are jessie * Both are running idential kernel and initrd (infact exact binary copies on both) * top shows very low CPU utilisation * iotop shows occasional R/W but not too much of write/read (less than 0.1 kb/sec) * both are currently text mode only * system is DELL Q15R core-i7-2630QM (see cpuinfo in the end) on SSD: vmstat 0 0 0 7003648 44012 89683200 012 157 583 1 0 99 0 0 0 0 0 7003532 44012 89684000 0 0 136 429 0 0 100 0 0 0 0 0 7003760 44012 89684000 0 0 205 510 0 0 100 0 0 0 0 0 7003904 44012 89684000 0 0 152 513 0 0 100 0 0 (using graphics and so sligtly low in mem but this is on the system which does not heat up) on SDCARD: vmstat 0 0 0 7935012 20884 18481200 0 0 110 313 0 0 100 0 0 0 0 0 7935012 20884 18481200 0 0 97 286 0 0 100 0 0 0 0 0 7935012 20884 18481200 0 0 99 275 0 0 100 0 0 0 0 0 7935012 20884 18481200 0 0 103 280 0 0 100 0 0 0 0 0 7934864 20892 18480400 020 176 470 0 0 100 0 0 I even applied all CPU microcodes and got the message perf_event_intel: PEBS enabled due to microcode update Has someone encountered this before ? I am not sure what is causing the fans to run fast and CPU to heatup when I use the OS on SD card ? I agree SD is slow but that will be IO rather than CPU right ? will that cause heatup ? iotop also shows READ/WRITE only occasionally SSD for I am fully exhausted not kwowing what to do. Can anyone help please ? CPU INFO --- processor : 7 vendor_id : GenuineIntel cpu family : 6 model : 42 model name : Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz stepping: 7 microcode : 0x29 cpu MHz : 1900.000 cache size : 6144 KB physical id : 0 siblings: 8 core id : 3 cpu cores : 4 apicid : 7 initial apicid : 7 fdiv_bug: no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat ps
Re: unmet dependencies: libcurl4-openssl-dev
On Thu, Feb 05 2015,Bob Proulx wrote: > Brian wrote: [snipped 12 lines] > Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/* > files? If so what is in it? Remove it and try the apt-get update and > apt-get install again. No, I don't have any preferences or anything in preferences.d directory. And if I comment out everything except the first wheezy main, and try to install rtmp-dev, I get libgnutls-dev broken packages error. sivaram -- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/878ugbbl98@gmail.com
Re: SSL error in (e)links(2) web browers
On Thu, 5 Feb 2015 14:06:47 -0700 Bob Proulx wrote: > Marko Randjelovic wrote: > > When I use links2 or elinks web browsers on some websites when https is > > protocol I get error "Error loading ... SSL error" and page is not > > loaded. > > This is probably due to the combination of supported protocols. When > negotiating the encryption it may not have an overlapping set that > works. For example if the site is old and stale and only offers SSLv3 > which has been deprecated then a browser with SSLv3 disabled for > security will not be able to connect to it. > > Do you have an example https page so that we could examine the offered > protocols and compare against those supported by those browsers? > > Bob https://webmail.sbb.rs/?r=s -- http://markorandjelovic.hopto.org One should not be afraid of humans. Well, I am not afraid of humans, but of what is inhuman in them. Ivo Andric, "Signs near the travel-road" signature.asc Description: PGP signature
