Re: Donate 1 minute of your time to test upgrades from F34 to F35
On 2021-09-07 12:14 p.m., Miroslav Suchý wrote: Do you want to make Fedora 35 better? Please spend 1 minute of your time and try to run: # Run this only if you use default Fedora modules # next time you run any DNF command default modules will be enabled again sudo dnf module reset '*' sudo dnf --releasever=35 --setopt=module_platform_id=platform:f35 \ --enablerepo=updates-testing --enablerepo=updates-testing-modular \ distro-sync This command does not replace `dnf system-upgrade`, but it will reveal potential problems. You may also run `dnf upgrade` before running this command. If you get this prompt: ... Total download size: XXX M Is this ok [y/N]: you can answer N and nothing happens, no need to test the actual upgrade. 0 root@gravitar:/home/digimer# dnf --releasever=35 --setopt=module_platform_id=platform:f35 --enablerepo=updates-testing --enablerepo=updates-testing-modular distro-sync AnyDesk Fedora - stable 2.1 kB/s | 1.6 kB 00:00 Fedora 35 - x86_64 13 MB/s | 78 MB 00:06 Fedora 35 - Source 3.0 MB/s | 7.3 MB 00:02 Fedora 35 openh264 (From Cisco) - x86_6 3.1 kB/s | 2.5 kB 00:00 Fedora Modular 35 - x86_64 3.8 MB/s | 3.3 MB 00:00 Fedora 35 - x86_64 - Updates 170 B/s | 257 B 00:01 Fedora 35 - Updates Source 280 B/s | 257 B 00:00 Fedora Modular 35 - x86_64 - Updates 460 B/s | 257 B 00:00 Fedora 35 - x86_64 - Test Updates 6.6 MB/s | 6.5 MB 00:00 Fedora Modular 35 - x86_64 - Test Updat 859 kB/s | 1.3 MB 00:01 google-chrome 2.6 kB/s | 3.5 kB 00:01 RPM Fusion for Fedora 35 - Free 1.5 MB/s | 946 kB 00:00 RPM Fusion for Fedora 35 - Free tainted 8.9 kB/s | 6.1 kB 00:00 RPM Fusion for Fedora 35 - Free - Updat 6.0 kB/s | 1.8 kB 00:00 RPM Fusion for Fedora 35 - Nonfree 513 kB/s | 243 kB 00:00 RPM Fusion for Fedora 35 - Nonfree tain 14 kB/s | 4.2 kB 00:00 RPM Fusion for Fedora 35 - Nonfree - Up 3.7 kB/s | 1.2 kB 00:00 Error: Problem 1: problem with installed package python3-opencensus-0.7.13-1.fc34.noarch - python3-opencensus-0.7.13-1.fc34.noarch does not belong to a distupgrade repository - nothing provides (python3.10dist(google-api-core) < 2 with python3.10dist(google-api-core) >= 1) needed by python3-opencensus-0.7.13-3.fc35.noarch Problem 2: package gstreamer-plugins-ugly-0.10.19-40.fc34.x86_64 requires libx264.so.161()(64bit), but none of the providers can be installed - x264-libs-0.161-6.20210412git55d517b.fc34.x86_64 does not belong to a distupgrade repository - problem with installed package gstreamer-plugins-ugly-0.10.19-40.fc34.x86_64 Problem 3: problem with installed package python3-opencensus-ext-azure-0.7.13-1.fc34.noarch - package python3-opencensus-ext-azure-0.7.13-3.fc35.noarch requires (python3.10dist(opencensus) < 1 with python3.10dist(opencensus) >= 0.7.13), but none of the providers can be installed - python3-opencensus-ext-azure-0.7.13-1.fc34.noarch does not belong to a distupgrade repository - nothing provides (python3.10dist(google-api-core) < 2 with python3.10dist(google-api-core) >= 1) needed by python3-opencensus-0.7.13-3.fc35.noarch Problem 4: problem with installed package python3-opencensus-ext-threading-0.7.13-1.fc34.noarch - package python3-opencensus-ext-threading-0.7.13-3.fc35.noarch requires (python3.10dist(opencensus) < 1 with python3.10dist(opencensus) >= 0.7.13), but none of the providers can be installed - python3-opencensus-ext-threading-0.7.13-1.fc34.noarch does not belong to a distupgrade repository - nothing provides (python3.10dist(google-api-core) < 2 with python3.10dist(google-api-core) >= 1) needed by python3-opencensus-0.7.13-3.fc35.noarch (try to add '--skip-broken' to skip uninstallable packages) -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that peop
Re: Need help to contact: digimer mbartos, ignotusp
On 2020-06-25 3:09 p.m., Pierre-Yves Chibon wrote: > On Thu, Jun 25, 2020 at 12:37:41PM -0400, Digimer wrote: >> digimer here, sorry, I'm not sure why my address was rejected. I can >> also be reached at 'mke...@alteeve.ca'. > > Could you update it in FAS and check if whichever account you use in FAS has a > corresponding bugzilla account? > > Thanks! > > Pierre Updated! >> On 2020-06-25 9:08 a.m., Pierre-Yves Chibon wrote: >>> Good Morning Everyone, >>> >>> As announced on devel-announce [1] I have sent an email to each account >>> listed >>> on dist-git to be either point of contact or included in the CC list of >>> tickets >>> opened on bugzilla. >>> >>> The following emails to the following account came back with and error: >>> - digimer (error: Recipient address rejected: alteeve.ca) >>> - Maintains: rpms/kronosnet >>> - mbartos (error: Recipient address rejected: Access denied) >>> - Maintains: rpms/libee, rpms/libestr, rpms/liblognorm >>> - ignotusp (error: No such user!) >>> - Maintains: rpms/wicd-kde >>> >>> Does anyone know how to contact these persons? >>> >>> If we have no way to contact them, we may have to ask FESCo to consider them >>> unresponsive. >>> >>> Thanks in advance for your help! >>> >>> Pierre >>> >>> >>> [1]: >>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VBMMXJT2M5TMWSH3DT3DY6VBPELSTQFV/ >>> >>> >>> ___ >>> devel mailing list -- devel@lists.fedoraproject.org >>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org >>> Fedora Code of Conduct: >>> https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >>> List Archives: >>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org >>> >> >> >> -- >> Digimer >> Papers and Projects: https://alteeve.com/w/ >> "I am, somehow, less interested in the weight and convolutions of >> Einstein’s brain than in the near certainty that people of equal talent >> have lived and died in cotton fields and sweatshops." - Stephen Jay Gould >> -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Need help to contact: digimer mbartos, ignotusp
digimer here, sorry, I'm not sure why my address was rejected. I can also be reached at 'mke...@alteeve.ca'. Madi On 2020-06-25 9:08 a.m., Pierre-Yves Chibon wrote: > Good Morning Everyone, > > As announced on devel-announce [1] I have sent an email to each account listed > on dist-git to be either point of contact or included in the CC list of > tickets > opened on bugzilla. > > The following emails to the following account came back with and error: > - digimer (error: Recipient address rejected: alteeve.ca) > - Maintains: rpms/kronosnet > - mbartos (error: Recipient address rejected: Access denied) > - Maintains: rpms/libee, rpms/libestr, rpms/liblognorm > - ignotusp (error: No such user!) > - Maintains: rpms/wicd-kde > > Does anyone know how to contact these persons? > > If we have no way to contact them, we may have to ask FESCo to consider them > unresponsive. > > Thanks in advance for your help! > > Pierre > > > [1]: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/VBMMXJT2M5TMWSH3DT3DY6VBPELSTQFV/ > > > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@lists.fedoraproject.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org > -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Trouble creating modular metadata for local repo
On 2020-01-07 9:05 a.m., Petr Pisar wrote: > On 2020-01-07, Digimer wrote: >> I'm trying to create a local repo of an offline collection of systems. >> When I try to install, I get: >> >> >> No available modular metadata for modular package 'foo.arch', it cannot >> be installed on the system >> >> > I guess the 'foo.arch' name is made up and it is actually a package > provided by Fedora. Because there is no such package in Fedora and thus > DNF should not suppose that the package is modular. > > Otherwise if it were a new unique yet modular package, there have to be > the "modules.yaml" file listing it. And in that case you would know what > modules are and how they are built and put into a repository. > > Could you explain us what the 'foo.arch' is in your case? > > -- Petr Since I wrote this, I've made some progress. I've taken the 'modules.yaml' file from the RHEL 8.1 ISO as a source, and now I can generate the modules.yaml file. The resolves the error for all RPMs already listed, but I am trying to add 'libssh2' without luck. I followed: https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/ and tried to add this; --- document: modulemd version: 2 data: name: libssh2 stream: 1.8 arch: x86_64 summary: A library implementing the SSH2 protocol description: >- libssh2 is a library implementing the SSH2 protocol as defined by Internet Drafts: SECSH-TRANS(22), SECSH-USERAUTH(25), SECSH-CONNECTION(23), SECSH-ARCH(20), SECSH-FILEXFER(06)*, SECSH-DHGEX(04), and SECSH-NUMBERS(10). license: module: - BSD dependencies: - buildrequires: platform: [] requires: platform: [] profiles: default: rpms: - libssh2 api: rpms: - libssh2 components: rpms: libssh2: rationale: Main libssh2 Package ref: latest arches: [aarch64, i686, ppc64le, s390x, x86_64] ... --- document: modulemd-defaults version: 1 data: module: libssh2 stream: 1.8 profiles: default [common] ... When I generate the modules.yaml using 'modifyrepo_c', I can see the libssh2 entries get added to the repodata/-modules.yaml.gz file. However, when I try to install, it still throws; Dependencies resolved. Package Architecture Version Repository Size Installing: libssh2 x86_64 1.8.0-8.module+el8.0.0+4084+cceb9f44.1 el8-striker01-repo 99 k Transaction Summary Install 1 Package Total download size: 99 k Installed size: 199 k Is this ok [y/N]: y Downloading Packages: libssh2-1.8.0-8.module+el8.0.0+4084+cceb9f44.1.x86_64.rpm 41 MB/s | 99 kB 00:00 Total 9.7 MB/s | 99 kB 00:00 Running transaction check No available modular metadata for modular package 'libssh2-1.8.0-8.module+el8.0.0+4084+cceb9f44.1.x86_64', it cannot be installed on the system The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: No available modular metadata for modular package I know this is RHEL 8, but the documentation is from Fedora (I can't find anything related to this regarding RHEL specifically). Hopefully I can still get help here. :) -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Trouble creating modular metadata for local repo
Hi all, I'm trying to create a local repo of an offline collection of systems. When I try to install, I get: No available modular metadata for modular package 'foo.arch', it cannot be installed on the system Googling leads me to: https://docs.fedoraproject.org/en-US/modularity/hosting-modules/ Which tells me to run: # createrepo_c /path/to/rpms/x86_64/os/ # modifyrepo_c --mdtype=modules modules.yaml /path/to/rpms/x86_64/os/ However, the 'modifyrepo_c' call returns: File "modules.yaml" is not regular file or doesn't exists I'm wondering how to fix this? The repo is simply a collection of RPMs, created specifically using the command: /usr/bin/createrepo_c -g /path/to/rpms/x86_64/os/comps.xml /path/to/rpms/x86_64/os Any help or guidance is much appreciated. :) -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Re: Best way to handle sub-package conflicts
On 2018-03-18 11:48 AM, Nicolas Mailhot wrote: > Le dimanche 18 mars 2018 à 11:22 -0400, Digimer a écrit : >> >> So this isn't a version conflict, as seems to be what Conflicts and >> Obsoletes are designed to handle, if I understand properly. > > It is a conflict between the packages. > > What you can’t do is to allow the installation of one package to replace > the others, because for rpm and dnf installations and updates have the > same constrains (so if foo-b is allowed to replace foo-a it will do it > for updates too) > > So you have too solutions: > > 1. make the packages conflict, to force users to choose one of them. > Installation of each packages will be forbidden while one of the others > is present > > 2. make sure the packages do not conflict, and can be parallel > installed. Handle role conflicts at runtime, making sure whatever is > executed in each role refuses to run if one of the others is already > running (via lockfile for example) Hi, I think "Conflict" is the way to go. However, given how much the guide urges not to use 'Conflicts', I worry that will make it harder/impossible later to have the package accepted into Fedora. Would a use-case like this be an acceptable exception, would you guess? As I mentioned in my reply to Micheal, I am not worried about auto-removal. If it simply refused to install one sub-package until the other is gone, that's fine. -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Best way to handle sub-package conflicts
On 2018-03-18 11:40 AM, Michael Schwendt wrote: > On Sun, 18 Mar 2018 11:22:23 -0400, Digimer wrote: > >> So the .spec creates four RPMs; "anvil-core", "anvil-striker", >> "anvil-node" and "anvil-dr". >> >> All machines require "anvil-core", plus one (and only one) of the other >> three packages. There is no scenario where, for example, 'anvil-node' >> and 'anvil-striker' would be installed on the same machine. So if a user >> has 'anvil-striker' RPM installed, and they try to install 'anvil-node', >> I want that to remove 'anvil-striker'. Similarly, if a machine has >> 'striker-node' already installed and the user tries to install >> 'anvil-dr', I want 'anvil-node' removed. This is because a single >> machine can only play one role at a time. >> >> So this isn't a version conflict, as seems to be what Conflicts and >> Obsoletes are designed to handle, if I understand properly. > > The description of the packaging scenario is not complete yet. > If -striker, -node and -dr are mutually exclusive, why is that? > Are there implicit conflicts in the packaged files? Then you cannot > avoid Conflicts tags. Or are there runtime conflicts? Then you should > look into a solution that would resolve the conflict with a configuration > file, which would define the operation mode of the software. > > So far, the scenario sounds very much as if you want to add Conflicts tags > to the subpackages as to achieve that only one of them can be > installed. Trying to simulate automatic removal of conflicts through > Obsoletes tags is not the right thing to do in your scenario. You would > end up with circular Obsoletes, which would confuse depsolvers or lead > to random behavior. The conflict is in the role the machine plays in the larger cluster, rather than an application-level conflict. So, for example, if the machine is "striker", it hosts the database and is not allowed to host servers. If a machine is a "node", it is allowed to be a live migration target, but must have synchronous storage replication. If a machine is "dr", it is allowed to host VMs, but it is not allowed to be a live migration target. These restrictions come from the design of the system, not from code-level incompatibility. I'm agreeing that "Conflicts" sounds like the right option, but my concern came from the guide's strong language against its use. I'm OK with the package not automatically removing the others, so long as the sub packages can't be installed at the same time. It is ok to just error and tell the user to remove the conflict first, then try again. -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Best way to handle sub-package conflicts
On 2018-03-18 11:12 AM, Michael Schwendt wrote: > On Sun, 18 Mar 2018 10:22:49 -0400, Digimer wrote: > >> Hi all, >> >> I am creating a new RPM package for a cluster project we've created. >> There is a common "core" package, and then three other packages that are >> installed depending on the machine's role in the cluster; >> >> foo-core >> foo-A >> foo-B >> foo-C >> >> If 'foo-A' is installed, I want 'foo-B' and 'foo-C' to be removed, and >> 'foo-B' replaces 'foo-A' and 'foo-C', etc. I originally planned to use >> 'Conflicts: ' in our spec, but reading this: >> >> https://fedoraproject.org/wiki/Packaging:Conflicts >> >> It seems like 'Conflicts' is strongly discouraged. So instead I tried >> 'Obsoletes', and this seemed to work in that, if 'foo-A' was installed >> and I tried to install 'foo-B', it would remove 'foo-A'. So I thought I >> was ok, until I bumped the version and tried to to an update. With >> 'foo-A' installed, it wanted to install 'foo-B' and 'foo-C' and failed, >> which makes sense now that I think of it. >> >> What is the best way to handle this in the .spec file? I'm having >> trouble finding the right term to search form. > > Could you proof-read your mail and correct the update scenario? > First you wanted foo-A to replace foo-B and foo-C. Next you write that > foo-B replaces foo-A and foo-C. Something's wrong in your description. > Under normal circumstances, a subpackage would never replace a > package with a different %name. > > Better split your packaging scenario in two clear parts: > 1) The packages that have been published before and which you start with. > Describe them and their inter-package dependencies. > 2) The set of packages you want to continue with after a major upgrade > that replaces/removes packages. Describe them and their inter-package > dependencies. > > Obsoletes tags usually are versioned, so they only remove older packages > up to a maximum version. That way you can reintroduce packages in the future. > If you keep building subpackages you've obsoleted before, they remain > available to be installed, and you would need to increase the version in > your Obsoletes tags to cover them. Nevertheless, subpackages with > different names would never replace eachother. Unless you've added > Obsoletes tags to do that. I'm sorry if I wasn't clear, perhaps I needed more coffee. Let me use specifics; Our cluster has hardware that play one of three roles; "Striker" (user dashboard and database host), "nodes" which hosts virtual servers that can live-migrate between nodes, and "dr" hosts which are used for disaster recovery in case the main cluster is destroyed. So the .spec creates four RPMs; "anvil-core", "anvil-striker", "anvil-node" and "anvil-dr". All machines require "anvil-core", plus one (and only one) of the other three packages. There is no scenario where, for example, 'anvil-node' and 'anvil-striker' would be installed on the same machine. So if a user has 'anvil-striker' RPM installed, and they try to install 'anvil-node', I want that to remove 'anvil-striker'. Similarly, if a machine has 'striker-node' already installed and the user tries to install 'anvil-dr', I want 'anvil-node' removed. This is because a single machine can only play one role at a time. So this isn't a version conflict, as seems to be what Conflicts and Obsoletes are designed to handle, if I understand properly. I hope I made more sense this time. :) -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Best way to handle sub-package conflicts
Hi all, I am creating a new RPM package for a cluster project we've created. There is a common "core" package, and then three other packages that are installed depending on the machine's role in the cluster; foo-core foo-A foo-B foo-C If 'foo-A' is installed, I want 'foo-B' and 'foo-C' to be removed, and 'foo-B' replaces 'foo-A' and 'foo-C', etc. I originally planned to use 'Conflicts: ' in our spec, but reading this: https://fedoraproject.org/wiki/Packaging:Conflicts It seems like 'Conflicts' is strongly discouraged. So instead I tried 'Obsoletes', and this seemed to work in that, if 'foo-A' was installed and I tried to install 'foo-B', it would remove 'foo-A'. So I thought I was ok, until I bumped the version and tried to to an update. With 'foo-A' installed, it wanted to install 'foo-B' and 'foo-C' and failed, which makes sense now that I think of it. What is the best way to handle this in the .spec file? I'm having trouble finding the right term to search form. Thanks! -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Self Introduction: Madison Kelly (digimer)
Hello, I'm fairly new to packaging. I helped maintain the 'cluster' package some years back, but haven't done packaging since it was retired when F16 went EOL. I'm lead developer of the Anvil! Intelligent Availability platform, a fully open source "smart" high availability cluster appliance that hosts and protects critical KVM/qemu servers (https://www.alteeve.com/w/What_is_an_Anvil!_and_why_do_I_care%3F). I work for Alteeve, the company that built and maintains the Anvil! project. As part of this, I am quite active in the open source availability world and can often be found lurking in the Clusterlabs IRC channel on freenode (#clusterlabs) and the Clusterlabs mailing list. I've been working almost exclusively in open source since the early 2000s and started off as a sysadmin and slowly and somewhat reluctantly found myself programming most days (though I struggle to call myself a programmer, but more an admin who can program). I've pushed my first package (perl-Log-Journald, https://bugzilla.redhat.com/show_bug.cgi?id=1499109) as a gentle step-in to the packaging world. Looking forward to meeting folks and learning more about packaging! cheers -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: New
On 22/01/17 01:17 AM, Sarthak Gupta wrote: > Hi Digimer > Thanks for your valuable advice and guidance. :D > I am good at C programming, HTML and know the basics of MySQL. I am > hoping to learn more through the open source. Basically I am not well > aware of the areas where I can get started. I am ready to contribute in > even the smallest of the things because I know it will benefit me in > some or the other kind. Please guide me further! :) Your enthusiasm is great, but you really need to find your own focus. The #1 key to success in IT, in my opinion, is to find what you have fun doing. If you are working on a project you enjoy, you will do well because you will be having fun, and thus stay focused in learning and doing a good job. So your first task is to start, even with just a vague idea, of what it is you think you will enjoy. There are many very high level divisions in IT. Pick one to start focusing, and see what you find. If you are really unsure; Start with this; 1. Do you like servers, workstations or mobile the most? -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: New
On 21/01/17 12:20 PM, Sarthak Gupta wrote: > Hi > I am new here and I want to contribute to open source. Can someone > please guide me. :) This is a surprisingly big question, despite being short. :) "Open source" covers an absolutely huge range of projects and interests. I would suggest you start by asking yourself, "what do I find interesting?". If you're just starting out, don't worry if you think of something and then decide you don't actually like it. That's part of learning, just switch to some other field and see if you like that. You might bounce around a while before you find what it is you really like. When you do pick a field that you think will interest you, look at the software people are using in it. Say you like web servers; There is the established Apache server, lightweight servers, servers designed to huge scale, etc. If you think you will like databases; There are postgresql, mariadb, nosql, etc. If you think you will like graphics or gaming, there are several projects there, too. Once you find a field, and then a project to help with, join that projects community (exactly how depends on the project). Introduce yourself and offer to help. You might start off doing simple things, like helping with translations if you speak two languages, editing documentation, looking so simple open bugs and contribute patches and stuff like that. As you start to contribute, even if just in small and simple ways at first, people in the project will certainly be happy and they will help you learn in return. You'll move on the more difficult bugs, writing extensions, or whatever the project needs and you think would be fun. Hope this helps, Digimer -- Digimer Papers and Projects: https://alteeve.com/w/ "I am, somehow, less interested in the weight and convolutions of Einstein’s brain than in the near certainty that people of equal talent have lived and died in cotton fields and sweatshops." - Stephen Jay Gould ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Re: Intent to orphan shorewall
On 09/02/16 06:12 AM, Michele Baldessari wrote: > On Mon, Feb 08, 2016 at 10:56:11AM -0500, Digimer wrote: >>> I see this is still orphaned. I am happy to step in if you guys changed >>> your mind, as I use shorewall quite a bit in my setups. >> >> I want to take it over, but work has proven more busy that I expected. >> If you have the cycles, please take it. I would be happy to be >> co-maintainer though. This would have been my first package, so it's >> probably smarter if I helped someone with experience rather than try to >> do it myself. :) > > Thanks, Digimer. I have taken ownership. Please do add yourself to the > ACLs and we can work on maintaining it together. I have updated it > locally and will test it once I am back home at the end of this week. > After that I will update it to 5.x in rawhide only for now. > > cheers, > Michele Fantastic, thanks! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Intent to orphan shorewall
On 08/02/16 08:56 AM, Michele Baldessari wrote: > On Thu, Dec 17, 2015 at 11:03:46PM -0500, Digimer wrote: >> On 17/12/15 09:26 PM, Orion Poplawski wrote: >>> On 12/17/2015 05:27 PM, Digimer wrote: >>>> I'll take co-maintainer to assist Alex as she comes up to speed. I >>>> maintained the "cluster" package in Fedora up until it was retired in >>>> F16. I'm a little rusty now, but shorewall is a fairly simple package >>>> and we already maintain a repo of our own, so I expect little trouble. >>>> >>>> digimer >>>> >>>> On 17/12/15 10:48 AM, Alex Bruneau wrote: >>>>> I am new to package maintaining, but Alteeve's Niche uses Shorewall >>>>> in one of our offerings, and I'd be happy to take it on. Our tech >>>>> lead is available to assist as well. Thank you for all of your work >>>>> on the package! >>> >>> So, Alex (nyz ?) appears to not be a packager, and I can't find >>> digimer's FAS name. I'll just have to ask that people add themselves to >>> the package: >>> >>> https://admin.fedoraproject.org/pkgdb/package/rpms/shorewall/ >> >> I just added myself as a watcher. >> >> Alex (nick is 'nyz', yes) just setup her account today. I'll chat with >> her tomorrow about setting up on FAS. > > I see this is still orphaned. I am happy to step in if you guys changed > your mind, as I use shorewall quite a bit in my setups. > > Please let me know, > Michele I want to take it over, but work has proven more busy that I expected. If you have the cycles, please take it. I would be happy to be co-maintainer though. This would have been my first package, so it's probably smarter if I helped someone with experience rather than try to do it myself. :) -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Intent to orphan shorewall
On 17/12/15 09:26 PM, Orion Poplawski wrote: > On 12/17/2015 05:27 PM, Digimer wrote: >> I'll take co-maintainer to assist Alex as she comes up to speed. I >> maintained the "cluster" package in Fedora up until it was retired in >> F16. I'm a little rusty now, but shorewall is a fairly simple package >> and we already maintain a repo of our own, so I expect little trouble. >> >> digimer >> >> On 17/12/15 10:48 AM, Alex Bruneau wrote: >>> I am new to package maintaining, but Alteeve's Niche uses Shorewall >>> in one of our offerings, and I'd be happy to take it on. Our tech >>> lead is available to assist as well. Thank you for all of your work >>> on the package! > > So, Alex (nyz ?) appears to not be a packager, and I can't find > digimer's FAS name. I'll just have to ask that people add themselves to > the package: > > https://admin.fedoraproject.org/pkgdb/package/rpms/shorewall/ I just added myself as a watcher. Alex (nick is 'nyz', yes) just setup her account today. I'll chat with her tomorrow about setting up on FAS. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Intent to orphan shorewall
I'll take co-maintainer to assist Alex as she comes up to speed. I maintained the "cluster" package in Fedora up until it was retired in F16. I'm a little rusty now, but shorewall is a fairly simple package and we already maintain a repo of our own, so I expect little trouble. digimer On 17/12/15 10:48 AM, Alex Bruneau wrote: > I am new to package maintaining, but Alteeve's Niche uses Shorewall in one of > our offerings, and I'd be happy to take it on. Our tech lead is available to > assist as well. Thank you for all of your work on the package! > > -- > Alex Bruneau > Technician, Alteeve's Niche! Inc. > 145 Front St East, Toronto, Canada > abrun...@alteeve.ca > -- > devel mailing list > devel@lists.fedoraproject.org > http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org > -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Re: Fedora 23 Final RC10 status is GO !
On 01/11/15 12:06 PM, Sérgio Basto wrote: > On Sex, 2015-10-30 at 17:47 +0100, Jan Kurik wrote: >> At the third round of Fedora 23 Final Go/No-Go Meeting, that just >> ends, has been Fedora 23 Final-RC10 declared as GOLD. >> GA of this release is planed on Tuesday 2015-Nov-03. >> > Today we got 531 updates for F23 , IMO, you should include it on Fedora > 23 Final before GA , doesn't make sense (to me) after download an ISO > have 1/2 Giga of updates, but this happens since RedHad 9 at least . > IMO, testing team should respin ISO with updates and testing again . > I have some difficulty in following all development, fortunately Fedora > is always at great speed, but it is not easy to follow. And do more > tests we not lose anything, IMHO. > > > Thanks, How does that compare to the normal volume of incoming updates? What I mean is, if they re-rolled and re-tested, would a roughly similar number of updates be waiting again? -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Geeqie... I'll take it -- but I'd like co-maintainers! [was Re: Orphaned Geeqie]
On 20/07/15 02:57 PM, Matthew Miller wrote: > On Mon, Jul 20, 2015 at 01:16:08PM +0200, Michael Schwendt wrote: >> If you're interested in this image viewer, feel free to adopt the >> package. > > I am interested, and I'll pick it up. However, I'd definitely > appreciate co-maintainers, and particularly someone who could generate > security patches if need be, given the state of upstream. As a user, I am very grateful, thank you! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Orphaned Geeqie
On 20/07/15 07:16 AM, Michael Schwendt wrote: > Hello, everyone! > > In pkgdb, I've orphaned "geeqie" for Fedora devel and Fedora 23: > https://admin.fedoraproject.org/pkgdb/package/geeqie/ > > If you're interested in this image viewer, feel free to adopt the > package. > > I wish I had good news about its current state of development, but things > have turnt worse. > > * the project has lost much of the initial momentum after forking GQview > * tickets at the old Sourceforge project home don't get answered > * the project has lost the gitorious repo > * the project has created a temporary geeqie.org web page and git repo > * there still is no official release tarball for version 1.2 released >11 months ago This is my primary image viewer still... I'm not able to take it over, but as a user, I'd be very grateful if someone did. :) -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Linux 4.0
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/02/15 01:23 PM, poma wrote: > On 23.02.2015 19:22, Stephen John Smoogen wrote: >> There was no deflection. You did not post any context and we >> can't read your mind. On Feb 23, 2015 11:16 AM, "poma" >> wrote: >>> >>> On 23.02.2015 18:54, Ian Pilcher wrote: >>>> On 02/23/2015 11:38 AM, poma wrote: >>>>> On 23.02.2015 14:41, Josh Boyer wrote: ... >>>>>> things might still pop up. If you are using out of tree >>>>>> drivers (vbox, nvidia) you might want to pay extra >>>>>> attention. >>>>> >>>>> >>>>> >> https://fedoraproject.org/wiki/Forbidden_items?rd=ForbiddenItems#NVIDIA_Proprietary_Graphics_Drivers >>>> >>>> >> That pages discusses the reasons that those items are not included in >>>> Fedora. I'm pretty sure that it hasn't yet been declared a >>>> thought- crime to discuss them. >>>> >>> >>> Don't deflect. >>> >> >> There was no deflection. You gave no context and we can't read >> your mind. Either post more context in what you want or expect a >> lot of missed guesses on what you inferred >> >>> For proprietary and closed source, here you can contact: >>> http://www.nvidia.com/page/contact_information.html >>> >>> The only honest discussion is here: >>> http://nouveau.freedesktop.org/wiki >>> >>> >>> >>> >>> -- devel mailing list devel@lists.fedoraproject.org >>> https://admin.fedoraproject.org/mailman/listinfo/devel Fedora >>> Code of Conduct: http://fedoraproject.org/code-of-conduct >> >> >> > > Don't top post Mister Context. Can we be more civil please? - -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU63FvAAoJECChztQA3mh0jDUQAMCwc/TP/pymsLcIhdVhS89c ezrA4HiSSBshZPqiJZUQAMkotlj7+xRiRe0GCAf8WNoSYi/R1uFf7JEX/CAemdk7 BL090fGbt0E8HFW7LD7+66ZC+zno9g0WKTiR+CKBVjG/ZpznrCizXQlxErgEAE+9 Fx3MFn6QuhKU8Or8IyTfQElAiYkL6DLZWpaQMuQNftI+6oZz9HmCI5EyOnartPq9 mD9lZAbXrTBSdVyu66OLdk8oEsn29w/xGxlISY3ZG/hMpl8TaKuUUZt0Mf3IjkNe NKed0joEgtZeklrhKE74sm21wd4+4w2HUSpfsKmykx8GIP6jpAUxxdHEX95XcmFS iD/UUifUeg/u/gg2mbTaaKScd+CnZOBFQqX3TJWk4q1zOsd2+KoU4NxAG1K8J6bg FncCl6fHdupozmV4wGxtdk0n0M+l9Ke9sroK3aVCX1YvFn1BdzX3ygUryZtLCTV/ poS4kbLOCwT4F/Ndn0j11RxAwmztu0Fkf5Ob91pZVAAbGsEN3l/EeEZTYpFbrqk/ GwdDTeqAH5VxUnmRfNvWUmWau3dy4uj9pOI8O5NEdKqDcAgwTmwQkYgmoWJLfFtd kLi2Xoc8DCSNMBGoMpAKYgXBza2Kt4U/bJUnGuRKjO+Dc7/PHR2SUo0q+Wumq6WF PJ85bVBhfKJelI0auKxl =icVe -END PGP SIGNATURE- -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: [Test-Announce] Fedora 21 Final status is Go, release on December 9, 2014
\o/ Thanks everyone! digimer On 04/12/14 01:21 PM, Jaroslav Reznik wrote: At the Fedora 21 Final Go/No-Go Meeting that just occurred, it was agreed to Go with the Fedora 21 Final by Fedora QA, Release Engineering and Development. Fedora 21 will be publicly available on Tuesday, December 09, 2014. Meeting details can be seen here: Minutes: http://bit.ly/1yjG357 Log: http://bit.ly/1yjG7SE Thanks everyone, this is a huge achievement after almost one year long development cycle and many changes not only under the hood how we produce Fedora! And now, let's back to work on to the next Next Fedora release ;-). Jaroslav ___ test-announce mailing list test-annou...@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/test-announce -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Who is the genius who is trying to remove yum?
On 11/10/14 01:55 PM, poma wrote: Fedora-Live-Xfce-x86_64-rawhide-20141011 https://kojipkgs.fedoraproject.org/work/tasks/1492/7831492/root.log .. Error creating Live CD : Failed to build transaction : dnf-yum conflicts with yum-3.4.3-155.fc22.noarch $ file dnf-yum-0.6.2-1.fc22.noarch/usr/bin/yum dnf-yum-0.6.2-1.fc22.noarch/usr/bin/yum: broken symbolic link to `dnf' poma It's not been a secret, and has been in the works for a while. http://fedoraproject.org/wiki/Changes/ReplaceYumWithDNF -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: New Group Calls For Boycotting Systemd
On 12/09/14 01:08 PM, Denys Vlasenko wrote: On 09/07/2014 12:24 AM, Sérgio Basto wrote: However there is a wider problem here. The "systemd of Fedora 14/15" is not the systemd of today. I agree 100% We need to decide if just because you manage to get an important core package into Fedora 4 years ago, that means you can forever more push any old stuff you want into Fedora, without going back and consulting with the community and FESCo. "On Qui, 2014-09-04 at 22:12 +0200, Ralf Corsepius wrote: Therefore I'd find it useful for systemd take a break and period of consolidation to sort out the bugs and impact of systemd on Fedora. " yeah this and Chris Adams wrote almost synthesized what I think. what is the systemd goals ? plans ? roadmap ? seems that systemd want to be a operating system. You are wasting your time. Lennart and his bunch proved to be impervious to any pleas to stop mad feature creep. They WANT to extend systemd in every imaginable way to scratch their favorite itch of the week. It's not a coincidence or an oversight. That's what they like doing. Possibly, that's the MAIN motivation behind systemd development now - to take over whatever part of the system they want, and enjoy it. And Fedora userbase is their hostages now. Fedora maintainers seem to be okay with it. Fine. In Linux, when all else fails, we can always move to a different distro. Oh please, can we cut the drama down a notch? -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: New Group Calls For Boycotting Systemd
On 04/09/14 11:50 AM, Ralf Corsepius wrote: On 09/04/2014 05:37 PM, Kevin Fenzi wrote: Do we really need another systemd thread? Yes, because Fedora has failed to discuss system and systemd development in advance before they had been deployed. Instead Fedora was confronted with completed facts. Ralf All Fedora development happens out in the open, for everyone to see. This reminds me of the "Beefy Miracle" fiasco... Everyone complained after it happened, but few said or did anything before then. Systemd was not snuck in. The people who put in the hours making Fedora knew it was coming. Those who objected might do well to put more time into helping with (or at least staying informed on) Fedora development. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: New Group Calls For Boycotting Systemd
On 04/09/14 11:11 AM, Sérgio Basto wrote: Hi, [1] since Fedora have some responsibility, unfortunately I think the group have some valid reasons , systemd should be the replacement of sysvinit , a built in DHCP !? why ? and others integration like crontab should be modular, for someone else could use his own crontab . OTOH , the support of systemd is not good, we got bug opened and they are ignored as nothing happens, as for example bug https://bugzilla.redhat.com/show_bug.cgi?id=1088619 [1] http://www.phoronix.com/scan.php?page=news_item&px=MTc3OTM best regards, This is the gift of drama that never stops giving. Trying to undo systemd at this point is next to impossible. All major distributions are using it or will be moving to it, so far as I know. Switching away at this point would be very disruptive and hurt Linux in general far more than it would help. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: SSD disk over Fedora 20... ?
On 13/03/14 08:10 PM, Álvaro Castillo wrote: Dear devel mailing list, I would like to know more information about SSD in Fedora. How I can manage spaces, partition's disk and more? I read about SSD with TRIM support improvements more lyfe cycle durability between other things. I read too that a bad partition scheme would be dangerously decreases a life time of SSD considerably. I am bit worried. More people that buys a laptop with SSD, or buys SSD to install Fedora on It. Grretings! I've been using an SSD in my laptop since Fedora 16 without issue. I used luks encryption, so I can't benefit from TRIM, and still no real issues. Keep good backups (same regardless of your disk type) and you're fine. As for partitioning and what-not, there is no difference. It's just another block device. The only real recommendation is to not use a swap partition. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Ignore - Re: Good Fedora-compatible multi-monitor video card recommendation
Sorry, I meant to post this to the general user's list. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Good Fedora-compatible multi-monitor video card recommendation
Hi all, What would be a good (as in, relatively painless) video card for driving as many 1080p monitors as possible? I'm not concerned about 3D performance at all... It will be to display terminals/rarely-changing web pages only. I know Matrox sort of specializes in multi-monitor setups, but I can't say I've heard them recommended much. Fedora 20, fwiw. Thanks! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: pacemaker in Fedora and RHEL
On 11/12/13 06:36, Christopher Meng wrote: > Hi all, > > I wonder if there are some reasonable explanations of package > "pacemaker" in the repo. > > I checked the package and the result returned is: > > Fedora: pacemaker-1.1.9-3.fc20 in rawhide. > > RHEL: pacemaker-1.1.10-14.el6. > > The latest version is 1.1.11RC1(1.1.10 Final stable). > > Why is the package in Fedora behind the one in RHEL in spite of the > maintainer of these two are the same people? > > Thanks. > -- > > Yours sincerely, > Christopher Meng Hi Christopher, I can't speak authoritatively, but I am willing to bet it's a couple of things. There was a huge push to get 1.1.10 ready for rhel 6.5, there has been a lot of work on 1.1.11 and Andrew's wife just gave birth, so he's on vacation for a bit. I would guess that pacemaker on fedora just didn't get to the front of the burner yet. digimer -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Using USB 3 plugs crashes Gnome
On 25/09/13 12:07, Xose Vazquez Perez wrote: > On 09/25/2013 12:14 AM, Digimer wrote: > >> I can't imagine why USB 3 would effect this, but there you go. Any >> advice on debugging? > > Déjà-vu: > http://lists.fedoraproject.org/pipermail/devel/2013-August/188273.html > I honestly forgot about having asked before. Sorry for the noise. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Re: Using USB 3 plugs crashes Gnome
87 12 45 00 54 50 07 01 01 D5 00 00 00 00 00 00 00 00 Handle 0x0046, DMI type 140, 15 bytes OEM-specific Type Header and Data: 8C 0F 46 00 4C 45 4E 4F 56 4F 0B 07 01 01 02 Strings: G4HT31WW 04/27/2012 Handle 0x0047, DMI type 140, 43 bytes OEM-specific Type Header and Data: 8C 2B 47 00 4C 45 4E 4F 56 4F 0B 08 01 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Handle 0xFEFF, DMI type 127, 4 bytes End Of Table digimer On 24/09/13 15:29, Kristofer Rye wrote: > Hello, > > I use USB 3.0 every day on my HP Pavilion DV6Z-QE with everything. > There are some odd glitches at times but usually it's my fault as I do > weird stuff to my kernel sometimes (really hard to explain). > > If the mouse is moving, that says to me that the mouse cursor is > displayed by the hardware (no surprise there), but that Xorg is also > in some sort of functional state. That leaves GNOME as the main > suspect. > > I've had problems before with a corrupt SD card -- one which I had to > reformat using my camera -- which caused GNOME to hang and stay hung > until I removed it from the computer. To me it seems like it's > something similar to that. > > That also makes me wonder what kind of USB controllers your laptop > has, and if they're properly supported (i.e. if someone has this issue > also or something similar). > > // Kristofer "four04" Rye > > > On Tue, Sep 24, 2013 at 6:14 PM, Digimer wrote: >> I know this doesn't make sense on the surface, but bear with me for a >> minute. >> >> I've got a Thinkpad W530 laptop. The first OS was Fedora 17 and it was >> perfectly stable. By coincidence or not, when I installed Fedora 18, it >> started crashing sporadically. This remained to this day on Fedora 19. >> >> I've finally narrowed it down to an unlikely source; USB 3. If I don't >> use the USB 3 ports, the system goes weeks without crashing. However, >> when I try to use the USB 3 ports, within a short time Gnome locks up. >> >> The mouse usually moves still, but I can't interact with anything on the >> screen. I can't alt + tab, alt + tilda, corner bump or anything else. I >> can ctrl + alt + fX to get to a terminal and kill the GUI. In a couple >> of occasions, if I leave it long enough, the windows would start >> responding to a limited amount, but they would all be jammed up to the >> top-left corner, have no windows and can't be moved or given focus (so I >> can only interact with the windows I can see part of). >> >> I can't imagine why USB 3 would effect this, but there you go. Any >> advice on debugging? >> >> Madi >> >> -- >> Digimer >> Papers and Projects: https://alteeve.ca/w/ >> What if the cure for cancer is trapped in the mind of a person without >> access to education? >> -- >> devel mailing list >> devel@lists.fedoraproject.org >> https://admin.fedoraproject.org/mailman/listinfo/devel >> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Using USB 3 plugs crashes Gnome
I know this doesn't make sense on the surface, but bear with me for a minute. I've got a Thinkpad W530 laptop. The first OS was Fedora 17 and it was perfectly stable. By coincidence or not, when I installed Fedora 18, it started crashing sporadically. This remained to this day on Fedora 19. I've finally narrowed it down to an unlikely source; USB 3. If I don't use the USB 3 ports, the system goes weeks without crashing. However, when I try to use the USB 3 ports, within a short time Gnome locks up. The mouse usually moves still, but I can't interact with anything on the screen. I can't alt + tab, alt + tilda, corner bump or anything else. I can ctrl + alt + fX to get to a terminal and kill the GUI. In a couple of occasions, if I leave it long enough, the windows would start responding to a limited amount, but they would all be jammed up to the top-left corner, have no windows and can't be moved or given focus (so I can only interact with the windows I can see part of). I can't imagine why USB 3 would effect this, but there you go. Any advice on debugging? Madi -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
USB-based Gnome 3 lockups
Hi all, When I got this laptop (Thinkpad W530), I ran F17. It was always perfectly stable. When I installed F18, it started to (seemingly) randomly lock up Gnome 3. I could never see much in syslog of use. I knew it was just gnome because I could still ctrl+alt+fX to other terminals. If I restarted dbus, gnome restarted and most of the time I could log back in. I thought it might have been my bluetooth mouse, but it still crashed when bt/wan were disabled (airport mode mechanical switch flipped). The random lock ups continued when I upgraded to Fedora 19 and I never was able to sort out why. Finally I started noticing a pattern; When I used the USB3 ports, it would crash within a few hours. I recently stopped using the USB3 ports and it's not crashed since. The USB2 ports are just fine. So how can I debug this further? Cheers digimer PS - Machine details; = lemass:/home/digimer# cat /etc/redhat-release Fedora release 19 (Schrödinger’s Cat) = = lemass:/home/digimer# uname -a Linux lemass.alteeve.ca 3.10.7-200.fc19.x86_64 #1 SMP Thu Aug 15 23:19:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux = = lemass:/home/digimer# lspci 00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) 00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04) 00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 (rev c4) 00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 2 (rev c4) 00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM77 Express Chipset LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller (rev 04) 02:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 08) 03:00.0 Network controller: Intel Corporation Centrino Ultimate-N 6300 (rev 3e) = = lemass:/home/digimer# lsusb Bus 002 Device 005: ID 18d1:4ee1 Google Inc. Nexus 4 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 04f2:b2ea Chicony Electronics Co., Ltd Integrated Camera [ThinkPad] Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 006: ID 05ac:1402 Apple, Inc. Ethernet Adapter [A1277] Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub = = lemass:/home/digimer# dmidecode # dmidecode 2.12 SMBIOS 2.7 present. 73 structures occupying 2985 bytes. Table at 0xDAE9D000. Handle 0x, DMI type 134, 16 bytes OEM-specific Type Header and Data: 86 10 00 00 00 53 54 4D 20 01 01 00 00 02 01 02 Strings: TPM INFO System Reserved Handle 0x0001, DMI type 4, 42 bytes Processor Information Socket Designation: CPU Socket - U3E1 Type: Central Processor Family: Core i7 Manufacturer: Intel(R) Corporation ID: A9 06 03 00 FF FB EB BF Signature: Type 0, Family 6, Model 58, Stepping 9 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception) CX8 (CMPXCHG8 instruction supported) APIC (On-chip APIC hardware supported) SEP (Fast system call) MTRR (Memory type range registers) PGE (Page global enable) MCA (Machine check architecture) CMOV (Conditional move instruction supported) PAT (Page attribute table) PSE-36 (36-bit page size exte
Re: Tools to mount and promote Fedora on cybers.
On 14/07/13 09:39, Álvaro Castillo wrote: Hello buddies, I want get more information about Fedora and tools to help on migration of cybers Windows into Fedora. But I only found old software such as Cyborg (2003), or Fedora KIOS Spin unmaintained (I don't know why was stopped maintain it). Can help me, please? Thank you so much! -- Álvaro Castillo Hi Álvaro, I think your question is not very clear. What does "cybers Windows" mean? I can't find any reference to a "Fedora KIOS Spin" (unless you mean "kiosk" spin). Promotion of any project, including Fedora, needs to be done carefully. If you push people away from tools they are happy with to something new, they may reject it out of hand. All then that is accomplished is a group of people who speak badly when they hear "Fedora". Promoting a project means that you have to share the good and the bad. People have to have a realistic view of what the technology can do and where people might run into trouble. You need to help people understand what they gain from a new project and how difficult they should expect the learning curve to be. There is a good chance that the benefits do not (yet) outweigh the learning curve. In such a case, they are better to stay on the tools they know for now. Hope this helps. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: well!
On 03/12/2013 12:41 AM, Charles Zeitler wrote: i don't like giving up control over my machine (partitioning), so i won't be upgrading to Fedora 18. i'll watch the web site for a return to sanity. charles zeitler Setting aside the drama, you can manually partition F18. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Frequent dbus(?) crashes with Samsung 840 Pro SSD
On 02/20/2013 10:37 PM, Chris Murphy wrote: On Feb 20, 2013, at 3:45 PM, Digimer wrote: Currently, as the OS disk, it mounts on boot with the default values set by Fedora; ==] /etc/fstab [ /dev/mapper/luks-bd252fe0-a16f-4a14-ad4e-b99a0d4c0716 / ext4 defaults,x-systemd.device-timeout=0 1 1 UUID=eca11946-68d8-444c-90f2-ad65455caf6d /boot ext4 defaults1 2 Thanks for the tips on secure erase. I'll use that in the future. I would do it now because as far as that SSD is concerned, every single block is in use, and then also you should be using the discard mount option, and also not using dmcrypt. The 840 Pro supports FDE, that's what you should use. But for reference dmcrypt supports TRIM passthrough, just not by default. https://wiki.archlinux.org/index.php/Dm-crypt_with_LUKS#Discard.2FTRIM_support_for_solid_state_disks_.28SSD.29 Chris Murphy I wanted to use the onboard FDE but didn't find docs on how to do it. As for discard, can I just add this after defaults? I'll read that link now. Thank you, again. :) -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Frequent dbus(?) crashes with Samsung 840 Pro SSD
On 02/20/2013 05:01 PM, Chris Murphy wrote: On Feb 20, 2013, at 12:42 PM, Digimer wrote: b) I 0'ed out the entire drive (over USB from F18 on my older SSD) before reinstalling F18 on the Samsung. FYI this isn't a good idea with SSDs. Use ATA Secure Erase instead with hdparm, or the included Windows utility can do this - it almost always requires a direct SATA connection because most of the USB to SATA bridge chipsets are crap and don't pass through these ATA commands. What mount options are you using? In particular do you have discard enabled? Chris Murphy Currently, as the OS disk, it mounts on boot with the default values set by Fedora; ==] /etc/fstab [ /dev/mapper/luks-bd252fe0-a16f-4a14-ad4e-b99a0d4c0716 / ext4defaults,x-systemd.device-timeout=0 1 1 UUID=eca11946-68d8-444c-90f2-ad65455caf6d /boot ext4 defaults1 2 Thanks for the tips on secure erase. I'll use that in the future. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Frequent dbus(?) crashes with Samsung 840 Pro SSD
On 02/19/2013 01:49 AM, Chris Murphy wrote: On Feb 18, 2013, at 10:13 PM, Digimer wrote: what's "offline data collection"? http://smartmontools.sourceforge.net/man/smartctl.8.html Read in particular the paragraph containing the word unfortunate. 0x0009 2 19 Transition from drive PhyRdy to drive PhyNRdy Have you had about 19 of these freezes? You said you've had the problem with lock screen which implies inactivity. I wonder if the system is sleeping/hibernating and the drive isn't waking up in time and dbus or gdm or gnome-shell are getting irritated. I'd ssh in remotely, run journalctl --follow and see what's displayed the next time you have a freeze. Chris Murphy An update; I reinstalled on the Samsung 840 Pro not long before I ran/reported the smart test earlier in the thread. I've been running now for a couple days with F18 and have not had another crash. The main differences from last time is that; a) I had installed windows on the drive and ran the Samsung SSD utils, though I don't think it changed anything unless it did so behind the scenes. b) I 0'ed out the entire drive (over USB from F18 on my older SSD) before reinstalling F18 on the Samsung. Not sure how or if these could have changed anything. However, this is the longest stretch I've gone without a crash since getting this Samsung drive. -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Frequent dbus(?) crashes with Samsung 840 Pro SSD
On 02/19/2013 01:49 AM, Chris Murphy wrote: On Feb 18, 2013, at 10:13 PM, Digimer wrote: what's "offline data collection"? http://smartmontools.sourceforge.net/man/smartctl.8.html Read in particular the paragraph containing the word unfortunate. 0x0009 2 19 Transition from drive PhyRdy to drive PhyNRdy Have you had about 19 of these freezes? You said you've had the problem with lock screen which implies inactivity. I wonder if the system is sleeping/hibernating and the drive isn't waking up in time and dbus or gdm or gnome-shell are getting irritated. I'd ssh in remotely, run journalctl --follow and see what's displayed the next time you have a freeze. Thanks for the link and key word! I've started to lose count, but I think it's been 12 or 13 lock ups. However, one of those failed to recover or instantly re-failed after restarting dbus. At least, this is how many I noticed. Does the number 19 come from: = 0x0009 2 19 Transition from drive PhyRdy to drive PhyNRdy 0x000a 2 19 Device-to-host register FISes sent due to a COMRESET = If so, is this a sign of a bad drive? If so, could gnome/dbus/whatever handle the failure better? I just reinstalled on the Samsung last night. As soon as I get a crash, I will run 'journalctl --follow' and 'dmesg' and report whatever is shown. Thanks again! -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Frequent dbus(?) crashes with Samsung 840 Pro SSD
On 02/18/2013 11:24 PM, Chris Murphy wrote: On Feb 18, 2013, at 8:44 PM, Digimer wrote: I went so far as to install Windows 7 on the 840 Pro, downloaded and ran Samsung's own tool to verify it was at the latest firmware and was healthy. The smartctl is below. update-smart-drivedb smartctl -t long /dev/sda smartctl -x /dev/sda Report that smartctl along with dmesg. [root@localhost digimer]# smartctl -a /dev/sda Total time to complete Offline data collection:(53956) seconds. Weird. 15 hours for an SSD offline data collection? On my 830 this figure is 1020 seconds, same as the extended self-test. Chris Murphy The output of the smartctl commands are below. Pardon the ignorance, but what's "offline data collection"? digimer ps - thanks for the help. :) localhost:~# smartctl -x /dev/sda smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.7.8-202.fc18.x86_64] (local build) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Samsung based SSDs Device Model: Samsung SSD 840 PRO Series Serial Number:S12RNEACC95023M LU WWN Device Id: 5 002538 55015d61e Firmware Version: DXM04B0Q User Capacity:256,060,514,304 bytes [256 GB] Sector Size: 512 bytes logical/physical Rotation Rate:Solid State Device Device is:In smartctl database [for details use: -P show] ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is:Tue Feb 19 00:11:44 2013 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled AAM feature is: Unavailable APM feature is: Unavailable Rd look-ahead is: Enabled Write cache is: Enabled ATA Security is: Disabled, frozen [SEC2] === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection:(53956) seconds. Offline data collection capabilities:(0x53) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time:( 2) minutes. Extended self-test routine recommended polling time:( 20) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 1 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAGSVALUE WORST THRESH FAIL RAW_VALUE 5 Reallocated_Sector_Ct PO--CK 100 100 010-0 9 Power_On_Hours -O--CK 099 099 000-89 12 Power_Cycle_Count -O--CK 099 099 000-53 177 Wear_Leveling_Count PO--C- 099 099 000-3 179 Used_Rsvd_Blk_Cnt_Tot PO--C- 100 100 010-0 181 Program_Fail_Cnt_Total -O--CK 100 100 010-0 182 Erase_Fail_Count_Total -O--CK 100 100 010-0 183 Runtime_Bad_Block PO--C- 100 100 010-0 187 Uncorrectable_Error_Cnt -O--CK 100 100 000-0 190 Airflow_Temperature_Cel -O--CK 062 059 000-38 195 ECC_Rate-O-RC- 200 200 000-0 199 CRC_Error_Count -OSRCK 100 100 000-0 235 POR_Recovery_Count -O--C- 099 099 000-6 241 Total_LBAs_Written -O--CK 099 099 000-1153722313 ||_ K auto-keep |
Re: Frequent dbus(?) crashes with Samsung 840 Pro SSD
On 02/18/2013 09:50 PM, Chris Murphy wrote:
On Feb 18, 2013, at 7:20 PM, Digimer wrote:
Two days ago, I reinstalled F18 on my Corsair drive. I had the Samsung
connected as a USB drive to restore my files and after a few hours, the system
locked up again ('tail -n 100' below). I pulled the Samsung out of the laptop
and booted with just the Corsair and it's been rock solid since.
I assume you've looked at smartctl -a on this drive, and that's why you don't
think it's just a bad SSD that needs to be swapped out for replacement? I'm
using an 830, which is related to the 840, but admittedly different in some
important ways; but I'm not experiencing problems like you're describing.
And what have you found in dmesg for the time this is happening? Or 'journalctl
--follow' using ssh?
Each time it crashed, it *looked* like a dbus hang-up.
Why do you say this? There's nothing in your syslog that implicates dbus, or
anything else for that matter. I also think that's the wrong diagnostic tool
for this, actually.
Chris Murphy
I went so far as to install Windows 7 on the 840 Pro, downloaded and ran
Samsung's own tool to verify it was at the latest firmware and was
healthy. The smartctl is below.
Next time it crashes, I will check dmesg and run that command.
If it's not dbus, which I readily admitted it might not be :), I would
love to hear suggestions. The reason I thought it was related to dbus
was that I kept seeing so many dbus messages at the time of each crash.
Also, restarting the dbus.service would (all but one time) recover Gnome
and restore the system to working. Of course, that could be normal and
unrelated.
Again, I am open to advice or suggestions.
==
[root@localhost digimer]# smartctl -a /dev/sda
smartctl 6.0 2012-10-10 r3643 [x86_64-linux-3.6.10-4.fc18.x86_64] (local
build)
Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model: Samsung SSD 840 PRO Series
Serial Number:S12RNEACC95023M
LU WWN Device Id: 5 002538 55015d61e
Firmware Version: DXM04B0Q
User Capacity:256,060,514,304 bytes [256 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate:Solid State Device
Device is:Not in smartctl database [for details use: -P showall]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 4c
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:Mon Feb 18 22:43:47 2013 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 0) The previous self-test routine
completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection:(53956) seconds.
Offline data collection
capabilities:(0x53) SMART execute Offline immediate.
Auto Offline data collection on/off
support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities:(0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability:(0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time:( 2) minutes.
Extended self-test routine
recommended polling time:( 20) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE
UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 100 100 010Pre-fail
Always - 0
9 Power_On_Hours 0x0032 099 099 000Old_age
Always -
Frequent dbus(?) crashes with Samsung 840 Pro SSD
esktop.PackageKit' (using servicehelper) Feb 16 12:40:51 lemass dbus[733]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Feb 16 12:40:51 lemass dbus-daemon[733]: dbus[733]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 16 12:40:51 lemass dbus[733]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 16 13:35:24 lemass dbus-daemon[733]: dbus[733]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Feb 16 13:35:24 lemass dbus[733]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Feb 16 13:35:24 lemass dbus-daemon[733]: dbus[733]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 16 13:35:24 lemass dbus[733]: [system] Successfully activated service 'org.freedesktop.PackageKit' Feb 16 14:05:58 lemass systemd[1]: Starting Getty on tty2... Feb 16 14:05:58 lemass systemd[1]: Started Getty on tty2. Feb 16 14:06:00 lemass dbus-daemon[733]: dbus[733]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Feb 16 14:06:00 lemass dbus[733]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) Feb 16 14:06:00 lemass dbus-daemon[733]: dbus[733]: [system] Successfully activated service 'net.reactivated.Fprint' Feb 16 14:06:00 lemass dbus[733]: [system] Successfully activated service 'net.reactivated.Fprint' Feb 16 14:06:00 lemass dbus-daemon[733]: Launching FprintObject Feb 16 14:06:00 lemass dbus-daemon[733]: ** Message: D-Bus service launched with name: net.reactivated.Fprint Feb 16 14:06:00 lemass dbus-daemon[733]: ** Message: entering main loop Feb 16 14:06:12 lemass systemd-logind[727]: New session 10 of user root. === As it stands right now, I'm sitting on a fairly expensive paper weight. I can't use it, obviously, but I am willing to test/torture it for you guys and gals. I'd love to find out why it's crashing fedora 18. lemass:/home/digimer# uname -a Linux lemass.alteeve.ca 3.7.7-201.fc18.x86_64 #1 SMP Tue Feb 12 22:35:01 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux -- Digimer Papers and Projects: https://alteeve.ca/w/ What if the cure for cancer is trapped in the mind of a person without access to education? -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Problem pairing mouse with F17
On 06/03/2012 11:07 PM, "Jóhann B. Guðmundsson" wrote: On 06/04/2012 02:30 AM, Digimer wrote: I can confirm that selinux is disabled (as sestatus shows 'disabled'). Any idea what I should next? File a bug report against Gnome-Bluetooth you can try running this "hciconfig hci0 sspmode 0" from the command line as root which was the only way I manage to get my Samsung Galaxy S-II running Android ICS 4.0.3 to pair with my laptop which is running F17 with the latest 3.5 rc kernel. If the workaround works for you and you need to keep the change across reboots you can create a simple type oneshot unit that does that for you. Like... # vim /etc/systemd/system/bluetooth-legacy-pairing.service which contains [Unit] Description=Persistant Bluetooth Legacy Pairing Hack [Service] Type=oneshot ExecStart=/sbin/hciconfig hci0 sspmode 0 RemainAfterExit=yes [Install] WantedBy=graphical.target JBG Thanks for the reply, Jóhann, but it didn't help. When I ran 'hciconfig hci0 sspmode 0', there was nothing returned. I tried to pair again twice with no luck. Syslog showed: === Jun 4 08:37:19 lework udevd[525]: specified group 'plugdev' unknown Jun 4 08:38:04 lework bluetoothd[770]: bluetoothd[770]: Discovery session 0x7f0ab7111eb0 with :1.168 activated Jun 4 08:38:04 lework bluetoothd[770]: Discovery session 0x7f0ab7111eb0 with :1.168 activated Jun 4 08:38:08 lework bluetoothd[770]: bluetoothd[770]: Stopping discovery Jun 4 08:38:08 lework bluetoothd[770]: Stopping discovery Jun 4 08:38:09 lework udevd[525]: specified group 'plugdev' unknown Jun 4 08:38:09 lework dbus-daemon[837]: dbus[837]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.168" (uid=1000 pid=14431 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=770 comm="/usr/sbin/bluetoothd -n ") Jun 4 08:38:09 lework dbus[837]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.168" (uid=1000 pid=14431 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=770 comm="/usr/sbin/bluetoothd -n ") === Jun 4 08:38:27 lework bluetoothd[770]: bluetoothd[770]: Discovery session 0x7f0ab7124180 with :1.168 activated Jun 4 08:38:27 lework bluetoothd[770]: Discovery session 0x7f0ab7124180 with :1.168 activated Jun 4 08:38:30 lework bluetoothd[770]: bluetoothd[770]: Stopping discovery Jun 4 08:38:30 lework bluetoothd[770]: Stopping discovery Jun 4 08:38:31 lework udevd[525]: specified group 'plugdev' unknown Jun 4 08:38:32 lework dbus-daemon[837]: dbus[837]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.168" (uid=1000 pid=14431 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=770 comm="/usr/sbin/bluetoothd -n ") Jun 4 08:38:32 lework dbus[837]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.168" (uid=1000 pid=14431 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=770 comm="/usr/sbin/bluetoothd -n ") === I created a rhbz here: https://bugzilla.redhat.com/show_bug.cgi?id=828199 -- Digimer Papers and Projects: https://alteeve.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Problem pairing mouse with F17
Hi all, I've installed F17 x86_64 on my Thinkpad T400s and have not been able to pair my razer orochi bluetooth mouse. When I put my F16 x86_64 HDD back in and boot, the mouse works fine over bluetooth. When I put the mouse into pairing mode, the bluetooth applet sees the mouse. However, when I click on it and try to pair, it simply says "failed" and I have the option to try again. This is what is shown in syslog; Jun 3 22:20:27 lework bluetoothd[770]: bluetoothd[770]: Discovery session 0x7f0ab7114aa0 with :1.142 activated Jun 3 22:20:27 lework bluetoothd[770]: Discovery session 0x7f0ab7114aa0 with :1.142 activated Jun 3 22:20:31 lework bluetoothd[770]: bluetoothd[770]: Stopping discovery Jun 3 22:20:31 lework bluetoothd[770]: Stopping discovery Jun 3 22:20:32 lework udevd[525]: specified group 'plugdev' unknown Jun 3 22:20:32 lework dbus-daemon[837]: dbus[837]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.142" (uid=1000 pid=13040 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=770 comm="/usr/sbin/bluetoothd -n ") Jun 3 22:20:32 lework dbus[837]: [system] Rejected send message, 3 matched rules; type="method_return", sender=":1.142" (uid=1000 pid=13040 comm="bluetooth-wizard ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.0" (uid=0 pid=770 comm="/usr/sbin/bluetoothd -n ") Jun 3 22:21:56 lework udevd[525]: specified group 'plugdev' unknown Jun 3 22:21:56 lework bluetoothd[770]: bluetoothd[770]: Refusing input device connect: No such file or directory (2) Jun 3 22:21:56 lework bluetoothd[770]: bluetoothd[770]: Refusing connection from 00:02:76:20:8B:21: setup in progress Jun 3 22:21:56 lework bluetoothd[770]: Refusing input device connect: No such file or directory (2) Jun 3 22:21:56 lework bluetoothd[770]: Refusing connection from 00:02:76:20:8B:21: setup in progress Jun 3 22:22:01 lework udevd[525]: specified group 'plugdev' unknown Jun 3 22:22:01 lework bluetoothd[770]: bluetoothd[770]: Discovery session 0x7f0ab711d790 with :1.142 activated Jun 3 22:22:01 lework bluetoothd[770]: Discovery session 0x7f0ab711d790 with :1.142 activated I can confirm that selinux is disabled (as sestatus shows 'disabled'). Any idea what I should next? Thanks. -- Digimer Papers and Projects: https://alteeve.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: R: Re: Primary Architectures: Another Proposal (RFC)
Can someone remove this user from the list until they fix their email program? On 04/10/2012 01:01 PM, pinto.e...@gmail.com wrote: > > Messaggio originale > Da: Horst H. von Brand > Inviato: 10/04/2012, 16:31 > A: Development discussions related to Fedora; Kevin Kofler > Oggetto: Re: Primary Architectures: Another Proposal (RFC) > > > Kevin Kofler wrote: >> Josh Boyer wrote: >>> "It builds" doesn't necessarily mean it works. In the rawhide case, >>> you might very well submit something that builds but is totally >>> broken. By the time you download the official build and test it >>> locally, it can already be in the day's compose and now you've just >>> inflicted a broken build on all the users. And no, "rawhide eats >>> babies" is not a valid excuse IMHO. >> >> As far as Rawhide goes, IMHO, if it builds, it's good enough for Rawhide. > > That is just irresponsible. BTW, there are too few rawhide consumers as > things stand; this would make rawhide be russian roulette, but with 5 > bullets instead of 1. > >> "If it compiles, ship it!" â Linus Torvalds > > Riiight... one tongue-in-cheek comment by the well-known punster Linus > leads to distribution wide policy. -- Digimer Papers and Projects: https://alteeve.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Hello
On 04/02/2012 10:59 AM, Dmitriy Nikolaev wrote: > Uups... I'm sorry. OK. I got it. THank you once again for your help > and explanations. > > With best regards. Happy to help. :) -- Digimer Papers and Projects: https://alteeve.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Hello
On 04/02/2012 10:45 AM, Dmitriy Nikolaev wrote: > Thank you for your fast answer. > That's interesting. But, could you, please, tell me also, if in the > future, not now, I would like to participate in kernel developing, > then is it possible to join those guys? Please reply to the mailing list. This kind of discussion is helpful for others to see and, later, find in the archives. It's entirely possible, but it will take time. First off; The kernel development is split into many, many parts. Second, the kernel development is not under the direction of any distribution, though distributions contribute. If you want to help, I suggest you start first with a smaller package. Get some experience and develop a name for yourself in the community. Over time, as you grow in experience, you will get to know people and be able to contribute to larger projects. Remember that opensource is a meritocracy; You need to have a body of work to point to when asking to join core projects like kernel development. Cheers. :) -- Digimer Papers and Projects: https://alteeve.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Hello
On 04/02/2012 10:34 AM, Dmitriy Nikolaev wrote: > Hello , guys! > > I would like to participate in developing Fedora releases(coding, > mostly in C/C++). Could you tell me, where I can find a source code > and other relative things, for instance, headers and libraries > descriptions? > > Thank you beforehand for your answers. > > With best regards. There is no central project, so to speak. It's best to pick a package you are interested in, look up who the maintainer is and contacting that person to see if they need/want help. Once you find a package, start helping with whatever they need. Pretty simple, all in all. :) -- Digimer Papers and Projects: https://alteeve.com -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: service version disclosure
On 01/07/2012 01:59 AM, Reindl Harald wrote: > > > Am 07.01.2012 07:52, schrieb Digimer: >> On 01/07/2012 01:02 AM, Reindl Harald wrote: >>> Am 07.01.2012 06:35, schrieb Digimer: >>>>> if you have a big customer which hires a 3rd party auditor >>>>> you are NOT in the poisiton to give such arguments or >>>>> you can give them but you can not change ANYTHING in >>>>> the fact that finally "fix it or shutdown the service" >>>>> is what you have to do >>>> >>>> If you have a "security expert" who can't grasp the concept of >>>> back-ported bug fixes, and is unwilling to test for specific >>>> vulnerabilities' existence, it's time to get a new expert. >>> >>> you are missing the point A BIG CUSTOMER has a security-expert >> >> No, I'm not missing the point. You're asking for a wholesale change in >> how a program works so that you can have an easier time with an >> uneducated customer. Your job, as a consultant or IT support is not make >> sure that your solution is safe. Making you customer feel comfortable >> without actually given them security is a bad idea. > > i know about the pros and cons for obscurity > > but i also know that from "SSH-2.0-OpenSSH_5.8" only "SSH-2.0" > is relevant for clients and having backports in mind this must > be the truth because if the whole version would matter all > LTS distributions would be broken by design This doesn't change the fundamental point; You are asking for a significant change in behaviour to a program that who-knows-how-many apps use, for no real reason other than to make a client feel better. -- Digimer E-Mail: digi...@alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "omg my singularity battery is dead again. stupid hawking radiation." - epitron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: service version disclosure
On 01/07/2012 01:02 AM, Reindl Harald wrote: > Am 07.01.2012 06:35, schrieb Digimer: >>> if you have a big customer which hires a 3rd party auditor >>> you are NOT in the poisiton to give such arguments or >>> you can give them but you can not change ANYTHING in >>> the fact that finally "fix it or shutdown the service" >>> is what you have to do >> >> If you have a "security expert" who can't grasp the concept of >> back-ported bug fixes, and is unwilling to test for specific >> vulnerabilities' existence, it's time to get a new expert. > > you are missing the point A BIG CUSTOMER has a security-expert No, I'm not missing the point. You're asking for a wholesale change in how a program works so that you can have an easier time with an uneducated customer. Your job, as a consultant or IT support is not make sure that your solution is safe. Making you customer feel comfortable without actually given them security is a bad idea. -- Digimer E-Mail: digi...@alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "omg my singularity battery is dead again. stupid hawking radiation." - epitron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: service version disclosure
On 01/07/2012 12:31 AM, Reindl Harald wrote: > > Am 07.01.2012 06:13, schrieb Stephen John Smoogen: >> On 6 January 2012 21:46, Kevin Kofler wrote: >>> Reindl Harald wrote: >>>> would it not be a good idea to NOT disclosure service versions? >>>> https://bugzilla.redhat.com/show_bug.cgi?id=718133 >>>> >>>> you will more and more have the "problem" of 3rd party >>>> security scans to your servers and currently in the case >>>> of openssh the only solution is to tkae the F16-src-rpm >>>> and rebuild it for your F15 machines >>> >>> If the scan is looking at the version to determine vulnerability, it is >>> completely broken, useless and unsupportable, because fixes can be >>> backported. > > if you have a big customer which hires a 3rd party auditor > you are NOT in the poisiton to give such arguments or > you can give them but you can not change ANYTHING in > the fact that finally "fix it or shutdown the service" > is what you have to do If you have a "security expert" who can't grasp the concept of back-ported bug fixes, and is unwilling to test for specific vulnerabilities' existence, it's time to get a new expert. >> I am going with Kevin on this one. The real hacking tools check to see >> if a vulnerability works or not. The broken "audit" scanners only >> check to see if a header is this or that. Not putting the header only >> gets you past the auditors and doesn't stop the real hacker from >> getting in if the vulnerability is there. > > that is not the point > the point is why in the wolrd must we spit out versions? > > yes, i know it is security by obscurity > but does it hurt? > > if i need to know my version of sshd or any other service > i make a "rpm -qa | grep package", if somebody else likes > to know he has to tell the question as i have for foreign > servers Connecting programs don't have the luxury of 'rpm -q', and must rely on the version returned by the server to know how to pass data. Things change over time, and you certainly can't expect a server to behave the same over (sometimes long) periods of time. -- Digimer E-Mail: digi...@alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "omg my singularity battery is dead again. stupid hawking radiation." - epitron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: service version disclosure
On 01/06/2012 11:09 PM, Reindl Harald wrote: > would it not be a good idea to NOT disclosure service versions? > https://bugzilla.redhat.com/show_bug.cgi?id=718133 > > you will more and more have the "problem" of 3rd party > security scans to your servers and currently in the case > of openssh the only solution is to tkae the F16-src-rpm > and rebuild it for your F15 machines > ___ > > however - why do we spit the current running versions to everyone? > > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > SSH-2.0-OpenSSH_5.8 Security through obscurity... -- Digimer E-Mail: digi...@alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "omg my singularity battery is dead again. stupid hawking radiation." - epitron -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30
On 10/12/2011 02:10 PM, Peter Robinson wrote: > On Wed, Oct 12, 2011 at 6:51 PM, Adam Williamson wrote: >> On Wed, 2011-10-12 at 18:41 +0100, Richard Hughes wrote: >>> On 12 October 2011 17:44, Kevin Fenzi wrote: >>>> All existing users of the Fedora Account System (FAS) at >>>> https://admin.fedoraproject.org/accounts are required to change their >>>> password and upload a NEW ssh public key before 2011-11-30. >>> >>> I have to upload a *new* public key? Why should I have two sets of keys? >> >> Meant 'replacement'. You can only have one key in FAS, afaict. >> >>>> * Nine or more characters with lower and upper case letters, digits and >>>> punctuation marks. >>>> * Ten or more characters with lower and upper case letters and digits. >>>> * Twelve or more characters with lower case letters and digits >>>> * Twenty or more characters with all lower case letters. >>> >>> This is just insane. My existing password is 8 digits and >>> alphanumeric, and given that I have to enter it over and over again >>> (and prove "I'm human", another WTF) when creating updates I'm really >>> wondering if I want to bother. >>> >>> Talk about putting up barriers. >> >> I can think of no reason why everyone shouldn't use a password manager. >> It's just hands down a better way to do things in every respect. Eight >> characters alphanumeric is not actually a very strong password; the >> numbers on how long it'd take to brute force with e.g. EC2 are quite >> tiny. And an account like yours certainly counts as high-value. > > In fact there are rainbow tables out there easily available of all 8 > alpha numeric combinations where you wouldn't even need EC2 to crack a > lot of them. I know of a couple DBs where they have Terabytes of pre > calculated password hashes and its just a simple string match. > > Peter If FAS uses salts, and the DB hasn't been compromised, then rainbow tables are useless. If re-encryption is used, then brute force will be much slower. Eight char passwords are not ideal, but they are also not trivially compromised if the system uses relatively basic/simple precautions. Again, baring a lead of the DB/salts therein. -- Digimer E-Mail: digi...@alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "At what point did we forget that the Space Shuttle was, essentially, a program that strapped human beings to an explosion and tried to stab through the sky with fire and math?" -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30
On 10/12/2011 12:44 PM, Kevin Fenzi wrote: > Subject: IMPORTANT: Mandatory password and ssh key change by 2011-11-30 > > Summary: > > All existing users of the Fedora Account System (FAS) at > https://admin.fedoraproject.org/accounts are required to change their > password and upload a NEW ssh public key before 2011-11-30. > Failure to do so may result in your account being marked inactive. > Passwords changed and NEW ssh public keys uploaded after 2011-10-10 > will meet this requirement. I'd like to add my voice to the concern about requiring new public keys. I can appreciate the desire for security, but forcing new SSH keys accomplishes nothing of practical use. Quite the contrary; It induces a fair hardship of those of us with keys configured on many other systems. The idea of maintaining a second set of keys for Fedora (and again for any other projects that follow suit) is, I'd argue, unreasonably burdensome. -- Digimer E-Mail: digi...@alteeve.com Freenode handle: digimer Papers and Projects: http://alteeve.com Node Assassin: http://nodeassassin.org "At what point did we forget that the Space Shuttle was, essentially, a program that strapped human beings to an explosion and tried to stab through the sky with fire and math?" -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Some thoughts on Audacious in Fedora
On 02/02/2011 01:32 PM, Digimer wrote: >> >> http://repos.fedorapeople.org/repos/mschwendt/audacious-2.5/fedora-audacious-2.5.repo >> >> This is not only for users to take a sneak peek at Audacious 2.5 development, >> but also to emphasize that the dependency on 3rd party plugin packages can >> be problematic. > > Audacious refuses to load or play MP3s for me since a recent update > (Fedora 14 x86_64). I'm guessing this is the kind of problem you are > talking about? If so, I'll give this a shot and report my success or > lack thereof. I installed the audacious-related RPMs from your repo, but MP3s still fail to play with the decoder error. lework:~$ sudo yum list installed | grep audacious [sudo] password for digimer: audacious.x86_64 2.5-0.1.alpha1.fc14 @fedora-audacious-2.5 audacious-devel.x86_64 2.5-0.1.alpha1.fc14 @fedora-audacious-2.5 audacious-libs.x86_64 2.5-0.1.alpha1.fc14 @fedora-audacious-2.5 audacious-plugin-fc.x86_64 0.6-3.fc14.0.1 @fedora-audacious-2.5 audacious-plugin-xmp.x86_643.3.0-2.fc14.1 @updates audacious-plugins.x86_64 2.5-0.2.alpha1.fc14 @fedora-audacious-2.5 audacious-plugins-amidi.x86_64 2.5-0.2.alpha1.fc14 @fedora-audacious-2.5 audacious-plugins-freeworld.x86_64 2.4.0-1.fc14 @rpmfusion-free audacious-plugins-freeworld-aac.x86_64 2.4.0-1.fc14 @rpmfusion-free audacious-plugins-freeworld-ffaudio.x86_64 audacious-plugins-freeworld-mms.x86_64 2.4.0-1.fc14 @rpmfusion-free audacious-plugins-freeworld-mp3.x86_64 2.4.0-1.fc14 @rpmfusion-free audacious-plugins-jack.x86_64 2.5-0.2.alpha1.fc14 @fedora-audacious-2.5 audacious-plugins-sid.x86_64 2.5-0.2.alpha1.fc14 @fedora-audacious-2.5 libmowgli.x86_64 0.9.50-0.1.fc14 @fedora-audacious-2.5 libmowgli-devel.x86_64 0.9.50-0.1.fc14 @fedora-audacious-2.5 (Trying to play an MP3): No decoder found for file:///home/digimer/Music/The%20Decemberists/Dark%20Was%20The%20Night%20-%20Disc%201/12%20Sleepless.mp3. -- Digimer E-Mail: digi...@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Some thoughts on Audacious in Fedora
On 02/02/2011 01:25 PM, Michael Schwendt wrote: > As the Fedora 14 update of Audacious from 2.4.0 to 2.4.3 has not been > smooth at all and is still annoying users, who need 3rd party plugin > packages which still haven't been pushed, the following consequences are > arising IMO: > > > Fedora 13 > > I'm offering Audacious 2.2 (audacious-2.2-16 and audacious-plugins-2.2-38) > in Fedora 13 to anyone interested in taking over. In other words, consider > Audacious in Fedora 13 semi-orphaned. > > In my point of view, it works well enough that it doesn't need an upgrade > to 2.4.x. Though, a lot has changed in the 2.4 series, and certainly there > are additional bug-fixes included. If to be upgraded in Fedora 13, this > would need the cooperation (and extra-work) of 3rd party plugin package > providers. Special precautions are to be taken as not to repeat the > problems we've run into with this recent update in Fedora 14. Whether > Fedora 13 is "new enough" with regard to all dependencies remains to be > examined by whomever. I believe that users with interest in later software > ought to upgrade to Fedora 14. > > > Fedora 14 > > Even before a strong RPM dependency in 3rd party plugin packages is > available to prevent breaking of decoder plugins, I have created a custom > repository for Audacious 2.5-alpha1 - which btw breaks the Plugin API > again and requires actual code changes and not just rebuilds: > > > http://repos.fedorapeople.org/repos/mschwendt/audacious-2.5/fedora-audacious-2.5.repo > > This is not only for users to take a sneak peek at Audacious 2.5 development, > but also to emphasize that the dependency on 3rd party plugin packages can > be problematic. Just a note: sudo yum list |grep audacious [sudo] password for digimer: audacious.x86_64 2.5-0.1.alpha1.fc14 @fedora-audacious-2.5 audacious-devel.x86_64 2.5-0.1.alpha1.fc14 @fedora-audacious-2.5 audacious-libs.x86_642.5-0.1.alpha1.fc14 @fedora-audacious-2.5 audacious-plugins.x86_64 2.5-0.2.alpha1.fc14 @fedora-audacious-2.5 libmowgli.x86_64 0.9.50-0.1.fc14 @fedora-audacious-2.5 libmowgli-devel.x86_64 0.9.50-0.1.fc14 @fedora-audacious-2.5 audacious-debuginfo.x86_64 2.5-0.1.alpha1.fc14 fedora-audacious-2.5 audacious-devel.i686 2.4.3-1.fc14 updates audacious-libs.i686 2.4.3-1.fc14 updates audacious-plugin-fc.x86_64 0.6-3.fc14.0.1 fedora-audacious-2.5 audacious-plugin-fc-debuginfo.x86_64 0.6-3.fc14.0.1 fedora-audacious-2.5 audacious-plugin-xmp.x86_64 3.3.0-2.fc14.1 updates audacious-plugins-amidi.x86_64 2.5-0.2.alpha1.fc14 fedora-audacious-2.5 audacious-plugins-debuginfo.x86_64 2.5-0.2.alpha1.fc14 fedora-audacious-2.5 audacious-plugins-freeworld.x86_64 2.4.0-1.fc14 rpmfusion-free audacious-plugins-freeworld-aac.x86_64 2.4.0-1.fc14 rpmfusion-free audacious-plugins-freeworld-ffaudio.x86_64 audacious-plugins-freeworld-mms.x86_64 2.4.0-1.fc14 rpmfusion-free audacious-plugins-freeworld-mp3.x86_64 2.4.0-1.fc14 rpmfusion-free audacious-plugins-jack.x86_642.5-0.2.alpha1.fc14 fedora-audacious-2.5 audacious-plugins-sid.x86_64 2.5-0.2.alpha1.fc14 fedora-audacious-2.5 audacious-plugins-uade.x86_642.09-5.fc11 rpmfusion-nonfree libmowgli-debuginfo.x86_64 0.9.50-0.1.fc14 fedora-audacious-2.5 lework:~$ sudo yum install audacious-plugin-fc.x86_64 audacious-plugin-xmp.x86_64 audacious-plugins-amidi.x86_64 audacious-plugins-freeworld.x86_64 audacious-plugins-freeworld-aac.x86_64 audacious-plugins-freeworld-ffaudio.x86_64 audacious-plugins-freeworld-mms.x86_64 audacious-plugins-freeworld-mp3.x86_64 audacious-plugins-jack.x86_64 audacious-plugins-sid.x86_64 audacious-plugins-uade.x86_64 libmowgli-debuginfo.x86_64 Loaded plugins: langpacks, presto, refresh-packagekit Adding en_US to language list Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package audacious-plugin-fc.x86_64 0:0.6-3.fc14.0.1 set to be installed ---> Package audacious-plugin-xmp.x86_64 0:3.3.0-2.fc14.1 set to be installed ---> Package audacious-plugins-amidi.x86_64 0:2.5-0.2.alpha1.fc14 set to be installed ---> Package audacious-plugins-freeworld.x86_64 0:2.4.0-1.fc14 set to be installed ---> Package audacious-plugins-freeworld-aac.x86_64 0:2.4.0-1.fc14 set to be installed ---> Package audacious-plugins-freeworld-ffaudio.x86_64 0:2.4.0-1.fc14 set to be installed ---> Package audacious-plugins-freeworld-mms.x86_64 0:2.4.0-1.fc14 set to be installed ---> Package audacious-plugins-freeworld-mp3.x86_64 0:2.4.0-1.fc14 set to be installed ---> Package audacious-plugins-jack.x86_64 0:2.5-0.2.alpha1.fc14 set to be in
Re: Some thoughts on Audacious in Fedora
On 02/02/2011 01:25 PM, Michael Schwendt wrote: > As the Fedora 14 update of Audacious from 2.4.0 to 2.4.3 has not been > smooth at all and is still annoying users, who need 3rd party plugin > packages which still haven't been pushed, the following consequences are > arising IMO: > > > Fedora 13 > > I'm offering Audacious 2.2 (audacious-2.2-16 and audacious-plugins-2.2-38) > in Fedora 13 to anyone interested in taking over. In other words, consider > Audacious in Fedora 13 semi-orphaned. > > In my point of view, it works well enough that it doesn't need an upgrade > to 2.4.x. Though, a lot has changed in the 2.4 series, and certainly there > are additional bug-fixes included. If to be upgraded in Fedora 13, this > would need the cooperation (and extra-work) of 3rd party plugin package > providers. Special precautions are to be taken as not to repeat the > problems we've run into with this recent update in Fedora 14. Whether > Fedora 13 is "new enough" with regard to all dependencies remains to be > examined by whomever. I believe that users with interest in later software > ought to upgrade to Fedora 14. > > > Fedora 14 > > Even before a strong RPM dependency in 3rd party plugin packages is > available to prevent breaking of decoder plugins, I have created a custom > repository for Audacious 2.5-alpha1 - which btw breaks the Plugin API > again and requires actual code changes and not just rebuilds: > > > http://repos.fedorapeople.org/repos/mschwendt/audacious-2.5/fedora-audacious-2.5.repo > > This is not only for users to take a sneak peek at Audacious 2.5 development, > but also to emphasize that the dependency on 3rd party plugin packages can > be problematic. Audacious refuses to load or play MP3s for me since a recent update (Fedora 14 x86_64). I'm guessing this is the kind of problem you are talking about? If so, I'll give this a shot and report my success or lack thereof. -- Digimer E-Mail: digi...@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Why should I ever bother filing another bug?
On 10-11-07 07:00 PM, Felix Miata wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=623742 was duped to newer bug > https://bugzilla.redhat.com/show_bug.cgi?id=624297 > > The older: > > 1-began life with equivalent summary: "system-config-display fails " > > 2-contains same comment 0 information as the latter > > 3-was directed to be filed by triagers on IRC > > 4-has 48 CCs > > If bug fixers plan to only fix bugs they themselves file or randomly choose > to attach patches to, there's no need for anyone else to file bugs, as the > fixers obviously can't be bothered to see what bugs already have been filed. > They might as well be the only testers too. > > If I was a regular triager in Redhat's Bugzilla, this would put an end to it. I've personally filed a good number of bugs that have, in fact, been resolved and closed. I've also posted bugs that have never been acted on. Generally, the more detailed your bug is, specifically in regards to how to reproduce it, the more likely it is that it will be acted on. I suspect that most of the bugs that are submitted by redhat folks themselves get dealt with because they know what other developers want and need in a bug. Try popping by IRC and asking why a particular bug hasn't been acted on. If it's a lack of time, then there you go. If it's a lack of information though, then someone might be able to help guide you as to what else is needed. You can also reply to your own bugs asking for follow-up. Regardless, I am certain that the developers appreciate people who attempt to submit bugs more than users who don't even bother. -- Digimer E-Mail: digi...@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Fedora - Cold Boot Attack
On 10-11-06 07:36 PM, Vaclav Mocek wrote: > Hi all, > > I have read some articles about the Cold Boot Attacks and I am > wondering whether my Fedora box is protected against such kinds of > attack, at least to some extent. > > I work like an Embedded SW/HW Developer and my experience is that data > could remain in the dynamic memory for quite long time, even in the room > temperature. I have used it successfully for debugging, when a booting > routine after the cold reset copies some parts of memory to another > location which could be read lately. > > It would be usefull to overwrite some parts of memory (keys etc.), > before the computer is switched off. So, my question is: Is there > already implemented and used some kind of protection? > > Vaclav M. It's a bit of a tangent, but I think Xen's dom0 kernel does this on boot. If so, perhaps it's code can be adapted? I think it would be a nice (optional?) feature, to be honest. Of course, this doesn't help if power is suddenly cut, but combined with encrypted storage, it would help remove another vector. -- Digimer E-Mail: digi...@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Problem with createrepo for modified DVD ISO
On 10-06-19 08:51 AM, mike cloaked wrote: > On Sat, Jun 19, 2010 at 5:37 AM, Bruno Wolff III wrote: >> On Fri, Jun 18, 2010 at 09:15:09 -0400, >> Digimer wrote: >>> Hi all, >>> >>> I asked this on buildsys, so this is something of a repost. I'm not >>> sure where to turn at this point, so if this isn't the right list, would >>> anyone be able to point me in the right direction? >> >> Probably the question belongs on users. >> >>> I've been trying to create my own (minorly) custom distro for Fedora >>> 13. All it really is is a custom kickstart and a changed up set of RPMs. >> >> I think revisor is the tool that is best for making custom install DVDs. >> I usually make live images using livecd-creator and can't give you specific >> information on using revisor. >> > > Surely mock/pungi is the best tool chain for creating install isos? Perhaps they are, and I will look into them. However, my curiosity has been piqued, so I'd still like to know how it's supposed to be done. It seems to me like it should be a somewhat straight forward task, so I am curious about where my understanding has failed. Cheers. :) -- Digimer E-Mail: li...@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Problem with createrepo for modified DVD ISO
On 10-06-19 12:37 AM, Bruno Wolff III wrote: > On Fri, Jun 18, 2010 at 09:15:09 -0400, >Digimer wrote: >> Hi all, >> >> I asked this on buildsys, so this is something of a repost. I'm not >> sure where to turn at this point, so if this isn't the right list, would >> anyone be able to point me in the right direction? > > Probably the question belongs on users. Noted, thank you. :) >> I've been trying to create my own (minorly) custom distro for Fedora >> 13. All it really is is a custom kickstart and a changed up set of RPMs. > > I think revisor is the tool that is best for making custom install DVDs. > I usually make live images using livecd-creator and can't give you specific > information on using revisor. Revisor is currently broken on F13. I posted a bug for it, but I understand the maintainer is away. I waited for about a week before deciding to give it a shot manually. >> My problem is; I've added some RPMs and removed others, so I need to >> regenerate the files in dvd:/repodata to properly reflect what is in >> dvd:/Packages. I've tried various incantations of 'createrepo Packages/' >> but none seem to work. When I move the generated files into >> dvd:/repodata, roll the ISO, burn and install, the installer complains >> that the repo data is bad (sorry, I don't have the exact error at the >> moment). > > The path to the packages might not be correct. If relative paths are used > and the repodata directory is not related to the location of the rpms the > same way, then you could see something like that. I'd not considered paths before, thanks, I will explore that. -- Digimer E-Mail: li...@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Problem with createrepo for modified DVD ISO
Hi all, I asked this on buildsys, so this is something of a repost. I'm not sure where to turn at this point, so if this isn't the right list, would anyone be able to point me in the right direction? I've been trying to create my own (minorly) custom distro for Fedora 13. All it really is is a custom kickstart and a changed up set of RPMs. My problem is; I've added some RPMs and removed others, so I need to regenerate the files in dvd:/repodata to properly reflect what is in dvd:/Packages. I've tried various incantations of 'createrepo Packages/' but none seem to work. When I move the generated files into dvd:/repodata, roll the ISO, burn and install, the installer complains that the repo data is bad (sorry, I don't have the exact error at the moment). So then, what is the magic incantation to properly regenerate the repodata for a modified Packages directory on a DVD? Thanks! -- Digimer E-Mail: li...@alteeve.com AN!Whitepapers: http://alteeve.com Node Assassin: http://nodeassassin.org -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
