Fwd: Debian-Stable and KDE crashes
-- Forwarded message -- From: Alexey Eromenko Date: Sat, Jan 14, 2012 at 9:26 AM Subject: Debian-Stable and KDE crashes To: debian-user It turns out, that Debian-stable (6.0.3, both i386 and AMD64) has constant KDE crashes, by default. Due to bug in konqueror-nsplugins: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549309 What to do? I would like to up priority to critical for this package, so that it either gets fixed or at least avoid installing it by default, in the next point release. Having default KDE crashing on users is 100% unacceptable. (part of the reason is me to blame; I was not Debian user before 6.0, so didn't test before release) How to up the bug priority ? Any good ideas? Is "debian-boot" the appropriate place for discussion of default Debian KDE install? If not, where? -- -Alexey Eromenko "Technologov" -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOJ6w=fclyduenqhek3kauppkfhegoyydkyktqxcqmmp1r8...@mail.gmail.com
Bug#655841: Please remove Gnash from default Debian install, as it crashes
Package: debian-installer Version: 20110106+squeeze3+b1 Severity: important Default Debian-6 KDE installs "gnash", an extremely unstable component, that constantly crashes KDE Konqueror, when user accesses any flash-enabled website (such as www.amd.com). This makes for very bad newbie user experience, and may drive users away. I suggest to remove this component from the default Debian KDE installs until it becomes stable. (starting with the next point release, 6.0.4) Related bugs: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549309 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655839 NOTE: I'm not sure this bug must be opened against "debian-installer", but I can't seem to find any better alternative. I am using Debian GNU/Linux 6.0.3 on AMD64 (also tried i386) -- -Alexey Eromenko "Technologov" -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOJ6w=Hv5LDNugRuO=dlnhfmgn-+0frjeswnrl9+nbahmll...@mail.gmail.com
Processed: your mail
Processing commands for cont...@bugs.debian.org: > usertag 549345 not-upstream Bug#549345: grub-efi-ia32 does not install User is phco...@gmail.com Usertags were: upstream-199-defer. Usertags are now: not-upstream upstream-199-defer. > tag 551630 fixed-upstream Bug #551630 [grub-efi] grub-efi: when grub fails to load initrd it deas not say where it searched Added tag(s) fixed-upstream. > usertag 632598 not-upstream Bug#632598: grub-mkconfig: should set safer permissions even when hashed passwords are found There were no usertags set. Usertags are now: not-upstream. > usertag 461851 not-upstream Bug#461851: Several improvements to /etc/grub.d/05_debian_theme Usertags were: upstream-199-defer. Usertags are now: not-upstream upstream-199-defer. > usertag 654727 not-upstream Bug#654727: grub2: non-standard gcc/g++ used for build (gcc-4.5) There were no usertags set. Usertags are now: not-upstream. > usertag 651512 not-upstream Bug#651512: grub-pc: debconf's 'grub/install_devices' refers to device IDs while debconf shows device names There were no usertags set. Usertags are now: not-upstream. > reassign 646415 os-prober Bug #646415 [grub-ieee1275] grub-ieee1275: system hang on G4 cube when running /usr/bin/os-prober (triggered during update-grub) Bug reassigned from package 'grub-ieee1275' to 'os-prober'. Bug No longer marked as found in versions grub2/1.99-12. > tag 641801 fixed-upstream Bug #641801 [grub-pc] grub: grub-mkpasswd-pbkdf2 HANGS when run with root user Added tag(s) fixed-upstream. > tag 624263 fixed-upstream Bug #624263 [grub-pc] grub-pc: stuck in grub-mkdevicemap at configure time Added tag(s) fixed-upstream. > usertag 562672 not-upstream Bug#562672: grub-common: Packages depending on grub can't be used in live-helper: "cannot find a device for /" Usertags were: upstream-199-defer. Usertags are now: not-upstream upstream-199-defer. > tag 632408 fixed-upstream Bug #632408 [grub-pc-bin] grub-pc-bin: fd0 read error Added tag(s) fixed-upstream. > usertag 633746 not-upstream Bug#633746: grub-pc should suggest or recommend xorriso There were no usertags set. Usertags are now: not-upstream. > tag 639931 fixed-upstream Bug #639931 [grub-pc] [grub2] "update-grub" adds line to "multiboot" with Xen kernel Added tag(s) fixed-upstream. > usertag 645603 not-upstream Bug#645603: grub Debian package does not seem to take preseeding into account There were no usertags set. Usertags are now: not-upstream. > tag 646788 fixed-upstream Bug #646788 [grub-common] grub-mkrescue: --xorriso=... broken Added tag(s) fixed-upstream. > reassign 649217 os-prober Bug #649217 [grub-common] grub-common: grub-mkconfig, an os-prober part generates multiple menuentry for same os Bug reassigned from package 'grub-common' to 'os-prober'. Bug No longer marked as found in versions grub2/1.99-12. > tag 564252 fixed-upstream Bug #564252 [grub-pc] grub-pc: non blocking error no such disk Added tag(s) fixed-upstream. > tag 595059 fixed-upstream Bug #595059 [grub2] grub2: GRUB displays a message like "cdrom: read error" at startup Added tag(s) fixed-upstream. > usertag 630224 not-upstream Bug#630224: grub-pc-bin: confusing package description There were no usertags set. Usertags are now: not-upstream. > tag 463107 fixed-upstream Bug #463107 [grub-pc] support for reading encrypted lvm partitions Added tag(s) fixed-upstream. > usertag 543376 not-upstream Bug#543376: make the grub packages non conflicting Usertags were: upstream-199-defer. Usertags are now: not-upstream upstream-199-defer. > usertag 592706 not-upstream Bug#592706: grub-pc: provide GRUB_SAVEDEFAULT in /etc/default/grub Usertags were: upstream-199-defer. Usertags are now: not-upstream upstream-199-defer. > usertag 623577 not-upstream Bug#623577: please allow grub-pc/install_devices_empty warning to be disabled There were no usertags set. Usertags are now: not-upstream. > tag 623975 fixed-upstream Bug #623975 [grub2] grub2: Add support for setkey! Added tag(s) fixed-upstream. > usertag 539648 not-upstream Bug#539648: rescue formatter option for grub2 switchover There were no usertags set. Usertags are now: not-upstream. > tag 533898 fixed-upstream Bug #533898 [grub-common] grub-mkdevicemap gives wrong alias for device on powerpc Added tag(s) fixed-upstream. > tag 549905 fixed-upstream Bug #549905 [grub-pc] grub seeks the floppy at boot time Added tag(s) fixed-upstream. > tag 590884 fixed-upstream Bug #590884 [grub-pc] grub-pc: upgrading with vmlinuz-2.6.32-5-amd64 kernel fails on device detection Added tag(s) fixed-upstream. > -- Stopping processing here. Please contact me if you need assistance. -- 590884: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590884 624263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624263 646788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646788 549905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=549905 463107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=463107 646415: http://bugs.debian.org/cgi-bin/bugreport.cgi?bu
Re: Fwd: Debian-Stable and KDE crashes
Hi, debian-boot it's all about debian installer development and not about desktop applications experience. So it's out of scope. I guess the right thing to do it's to contribute with improvements/information, if possible, in the bug reports to the affected package. In case of discussions please use the proper mailing lists, in Debian [1] and/or in upstream if it's about development and not packaging/integration in Debian. 1 - http://lists.debian.org/ Just my 0,02 €. -- Melhores cumprimentos/Best regards, Miguel Figueiredo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f1155df.5070...@debianpt.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 655841 gnash Bug #655841 [debian-installer] Please remove Gnash from default Debian install, as it crashes Bug reassigned from package 'debian-installer' to 'gnash'. Bug No longer marked as found in versions debian-installer/20110106+squeeze3. > thanks Stopping processing here. Please contact me if you need assistance. -- 655841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132653720511628.transcr...@bugs.debian.org
Re: Fwd: Debian-Stable and KDE crashes
Upstream package is clearly unstable in this case, and no reason to push it into debian stable, esp. for default install. Pushing "gnash" is like pushing an alpha version of pulseaudio into Debian-stable. (something that Fedora does happily, but simply NOT appropriate behavior for Debian to do) "gnash" package is unstable, and will probably not be fixed anytime soon. (upstream project had last release 10 months ago, which points at slow development) -- -Alexey Eromenko "Technologov" -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOJ6w=EvOvo=3cza1mygar8_uoc2rk4hemathy8oc1y2qrh...@mail.gmail.com
Processed: Re: Bug#655841: Please remove Gnash from default Debian install, as it crashes
Processing commands for cont...@bugs.debian.org: > reassign 655841 tasksel Bug #655841 [gnash] Please remove Gnash from default Debian install, as it crashes Bug reassigned from package 'gnash' to 'tasksel'. > thanks Stopping processing here. Please contact me if you need assistance. -- 655841: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132654739825188.transcr...@bugs.debian.org
Bug#655841: Please remove Gnash from default Debian install, as it crashes
> gnash is not only installed with KDE, from what I see as its > installation is triggerred by the desktop task, that's common to KDE > and GNOME, at least. > > It is triggerred by "browser-plugin-gnash". > > What do you suggest as alternative? I don't think it is a good idea to > not provide any flash-enabled web browser. Unfortunately the Free Software community has not yet developed stable flash player, therefore I suggest to avoid installing _unstable_ software by default. The rule of thumb is to avoid regressions in general, and crashes in particular. If a particular (even necessary) component is not ready it should not be pushed into a default desktop installation. It can be provided with a "BETA" or "technical preview" label for advanced users to install manually. In many cases, the lack of flash player will _improve_ user experience: www.amd.com and www.google.com/finance are two examples; If they detect browser without flash, they give the user static version of the content. With gnash -- it just crash. Therefore I suggest to remove "gnash" from the "desktop-task", and put a "BETA" tag in the package description for the near point release (6.0.4). And later make some serious review of this package for Wheezy, before deciding to re-include it by default. (I will help with the testing) -- -Alexey Eromenko "Technologov" -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOJ6w=HNs=EBz70mDqbgquykn=jlwpigbayjzo6b6cvkcee...@mail.gmail.com
Bug#655841: Please remove Gnash from default Debian install, as it crashes
Quoting Alexey Eromenko (al4...@gmail.com): > Unfortunately the Free Software community has not yet developed stable > flash player, therefore I suggest to avoid installing _unstable_ > software by default. > > The rule of thumb is to avoid regressions in general, and crashes in > particular. Thank you for explaining me how software development works. I wasn't aware about this. I thought the point was constantly making systems crash. > > If a particular (even necessary) component is not ready it should not > be pushed into a default desktop installation. It can be provided with > a "BETA" or "technical preview" label for advanced users to install > manually. > > In many cases, the lack of flash player will _improve_ user > experience: www.amd.com and www.google.com/finance are two examples; > If they detect browser without flash, they give the user static > version of the content. With gnash -- it just crash. I have a small intuition that some people might disagree, here. signature.asc Description: Digital signature
Bug#655579: debian-installer: Unable to perform an installation : USB-input devices unusable
Hi, from the info you supplied (thanks!) from a previous installation it seems the keyboard uses module hid-apple. I have checked kernel-wedge package and that module it's already included in the input modules [1] for the installer's kernel. One thing you can try is to connect a 2nd keyboard and check if the module it's indeed loaded when you connect the keyboard. dmesg should recognize the keyboard when you plug it and lsmod shoud report the module hid-apple. 1 - http://anonscm.debian.org/gitweb/?p=d-i/kernel-wedge.git;a=blob;f=modules/input-modules;h=62fc503cfa7753bb544d89cfd4332e75091d5717;hb=HEAD -- Melhores cumprimentos/Best regards, Miguel Figueiredo -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f119b3c.8090...@debianpt.org
Bug#655579: debian-installer: Unable to perform an installation : USB-input devices unusable
Hi, Thank you for your mail. I tried your suggestion (from your previous mail), here the results : - used distribution - today's daily build of wheezy-netinst CD - tried with hitting F6 twice at the very first screen, before choosing an install method, the monitor screen just flickered. I then went as usual to "Advanced options"-"Graphical expert install", but again the same - neither the keyboard, nor the mouse worked. - restarted, booted from the CD again, but then went to "menu"-option, and used the boot-prompt directly : boot: install expertgui There, we have the keyboard alive again :D So, it worked finally, at least in the good old ncurses-like installer ;) So, I'm starting to think - could be "X" fault that the input devices do not work at the usual "graphical expert install " ? The keyboard works at the first menu-screen, so one can choose the way of installation; it then works from the "menu"-option and typing "install expertgui" at the boot-prompt, but not elsewhere ? Hm... One more clarification, Miguel - the reports I attached previously were not from my installed Debian, but from the console of the Squeeze 6.0.3-DVD ;) Let me know if I can or should provide any additional information/reports, thank you again for your support, Best Regards On 01/14/2012 05:11 PM, Miguel Figueiredo wrote: Hi, from the info you supplied (thanks!) from a previous installation it seems the keyboard uses module hid-apple. I have checked kernel-wedge package and that module it's already included in the input modules [1] for the installer's kernel. One thing you can try is to connect a 2nd keyboard and check if the module it's indeed loaded when you connect the keyboard. dmesg should recognize the keyboard when you plug it and lsmod shoud report the module hid-apple. 1 - http://anonscm.debian.org/gitweb/?p=d-i/kernel-wedge.git;a=blob;f=modules/input-modules;h=62fc503cfa7753bb544d89cfd4332e75091d5717;hb=HEAD -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f11a130.5010...@gmx.de
Bug#655579: debian-installer: Unable to perform an installation : USB-input devices unusable
Hi, Miguel, Here the results from the other test, with a second keyboard : - I used an old Samsung "Pleomax" wired usb-keyboard (although it is always reported as "chesen") - the Apple-keyboard was unplugged before booting off the wheezy-cd - when reached the main menu screen, I went again to the "graphical expert install" to see if the samsung-keyboard would work - no, same as with the apple-keyboard - restarted, booted from the cd and went to "menu", so I could have the possibility to switch to a console - plugged-in a USB-stick in order to save reports on, ran "dmesg" and saw the stick was seen - plugged the Apple-keyboard and ran "dmesg" again - the apple keyboard was seen as well Please, find attached the logs from dmesg and lsmod. I now think that the issue could be narrowed down to the "graphical"-installers, because usb-devices seem to work pretty normal outside of them, that is : - seen by the BIOS fist, during POST - you can choose F8 in oder to tell BIOS what device to boot from - you can choose an installation method from the first screen of the debian-cd - you can type in a way of installation at the "menu"-boot prompt But, as soon as a grahical install has loaded (in my case - the "graphical expert install" ), input devices just freeze there :) Waiting forward to hearing from you soon & thanx a lot, Best Regards [0.783064] usbcore: registered new interface driver usbfs [0.783083] usbcore: registered new interface driver hub [0.803311] usbcore: registered new device driver usb [0.828064] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [0.828067] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.828068] usb usb1: Product: EHCI Host Controller [0.828070] usb usb1: Manufacturer: Linux 3.1.0-1-amd64 ehci_hcd [0.828072] usb usb1: SerialNumber: :00:1a.7 [0.852025] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [0.852027] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.852029] usb usb2: Product: EHCI Host Controller [0.852030] usb usb2: Manufacturer: Linux 3.1.0-1-amd64 ehci_hcd [0.852032] usb usb2: SerialNumber: :00:1d.7 [0.896971] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [0.896973] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.896974] usb usb3: Product: UHCI Host Controller [0.896976] usb usb3: Manufacturer: Linux 3.1.0-1-amd64 uhci_hcd [0.896977] usb usb3: SerialNumber: :00:1a.0 [0.897187] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [0.897189] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.897191] usb usb4: Product: UHCI Host Controller [0.897193] usb usb4: Manufacturer: Linux 3.1.0-1-amd64 uhci_hcd [0.897194] usb usb4: SerialNumber: :00:1a.1 [0.897398] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001 [0.897400] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.897402] usb usb5: Product: UHCI Host Controller [0.897403] usb usb5: Manufacturer: Linux 3.1.0-1-amd64 uhci_hcd [0.897405] usb usb5: SerialNumber: :00:1a.2 [0.897579] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001 [0.897581] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.897583] usb usb6: Product: UHCI Host Controller [0.897584] usb usb6: Manufacturer: Linux 3.1.0-1-amd64 uhci_hcd [0.897586] usb usb6: SerialNumber: :00:1d.0 [0.897772] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001 [0.897774] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.897776] usb usb7: Product: UHCI Host Controller [0.89] usb usb7: Manufacturer: Linux 3.1.0-1-amd64 uhci_hcd [0.897779] usb usb7: SerialNumber: :00:1d.1 [0.897964] usb usb8: New USB device found, idVendor=1d6b, idProduct=0001 [0.897966] usb usb8: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.897968] usb usb8: Product: UHCI Host Controller [0.897969] usb usb8: Manufacturer: Linux 3.1.0-1-amd64 uhci_hcd [0.897971] usb usb8: SerialNumber: :00:1d.2 [1.380010] usb 3-2: new low speed USB device number 2 using uhci_hcd [1.556967] usb 3-2: New USB device found, idVendor=0a81, idProduct=0101 [1.556969] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [1.556971] usb 3-2: Product: USB Keyboard [1.556973] usb 3-2: Manufacturer: CHESEN [1.595144] input: CHESEN USB Keyboard as /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.0/input/input0 [1.595188] generic-usb 0003:0A81:0101.0001: input,hidraw0: USB HID v1.10 Keyboard [CHESEN USB Keyboard] on usb-:00:1a.0-2/input0 [1.624017] input: CHESEN USB Keyboard as /devices/pci:00/:00:1a.0/usb3/3-2/3-2:1.1/input/input1 [1.624066] generic-usb 0003:0A81:0101.0002: input,hidraw1: USB HID v1.10 Device [CHES
Bug#655841: Please remove Gnash from default Debian install, as it crashes
On Sat, Jan 14, 2012 at 8:42 AM, Alexey Eromenko wrote: >> gnash is not only installed with KDE, from what I see as its >> installation is triggerred by the desktop task, that's common to KDE >> and GNOME, at least. >> >> It is triggerred by "browser-plugin-gnash". >> >> What do you suggest as alternative? I don't think it is a good idea to >> not provide any flash-enabled web browser. > > Unfortunately the Free Software community has not yet developed stable > flash player, therefore I suggest to avoid installing _unstable_ > software by default. lightspark is an alternative. Of course, it's also experimental, but who knows, it may be a bit more stable/complet at this point? I haven't really looked into it. Just something worth considering... Best wishes, Mike -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CANTw=MMv5wMCPOK_zhhYNMxEyn0qNDvSJ4206ZOZ25e=e9_...@mail.gmail.com
Bug#655841: Please remove Gnash from default Debian install, as it crashes
Alexey Eromenko wrote: > Default Debian-6 KDE installs "gnash", an extremely unstable > component, that constantly crashes KDE Konqueror, when user accesses > any flash-enabled website (such as www.amd.com). Wouldn't that be a bug in konqueror-nsplugins? No plugin should be able to crash the browser it's running in; at least chromium and I think firefox/iceweasel deal with crashing plugins. Also, #549309 seems to suggest this only affects konqueror. Since the KDE task also includes iceweasel, gnash should work (as well as it ever does) there. -- see shy jo signature.asc Description: Digital signature
Bug#655841: Please remove Gnash from default Debian install, as it crashes
Michael Gilbert wrote: > lightspark is an alternative. Of course, it's also experimental, but > who knows, it may be a bit more stable/complet at this point? I > haven't really looked into it. Just something worth considering... The end game, which I am increasingly sure will happen by the next stable release, is going to be Debian shipping without flash in the default desktop installs. Really the only blocker is that users have to know to go to http://youtube.com/html5 to enable non-flash videos. -- see shy jo signature.asc Description: Digital signature
Bug#655841: Please remove Gnash from default Debian install, as it crashes
browser-plugin-gnash from backports doesn't make konqueror crash anymore so someone could identify what changes fix that and include them in 6.0.4. I'm not sure to be able to do that and upstream is pretty dead especially about KDE things. Patches welcome. By the way on KDE I guess it should be more appropriate using konqueror-plugin-gnash (KPARTS plugin) which is unmaintained upstream, missing implementations, more failures. If it worked enough, it could be added to KDE install. Feedbacks from KDE users welcome. Patches as well. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120114185655.GA21195@phenomenon
Bug#655099: Reopen - issue still present (Re: Bug#655099 closed by Miguel
Figueiredo ()) Reply-To: In-Reply-To: On Tue, Jan 10, 2012 at 09:24:15PM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the installation-reports package: > > #655099: installation-reports: amd 64 install freezes in partitioning step > > It has been closed by Miguel Figueiredo . > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Miguel Figueiredo > by replying to this email. > [...] > Fixed with linux-image-3.1.8. This issue must be reopened, it has not been fixed. Allow me to elaborate: The orignal issue is that the squeeze install freezes in the partitioning step (see messages #5, #10 and #15). As far as I can see, nothing has been done to address this. So this problem still persists. I still can not install squeeze. During my attempts to find a work-around, I also found that the testing installer shows the same problem (see message #20). Mr. Figueiredo suggests in messages #25 and #30 that the issue may be due to version mismatch between kernel and modules. But this is probably unrelated. The error message observed by Mr. Figueiredo in his installation attempt is not present in the logs from my installation attempt. And the version number mismatch in the current testing installer can certainly not explain the same error in the squeeze installer. Further, after the issue was closed, I have now tried the most recent testing installer (debian-testing-amd64-netinst.iso, dated 20110114 15:10). The issue is still present there. Installation freezes in the partitioning step, with the same message - "No volume groups found". To sum it up: The issue is still there, and the suggested explanation and fix may have nothing to do with the issue. Please reopen. And let me know if there is anything I can do, or any information I can give, to help resolve this issue. With kind regards Asbjørn Sæbø -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120114203929.ga22...@stud.ntnu.no
Bug#655099: Ubuntu 11.10 installer works
I have now also tried installing Ubuntu 11.10 on this system. That works, which indicates that the HW should be OK. Asbjørn Sæbø -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120114204133.gb22...@stud.ntnu.no
Bug#655923: Missing xhci-hcd module in installer
Package: kernel-wedge Version: 2.74+squeeze3.1 Severity: important Tags: d-i patch squeeze Another addition needed for squeeze: --- a/modules/usb-modules +++ b/modules/usb-modules @@ -1,4 +1,5 @@ ehci-hcd ? ohci-hcd ? uhci-hcd ? +xhci-hcd ? usbcore ? --- END --- This has already been fixed in wheezy/sid. Ben. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kernel-wedge depends on: ii debhelper 8.9.14 ii make 3.81-8.1 kernel-wedge recommends no packages. kernel-wedge suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120114205037.7002.85769.reportbug@deadeye
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 634799 fixed-upstream Bug #634799 [grub-pc] grub-pc: grub2 claims hurd-i386's grub.cfg is out of partition Added tag(s) fixed-upstream. > tag 584499 fixed-upstream Bug #584499 [grub-pc] Setting up grub-pc hangs forever Added tag(s) fixed-upstream. > tag 614548 fixed-upstream Bug #614548 [grub2] Grub installation on mdadm raid-0 array fails Added tag(s) fixed-upstream. > tag 612692 fixed-upstream Bug #612692 [grub-pc] grub-setup segfaults when presented with partitioned raid Added tag(s) fixed-upstream. > tag 644982 fixed-upstream Bug #644982 [grub-common] grub-common: fails to detect ext3: grub-probe -t fs --device /dev/md0 => error: out of disk Added tag(s) fixed-upstream. > reassign 651531 os-prober Bug #651531 [grub2] grub2: missing system Windows XP Bug reassigned from package 'grub2' to 'os-prober'. > usertag 634495 not-upstream Bug#634495: FW: Important important important Installation failure: FW: (Failed to load grub package) User is phco...@gmail.com There were no usertags set. Usertags are now: not-upstream. > -- Stopping processing here. Please contact me if you need assistance. -- 634495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634495 584499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584499 651531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651531 644982: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644982 614548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614548 634799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=634799 612692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.132657528026950.transcr...@bugs.debian.org
Bug#655099: It seems to b a parted bug
Doing some searching, I found bug #602568, which seems to have much in relation with this issue. Taking some hints from there, I found that the issue seems to be a parted problem related to the small additional USB stick mentioned in my message #1 as "Other USB stick". Trying to use parted from the testing-installer, I get the error messages below, reporting a bug in parted. Without this USB stick present, installation of squeze (where I originally met the problem) progresses past partitioning as expected, without problems. I.e.: I am able to partition, format partitions and choose mount points. Some of the issues raised in 602568 still seems to be open, see message #81 in that thread. The failure of parted is not detected or properly reported by the installer (or the layers between the installer and parted). That must be fixed. There is also a new parted bug, it seems. As in #605286 there is an assertion, but it is in another function. Please advice on how to proceed: Should this bug be changed to some parted package, or should I open a coupl of new bugs? With kind regards Asbjørn S. Error message using parted in debian installer on small USB stick: -- Installer-image: debian-testing-amd64-netinst.iso, dated 20120114-15:10 Method: During installation, entered below command from a console. Command: parted /dev/sdd unit co print unit s print Output: You found a bug in GNU Parted! Here's what you have to do: Don't panic! The bug has most likely not affected any of your data. Help us to fix this bug by doing the following: Check whether the bug has already been fixed by checking the last version of GNU Parted that you can find at: http://ftp.gnu.org/gnu/parted/ Please check this version prior to bug reporting. If this has not been fixed yet or if you don't know how to check, please visit the GNU Parted website: http://www.gnu.org/software/parted for further information. Your report should contain the version of this release (2.3) along with the error message below, the output of parted DEVICE unit co print unit s print and the following history of commands you entered. Also include any additional information about your setup you consider important. Assertion (head_size <= 63) at ../../../libparted/labels/dos.c:662 in function probe_partition_for_geom() failed. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120114230339.ga22...@stud.ntnu.no
Bug#655841:
Status update: Testing of Gnash. Platform: Debian 6.0.3. (only "main" repo) Test 1 : YouTube http://www.youtube.com/watch?v=a4NCnH7RPZY&feature=g-logo&context=G2ee8eb5FOAA IceWeasel 3.5: WORKS Google Chromium 6: WORKS Konqueror: CRASH Test 2 : Google Finance http://www.google.com/finance?q=EURUSD IceWeasel 3.5: FAILS (gray rectangle) Google Chromium 6: FAILS (gray rectangle) Konqueror: CRASH Bottom line: Removing "Gnash" gives at least static data on Google Finance, and solves konqueror crash, at the expense of YouTube (with IceWeasel and Chromium). Removing "konqueror-nsplugins" solves konqueror crash, but does not solve the Google Finance issues with Gnash. In essence: We have 2 bugs with "gnash": Konqueror browser and Google finance incompatibility. "Maturity problems" -- -Alexey Eromenko "Technologov" -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOJ6w=E_q4E9tRk4fk9CH=Fket==xw7zx5dal6u_noihl_a...@mail.gmail.com
