![]() |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
EDIT: Hm, gizmo-project depends on libssl0.9.7, which comes from: Code:
libssl0.9.7: Quote:
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
Opening Control panel > Panels > Status Bar > Clicking OK brings back my setup after a few seconds. >> No reboot necessary My applets: Large statusbar clock (Maybe less often with alarms in Large statusbar clock disabled ?? ) (older) Advanced power Load applet Quick clip Advanced backlight control (plain OS 43-7 cloned to int. mmc) |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Can you get rid of large statusbar clock at least temporarily and try to reproduce? We know that's buggy so any crashes while it's enabled don't really tell us anything interesting.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
Also, these crashes aren't that common, my feeling is that they have increased lately. ( Also File manager hasn't loaded for a while until I changed my ext mmc yesterday. This has happened before. Is there any knowledge about that? It has happened when I have a LOT of files in some folders on my mmc:s, which makes the file manager take a LONG time to update, AND (or?) have a LOT of apps installed.) ( My main point was that rebooting isn't necessary.) |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
I once had a bug where both internal and external cards had unmounted, and file manager only displayed 'bluetooth'. I don't remember why it did that though, it was a while ago. Like a month.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Since instalation of Diablo community SSU, I get a false "Updates Available" prompt every week or so. Eight apps are updated, but they are same version.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
i see something similar because i have both extras and extras-devel active, and both contain a copy of the gconf manager. So when one of them fails a refresh (usually -devel) i get a "updates waiting" indicator that is just about the same version but from a different repository. |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
Did you at any point install the community ssu using the testing repository or similar? |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Does the application manager log say anything interesting?
There seems to be something hinky happening with Diablo extras at the moment. I get this complaint from apt-get update: Code:
W: GPG error: http://repository.maemo.org diablo Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY E40DC434616730BD |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
will diablo-turbo be pushed via CSSU at some point?
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
1 Attachment(s)
Quote:
I'd be happy to apply some of the patches floating around in b.m.o marked for diablo - I just don't know how to return the built packages to the community. For example, I just applied the control panel patch from bug 3470 and built a package in scratchbox (1.0.17). For those who are interested, I just used: Code:
apt-get source hildon-control-panel |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
1 Attachment(s)
Quote:
Once that was done, I used the patch found in BMO 2710 to eliminate the "invalid source" dialog box. Finally, I built the package in my scratchbox (1.0.17), using similar steps to those used for the control panel. I did need to do "fakeroot apt-get install libapt-pkg-dev" in order to get the package to build, but this should not be relevant for installation, since it is a compile-time dependency only. I've also attached the resulting deb right here. If there is a better way to distribute this stuff, please let me know. ETA: According to the author of the patch, Code:
echo 'red-pill-show-legalese 0' >>~/.osso/hildon-application-manager |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
i got this error - packages 404 not found.
what should i do.? i've added the stable version to tha repo. disabled the testing repo. but its failed to refresh. what to do.? |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Removed -testing from repo and upgraded. Good so far. Opera11 is sweet as well.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
So why is an update available for the SSU package?
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Do not see one here.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
OK. In App Manager, the info shows the package status as "Broken and cannot update"; the installed and available versions are the same.
Not sure what might have changed, or when. The only recent config change was the 0.5.6. update to ASUI. (Now at 0.5.7, but the SSU "update" was flagged at the same time the ASUI update was.) |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
It's been showing up for me for a while too. I've assumed it was something to do with the DiabloTurbo kernel, though I'm using ASUI too.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
You do not happen to have both community ssu and -testing enabled at the same time?
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Nope. It's pretty standard: Extras, Extras-devel, Community SSU, and the 3 Nokia ones.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
I did have community ssu-testing in my catalog, but on disabling it, I'm still seeing the "broken" update.
I haven't installed Diablo Turbo (yet). |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
This is really good news. I'm going to upgrade as soon as I get home from work.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Anyone having the "broken cssu update" AFTER installing DiabloTurbo, is because it doesn't installed osso-sofware-version-unlocked
If this is the case, install osso-software-version-rx??-unlocked (apt-get install osso-software-version-rx??-unlocked). (where ??=34 for N800, 44 for N810, 48 for N810-WiMax) to fix the problem. |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Thanks, maacruz. I think I'd tried that once before. On the N810 I get a bunch of package errors for dbus, dbus-1-utils, gconf2, libdbus-1-3, libgcon2-6, mini-rc, sysvinit, osso-pdf-viewer. Something is depending on older versions than are (or will be) installed. Maybe I'll poke around some more, but I'd rather not mess it up more.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
Download directly the package from the repo: http://repository.maemo.org/communit...0.33-1_all.deb Remove the osso-software-version-rx44 package by hand (dpkg -r osso-software-version-rx44) And install the new one by hand (dpkg -i osso-software-version-rx44-unlocked_5.2010.33-1_all.deb) That will solve your problem. |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
I wonder if I'm the only person with N800+CSSU+ASUI but not Diable Turbo.
Could ASUI have linked to one of the things DT required that, in turn, required the osso-unlocked package? |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
nope, i have yet to go turbo (seems all too easy to mess up the install).
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
Quote:
Just download all the deb files, apt-get install osso-software-version-rx34-unlocked, dpkg -i *, dpkg -i sysvinit_2.85-22.osso15-dt1_armel.deb and reboot. Can't go wrong. |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
the thread on the subject suggests otherwise.
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
Last Nokia SSU was much much worse. Rest of problems were the "phantom" update, for users who don't like following the instructions, and one incompatibility with boingo-mobile, already fixed. |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Can't install CSSU because of a conflicting package called libqt-test. What apps are using this and should I remove it to install CSSU.
Thanks in advance. |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
Quote:
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
I think he has an N900!
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Yeah here it is.
hildon-application-manager 2.2.71 connected to 792019a9-0b00-41c5-9cb0-990488d63ab1 connected to 792019a9-0b00-41c5-9cb0-990488d63ab1 apt-worker: domain change: osso-pdf-viewer (nokia-system -> unsigned) apt-worker: domain change: hildon-status-menu (nokia-system -> unsigned) apt-worker: domain change: maemo-statusmenu-fmtx (nokia-system -> unsigned) apt-worker: domain change: osso-applet-notificationlight (nokia-system -> unsigned) apt-worker: domain change: libvte4 (nokia-system -> unsigned) apt-worker: domain change: camera-ui (nokia-system -> unsigned) apt-worker: domain change: libqt4-translations (nokia-system -> unsigned) apt-worker: domain change: libvte-common (nokia-system -> unsigned) |
Re: [Announce] First "stable" Diablo community SSU released and call for participation
Quote:
|
Re: [Announce] First "stable" Diablo community SSU released and call for participation
:S damn, Just noticed this is Maemo 4 xD. wrong post :(.
|
All times are GMT. The time now is 09:07. |
vBulletin® Version 3.8.8