devel July 2013

devel@lists.fedoraproject.org

308 participants
304 discussions

F20 Self Contained Change: Enlightenment
by Jaroslav Reznik 18 Jul '13

18 Jul '13

= Proposed Self Contained Change: Enlightenment = https://fedoraproject.org/wiki/Changes/Enlightenment Change owner(s): Rahul Sundaram <sundaram AT fedoraproject org>, Christopher Meng <i AT cicku me>, Dan Mashal <dan.mashal AT fedoraproject org> Enlightenment 0.17 a new stable release has been released after 12 years or so of development. As many desktops are being landed on Fedora, Integrating Enlightenment in Fedora can not only enlarge the number of available desktops in Fedora, but also improve user experiences and give users another choice of Desktop Environment. == Detailed description == Enlightenment 0.17 (a.k.a E17) is the next generation of graphical desktop shell from the Enlightenment project. When you first run it and get past the initial setup wizard, you should end up with a desktop not unlike the above. It is a very traditional UNIX/X11 style desktop, because that is what E primarily is and attempts to be, BUT with a bunch of bells, whistles and modernities that were never there, as well as a different core design philosophy. There seems to be some obsession with Window Manager vs. Desktop Environment debates. It doesn't much matter what you call it. It manages windows. It does compositing. It manages files. It launches applications. It handles UI and system settings. Before we go any further, it is time to clean up some common misconceptions. * First, Enlightenment is not new. It is OLD. * It predates larger desktop environments like GNOME or XFCE. It is just barely younger than KDE. * It never started life as an attempt to "be a full desktop environment". * It started life as simply a window manager. This was back towards the latter part of 1996, and its first 0.1 release came in the first part of 1997. It was a window manager with some extras to scratch the itch that "everything was gray bevels and UIs had to be plain to be functional or useful, and that computers/X11 were not capable of more". * It handily proved that to be wrong. It could manage function AND form more flexibly than anything else, and to this date is still in an enviable position of flexibility in both behavior features and in terms of visuals. In fact, its Achilles heel simply may be that it has too many options and too much flexibility. Some of the extras filled in the gaps, like setting wallpaper, that was always done by 3rd party tools and not the window manager at the time. If you are after a constrained and simple UI, then Enlightenment (E) is not for you. It can be configured to be plain and simple if you try, or to be buzzing with activity and complexity, but this is up to you. Its default is somewhere in between these to give you a taste of what it can do on both ends of the spectrum. The default look is not what you are stuck with. Enlightenment was the first Window Manager (WM) to introduce themes in X11 (pre-packaged sets of data that you just grab and select, providing you with a vast new look and feel). Today in Enlightenment, these themes come as "Edje" files (.edj), and are pre- packaged data files containing all images, layout, animation etc. that you may need. They never get "unpacked". They are used "live as-is", and only the data needed from the file is sourced and decoded, so even if the theme is massive, only the pieces needed at any one time are decoded into memory, which is normally a fraction of the actual file size. They are also live data and need to be there while E17 runs as it is forever digging bits of data out of these files as it needs it. It is an accepted fact that the default look will not be for everyone. It tries to strike a balance of being unique (not mimicking some other desktop look), yet still being stylish. It is meant to echo some of the past from where Enlightenment comes from, and yet roll in modern effects and feels. It sacrifices some "usability" for look, yet tries to keep a balance and still be functional. It will not be for everyone, but it is hoped that it keeps you mostly happy until you find other themes that exactly meet your visual needs. You will find this as an on-going philosophy in Enlightenment. One size does NOT fit all. That's what options are for. Thats why we have themes. Do not have the misconception that what you see is what you are stuck with. You are expected to experiment and discover what is good for you. Maybe the default is fine. Maybe it is not. That's why we pioneered themes and spent immense amounts of time making them nicely packaged, efficient and powerful enough to fine-tune almost any aspect of the UI. == Scope == Just package every dependency and promise that they can be reviewed 'PASS'. * Proposal owners: Package all dependencies and push them to review queue. * Other developers: Keep existed dependency packages updated, make sure the default backgrounds and theme is available. * Release engineering: Nothing here currently. If there are sufficient interests and participation, a Fedora Enlightenment spin could be released. * Policies and guidelines: N/A (not a System Wide Change) _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

1 0

Developers guide for Fedora Linux
by Mateusz Marzantowicz 18 Jul '13

18 Jul '13

Hello, I'm writing some apps for Linux, from time to time. I'd like to know if there is any comprehensive developers guide for Fedora. I see lot of changes are made to Fedora (and maybe soon RHEL) like no syslog by default, systemd machinery, etc. How can one use all that new exciting features and APIs in their own programs? Please, enlighten me with some (preferably official) resources e.g. about logging using journald in C/C++ or Python/Perl. Thanks in advance, Mateusz Marzantowicz

3 2

Re: F20 Self Contained Change: Remove deprecated calls of using ntpdate in favor of ntpd (fwd)
by Paul Wouters 18 Jul '13

18 Jul '13

On Wed, 17 Jul 2013, Chris Murphy wrote: > a. ntpd/ntpdate aren't installed by default with Fedora 19. I don't see the > feature proposing this be changed. That's a bug then. It is needed for DNSSEC. > b. A default installation of Fedora 18/19, has no means of updating the RTC > correctly if it's off by more than 15 minutes; and 60 minutes with newer > kernels. An RTC wrong by more than an hour, e.g. two months ago, if I have an > internet connection chrony sets the system clock to the correct date/time. It won't be able to do so when DNSSEC is enabled. > If I don't have an internet connection, I'm relegated to a system time based > on the wrong RTC, which seems grossly broken to me. Yes, and using at least the last good known timestamp from shutdown would be a plus. > d. This long bug, 816752, suggests, as a solution, installing ntpdate in > order to set the RTC. So if ntpdate is being deprecated as part of the > proposed feature, why is installing and using ntpdate being suggested as a > fix for the lack of chrony-kernel RTC sync support? > https://bugzilla.redhat.com/show_bug.cgi?id=816752#c75 What I learned today, you can read "ntpdate" as "ntpd -q -g -x" > e. Why isn't this functionality being added to chrony, rather than bouncing > us back to ntpd? Well, my f18 does not even have chrony installed. Did that change for f19? I don't see it at https://fedoraproject.org/wiki/Releases/19/FeatureList > The time situation on Fedora makes me think the left hand and right hand are > doing different things. Well, we're discussing it now. So the ntpdate feature could just be renamed to "deal with time and no RTC properly" Paul

5 4

retired gmaven and gshell
by gil 18 Jul '13

18 Jul '13

hi retired gmaven and gshell from rawhide , cause: 1 - gmaven is upstream dead and require gshell 2 - gshell have encountered some problem with the new jline2 (2.10) see also: https://bugzilla.redhat.com/show_bug.cgi?id=914056 https://bugzilla.redhat.com/show_bug.cgi?id=916924 https://bugzilla.redhat.com/show_bug.cgi?id=985693 regards gil

1 0

Rawhide: glibc, ldconfig, and community-mysql-libs, oh my
by Adam Williamson 18 Jul '13

18 Jul '13

Would anyone care to take a guess at what the hell is going on here? [adamw@adam ~]$ sudo yum update (snip) Error: Package: community-mysql-libs-5.5.32-6.fc20.x86_64 (@rawhide) Requires: /usr/sbin/ldconfig Removing: glibc-2.17.90-3.fc20.x86_64 (@fedora/rawhide) Not found Updated By: glibc-2.17.90-4.fc20.x86_64 (rawhide) Not found (snip) [adamw@adam ~]$ sudo yum check Loaded plugins: auto-update-debuginfo, langpacks, refresh-packagekit Unable to send message to PackageKit check all [adamw@adam ~]$ rpm -q --requires community-mysql-libs-5.5.32-6.fc20.x86_64 | grep ldconf /usr/sbin/ldconfig /usr/sbin/ldconfig [adamw@adam ~]$ rpm -q --whatprovides "/usr/sbin/ldconfig" glibc-2.17.90-3.fc20.x86_64 [adamw@adam ~]$ rpm -q --provides glibc-2.17.90-3.fc20.x86_64 | grep ldconfig ldconfig So...my yum update fails because the new glibc doesn't provide /usr/sbin/ldconfig, which community-mysql-libs requires. But then, neither does the current glibc, according to rpm -q. But according to rpm -q --whatprovides , it does! And according to the Koji 'information' pages, both -3 and -4 Provide: ldconfig and Require: /sbin/ldconfig , with no mention of /usr/sbin/ldconfig in either. What the fracking hell? Why is yum apparently okay with -3 but not okay with -4 even though their provides are identical? And why is this suddenly popping up now? -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net

6 7

cloud images and journald/rsyslog
by Matthew Miller 18 Jul '13

18 Jul '13

I'm putting this in a separate thread so it doesn't get buried in the enthusiasm over the other one. :) Here's our dilemma (Or trilemma?) in the Fedora Cloud SIG. 1) Double-logging is a significant waste of scarce resources 2) If we disable persistent journald (the f19 approach), we lose the nice features that journalctl offers. And, they really are nice. 3) If we leave out rsyslog, we lose text /var/log/messages ... ... which is less of a big deal from the server-room emergency-analysis angle that might apply in the general case ... ... but it's a pretty big change from the rest of Fedora, and we'd prefer not to do that just for the cloud image. So, it'd be nice to at least have rsyslogd moved from @core to @standard (from minimal to default). I'm also pretty well sold on the idea that journald is better on the desktop. But that's not my thing. On the server, I don't think I've _ever_ run a serious system where I didn't have a custom syslog configuration (be it sysklogd, rsyslog, or syslog-ng). I absolutely don't think that will go away. (And on those systems, generally I don't look in /var/log/messages anymore anyway.) -- Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>

9 17

F20 Self Contained Change: OS Installer Support for LVM Thin Provisioning
by Jaroslav Reznik 17 Jul '13

17 Jul '13

= Proposed Self Contained Change: OS Installer Support for LVM Thin Provisioning = https://fedoraproject.org/wiki/Changes/InstallerLVMThinProvisioningSupport Change owner(s): David Lehman <dlehman(a)fedoraproject.org> LVM has introduced thin provisioning technology, which provides greatly improved snapshot functionality in addition to thin provisioning capability. This change will make it possible to configure thin provisioning during OS installation. == Detailed description == Thin Provisioning support in the installer will include a new automatic partitioning variant as well as support for thin volumes during custom storage configuration. == Scope == Proposal owners: implement Thin Provisioning functionality in the installer Other developers: N/A (not a System Wide Change) Release engineering: N/A (not a System Wide Change) Policies and guidelines: N/A (not a System Wide Change) _______________________________________________ devel-announce mailing list devel-announce(a)lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel-announce

5 7

Re: F20 Self Contained Change: Remove deprecated calls of using ntpdate in favor of ntpd
by Mike 17 Jul '13

17 Jul '13

Which gets me wondering if that is the best way to test for remote ntp connectivity. So, I'm curious now, if there is no remote NTP server listening, will the anaconda server reject you from using that as a NTP server? Mike ------------------------------ > > Message: 12 > Date: Wed, 17 Jul 2013 13:48:04 -0700 > From: Adam Williamson <awilliam(a)redhat.com> > To: Development discussions related to Fedora > <devel(a)lists.fedoraproject.org> > Subject: Re: F20 Self Contained Change: Remove deprecated calls of > using ntpdate in favor of ntpd > Message-ID: <1374094084.1594.8.camel@adam> > Content-Type: text/plain; charset="UTF-8" > > On Wed, 2013-07-17 at 13:44 -0700, Adam Williamson wrote: > > On Wed, 2013-07-17 at 16:09 +0200, Miroslav Lichvar wrote: > > > > > > e. Why isn't this functionality being added to chrony, rather than > bouncing us back to ntpd? > > > > > > Which functionality exactly? Both ntpd and chronyd (in default > > > configuration) let the kernel sync the RTC. > > > > The ability to invoke chronyd in a way that mimics ntpdate. This thread > > has turned up that you can invoke *ntpd* in this way: ntpd -q -g -x. But > > no-one has yet provided an equivalent invocation for chronyd, and I > > could not figure one out from the manpage. > > > > Aside from anything else, anaconda requires something like this to be > > available in order to check whether an NTP server is valid and > > available: a simple, one-off command which will 'return true' in some > > obvious way if the specified server exists and responds correctly, and > > 'return false' if it doesn't. For now it is using ntpdate; I suppose we > > could switch it to ntpd, but it would make an awful lot more sense if > > chronyd could do this. > > In fact, now I look at it, ntpd as it stands cannot replace ntpdate for > anaconda's purposes, because anaconda calls ntpdate with the -q option, > which means "query only, do not set the clock" - obviously, this is > appropriate when we just want to test the functionality of an NTP > server. ntpd does not have an equivalent option. > -- > Adam Williamson > Fedora QA Community Monkey > IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora > http://www.happyassassin.net >

3 2

Fedora ARM Weekly Status Meeting Minutes 2013-07-17
by Paul Whalen 17 Jul '13

17 Jul '13

Thanks to those that were able to join us for the status meeting today, for those unable the minutes are posted below: Minutes: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-07-17/fedora-meeting… Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting-1/2013-07-17/fedora-meeting… Log: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-07-17/fedora-meeting… =================================================== #fedora-meeting-1: Fedora ARM weekly status meeting =================================================== Meeting summary --------------- * 0) Status of ACTION items from our previous meeting (pwhalen, 20:04:17) * LINK: http://meetbot.fedoraproject.org/fedora-meeting-1/2013-07-10/fedora-meeting… (pwhalen, 20:04:25) * ACTION: dgilmore to setup koji hub&db for aarch64 (pwhalen, 20:09:14) * ACTION: handsome_pirate Is talking to ghc upstream (pwhalen, 20:09:56) * ACTION: msalter is working on openjdk for aarch64 (bconoboy, 20:11:09) * ACTION: kylem to create a list of new supported platforms in 3.11 (pwhalen, 20:13:38) * 1) Problem packages (pwhalen, 20:13:56) * ghostscript/systemtap blocker resolved (bconoboy, 20:14:27) * 2) Kernel Status Update (pwhalen, 20:19:30) * kernel-3.11.0-0.rc1.git0.1.fc20 just finished (pwhalen, 20:21:03) * LINK: http://arm.koji.fedoraproject.org/koji/buildinfo?buildID=153355 (pwhalen, 20:21:15) * 3a) Aarch64 Status Update, problem packages (pwhalen, 20:26:07) * openjdk bootstrap still in progress. msalter hopes to have it wrapped up by next week (pwhalen, 20:38:53) * 3b) Moving to Koji - update (pwhalen, 20:39:39) * 4) F20 PA Promotion Criteria discussion (pwhalen, 20:41:06) * LINK: http://meetbot.fedoraproject.org/fedora-meeting/2013-07-17/fesco.2013-07-17… (pwhalen, 20:42:11) * "build ARM on primary infrastructure. whether it is released as a primary Fedora 20 or as 'Fedora 20 for ARM' depends on how well it fulfills release criteria and functionality criteria closer to release time" (bconoboy, 20:45:14) * From the QA meeting "QA does not see any definite roadblocks to ARM becoming a primary arch for F20, but expects that minor changes will be needed to the release criteria to define the ARM 'release blocking images' and assistance will be needed from ARM-focused testers to complete ARM validation testing (bconoboy, 20:46:59) * 5) Open Floor (pwhalen, 20:51:48) * Masta to create beaglebone black remix (bconoboy, 20:54:40) * PA is not assured- we must be especially vigilant to fix issues as they crop up during the transition (bconoboy, 20:55:04) * LINK: http://parasense.fedorapeople.org/f19-beagleboneblack-MATE.img.xz is a beta beaglebone black image (bconoboy, 20:56:01) * PA is not assured- we must be especially vigilant to fix issues as they crop up during the transition (pwhalen, 20:56:18) Meeting ended at 20:57:51 UTC. Action Items ------------ * dgilmore to setup koji hub&db for aarch64 * handsome_pirate Is talking to ghc upstream * msalter is working on openjdk for aarch64 * kylem to create a list of new supported platforms in 3.11 Action Items, by person ----------------------- * dgilmore * dgilmore to setup koji hub&db for aarch64 * handsome_pirate * handsome_pirate Is talking to ghc upstream * kylem * kylem to create a list of new supported platforms in 3.11 * msalter * msalter is working on openjdk for aarch64 * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * pwhalen (60) * pbrobinson (39) * handsome_pirate (35) * masta (20) * bconoboy (19) * ctyler (9) * kylem (6) * jcapik (5) * zodbot (5) * dgilmore (5) * dmarlin (2) * ahs3 (2) * nirik (1) * agreene (1) * msalter (0) * j_dulaney (0) * ddd_ (0) * jonmasters (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

Fwd: Continuing issues with gnome-shell, upower, and KVM hardware
by Philip Prindeville 17 Jul '13

17 Jul '13

I tried researching this issue out-of-band but I'm not getting any traction. I have an F18 machine that had been running F13-16 perfectly, but somewhere between the X driver changes, the new version of gnome-shell, a cogl update, and the transition from PackageKit to upower started being very unstable. I have an MSI Phenom motherboard, RV700 card, an IOGear 1792 (HDMI+usb+audio) KVM, a Microsoft USB keyboard, and a Apple mouse. Fedora sees the mouse only sporadically, and occasionally the system will get so wedged that the keyboard, mouse, and network logins won't work. I've attached some information that's hopefully pertinent, but with the number of components that changed between F17 and F18 it isn't clear where to go looking for a smoking gun. I'm hoping that one of the package owners will see some information below that stands out to them as being significant. Thanks. -Philip On Jul 15, 2013, at 12:54 PM, Philip Prindeville <philipp(a)fedoraproject.org> wrote: > Hi Adam, > > I installed the updated version of gnome-shell [Dave] suggested and that resolved some of my display corruption issues, but using a KVM continues to befuddle my keyboard/mouse. > > This is the sort of logging I get: > > ... > Jul 15 12:38:18 localhost colord: Device added: xrandr-Dell-DELL U2412M-YMYH132P0L7L > Jul 15 12:38:18 localhost colord: Profile added: icc-9c9ea1791dd05d3c58c2bad614907d9c > Jul 15 12:38:18 localhost colord: Profile added: icc-8f75b0a711924df8447ac14513998fb1 > Jul 15 12:38:18 localhost colord: Profile added: icc-2de986f6b2714ea628263a031b4add31 > Jul 15 12:38:18 localhost colord: Profile added: icc-f6a60e3600700ebad109f1892edd681e > Jul 15 12:38:19 localhost colord: Profile added: icc-8d7af8950b969e19a7dd8cdf1bb2214a > Jul 15 12:38:20 localhost goa[11067]: goa-daemon version 3.6.3 starting [main.c:112, main()] > Jul 15 12:38:20 localhost dbus-daemon[520]: dbus[520]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.141" (uid=1000 pid=10940 comm="/usr/bin/gnome-shell ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=747 comm="/usr/sbin/console-kit-daemon --no-daemon ") > Jul 15 12:38:20 localhost dbus[520]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.141" (uid=1000 pid=10940 comm="/usr/bin/gnome-shell ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=747 comm="/usr/sbin/console-kit-daemon --no-daemon ") > Jul 15 12:38:23 localhost dbus-daemon[520]: ** Message: No devices in use, exit > Jul 15 12:38:24 localhost kernel: [60572.444941] usb 1-3: USB disconnect, device number 2 > Jul 15 12:38:24 localhost kernel: [60572.444950] usb 1-3.4: USB disconnect, device number 4 > Jul 15 12:38:24 localhost acpid: input device has been disconnected, fd 11 > Jul 15 12:38:24 localhost acpid: input device has been disconnected, fd 12 > Jul 15 12:38:28 localhost kernel: [60576.119049] usb 1-3: new high-speed USB device number 5 using ehci-pci > Jul 15 12:38:37 localhost systemd-logind[512]: Removed session 1. > Jul 15 12:38:43 localhost kernel: [60591.288141] usb 1-3: device descriptor read/64, error -110 > Jul 15 12:38:58 localhost kernel: [60606.558250] usb 1-3: device descriptor read/64, error -110 > Jul 15 12:38:58 localhost kernel: [60606.761266] usb 1-3: new high-speed USB device number 6 using ehci-pci > Jul 15 12:39:13 localhost kernel: [60621.930366] usb 1-3: device descriptor read/64, error -110 > Jul 15 12:39:29 localhost kernel: [60637.200445] usb 1-3: device descriptor read/64, error -110 > Jul 15 12:39:29 localhost kernel: [60637.403463] usb 1-3: new high-speed USB device number 7 using ehci-pci > Jul 15 12:39:39 localhost kernel: [60647.850213] usb 1-3: device not accepting address 7, error -110 > Jul 15 12:39:39 localhost kernel: [60647.952238] usb 1-3: new high-speed USB device number 8 using ehci-pci > Jul 15 12:39:50 localhost kernel: [60658.398992] usb 1-3: device not accepting address 8, error -110 > Jul 15 12:39:50 localhost kernel: [60658.399016] hub 1-0:1.0: unable to enumerate USB device on port 3 > Jul 15 12:39:50 localhost kernel: [60658.680989] usb 3-3: new full-speed USB device number 2 using ohci_hcd > Jul 15 12:39:50 localhost kernel: [60658.822032] usb 3-3: not running at top speed; connect to a high speed hub > Jul 15 12:39:50 localhost kernel: [60658.826036] usb 3-3: New USB device found, idVendor=0409, idProduct=005a > Jul 15 12:39:50 localhost kernel: [60658.826042] usb 3-3: New USB device strings: Mfr=0, Product=0, SerialNumber=0 > Jul 15 12:39:50 localhost kernel: [60658.828072] hub 3-3:1.0: USB hub found > Jul 15 12:39:50 localhost kernel: [60658.830017] hub 3-3:1.0: 4 ports detected > Jul 15 12:39:51 localhost kernel: [60659.132059] usb 3-3.4: new low-speed USB device number 3 using ohci_hcd > Jul 15 12:39:51 localhost kernel: [60659.326063] usb 3-3.4: New USB device found, idVendor=045e, idProduct=00db > Jul 15 12:39:51 localhost kernel: [60659.326068] usb 3-3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > Jul 15 12:39:51 localhost kernel: [60659.326072] usb 3-3.4: Product: Natural® Ergonomic Keyboard 4000 > Jul 15 12:39:51 localhost kernel: [60659.326075] usb 3-3.4: Manufacturer: Microsoft > Jul 15 12:39:51 localhost kernel: [60659.358641] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/input/input16 > Jul 15 12:39:51 localhost kernel: [60659.358979] microsoft 0003:045E:00DB.0007: input,hidraw2: USB HID v1.11 Keyboard [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:12.0-3.4/input0 > Jul 15 12:39:51 localhost kernel: [60659.406290] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/input/input17 > Jul 15 12:39:51 localhost kernel: [60659.406507] microsoft 0003:045E:00DB.0008: input,hidraw3: USB HID v1.11 Device [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:12.0-3.4/input1 > Jul 15 12:39:51 localhost kernel: [60659.432404] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.2/input/input18 > Jul 15 12:39:51 localhost kernel: [60659.432799] microsoft 0003:045E:00DB.0009: input,hidraw4: USB HID v1.10 Mouse [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:12.0-3.4/input2 > Jul 15 12:39:51 localhost mtp-probe: checking bus 3, device 3: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4" > Jul 15 12:39:51 localhost mtp-probe: bus: 3, device: 3 was not an MTP device > > > (I'm actually having to use 2 keyboards and mice, with the 2nd ones connected directly…) > > I see a lot of instances of switching away from the port that Fedora 18 is connected to, and then when I switch back the messages: > > > Jul 15 12:38:43 localhost kernel: [60591.288141] usb 1-3: device descriptor read/64, error -110 > Jul 15 12:38:58 localhost kernel: [60606.558250] usb 1-3: device descriptor read/64, error -110 > > > or something similar occur, and I have to reboot. > > I'm wondering if the root-cause might not be: > > > Jul 15 12:38:20 localhost dbus-daemon[520]: dbus[520]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.141" (uid=1000 pid=10940 comm="/usr/bin/gnome-shell ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=747 comm="/usr/sbin/console-kit-daemon --no-daemon ") > Jul 15 12:38:20 localhost dbus[520]: [system] Rejected send message, 2 matched rules; type="method_call", sender=":1.141" (uid=1000 pid=10940 comm="/usr/bin/gnome-shell ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination=":1.8" (uid=0 pid=747 comm="/usr/sbin/console-kit-daemon --no-daemon ") > > > This is the hardware I have: > > [philipp@builder ~]$ sudo usb-devices > > > T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 > D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0002 Rev=03.09 > S: Manufacturer=Linux 3.9.9-201.fc18.x86_64 ehci_hcd > S: Product=EHCI Host Controller > S: SerialNumber=0000:00:12.2 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6 > D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0002 Rev=03.09 > S: Manufacturer=Linux 3.9.9-201.fc18.x86_64 ehci_hcd > S: Product=EHCI Host Controller > S: SerialNumber=0000:00:13.2 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=02 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 2 Spd=480 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=048d ProdID=1336 Rev=01.00 > S: Manufacturer=Generic > S: Product=Mass Storage Device > S: SerialNumber=00000000000006 > C: #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage > > T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0001 Rev=03.09 > S: Manufacturer=Linux 3.9.9-201.fc18.x86_64 ohci_hcd > S: Product=OHCI Host Controller > S: SerialNumber=0000:00:12.0 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=03 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=12 MxCh= 4 > D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=0409 ProdID=005a Rev=01.00 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=03 Lev=02 Prnt=02 Port=03 Cnt=01 Dev#= 3 Spd=1.5 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=045e ProdID=00db Rev=01.73 > S: Manufacturer=Microsoft > S: Product=Natural® Ergonomic Keyboard 4000 > C: #Ifs= 3 Cfg#= 1 Atr=a0 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid > I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid > I: If#= 2 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid > > T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0001 Rev=03.09 > S: Manufacturer=Linux 3.9.9-201.fc18.x86_64 ohci_hcd > S: Product=OHCI Host Controller > S: SerialNumber=0000:00:12.1 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=051d ProdID=0002 Rev=01.06 > S: Manufacturer=APC > S: Product=Back-UPS ES 750 FW:819.z3.D USB FW:z3 > S: SerialNumber=3B0717X70632 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid > > T: Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0001 Rev=03.09 > S: Manufacturer=Linux 3.9.9-201.fc18.x86_64 ohci_hcd > S: Product=OHCI Host Controller > S: SerialNumber=0000:00:13.0 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=05 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=046d ProdID=c00e Rev=11.10 > S: Manufacturer=Logitech > S: Product=USB-PS/2 Optical Mouse > C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=98mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=02 Driver=usbhid > > T: Bus=06 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 3 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0001 Rev=03.09 > S: Manufacturer=Linux 3.9.9-201.fc18.x86_64 ohci_hcd > S: Product=OHCI Host Controller > S: SerialNumber=0000:00:13.1 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > > T: Bus=06 Lev=01 Prnt=01 Port=02 Cnt=01 Dev#= 2 Spd=1.5 MxCh= 0 > D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 > P: Vendor=045e ProdID=000b Rev=02.07 > S: Product=Microsoft Natural Keyboard Elite > C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid > > T: Bus=07 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2 > D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > P: Vendor=1d6b ProdID=0001 Rev=03.09 > S: Manufacturer=Linux 3.9.9-201.fc18.x86_64 ohci_hcd > S: Product=OHCI Host Controller > S: SerialNumber=0000:00:14.5 > C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA > I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub > [philipp@builder ~]$ > > > The Apple mouse doesn't appear in the usb-devices dump, not sure why. And a hid dump: > > > [philipp@builder ~]$ sudo usbhid-dump > 004:002:000:DESCRIPTOR 1373914062.287125 > 05 84 09 04 A1 01 09 24 A1 00 85 01 09 FE 79 01 > 75 08 95 01 15 00 26 FF 00 B1 22 85 02 09 FF 79 > 02 B1 22 85 03 05 85 09 89 79 04 B1 22 85 04 09 > 8F 79 03 B1 22 85 05 09 8B B1 22 85 06 06 86 FF > 09 60 81 A2 09 60 B1 A2 85 07 05 85 09 85 75 10 > 27 FF FF 00 00 B1 A2 85 08 05 84 09 40 67 21 D1 > F0 00 55 05 B1 22 85 09 09 30 B1 A2 85 0A 09 FD > 75 08 26 FF 00 65 00 55 00 79 03 B1 22 85 0B 05 > 85 09 2C B1 22 85 0C 09 66 25 64 81 A2 09 66 B1 > A2 09 68 75 10 27 FF FF 00 00 66 01 10 81 A2 09 > 68 B1 A2 85 0D 09 83 75 08 25 64 65 00 B1 22 85 > 0E 09 67 B1 22 85 0F 09 8C B1 22 85 10 09 8E B1 > 22 85 11 09 29 15 01 B1 A2 85 12 09 8D 15 00 B1 > 22 05 84 09 02 A1 02 85 16 05 85 75 01 25 01 09 > 44 81 A2 09 44 B1 A2 09 45 81 A2 09 45 B1 A2 09 > D0 81 A2 09 D0 B1 A2 09 D1 81 A2 09 D1 B1 A2 09 > 42 81 A2 09 42 B1 A2 05 84 09 69 81 A2 09 69 B1 > A2 05 85 09 43 81 A2 09 43 B1 A2 09 4B 81 A2 09 > 4B B1 A2 05 84 09 65 81 A2 09 65 B1 A2 95 17 81 > 01 B1 01 C0 85 17 05 85 09 2A 95 01 75 10 27 FF > FF 00 00 66 01 10 B1 A2 85 18 05 84 09 5A 75 08 > 15 01 25 03 65 00 B1 A2 C0 09 12 A1 00 85 1C 06 > 86 FF 09 16 75 18 15 00 27 FF FF FF 00 B2 A2 01 > 85 20 05 85 09 85 75 10 27 FF FF 00 00 B1 A2 85 > 22 09 66 75 08 25 64 B1 A2 85 23 09 68 75 10 27 > FF FF 00 00 66 01 10 09 68 B1 A2 85 24 09 2A B1 > A2 85 25 05 84 09 40 67 21 D1 F0 00 55 05 B1 22 > 85 26 09 30 B1 A2 85 27 06 86 FF 09 24 75 08 16 > E8 00 26 FE 00 65 00 55 00 B1 A2 85 28 09 18 75 > 20 17 01 00 00 80 27 FF FF FF 7F B2 A2 01 C0 05 > 84 09 1A A1 00 85 30 05 84 09 40 75 08 15 00 26 > FF 00 67 21 D1 F0 00 55 07 B1 22 85 31 09 30 B1 > A2 85 32 09 53 15 57 25 61 B1 A2 85 33 09 54 15 > 7F 26 8B 00 B1 A2 85 34 06 86 FF 09 24 16 75 00 > 26 8B 00 65 00 55 00 B1 A2 85 35 09 61 15 00 25 > 02 B1 A2 85 36 09 52 25 0D B1 A2 C0 09 05 A1 00 > 85 40 09 7C 25 01 B1 A2 85 41 09 7D 75 10 16 FF > FF 26 FF 7F 66 01 10 B1 A2 C0 05 84 09 16 A1 00 > 85 50 09 35 75 08 15 00 25 64 65 00 B1 A2 85 51 > 06 86 FF 09 24 16 6D 00 26 B8 00 B1 A2 C0 06 86 > FF 09 01 A1 00 85 60 09 23 75 10 15 00 27 FF FF > 00 00 B1 A2 85 61 09 26 75 08 15 84 25 8C B1 A2 > 85 62 09 25 75 20 17 01 00 00 80 27 FF FF FF 7F > B2 A2 01 C0 85 7F 05 84 09 FE 79 05 75 08 95 01 > 15 00 26 FF 00 B1 22 85 7E 06 86 FF 09 42 79 06 > B1 22 85 7D 05 84 09 FF 79 02 B1 22 85 7C 09 FD > 79 03 B1 22 85 7B 05 85 09 85 75 10 27 FF FF 00 > 00 B1 A2 05 84 09 02 A1 02 85 7A 05 85 09 44 75 > 01 25 01 B1 A2 09 45 B1 A2 09 D0 B1 A2 09 D1 B1 > A2 09 42 B1 A2 05 84 09 69 B1 A2 05 85 09 43 B1 > A2 09 4B B1 A2 05 84 09 65 B1 A2 95 17 B1 01 C0 > 85 79 06 86 FF 09 72 75 08 95 01 B1 A2 85 78 05 > 84 09 5A 15 01 25 03 B1 A2 85 75 06 86 FF 09 29 > 26 FF 00 B1 A2 85 74 09 2A 75 20 17 01 00 00 80 > 27 FF FF FF 7F B1 A2 C0 > > 005:002:000:DESCRIPTOR 1373914062.295285 > 05 01 09 02 A1 01 09 01 A1 00 05 09 19 01 29 03 > 15 00 25 01 95 03 75 01 81 02 95 01 75 05 81 03 > 05 01 09 30 09 31 09 38 15 81 25 7F 75 08 95 03 > 81 06 C0 C0 > > 006:002:000:DESCRIPTOR 1373914062.300087 > 05 01 09 06 A1 01 05 07 19 E0 29 E7 15 00 25 01 > 95 08 75 01 81 02 95 01 75 08 81 01 95 05 75 01 > 05 08 19 01 29 05 91 02 95 01 75 03 91 01 95 06 > 75 08 15 00 25 65 05 07 19 00 29 65 81 00 C0 > > 003:003:002:DESCRIPTOR 1373914062.321737 > 05 01 09 02 A1 01 09 01 A1 00 05 09 19 01 29 05 > 15 00 25 01 95 05 75 01 81 02 95 01 75 03 81 01 > 05 01 09 30 09 31 09 38 15 81 25 7F 75 08 95 03 > 81 06 C0 C0 > > 003:003:001:DESCRIPTOR 1373914062.355724 > 05 0C 09 01 A1 01 85 01 05 0C 19 00 2A FF 03 95 > 01 75 10 15 00 27 FF 03 00 00 81 00 05 07 19 00 > 29 FF 75 08 26 FF 00 81 00 81 01 06 00 FF 0A 03 > FE 0A 04 FE 95 02 75 01 25 01 81 02 0A 05 FF 95 > 01 75 05 25 1F 81 02 75 09 81 01 0A 02 FF 26 FF > 00 75 08 81 02 C0 > > 003:003:000:DESCRIPTOR 1373914062.380723 > 05 01 09 06 A1 01 05 08 19 01 29 03 15 00 25 01 > 75 01 95 03 91 02 09 4B 95 01 91 02 95 04 91 01 > 05 07 19 E0 29 E7 95 08 81 02 75 08 95 01 81 01 > 19 00 29 91 26 FF 00 95 06 81 00 C0 > > [philipp@builder ~]$ > > > and running usbhid-dump causes the following additional logging: > > > Jul 15 12:41:30 localhost systemd-logind[512]: New session 20 of user philipp. > Jul 15 12:47:42 localhost acpid: input device has been disconnected, fd 12 > Jul 15 12:47:42 localhost acpid: input device has been disconnected, fd 11 > Jul 15 12:47:42 localhost kernel: [61130.622672] hid-generic 0003:051D:0002.000A: hiddev0,hidraw0: USB HID v1.10 Device [APC Back-UPS ES 750 FW:819.z3.D USB FW:z3] on usb-0000:00:12.1-1/input0 > Jul 15 12:47:42 localhost kernel: [61130.628100] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:13.0/usb5/5-3/5-3:1.0/input/input19 > Jul 15 12:47:42 localhost kernel: [61130.629555] hid-generic 0003:046D:C00E.000B: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:13.0-3/input0 > Jul 15 12:47:42 localhost kernel: [61130.643041] input: Microsoft Natural Keyboard Elite as /devices/pci0000:00/0000:00:13.1/usb6/6-3/6-3:1.0/input/input20 > Jul 15 12:47:42 localhost kernel: [61130.643417] hid-generic 0003:045E:000B.000C: input,hidraw2: USB HID v1.10 Keyboard [Microsoft Natural Keyboard Elite] on usb-0000:00:13.1-3/input0 > Jul 15 12:47:42 localhost kernel: [61130.670617] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.2/input/input21 > Jul 15 12:47:42 localhost kernel: [61130.672344] microsoft 0003:045E:00DB.000D: input,hidraw3: USB HID v1.10 Mouse [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:12.0-3.4/input2 > Jul 15 12:47:42 localhost kernel: [61130.715442] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.1/input/input22 > Jul 15 12:47:42 localhost kernel: [61130.715885] microsoft 0003:045E:00DB.000E: input,hidraw4: USB HID v1.11 Device [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:12.0-3.4/input1 > Jul 15 12:47:42 localhost kernel: [61130.747081] input: Microsoft Natural® Ergonomic Keyboard 4000 as /devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4/3-3.4:1.0/input/input23 > Jul 15 12:47:42 localhost kernel: [61130.747387] microsoft 0003:045E:00DB.000F: input,hidraw5: USB HID v1.11 Keyboard [Microsoft Natural® Ergonomic Keyboard 4000] on usb-0000:00:12.0-3.4/input0 > Jul 15 12:47:48 localhost apcupsd[1045]: Communications with UPS restored. > Jul 15 12:47:48 localhost wall[11686]: wall: user root broadcasted 1 lines (42 chars) > > > Here's some of the logging I saw yesterday before the system hung: > > > Jul 14 18:49:06 builder mtp-probe: checking bus 3, device 13: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-3/3-3.4" > Jul 14 18:49:06 builder mtp-probe: bus: 3, device: 13 was not an MTP device > > At this point, I'm kind of floundering as to what's going on. > > Any idea who to talk to? > > Thanks, > > -Philip > >

1 0

← Newer
1
...
12
13
14
15
16
17
18
...
31
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

devel July 2013