Re: Online list of messages to debian-user is down ?
On 11/11/2017 10:08 PM, kamaraju kusumanchi wrote: On Sat, Nov 11, 2017 at 7:26 AM, kamaraju kusumanchi wrote: On Sat, Nov 11, 2017 at 7:04 AM, Laurent Lyaudet wrote: Hello, When I go to : https://lists.debian.org/debian-user/2017/11/threads.html there is this message at the end of the webpage : "The last update was on 23:20 GMT Thu Nov 09. There are 348 messages. Page 1 of 1." It used to be refreshed every 20 minutes but it doesn't seem to work anymore. I tried Ctrl+F5 in Firefox and tried another laptop but it changed nothing. Best regards, Laurent Lyaudet I see the same on my end as well. May be the listmas...@lists.debian.org.(CCed) can help on this. Looks like it got some refreshes. I now see "The last update was on 00:40 GMT Sun Nov 12. There are 407 messages. Page 1 of 1." Appears to be working, I see: The last update was on 07:40 GMT Sun Nov 12. There are 415 messages. Page 1 of 1.
Re: codesearch across lines
On 2017-11-11, kamaraju kusumanchi wrote: > On Sat, Nov 11, 2017 at 9:08 AM, Curt wrote: >> On 2017-11-11, kamaraju kusumanchi wrote: >>> >>> Thanks. How can I specify the flag in the searches? So, in my example, I >>> tried >>> >>> pandas str /m >>> >>> But that query is not finishing. >>> >> >> '(?i) PanDas' seemed to work. >> > Ok. That works and does case insensitive search. But the corresponding > multiline option does not seem to achieve what I want. I tried > > (?m) pandas str > > and it dies not give any results. > It doesn't die for me. It gives no results, though. This "works" (for an arbritrary meaning of "work" because I am not cut out for regular expressions or even irregular expressions and I feel a migraine coming on): (?m)(\W|^)panda.*str(\W|$) At least there's results and that's always gratifying (in a way). -- "If you want to build a ship, don’t herd people together to collect wood and don’t assign them tasks and work, but rather teach them to long for the endless immensity of the sea." — Antoine de Saint-Exupéry
Re: Compatible laptops
On Sunday, November 12, 2017 02:39:22 AM dekks herton wrote: > in general - any modern laptop will run debian fine [with any DE you > choose] with IMO the following caveats > > 1) Avoid ones with hybrid dual graphics ie intel/nvidia aka optimus > 2) Avoid anything realtek I'd add, "avoid Broadcom if you want to use WiFi"--it requires some extra steps for installation (and is even more of a pain until you realize that is what you need to do)" > 3) If its got fancy Dolby sound or quad speakers they wont work on Debian > 4) Always check reviews for PWM flickering on screen dimming if you have > sensitive eyes > > I personally use Thinkpads as a lot of Linux devs use them.
Re: codesearch across lines
On 2017-11-12 at 05:57, Curt wrote: > On 2017-11-11, kamaraju kusumanchi > wrote: > >> On Sat, Nov 11, 2017 at 9:08 AM, Curt wrote: >>> '(?i) PanDas' seemed to work. >>> >> Ok. That works and does case insensitive search. But the >> corresponding multiline option does not seem to achieve what I >> want. I tried >> >> (?m) pandas str >> >> and it dies not give any results. That would be because this is most likely searching for the literal sequence ' pandas str' somewhere in the document. (Vs., previously, searching for lines in the document which contain that literal sequence.) > It doesn't die for me. It gives no results, though. > > This "works" (for an arbritrary meaning of "work" because I am not > cut out for regular expressions or even irregular expressions and I > feel a migraine coming on): > > (?m)(\W|^)panda.*str(\W|$) That would be expected to find only documents containing 'panda' followed by 'str'. To also find ones which contain 'str' followed by 'pandas' (and add the missing 's' back in), you'd probably want: (?m)(\W|^)(pandas.*str|str.*pandas)(\W|$) I have not tested this, but I use similar '(a.*b|b.*a)' regexes on a semi-regular basis for searching one of my own text archives. (Also, I'm not sure the '\W' bits are needed, but I don't know the field of what's-being-searched-for well enough to be certain about why those may have been added.) -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: Re: Compatible laptops
On 11/12, rhkra...@gmail.com wrote: On Sunday, November 12, 2017 02:39:22 AM dekks herton wrote: in general - any modern laptop will run debian fine [with any DE you choose] with IMO the following caveats 1) Avoid ones with hybrid dual graphics ie intel/nvidia aka optimus 2) Avoid anything realtek I'd add, "avoid Broadcom if you want to use WiFi"--it requires some extra steps for installation (and is even more of a pain until you realize that is what you need to do)" Until the last 18 months i would have agreed but they hired one of the leading kernal gfx hackers and now forced by the Pi market are supporting newer stuff. Enough to come off my black list, however i'm keeping an eye on them to see if they relapse. -- regards. Jabber IM:dekkz...@jabber.hot-chilli.net signature.asc Description: PGP signature
Re: codesearch across lines
On 2017-11-12, The Wanderer wrote: > >> (?m)(\W|^)panda.*str(\W|$) > > That would be expected to find only documents containing 'panda' > followed by 'str'. To also find ones which contain 'str' followed by > 'pandas' (and add the missing 's' back in), you'd probably want: > > (?m)(\W|^)(pandas.*str|str.*pandas)(\W|$) > > I have not tested this, but I use similar '(a.*b|b.*a)' regexes on a > semi-regular basis for searching one of my own text archives. I tried that, actually, following the same logic, or thought I did (there might have been a typo somewhere) yet it produced *less* results, but trying the formula again now it seems to "work" (although the regex is pretty useless because it matches reams and reams of stuff because 'anda' 'panda' 'pandas' 'expandable' 'str' 'struct' 'instruction' 'castration', etc. are all matched). This produces two hits (from the same file) only: (?m)(\W|^)\bpanda\b.*\bstr\b|\bstr\b.*\bpanda\b(\W|$) I'm not certain how you're supposed to construct the formula to only match the literal strings (if literal is indeed the term) "panda" and "str". I also have no idea what the expected results might look like. To add insult insult to injury, I know nothing about regexes either. ;-) > (Also, I'm not sure the '\W' bits are needed, but I don't know the field > of what's-being-searched-for well enough to be certain about why those > may have been added.) >
Re: codesearch across lines
On 11/12/2017 08:23 AM, Curt wrote: On 2017-11-12, The Wanderer wrote: (?m)(\W|^)panda.*str(\W|$) That would be expected to find only documents containing 'panda' followed by 'str'. To also find ones which contain 'str' followed by 'pandas' (and add the missing 's' back in), you'd probably want: (?m)(\W|^)(pandas.*str|str.*pandas)(\W|$) I have not tested this, but I use similar '(a.*b|b.*a)' regexes on a semi-regular basis for searching one of my own text archives. I tried that, actually, following the same logic, or thought I did (there might have been a typo somewhere) yet it produced *less* results, but trying the formula again now it seems to "work" (although the regex is pretty useless because it matches reams and reams of stuff because 'anda' 'panda' 'pandas' 'expandable' 'str' 'struct' 'instruction' 'castration', etc. are all matched). This produces two hits (from the same file) only: (?m)(\W|^)\bpanda\b.*\bstr\b|\bstr\b.*\bpanda\b(\W|$) I'm not certain how you're supposed to construct the formula to only match the literal strings (if literal is indeed the term) "panda" and "str". I also have no idea what the expected results might look like. To add insult insult to injury, I know nothing about regexes either. ;-) (Also, I'm not sure the '\W' bits are needed, but I don't know the field of what's-being-searched-for well enough to be certain about why those may have been added.) To paraphrase, "A code fragment is worth a thousand bytes of descriptive text" ;/ Post a half dozen lines of code followed by the desired output. The posted lines should be < 30 characters to prevent confusion caused by line wrap problems when displayed. The example meed not be valid code in language used -- only character sequences are of interest.
Re: Talking about RAID - disks with same id
Le 10/11/2017 à 09:12, deloptes a écrit : Joe Pfeiffer wrote: Here's what I see when I look at my RAID disks: /dev/sda2: UUID="67d3c233-96a0-737c-5f88-ed9b936ea3ae" UUID_SUB="48b56869-6f19-21b9-283f-3eee3ac90cf8" LABEL="snowball:1" TYPE="linux_raid_member" PARTUUID="3bb3729a-528b-4384-b6a5-b6d9e148ed2a" /dev/sdb2: UUID="67d3c233-96a0-737c-5f88-ed9b936ea3ae" UUID_SUB="1f48f805-4173-78cd-1f52-957920f66335" LABEL="snowball:1" TYPE="linux_raid_member" PARTUUID="1bdd3893-9346-49d2-8292-a61075ad0c5e" you see in your case PARTUUID is different for both members. In my case it is identical and this is what is bothering me and here's the relevant line in my /etc/mdadm/mdadm.conf ARRAY /dev/md/1 metadata=1.2 UUID=67d3c233:96a0737c:5f88ed9b:936ea3ae name=snowball:1 It looks like the new style raid Indeed, superblock format 1.x. In addition to the "array UUID" which is common to all members of the array, it adds a specific "device UUID" for each member. blkid labels it "UUID_SUB". However this raid was created ~12y ago without metadata. I don't think so. If the array was created without metadata, blkid would not report the members as TYPE="linux_raid_member". It was rather probably created with the old metadata format 0.90. You can check with mdadm --examine /dev/sd[fg]1
Re: Talking about RAID - disks with same id
Le 10/11/2017 à 17:46, Joe Pfeiffer a écrit : deloptes writes: you see in your case PARTUUID is different for both members. In my case it is identical and this is what is bothering me It's my understanding that PTUUID on a disk using an MBR corresponds to the UUID on a disk using a GPT, not to PARTUUID (I don't know what on an MBR-based disk would correspond to PARTUUID, if anything). In the blkid syntax : PTUUID = partition table UUID (in the partition table). PARTUUID = partition UUID (in the partition table). UUID = filesystem or other contents UUID (in the partition data). There are no PTUUID nor PARTUUID in the MSDOS partition table format. There is only a 32-bit "disk identifier" field in the MBR, which can be displayed by fdisk. blkid uses it as a poor-man's PTUUID. Also, since version 3.8, the kernel combines the MSDOS disk identifier (PTUUID) and the partition numbers to create fake partition UUIDs (PARTUUIDs). The GPT partition table format has real 128-bit independent PTUUID and PARTUUIDs.
Re: Re: Reproducible bug
Hello, Thanks for your feedback. Laurent Lyaudet wrote: >> >> My install is up-to-date with latest security updates (that's the >> >> first thing I do anytime I start my laptop). deloptes wrote: > There is a rule: "never touch a running system" which means if something > works let it work. through your process you are exposed to bugs without a > way back. this is just an advise to review the process I think this is a very bad advice. You should always be uptodate with security updates since there is plenty of people ready to exploit already corrected security issues. The people that correct these security issues do this hard work for a reason. Never let your system stay insecure or say people to do so, unless you want them to be screwed by perverts behind a computer. > I don't use Gnome, because gtk with the concept behind caused a lot of > trouble long time ago and could not convince me that it will ever get > better so I can't help much. But ... there should be logging facility and > you need perhaps to enable something somewhere to see where it is coming > from or what is happening when the problem appears. > I usually look first in ~/.xsession-errors > someone else perhaps could help on where and how to debug gtk/gnome Thanks for this indication. I found no such file with : find / -name 'xsession*' I will google for gnome error logging. Best regards, Laurent Lyaudet 2017-11-10 21:47 GMT+01:00 Laurent Lyaudet : > Hi, > > Thanks for the response. > I did not install any gnome extension or tweaking tools for gnome. > So I'm afraid the cause is somewhere else. > Note that if it's a malware, I'm glad you cannot reproduce the bug ;) > > Best regards, >Laurent Lyaudet > > > > > 2017-11-10 21:22 GMT+01:00 RRRoy BBBean : > >> On Fri, 2017-11-10 at 20:26 +0100, Laurent Lyaudet wrote: >> > Hello Roberto, >> > As you suggested, I took my laptop at work and tested with the wifi >> > there. >> > I reproduced the bug also there. >> > I don't know if I can reproduce it with any wifi network but at least >> > it is >> > not particular to my home network only. >> > >> I tried this on my computer. I cannot reproduce the error. >> >> Last year I was working a lot with Gnome3 on Fedora24. I was installing >> and trying out lots of cool Gnome Shell Extension. After a few days, I >> noticed that various Gnome-related things started acting crazy or not >> working at all. I deinstalled most of these additional extensions, and >> now (on both Fedora and Debian) I stick with the default Gnome Shell >> Extensions plus a small number of additional extensions that I can't >> live without. >> >> Let me suggest that if you have installed additional Gnome Shell >> Extensions on top of the defaults, you remove them and see if the >> problem goes away. You will probably need to restart your laptop to be >> sure you get a clean load of Gnome. >> >> >
Re: Talking about RAID - disks with same id
Thanks Pascal, Pascal Hambourg wrote: > Le 10/11/2017 à 09:12, deloptes a écrit : >> >> >> It looks like the new style raid > > Indeed, superblock format 1.x. In addition to the "array UUID" which is > common to all members of the array, it adds a specific "device UUID" for > each member. blkid labels it "UUID_SUB". > >> However this raid was created ~12y ago without metadata. > > I don't think so. If the array was created without metadata, blkid would > not report the members as TYPE="linux_raid_member". It was rather > probably created with the old metadata format 0.90. You can check with > > mdadm --examine /dev/sd[fg]1 Indeed Creation Time : Mon Jul 26 21:49:51 2010 means data was migrated to those disks, which were assembled 2010 - data dates back to 2002. Seagate is definitely older than 2010. Anyway, thanks for the snip - useful! So if you know if in this context I have real RAID - I mean data is written to both drives? It would be nice, though I decided already to replace 2x1G+2x0.5G for 2x2G - wife blessed the budget :) regards
Re: Re: Reproducible bug
Laurent Lyaudet wrote: > I think this is a very bad advice. No it is a wise advise. When you make a change and if you want to be sure it works - make it on a test system. Otherwise you see what happens! > You should always be uptodate with security updates since there is > plenty of people ready to exploit already corrected security issues. > true > The people that correct these security issues do this hard work for a > reason. > true, but often the introduce regressions ;-) they are also humans > Never let your system stay insecure or say people to do so, unless you > want them to be screwed by perverts behind a computer. what means stay insecure? don't use internet and its done :) its always money / time / risk ratio regards
Re: Re: Reproducible bug
On 11/12/17, Laurent Lyaudet wrote:
> deloptes wrote:
>> I don't use Gnome, because gtk with the concept behind caused a lot of
>> trouble long time ago and could not convince me that it will ever get
>> better so I can't help much. But ... there should be logging facility and
>> you need perhaps to enable something somewhere to see where it is coming
>> from or what is happening when the problem appears.
>
>> I usually look first in ~/.xsession-errors
>
>> someone else perhaps could help on where and how to debug gtk/gnome
>
> Thanks for this indication. I found no such file with :
>
> find / -name 'xsession*'
>
> I will google for gnome error logging.
Does "find" find hidden files without being specifically told how to
do so? The other thing is that maybe you've just been phenomenally
blessed to have no errors. That *could* happen.. :)
~/.xession-errors can be found manually via a text editor or file
manager. Either can be pointed to the /home/[username] ("~/")
directory. If hidden "dot files and folders" are not showing, it's
*almost* universal that a user can do a "CTRL+H" keyboard combination
from *almost* anywhere to alternately reveal and then re-hide hidden
files.
/var/log is another place for some log files. Maybe there's something
in /var/log/syslog (or one or another of its archived versions) that
could show something.
What I'm thinking is maybe there's a warning or error message at boot
that might indicate something's not loading or otherwise performing as
expected during the boot process. That would have a trickle down
effect into overall system operability.
And then again... maybe not. :)
But like in my case just now, I making sure I was referencing the
correct log file... and found mine has a warning about a power button
conflict of interest going on under the hood.. along with a bunch of
other interesting things I keep forgetting to go back and play with
for the purpose of learning more about Debian.
Cindy :)
--
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with duct tape *
Hidden files [was: Reproducible bug]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, Nov 12, 2017 at 12:26:40PM -0500, Cindy-Sue Causey wrote:
[...]
> Does "find" find hidden files without being specifically told how to
> do so? The other thing is that maybe you've just been phenomenally
> blessed to have no errors. That *could* happen.. :)
The secret about hidden files is... that there are no hidden
files [1] :-)
There's just this convention that "ls" (and most GUI "file
managers" don't show files bearing a name which starts with
"." (dot). There's an option for "ls" to show those files
anyway ("-a", think "all"), and the GUIs typically call that
"show hidden files" (in some reminiscence of DOS hidden files,
which were something completely different!), thus causing
confusion.
GUIs have seldom qualms about causing confusion, which is
a pity, and the damage is kind of done now :-(
Typically, files and directories you don't want to "see always",
like "." (aka "self"), ".." (aka parent) and configuration
files and directories are named starting with a dot.
And yes, find does find those files by default.
[1] In Unix-like operating systems, that is.
Cheers
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAloIiZsACgkQBcgs9XrR2kZoCACeNJL374rGau2azu3c30Emam0t
J4AAnjvjCoJzD8qd6b45L3O36bAxwCDy
=Daeb
-END PGP SIGNATURE-
Re: Reproducible bug
On 2017-11-12, Cindy-Sue Causey wrote: > On 11/12/17, Laurent Lyaudet wrote: >> deloptes wrote: >>> I don't use Gnome, because gtk with the concept behind caused a lot of >>> trouble long time ago and could not convince me that it will ever get >>> better so I can't help much. But ... there should be logging facility and >>> you need perhaps to enable something somewhere to see where it is coming >>> from or what is happening when the problem appears. >> >>> I usually look first in ~/.xsession-errors >> >>> someone else perhaps could help on where and how to debug gtk/gnome >> >> Thanks for this indication. I found no such file with : >> >> find / -name 'xsession*' >> >> I will google for gnome error logging. > > > Does "find" find hidden files without being specifically told how to > do so? The other thing is that maybe you've just been phenomenally > blessed to have no errors. That *could* happen.. :) It seems the initial dot is part of the name. So his search syntax would not find a dot file. If he had put a wildcard at both ends of the string, but he didn't, and then he isn't looking in his home directory, either, is he? -- "The world is full of shipping clerks who have read the Harvard Classics." — Charles Bukowski
Re: Talking about RAID - disks with same id
Le 12/11/2017 à 17:57, deloptes a écrit : So if you know if in this context I have real RAID - I mean data is written to both drives? Sorry, I cannot tell. Insufficient data. You can check in /proc/mdstat.
where to bugreport a possible filesystem problem
Dear List! I've a problem with a drbd/ocfs2 dual primary configuration (2 nodes). The problem is if I write a file to the mounted ocfs2 fs then add extended attributes to it after this if I try to read back it is doesn't show any change until read the same file attributes from the other node. After if I go back to the original I get the correct values. But why I need to go to the othet node? root@node01:/# touch /srv/f root@node01:/# setfacl -m g:adm:rwx /srv/f root@node01:/# getfacl /srv/f getfacl: Removing leading '/' from absolute path names # file: srv/f # owner: root # group: root user::rw- group::rwx other::r-- root@node02:~# getfacl /srv/f getfacl: Removing leading '/' from absolute path names # file: srv/f # owner: root # group: root user::rw- group::r-- group:adm:rwx mask::rwx other::r-- root@node01:/# getfacl /srv/f getfacl: Removing leading '/' from absolute path names # file: srv/f # owner: root # group: root user::rw- group::r-- group:adm:rwx mask::rwx other::r-- So could someone please write me where the exact list / bugreport where I can send this question beside this list? Thany you!
Re: Talking about RAID - disks with same id
Pascal Hambourg wrote: > /proc/mdstat this looks good, however I tried writing to the disk and only one disk led indicates writes, so I think it is not writing on both disks. Anyway I will replace those disks thanks and regards
Re: where to bugreport a possible filesystem problem
Papp Rudolf Péter wrote: > The problem is if I write a file to the mounted ocfs2 fs then add > extended attributes to it after this if I try to read back it is doesn't > show any change until read the same file attributes from the other node. > After if I go back to the original I get the correct values. But why I > need to go to the othet node? > So could someone please write me where the exact list / bugreport > where I can send this question beside this list? Filesystems problems are (in most cases) Kernel problems, so the best package to report this against is the kernel package you are experiencing that problem with. Also: have you tried with a newer kernel, for example from backports? Maybe the problem is fixed there. Then you could add this as an additional data point into your bug report. Grüße, Sven. -- Sigmentation fault. Core dumped.
KVM PCI Passthrough NVidia GeForce GTX 1080 Ti error code 43
Dear all, Please help me passthrough my GPU the a KVM guest. The system I am using: lshw: https://pastebin.com/tB7FqqxN Host OS:Debian 9 Stretch Mainboard: Supermicro C7Z170-M (activated VT-d in Bios) CPU: Intel Core i7-7700K CPU @ 4.20GHz GPU: EVGA GeForce GTX1080 Ti The GPU is not listed because I have blacklisted it: $ cat /etc/modprobe.d/blacklist.conf blacklist nouveau lspci: https://pastebin.com/6qYuJRPg I found this guide: https://scottlinux.com/2016/08/28/gpu-passthrough-with-kvm-and-debian-linux/ After installing Win7 guest, enabling PCI passthrough using virt-manager, installing the NVidia driver in the guest, Windows reports the error 43 for the GPU. Windows has stopped this device because it has reported problems. (Code 43) This is described in the above mentioned post and a workaround is linked: https://www.reddit.com/r/VFIO/comments/479xnx/guests_with_nvidia_gpus_can_enable_hyperv/ Unfortunately I do not know how to apply the workaround. I understand that I should create a file '/usr/libexec/qemu-kvm-hv-vendor' with the following content: #!/bin/sh exec /usr/bin/qemu-kvm \ `echo "\$@" | sed 's|hv_time|hv_time,hv_vendor_id=whatever|g'` Or according to the original redhat mailing list post by Alex Williamson: https://www.redhat.com/archives/vfio-users/2016-March/msg00092.html $ cat /usr/libexec/qemu-kvm-hv-vendor #!/bin/sh exec /usr/bin/qemu-kvm \ `echo "\$@" | sed 's|hv_time|hv_time,hv_vendor_id=KeenlyKVM|g'` But since there is no qemu-kvm present and the directory '/usr/libexec' does not exist on my system, I wonder how I should proceed. Any help fixing my problem would be highly appreciated. Thanky you very much in advance and best regards, Ramon
Re: Re: Reproducible bug
Hello, Well, find behavior and hidden files was not the intended topic of this thread ;) I do already know about Ctrl+H, ls -a, etc. And indeed my find command is incorrect since I forgot the dot or some wildcard at the beginning. After correction, I can say there is no .xsession-errors file on my system. The only matches were /usr/share/xsessions /etc/X11/Xsession.d/40x11-common_xsessionrc So yes, it may be strange if usually there is plenty of X session errors. After googling, I looked at /var/log/messages with a lot of, well, messages that I didn't found interesting and related to my problem. I also looked at /var/log/gdm3/ but it was empty. Regarding the boot errors, I have plenty of them as with any laptop I've seen running with Linux since laptops tend to have weird hardware. However, despite the same boot errors since I installed Debian on this laptop, the bug I'm talking in this thread was not present until a few weeks ago. I also forgot to say that soon after the bug started I found that hitting the super/windows/apple key works despite the click not working. And I already know some people out there will say "problem solved, he can put up with the bug". Best regards, Laurent Lyaudet 2017-11-12 17:32 GMT+01:00 Laurent Lyaudet : > Hello, > > Thanks for your feedback. > > Laurent Lyaudet wrote: > > >> >> My install is up-to-date with latest security updates (that's the > >> >> first thing I do anytime I start my laptop). > deloptes wrote: > > There is a rule: "never touch a running system" which means if something > > works let it work. through your process you are exposed to bugs without a > > way back. this is just an advise to review the process > > I think this is a very bad advice. > You should always be uptodate with security updates since there is plenty of > people ready to exploit already corrected security issues. > > The people that correct these security issues do this hard work for a reason. > > Never let your system stay insecure or say people to do so, unless you want > them to be screwed by perverts behind a computer. > > > I don't use Gnome, because gtk with the concept behind caused a lot of > > trouble long time ago and could not convince me that it will ever get > > better so I can't help much. But ... there should be logging facility and > > you need perhaps to enable something somewhere to see where it is coming > > from or what is happening when the problem appears. > > > I usually look first in ~/.xsession-errors > > > someone else perhaps could help on where and how to debug gtk/gnome > > Thanks for this indication. I found no such file with : > > find / -name 'xsession*' > > I will google for gnome error logging. > > > Best regards, > >Laurent Lyaudet > > > > 2017-11-10 21:47 GMT+01:00 Laurent Lyaudet : > >> Hi, >> >> Thanks for the response. >> I did not install any gnome extension or tweaking tools for gnome. >> So I'm afraid the cause is somewhere else. >> Note that if it's a malware, I'm glad you cannot reproduce the bug ;) >> >> Best regards, >>Laurent Lyaudet >> >> >> >> >> 2017-11-10 21:22 GMT+01:00 RRRoy BBBean : >> >>> On Fri, 2017-11-10 at 20:26 +0100, Laurent Lyaudet wrote: >>> > Hello Roberto, >>> > As you suggested, I took my laptop at work and tested with the wifi >>> > there. >>> > I reproduced the bug also there. >>> > I don't know if I can reproduce it with any wifi network but at least >>> > it is >>> > not particular to my home network only. >>> > >>> I tried this on my computer. I cannot reproduce the error. >>> >>> Last year I was working a lot with Gnome3 on Fedora24. I was installing >>> and trying out lots of cool Gnome Shell Extension. After a few days, I >>> noticed that various Gnome-related things started acting crazy or not >>> working at all. I deinstalled most of these additional extensions, and >>> now (on both Fedora and Debian) I stick with the default Gnome Shell >>> Extensions plus a small number of additional extensions that I can't >>> live without. >>> >>> Let me suggest that if you have installed additional Gnome Shell >>> Extensions on top of the defaults, you remove them and see if the >>> problem goes away. You will probably need to restart your laptop to be >>> sure you get a clean load of Gnome. >>> >>> >> >
Re: Compatible laptops
On Sun, 12 Nov 2017 13:23:46 + dekkz...@gmail.com sent: > On 11/12, rhkra...@gmail.com wrote: > >On Sunday, November 12, 2017 02:39:22 AM dekks herton wrote: > >> in general - any modern laptop will run debian fine [with any DE > >> you choose] with IMO the following caveats > >> > >> 1) Avoid ones with hybrid dual graphics ie intel/nvidia aka optimus > >> 2) Avoid anything realtek > > > >I'd add, "avoid Broadcom if you want to use WiFi"--it requires some > >extra steps for installation (and is even more of a pain until you > >realize that is what you need to do)" > > Until the last 18 months i would have agreed but they hired one of > the leading kernal gfx hackers and now forced by the Pi market are > supporting newer stuff. Enough to come off my black list, however i'm > keeping an eye on them to see if they relapse. > After contemplation, my reply is: On an older Toshiba laptop I was given, mine starting to show signs of faults after 10 years work. I had a bit of trouble getting Broadcom WI-FI to work and had to take a couple of runs at it to get the desired result. That could have been because my expectation was, it would be straight forward. So probably my fault. Charlie
Re: Compatible laptops
On Mon, 13 Nov 2017 08:55:51 +1100 Charlie S wrote: > On Sun, 12 Nov 2017 13:23:46 + dekkz...@gmail.com sent: > > > On 11/12, rhkra...@gmail.com wrote: > > >On Sunday, November 12, 2017 02:39:22 AM dekks herton wrote: > > >> in general - any modern laptop will run debian fine [with any DE > > >> you choose] with IMO the following caveats > > >> > > >> 1) Avoid ones with hybrid dual graphics ie intel/nvidia aka > > >> optimus 2) Avoid anything realtek > > > > > >I'd add, "avoid Broadcom if you want to use WiFi"--it requires some > > >extra steps for installation (and is even more of a pain until you > > >realize that is what you need to do)" > > > > Until the last 18 months i would have agreed but they hired one of > > the leading kernal gfx hackers and now forced by the Pi market are > > supporting newer stuff. Enough to come off my black list, however > > i'm keeping an eye on them to see if they relapse. > > > > After contemplation, my reply is: > > On an older Toshiba laptop I was given, mine starting to show signs of > faults after 10 years work. I had a bit of trouble getting Broadcom > WI-FI to work and had to take a couple of runs at it to get the > desired result. That could have been because my expectation was, it > would be straight forward. So probably my fault. > It might be worth a reminder at this point that a particular 'model' of laptop (or other form) generally represents a desired set of capabilities, and the actual hardware may vary from time to time. It is necessary to go down to the level of all the letters on the end of the model name, or even an SKU designation if provided, to be sure that a particular laptop exactly complies with a published specification. For example, an HP laptop bought by a colleague of mine about six months after I had bought the 'same' model has a separate numeric keypad and mine doesn't. -- Joe
Re: Compatible laptops
On 11/12/2017 04:55 PM, Charlie S wrote: On Sun, 12 Nov 2017 13:23:46 + dekkz...@gmail.com sent: On 11/12, rhkra...@gmail.com wrote: On Sunday, November 12, 2017 02:39:22 AM dekks herton wrote: in general - any modern laptop will run debian fine [with any DE you choose] with IMO the following caveats 1) Avoid ones with hybrid dual graphics ie intel/nvidia aka optimus 2) Avoid anything realtek I'd add, "avoid Broadcom if you want to use WiFi"--it requires some extra steps for installation (and is even more of a pain until you realize that is what you need to do)" Until the last 18 months i would have agreed but they hired one of the leading kernal gfx hackers and now forced by the Pi market are supporting newer stuff. Enough to come off my black list, however i'm keeping an eye on them to see if they relapse. After contemplation, my reply is: On an older Toshiba laptop I was given, mine starting to show signs of faults after 10 years work. I had a bit of trouble getting Broadcom WI-FI to work and had to take a couple of runs at it to get the desired result. That could have been because my expectation was, it would be straight forward. So probably my fault. Charlie No, Broadcom is real PITA! Altho Mint 17 recognized a Broadcom board right off the bat with no actual installation problem at all! --doug
No KODI for buster?
Hi all, There is no KODI for the buster? How come?
Re: No KODI for buster?
On Mon, Nov 13, 2017 at 09:51:17AM +0900, Man_without_clue wrote: > Hi all, > > There is no KODI for the buster? > > How come? > > https://qa.debian.org/excuses.php?package=kodi -- Roberto C. Sánchez
Re: No KODI for buster?
On 2017/11/13 10:45, Roberto C. Sánchez wrote: On Mon, Nov 13, 2017 at 09:51:17AM +0900, Man_without_clue wrote: Hi all, There is no KODI for the buster? How come? https://qa.debian.org/excuses.php?package=kodi Oh no.. Not considered???
Re: No KODI for buster?
On 2017-11-12 at 21:37, Man_without_clue wrote: > On 2017/11/13 10:45, Roberto C. Sánchez wrote: > >> On Mon, Nov 13, 2017 at 09:51:17AM +0900, Man_without_clue wrote: >> >>> Hi all, >>> >>> There is no KODI for the buster? >>> >>> How come? >> >> https://qa.debian.org/excuses.php?package=kodi > > Oh no.. > > Not considered??? What that means (as I understand matters) is "Because this other reason means this package couldn't make it in anyway, the automatic tools did not consider whether or not to include it". The other reason is cited on that page: one of the build dependencies of kodi, in this case apparently libcec (libcec4 / libcec-dev), has a problem which is keeping it out. Presumably, once that other package gets fixed, it will make it in, and kodi will also get back in at that point. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Debian 8 and Debian 9 Dual Boot
My first Linux install was about one year ago. After some missteps, I have used Debian 8 in reasonable satisfaction on the desktop during that year. Now I want to leave 8 in place and do a network install for Debian 9 on the same disk and switch back and forth at boot time. LVM reports as follows: dan@debian:/$ sudo vgdisplay -C VG #PV #LV #SN AttrVSize VFree debian-vg 1 5 0wz--n- 976.56g 938.20g Currently, Debian 8 needs less than 40g for me as you can see: dan@debian:/$ sudo lvdisplay -C LV VGAttr LSize ... home debian-vg -wi-ao 10.00g root debian-vg -wi-ao 8.38g swap_1debian-vg -wi-ao 7.81g tmp debian-vg -wi-ao 380.00m var debian-vg -wi-ao 11.79g So there is plenty of disk space for the two Debians and more besides. The question is how to prepare to install 9? My guess is to define another volume group called debian9-vg perhaps but how will this be recognized during network install? I've clobbered stuff before during installs and I'm gun shy. Maybe there is a better way. Any thoughts on this will be appreciated. -Dan
Discrete Fourier Transform (DFT) viewer and/or file format
I have some DFTs that i wish to inspect. (Apparently DFT is a common acronym, but here i mean Discrete Fourier Transform. And properly speaking it doesn't make sense to inspect a transform, but only to inspect transformed data, but i'm speaking colloquially.) DFTs are a common artifact in digital signal processing. Lots of Debian packages are focused on FFTs (Fast Fourier Transforms, a way of computing DFTs). Nevertheless i couldn't find either a standard file format to store one, or software specifically for viewing DFTs. Of course, lots of software can take data, then transform it, then display the transform that it created, but i would like something that can take an already created DFT in some standard format, then display it. TIA for any information or pointers or advice from anybody! :) dan
Re: No KODI for buster?
On 2017/11/13 12:04, The Wanderer wrote: On 2017-11-12 at 21:37, Man_without_clue wrote: On 2017/11/13 10:45, Roberto C. Sánchez wrote: On Mon, Nov 13, 2017 at 09:51:17AM +0900, Man_without_clue wrote: Hi all, There is no KODI for the buster? How come? https://qa.debian.org/excuses.php?package=kodi Oh no.. Not considered??? What that means (as I understand matters) is "Because this other reason means this package couldn't make it in anyway, the automatic tools did not consider whether or not to include it". The other reason is cited on that page: one of the build dependencies of kodi, in this case apparently libcec (libcec4 / libcec-dev), has a problem which is keeping it out. Presumably, once that other package gets fixed, it will make it in, and kodi will also get back in at that point. oh, ok, thank you. Hope it will be back soon.
Re: Discrete Fourier Transform (DFT) viewer and/or file format
On 11/12/2017 09:45 PM, Dan Hitt wrote: I have some DFTs that i wish to inspect. (Apparently DFT is a common acronym, but here i mean Discrete Fourier Transform. And properly speaking it doesn't make sense to inspect a transform, but only to inspect transformed data, but i'm speaking colloquially.) DFTs are a common artifact in digital signal processing. Lots of Debian packages are focused on FFTs (Fast Fourier Transforms, a way of computing DFTs). Nevertheless i couldn't find either a standard file format to store one, or software specifically for viewing DFTs. Of course, lots of software can take data, then transform it, then display the transform that it created, but i would like something that can take an already created DFT in some standard format, then display it. TIA for any information or pointers or advice from anybody! :) dan A useful set of expertise is available at the USENET group at comp.dsp . HTH
Re: Discrete Fourier Transform (DFT) viewer and/or file format
On Sun, Nov 12, 2017 at 8:50 PM, Richard Owlett wrote: > On 11/12/2017 09:45 PM, Dan Hitt wrote: >> >> I have some DFTs that i wish to inspect. (Apparently DFT is a common >> acronym, but here i mean Discrete Fourier Transform. And properly >> speaking it doesn't make sense to inspect a transform, but only to >> inspect transformed data, but i'm speaking colloquially.) >> >> DFTs are a common artifact in digital signal processing. Lots of >> Debian packages are focused on FFTs (Fast Fourier Transforms, a way of >> computing DFTs). Nevertheless i couldn't find either a standard file >> format to store one, or software specifically for viewing DFTs. >> >> Of course, lots of software can take data, then transform it, then >> display the transform that it created, but i would like something that >> can take an already created DFT in some standard format, then display >> it. >> >> TIA for any information or pointers or advice from anybody! :) >> >> dan >> >> > > A useful set of expertise is available at the USENET group at comp.dsp . > HTH Thanks Richard. Maybe you're exactly right, because if i can find any free software that's relevant to what i want, then i can probably get it to Debian. (If i have something specific, then can bring it up here in fact if i have trouble installing it.) How do you normally access usenet? In the old days (meaning, decades ago) i used to read usenet with rn. I suppose a modern equivalent would be google groups, but if i do get back in the usenet scene, i'm wondering if there's a more command-liney thing or just other alternatives to consider before walking down the google trail. Anyhow, whether or not you have an answer about the best way to go to usenet, i appreciate the suggestion because that group (comp.dsp) is probably where i can find what i'm looking for if it exists at all. dan
Re: Debian 8 and Debian 9 Dual Boot
On 11/12/17 19:27, Dan Norton wrote: My first Linux install was about one year ago. After some missteps, I have used Debian 8 in reasonable satisfaction on the desktop during that year. Now I want to leave 8 in place and do a network install for Debian 9 on the same disk and switch back and forth at boot time. I think your best bet is to migrate from Debian 8 to Debian 9: 1. Image, backup, and/or archive everything. You will especially want to get a copy of the /etc tree onto a USB flash drive so you can see LVM, fstab, etc., configuration settings for mounting the Debian 8 disk under Debian 9. 2. Put your bulk data onto a separate drive or a file server/ NAS. 3. If your computer has a spare drive bay, buy a new drive, unplug your old drive, install the new drive, install Debian 9 onto the new drive, reconnect the old drive and mount read-only under Debian 9, and migrate your settings and remaining data from the old drive to the new drive. Your BIOS/UEFI should allow you to boot from either drive during this process. So long as you don't damage the Debian 8 disk, you can always fall back to Debian 8 if the migration goes badly. 4. If you computer does not have a spare drive bay, buy a new drive and a USB external drive enclosure, put your old drive in the enclosure, install the new drive, install Debian 9 onto the new drive, plug in the old drive and mount read-only under Debian 9, and migrate your settings and remaining data from the old drive to the new drive. Again, your BIOS/UEFI should allow you to boot from either drive and you can fall back to Debian 8 if necessary. David
Re: where to bugreport a possible filesystem problem
I tried with newer kernel from backports as you suggested - also installed the fresh firmware packages too - no change. Weird... Anyway I report back for linux-image package perhaps. Thank you Sven! 2017-11-12 20:19 keltezéssel, Sven Hartge írta: Papp Rudolf Péter wrote: The problem is if I write a file to the mounted ocfs2 fs then add extended attributes to it after this if I try to read back it is doesn't show any change until read the same file attributes from the other node. After if I go back to the original I get the correct values. But why I need to go to the othet node? So could someone please write me where the exact list / bugreport where I can send this question beside this list? Filesystems problems are (in most cases) Kernel problems, so the best package to report this against is the kernel package you are experiencing that problem with. Also: have you tried with a newer kernel, for example from backports? Maybe the problem is fixed there. Then you could add this as an additional data point into your bug report. Grüße, Sven.
