Bug#633037: splashy: /run transition: Please switch to /run
Sorry I couldn't get to this in time. Splashy has now been removed from Debian as everybody is moving to Plymouth. If you still need to use Splashy, I can create a PPA on Launchpad, or Alioth, to make it easier to get updates. However, you can also clone the Git repositories directly. Note that the wiki page has been disabled on Alioth due to constant security issues with DokuWiki. I might just render the pages as HTML and put them where people can see the info without abusing it. -- A bug magnet El Nov 10, 2011, a las 9:56, Michael Biebl bi...@debian.org escribió: Am 13.10.2011 02:49, schrieb Luis Mondesi: This is well overdue... I'll try to upload a new package very soon (5 to 7 days from now). ping? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#648063: [Splashy-devel] Bug#648063: RM: splashy -- RoQA; FTBFS, NMU-maintained, obsolete, 'falling' popcon
I agree. Please remove it from Debian as people who would use this for embedded systems will probably be customizing it directly. Normal users should migrate to Plymouth. -- A bug magnet El Nov 8, 2011, a las 13:14, Didier Raboud o...@debian.org escribió: Package: ftp.debian.org Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi dear FTP team, Note as introduction that I'm not any of the maintainers of splashy, nor officially a member of the QA team. I hereby request the removal of the splashy source from unstable, for the following reasons: - - It currently FTBFS since May 2011 (#625013) without any sign of life from the maintainers; - - It was not present in the last stable release (dropped from testing before release); - - It's last upload was a NMU, in November 2009, without acknowledgement (so far). The latest maintainer upload was in April 2009; - - It's popcon statistices are falling, especially since libsplashy1-dev has no reverse build-depends anymore. - - It's technology is outdated and is well-replaced by plymouth's. Finally, to other readers of this bugreport, please note that I have absolutely no personal grief against (nor in favor) of splashy; I just tend to think that it's time in Debian should probably be over. Cheers, OdyX -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQGcBAEBCAAGBQJOuXF5AAoJEIvPpx7KFjRVm90L/0X8AoISOtMuzm51D8j04uwP X6DIRTUVYIp63RLeMA83MzDljT0Z2MaCIi2op0ZZNxo1j3OMb2rvbld+skzpyaA1 eqN8uuvbpgbw+yqeRYan77hpC7qkn1qfjfBHtaRlib3+HPWVnL8kr1zmwDtOfzfa 1Tpz9q0fJ8KtAy3O5IsT8yhqA1OKgQOw4g4Zn1lsbz1hdTmd0vJDyUjsnUV3wrTD jX2FwEgoTvtq/y/y/GWofXv6pz7kp9Mp68BMNWgGbuZ2CKaI1jnxfC8Wt2AcgkSv 5QU76sfvq2EMd0tGKUCRc4ZFp3XfAp+MY2WAk4b3gL4olxQiIhnCPb/DV/nq1acS gy6l+yUo4OA+1Y16ztl3ET9UIwkp0XEU4Gt2f9R0HshZPFrVohUTesLWl2ocVjmZ 3s6enr5ajZ7RDFxUMq5aGXEVEA2HvnNutQigTngeM6IFddYoMoCB5OrtLaKB6mSA Q3aKD7jeaG6sxM+YZX1hZwHYpPkIU5PtsmBfK9WhYg== =DM8Q -END PGP SIGNATURE- ___ Splashy-devel mailing list splashy-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/splashy-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585558: Splashy fails to run on intel based cards
Sorry about the long (dormant) state. I'll work on these over the long weekend and reload. -- A bug magnet On Sep 1, 2010, at 10:49, Anthony L. Awtrey t...@awtrey.com wrote: Hi there, It's September 2010 now, these issues (#585558 and #583665) are still open and are real show-stoppers. There has been no activity in the git repository for this package indicating work is being done. My latest test of squeeze shows these are still issues. Is this going to be fixed before the Squeeze release? Would patches help? Tony -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579295: slim: doesn't unlock gnome-keyring
Package: slim Version: 1.3.1-5 Severity: normal Tags: squeeze Slim doesn't unlock gnome-keyring, even though you add the following lines to the /etc/pam.d/slim file: authoptionalpam_gnome_keyring.so session optionalpam_gnome_keyring.so auto_start These lines are suggested by the /usr/share/doc/libpam-gnome-keyring/README.Debian file, which is part of the libpam-gnome-keyring package. Every time I login in nm-applet asks for unlock the default keyring. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32.7-mundungus (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages slim depends on: ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libgcc1 1:4.4.2-9 GCC support library ii libjpeg62 6b-16.1The Independent JPEG Group's JPEG ii libpam0g 1.1.1-2Pluggable Authentication Modules l ii libpng12-01.2.43-1 PNG library - runtime ii libstdc++64.4.2-9The GNU Standard C++ Library v3 ii libx11-6 2:1.3.3-3 X11 client-side library ii libxft2 2.1.14-2 FreeType-based font drawing librar ii libxmu6 2:1.0.5-1 X11 miscellaneous utility library Versions of packages slim recommends: ii xterm 256-1 X terminal emulator Versions of packages slim suggests: pn scrot none (no description available) -- debconf information: * shared/default-x-display-manager: slim -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#579295: slim: doesn't unlock gnome-keyring
Slim unlocks the keyring using the /etc/pam.d/slim file shown in bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=476248 Cheers, Luis Gallardo http://lgallardo.com
Bug#524286: Same here
We already have a patch on our git repository. I cannot upload myself. If somebody can NMU be my guest. -- A bug magnet On Apr 18, 2009, at 9:06, Michael Biebl bi...@debian.org wrote: Khapin wrote: I'm having exactly the same problem here with udev 0.125-7 on a Testing... If there is any info/test I could do to help fixing that bug, just ask. btw, this bug should have its severity set to grave or even critical, as it prevents the system from working properly: no mouse, no network, no sound, no ACPI information about the battery, etc. This looks a lot like the splashy bug, where the RC bugs are currently piling up [1]. Could the splashy maintainers please take some action. This bug is highly annoying. Michael [1] http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=splashy;dist=unstable -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#523187: [Splashy-devel] Bug#523187: acpid upgarade problem
Ouch. Time to revert our last update I guess. -- A bug magnet On Apr 16, 2009, at 17:09, luca boncompagni lbo...@gmail.com wrote: Hi, I'm not able to upgrade acpid because I installed splashy, but I do not enable it, I do not pass the splashy options in the boot parameters. The upgrade scripts try to stop acpid but it fails because in the log_end_msg functions it fails in the line 341 of / etc/lsb-base-logging.sh 338 [ -x $SPL_UPD ] || return 1; 339 [ ! -d $STEPS_DIR ] mkdir -p $STEPS_DIR 340 SPL_PRG=$STEPS_DIR/$RUNLEVEL-progress 341 [ -f $SPL_PRG ] || return 1; It cause also the problem that my system was not able to automatically load the kernel modules. To solve all the problems, I have to enable splashy, remove it, and then upgrade acpid. Thanks, Luca ___ Splashy-devel mailing list splashy-de...@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/splashy-devel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#511751: Avrdude fails with avrdude: error: usbtiny_receive: No error (expected 8, got 4) using USBTiny in AMD64 architecture.
Package: avrdude
Version: 5.5-4
Severity: grave
Avrdude fails to complete a request to getting info, or to program a chip,
through
USBTiny adapter (http://www.ladyada.net/make/usbtinyisp/).
The error message is:
avrdude: error: usbtiny_receive: No error (expected 8, got 4)
There is a patch http://savannah.nongnu.org/patch/download.php?file_id=14754
discussed at http://savannah.nongnu.org/patch/?6233, that fixes this error
among others.
The patch attached here, is built and verified,with the Debian source package.
The only changes are related to this fail.
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.28_amd64 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages avrdude depends on:
ii libc6 2.7-16 GNU C Library: Shared libraries
ii libncurses5 5.7+20081213-1 shared libraries for terminal hand
ii libreadline5 5.2-3 GNU readline and history libraries
ii libusb-0.1-4 2:0.1.12-13userspace USB programming library
avrdude recommends no packages.
Versions of packages avrdude suggests:
ii avrdude-doc 5.5-5 documentation for avrdude
-- no debconf information
--- avrdude-5.5.orig/usbtiny.c 2007-10-29 15:40:04.0 +
+++ avrdude-5.5/usbtiny.c 2009-01-14 02:39:55.0 +
@@ -138,7 +138,7 @@
fprintf( stderr, Operation %d not defined for this chip!\n, op );
return -1;
}
- memset(cmd, 0, sizeof(cmd));
+ memset(cmd, 0, 4);
avr_set_bits(p-op[op], cmd);
return pgm-cmd(pgm, cmd, res);
@@ -286,19 +286,19 @@
int nbytes;
// Make sure its empty so we don't read previous calls if it fails
- memset(res, '\0', sizeof(res) );
+ memset(res, '\0', 4 );
nbytes = usb_in( USBTINY_SPI,
(cmd[1] 8) | cmd[0], // convert to 16-bit words
(cmd[3] 8) | cmd[2], //
- res, sizeof(res), 8 * sck_period );
+ res, 4, 8 * sck_period );
if (verbose 1) {
// print out the data we sent and received
printf( CMD: [%02x %02x %02x %02x] [%02x %02x %02x %02x]\n,
cmd[0], cmd[1], cmd[2], cmd[3],
res[0], res[1], res[2], res[3] );
}
- return ((nbytes == sizeof(res)) // should have read 4 bytes
+ return ((nbytes == 4) // should have read 4 bytes
res[2] == cmd[1]); // AVR's do a delayed-echo thing
}
Bug#505291: wrong init directory in initramfs-tools?
That would break swsusp. -- A bug magnet On Jan 12, 2009, at 15:04, Thomas Renard cybae...@web.de wrote: I tried to move libsplashy and splashy from /usr/share/initramfs-tools/scripts/local-premount to /usr/share/initramfs-tools/scripts/init-premount (init-premount is executed before local-top which does lvm and cryptsetup) and update-initramfs -u This works for me with no problems (and the graphical passphrase reader). Why are these scripts located in local-premount in the git source? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505270:
Awesome! this is needed anyway for the fadein to work correctly. I'll apply this and repackage for Sid. Hopefully we will be accepted for Lenny. On Jan 5, 2009, at 6:32, Tim Richardson t...@tim-richardson.net wrote: I did a sleep 0.5 All three machines are fixed with this. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#501315: splashy: Should be in Lenny
Yes. This is a simple fix. Let me work on it this afternoon. On Dec 15, 2008, at 7:27, Marc Fargas teleni...@telenieko.com wrote: Package: splashy Version: 0.3.10-2.1 Followup-For: Bug #501315 Hi, The error mentioned in this bug happens in Lenny should the fix be applied there before release? Cheers, Marc -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable'), (500, 'testing- proposed-updates'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages splashy depends on: ii initramfs-tools0.92j tools for generating an initramfs ii libc6 2.7-16GNU C Library: Shared libraries ii libdirectfb-1.0-0 1.0.1-11 direct frame buffer graphics - sha ii libgcc11:4.3.2-1 GCC support library ii libglib2.0-0 2.16.6-1 The GLib library of C routines ii libmagic1 4.26-1File type determination library us ii libsplashy10.3.10-2.1Library to draw splash screen on b ii lsb-base 3.2-20Linux Standard Base 3.2 init scrip ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime splashy recommends no packages. Versions of packages splashy suggests: ii console-common0.7.80 basic infrastructure for text cons pn splashy-themesnone (no description available) pn upstart none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#505270: More infor re splashy bug 505270
Thanks for sending me your initrd. I'm getting closer to fixing this bug. It looks like the changes in the path for themes and default theme has something to do with this and other crashes. We are now using /usr to store themes and this is a separate partition for most people. Also, the directory wasn't properly link in cpio when running from initramfs. We will need to ensure that splashy does read from the right path once changed. Expect a fix this weekend. On Dec 9, 2008, at 7:10, tim richardson [EMAIL PROTECTED] wrote: Tim, Is it possible that your problem is related to /etc/splashy/ config.xml ? Try copying this file to /root/config.xml and purging Splashy 0.3.10 (dpkg --purge splashy) (from Lenny) and installing the Sid version (0.3.12), then copy your config.xml back to /etc/splashy. Luis, I think you are following a false lead. See below for my clues, but first, I followed your request: 1) I reverted to 0.3.10 and verified that it worked. Then, I copied config.xml as you suggested 2) I purged and went back to Sid. libsplashy and uswsusp were also updated. After the updgrade, I verified that the bug reappeared (splashy flashes momentarily, and then it disappears, as described earlier in the bug report) Then I copied the saved config.xml to /etc/splashy (Of course, bug 504389 appeared after going back to 0.3.12, for which I have submitted a patch http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504389 ) 3) The saved config file made no difference. The startup behavious of 0.3.12 is still broken. I actually see this on all three machines running Debian, one of them being an AMD desktop with Nvidia video so it has nothing to do with intel graphics. My clues: :-) It is very strange that a very simple fix solves the problem: creating /etc/directfbrc and putting in a path to the log-file as I described earlier. That is, this content in /etc/directfbrc solves the problem. log-file=/tmp/directfb.log Move that file, and the bug reappears. 100% guaranteed. It also fixes it on all three of my machines. Clue part 2: change the log-file path to be /root/directfb.log and the bug reappears. So it only fixes the problem when /tmp is used There is not actually any log file created in /tmp. I hope this is a huge clue, but I don't know enough about directfb to make any sense of it. My wild guess is that without /etc/directfbrc, directfb falls back to a default location that is not writable. Why would that affect this new version of splashy? Change of execution to premount, maybe? Also strange: I can not duplicate the error on any virtualbox machines. I even made a virtual machine with a separate /home partition. Couldn't reproduce it. The new file calls the themes from /usr/share/splashy/themes/. I just want to rule out that this is not the cause of your problem. Can you send a copy of your initrd (/boot/initrd.img-`uname -r`) and /etc/fstab to my email? I will send my initrd.img via yousendit.com /etc/fstab is: # /etc/fstab: static file system information. # # file system mount point type options dump pass proc/proc procdefaults0 0 /dev/hda1 / ext3errors=remount-ro 0 1 /dev/hda6 /home ext3defaults0 2 /dev/hda5 noneswapsw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352108: reboot from kde and kdm splashy not displayed, slow reboot
The problem could be that KDM holds the console/framebuffer until it has died/killed by init. Which would not allow splashy's libdirectfb to use the framebuffer. Another problem might be at your /etc/rc6.d/K* scripts level. Make sure that /etc/rc6.d/S01splashy-init and /etc/rc6.d/K01splashy-init exist. To troubleshoot this better you might want to join us at #splashy on irc.freenode.net. -- )(- Luis Mondesi System Administrator Kiskeyix.org We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on -- Steve Jobs in an interview for MacWorld Magazine 2004-Feb No .doc: http://www.gnu.org/philosophy/no-word-attachments.es.html
Bug#350179: splashy 0.1.6.svn5
Can you please try to purge svn2 and install svn5? If you have alioth's repository in your /etc/apt/sources.list you can do this by: apt-get --purge remove splashy splashy-themes apt-get install splashy optionally install splashy-themes if you need more themes. -- )(- Luis Mondesi System Administrator Kiskeyix.org We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on -- Steve Jobs in an interview for MacWorld Magazine 2004-Feb No .doc: http://www.gnu.org/philosophy/no-word-attachments.es.html
Bug#297734: rhythmbox loops forever displaying error dialog
Sorry, i haven't use rythmbox in a while. Everytime i use it it simply doesn't work. Perhaps I should compile a version without gstreamer (is this possible?). I'd say close the bug. I'll try again later if you guys have a beta ready to be released. On 1/31/06, Loïc Minier [EMAIL PROTECTED] wrote: severity 297734 normal thanks Hi, On mer, mar 02, 2005, Luis Mondesi wrote: Under certain conditions, rhythmbox displays a dialog that says: cannot open play pipe (sorry if I didn't catch the correct words, but it was something along those lines). That dialog keeps looping forever. The only way to stop it is to switch to a different console (CTRL+ALT+F1) and use pkill rhythmbox. This is because the error dialog steals focus from you and it opens so fast that it doesn't allow you to close the application. Luis, do you still get this bug with Rhythmbox 0.9.2? Thanks, -- Loïc Minier [EMAIL PROTECTED] Current Earth status: NOT DESTROYED -- )(- Luis Mondesi System Administrator Kiskeyix.org We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on -- Steve Jobs in an interview for MacWorld Magazine 2004-Feb No .doc: http://www.gnu.org/philosophy/no-word-attachments.es.html
Bug#335216: Move getopt to /bin?
The logical resolution to this bug (Debian #335216, /lib/lsb/init-functions uses getopt to parse arguments, requiring /usr to be mounted) seems to be to move getopt into /bin. I agree. ldd shows that getopt doesn't require any libs from /usr. So, moving it to /bin would make things easier (than trying to implement the functionality in sh code or something else). )(- Luis Mondesi System Administrator Kiskeyix.org We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on -- Steve Jobs in an interview for MacWorld Magazine 2004-Feb No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#310243: kernel-image-2.6.8-powerpc: xfs data corruption
On 6/4/05, Joerg Rossdeutscher [EMAIL PROTECTED] wrote: Hi, I found your bug report in the debian bugtracker: #310243 kernel-image-2.6.8-powerpc: xfs data corruption I have the same problem with this kernel version on an amd64 ubuntu. Have you found a way to fix it? My machine is a IMAP/SMTP/POP3 server and crashes only about once a month, so it's very hard to debug. TIA, bye, Ratti Unfortunately I have not found a solution to this problem. I'm not sure if the problem is because the drive is bad (which could be), a limitation of the Mac's BIOS (after 19GB of data it gets corrupted) or what. I believe that I have rule out the possibility that XFS had anything to do with it. This is because I have reformatted the drive using various other filesystems (I even wrote zeros to the whole drive usind dd and /dev/zero and then reformatted the drive using badblocks and ext3). No matter what I did, the drive always went back to be corrupted after writing a given number of gigs (copying UTF8 encoded filenames from another Macintosh running MacOS X. I'm not sure if this is why this happens). I have since removed the drive from the computer. I'll put it back in a x86 system and see if it works. That way I will rule out whether it's the drive that has problems or the BIOS of the Powerpc system that has limitations. Though that drive is 40GB an there is already another 40GB drive in that same computer (this was set as a slave in the same IDE bus). Feel free to lower this bug report's level to low or less until I can find out what the problem is -- )(- Luis M System Administrator Kiskeyix.org We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on -- Steve Jobs in an interview for MacWorld Magazine 2004-Feb No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html
Bug#109846: sshd: Disable PAM if you do not want to use passwords
On 4/24/05, Ludovic Rousseau [EMAIL PROTECTED] wrote: Hello, snip Hello, ummm, are they the same? I don't think so. What happens if you do this: PasswordAuthentication yes UsePAM no instead of PasswordAuthentication no UsePAM no then passwords are effectively disabled. I'm guessing that sshd will work by checking your password, by itself, from /etc/passwd. But most of us with other systems for authentication, say pam_mysql, pam_ldap, just to name a few. Those won't be able to login to the system. So, these two options are related, but they are not the same. However, I'm with you in that a Note should exist in the Debian README file saying that pam_unix in /etc/pam.d/ssh with authenticate against /etc/passwd also. So, if you want to disable password authentication completely, you must set UsePAM to no, as well as the older method of authentication. For some reason this sounds to me like an obvious thing to know (especially by experienced sysadmins). However, I see your point. -- )(- Luis M System Administrator Kiskeyix.org We think basically you watch television to turn your brain off, and you work on your computer when you want to turn your brain on -- Steve Jobs in an interview for MacWorld Magazine 2004-Feb No .doc: http://www.fsf.org/philosophy/no-word-attachments.es.html
