Bug#973715: fwupd-amd64-signed: apt-listbugs keep listing this bug as grave even tho it seems is fixed
Package: fwupd-amd64-signed Followup-For: Bug #973715 X-Debbugs-Cc: paj...@gmail.com fwupd-amd64-signed: apt-listbugs keep listing this bug as grave even tho it seems is fixed Im not sure why, but i believe is because it is fixed in a different package -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fwupd-amd64-signed depends on: pn fwupd fwupd-amd64-signed recommends no packages. fwupd-amd64-signed suggests no packages.
Bug#951588: kontact: akonadi is not operational
Package: kontact Version: 4:19.08.3-1 Severity: grave Justification: renders package unusable Application: Akonadi Control (akonadi_control), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff192558800 (LWP 1433258))] Thread 5 (Thread 0x7ff189e1f700 (LWP 1433262)): #0 0x7ff195d5abef in __GI___poll (fds=0x7ff1800021e0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff19510710e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff19510722f in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff1962e381b in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff19628c71b in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff1960cd731 in QThread::exec() () from /usr/lib/x86_64-linux- gnu/libQt5Core.so.5 #6 0x7ff196bf14e6 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7ff1960ce8b2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff195c52fb7 in start_thread (arg=) at pthread_create.c:486 #9 0x7ff195d651af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7ff18a703700 (LWP 1433261)): #0 0x7ff195d5abef in __GI___poll (fds=0x55fdcd713ff0, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff19510710e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff195107473 in g_main_loop_run () from /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0 #3 0x7ff18b9c89e6 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #4 0x7ff19512fd7d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff195c52fb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff195d651af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff18af04700 (LWP 1433260)): #0 0x7ff195d5abef in __GI___poll (fds=0x55fdcd6ffb90, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff19510710e in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff19510722f in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff195107281 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff19512fd7d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff195c52fb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff195d651af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff1912c6700 (LWP 1433259)): #0 0x7ff195d5abef in __GI___poll (fds=0x7ff1912c5ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff194ff1cf7 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff194ff391a in xcb_wait_for_event () from /usr/lib/x86_64-linux- gnu/libxcb.so.1 #3 0x7ff191eabca0 in ?? () from /usr/lib/x86_64-linux- gnu/libQt5XcbQpa.so.5 #4 0x7ff1960ce8b2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff195c52fb7 in start_thread (arg=) at pthread_create.c:486 #6 0x7ff195d651af in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff192558800 (LWP 1433258)): [KCrash Handler] #6 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #7 0x7ff195c90535 in __GI_abort () at abort.c:79 #8 0x55fdcbc662e2 in akMessageHandler (type=QtFatalMsg, msg=..., context=...) at ./src/shared/akdebug.cpp:205 #9 akMessageHandler (type=, context=..., msg=...) at ./src/shared/akdebug.cpp:194 #10 0x55fdcbc6834e in (anonymous namespace)::RemoteLogger::dbusLogger (type=QtFatalMsg, ctx=..., msg=...) at ./src/shared/akremotelog.cpp:178 #11 0x7ff1960c64b1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7ff1960c65c9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7ff196096a44 in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x55fdcbc3c4e1 in AgentManager::AgentManager (this=0x7ffd636395f0, verbose=, parent=) at /usr/include/x86_64-linux- gnu/qt5/QtCore/qlogging.h:91 #15 0x55fdcbc3e374 in main (argc=, argv=) at ./src/akonadicontrol/main.cpp:76 [Inferior 1 (process 1433258) detached] -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kontact depends on:
Bug#875547: animals: can't be played as non root user
On Mon, Apr 16, 2018 at 7:34 PM, Markus Koschany wrote: > Control: tags -1 pending > > Dear maintainer, > > I've uploaded a new revision of animals versioned as 201207131226-2.1 > that addresses the issue. Please find attached the debdiff. > Thanks for uploading a fix!
Bug#840342:
Control: fixed -1 304.134-1 thanks Whatever was broken, its fixed now for me I have tried sid version with kernel 4.8, not 4.9 yet I tried ace-freecell and glxgears and it works How can I reproduce your problem David?
Bug#836614:
This is the second time since I got this package 3 years ago that my mentor has to make an upload, so Im not sure hes around :) I messaged him privately a week ago, but im also putting it here in case somebody else can review the fix in this package since the severity has been raised Im sorry is not not a one liner to make easier the review, but I think its not very large fix either. I did switch to dh which I believe auto applies the hardening I also did some extra maintenance like dropping the -dbg package which I believe it auto generates the new -dbgsym packages you can review it here: https://mentors.debian.net/debian/pool/main/a/animals/ animals_201207131226-2.dsc https://mentors.debian.net/package/animals Thanks!
Bug#826712: im a little too late to the party
On Wed, Jun 15, 2016 at 2:21 PM, Luca Boccassi wrote: > Wouldn't have made a difference, a package in non-free cannot block the > migration of a package in the main archive. > And we wouldn't want to block the migration of the kernel even if it > would be possible. > Oh, I didnt check it and assume this was the package migrating and breaking Thanks for your work! Lets offer some of our crops to the ftp masters so this and the rest of the nvidia drivers make it soon to the archive :)
Bug#800585: cheese does not specify all dependencies it require
Package: cheese Version: 3.16.1-1 Followup-For: Bug #800585 probably related, im getting ** Message: cheese-application.vala:211: Error during camera setup: One or more needed GStreamer elements are missing: cluttervideosink. starting cheese -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages cheese depends on: ii cheese-common 3.16.1-1 ii gnome-video-effects0.4.1-2 ii libc6 2.19-22 ii libcanberra-gtk3-0 0.30-2.1 ii libcheese-gtk233.16.1-1 ii libcheese7 3.16.1-1 ii libclutter-1.0-0 1.24.0-1 ii libclutter-gtk-1.0-0 1.6.4-1 ii libgdk-pixbuf2.0-0 2.32.0-1 ii libglib2.0-0 2.44.1-1.1 ii libgnome-desktop-3-10 3.16.2-2 ii libgstreamer1.0-0 1.4.5-2 ii libgtk-3-0 3.16.6-1 Versions of packages cheese recommends: ii gnome-icon-theme3.12.0-1 ii gvfs1.24.2-1 ii hicolor-icon-theme 0.13-1 ii nautilus-sendto 3.8.2-1 ii yelp3.16.1-1 Versions of packages cheese suggests: ii gnome-video-effects-frei0r 0.4.1-2 -- no debconf information
Bug#783169: alternatives
There is this package from kde in debian called storageservicemanager that supposedly is able to sync google-drive folders. It didnt work to me be, maybe due to this same api shift from google. I dont know if it is as unmaintained upstream as this one (because if that is the reason, this has been deprecated for a while afaik) While not a drop in replacement, I was able to move all my files from google-drive to sparkleshare, which is packaged in debian and it is very easy to set up in your own server. It even allows you to save encrypted folders on the server very easily. You can find an script to help you prepare your server in the upstream website (which is not packaged afaik). I used preparing your server instead of installing it intentionally since it only creates a user in the server and allows to connect with it via a git-shell and nothing else the packaged version in the archive is 1.2 and upstream is version 1.4 Hope it helps somebody else ;) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766353:
>> b) It is (more than) a courtesy for users / developers who run testing > >I agree with that one, but it is too late now. >> e) Is there any problem of uploading libjpeg-progs just with the >>appropriate breaks/relationship? I think the RMs would have no >>problem accelerating this into testing. > This would be pointless since the bug was in libjpeg-turbo-progs and is now > fixed and is not more reproducible when starting from wheezy or current > testing. > > The number of users still having the broken libjpeg-turbo-progs is smaller > everyday. I had to fix this manually... I would had been thankful if I never had to dig into this bug. Why is too late? add the breaks/replace... remove it in some forthcoming upload in 6 months. Me think you can even break an specific version... so you could help those people with the broken package installed and no making it break the current version that is not broken... And that upload could be used to close this RC bug that is still open for the current version and needs to be fixed before jessie Thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#736964: [lightdm] Password is shown in cleart text while typing
Package: lightdm Followup-For: Bug #736964 Its happened to me too... I can help reproduce it if theres still doubt about this. Im not at my computer right now, but just ask and you shall receive... later Btw.. even tho autologin does not work... you can just press ok to login... no need to enter the password yet another time :) -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/4 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 lightdm depends on: ii adduser3.113+nmu3 ii consolekit 0.4.6-3+b1 ii dbus 1.7.10-2 ii debconf [debconf-2.0] 1.5.52 ii libc6 2.17-97 ii libgcrypt111.5.3-3 ii libglib2.0-0 2.36.4-1 ii libpam0g 1.1.3-9 ii libxcb11.10-2 ii libxdmcp6 1:1.1.1-1 ii lightdm-gtk-greeter [lightdm-greeter] 1.6.1-5 Versions of packages lightdm recommends: ii xserver-xorg 1:7.7+5 Versions of packages lightdm suggests: ii accountsservice 0.6.34-2 ii upower 0.9.23-2+b1 -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677416: This still happens
Just to notice that this still happens -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657281: src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free [was: Re: Bug#657281: Any news on this?]
ops... i totally forgot to resend this to release team... On Sat, Jan 26, 2013 at 1:36 PM, Neil McGovern wrote: > On Mon, Dec 17, 2012 at 12:42:14AM +0100, alberto fuentes wrote: >> Since its being a while without response and we are getting closer to >> release, i was thinking about requesting a wheezy-ignore for the bug or >> something to the release team >> > > I'm not happy adding an ignore tag if there isn't any evidence of > progress being made. > > (FWIW, contacting debian-release is useful if you want a ignore tag) > > Neil -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#657281: src/java/org/apache/fop/pdf/ sRGB Color Space Profile.icm is non-free [was: Re: Bug#657281: Any news on this?]
Sorry about that :) I did not blindly ping the bug. Since its being a while without response and we are getting closer to release, i was thinking about requesting a wheezy-ignore for the bug or something to the release team What do you think about that? On Sun, Dec 16, 2012 at 6:31 PM, Sylvestre Ledru wrote: > On 16/12/2012 14:04, alberto fuentes wrote: > > Any news on this? > > Still No :/ > > Next time, please provide some context in your email ;) > > > Sylvestre > > >
Bug#658352:
Hey steve, you tagged this as pending 26th sep. I wonder how are you doing and if you forgot about this bug ;)
Bug#656762:
hi! Can somebody of the gnome-team comment on the status of this, or at least know what do you plan to do about it? :) bugs upstream status are UNCONFIRM The debug mode for the window could be a workaround in debian, although i dont know the implications of setting the window to debug mode. Maybe somebody from gnome-team can comment on this too Thanks! PS: we are getting close to be able to release! Thanks for the good work!
Bug#558784: Request for wheezy-ignore for Bug#558784 apt: re-adds removed keys
This bug has been already tagges as squeezy-ignore... and there seems to not be enough interest in fixig it
Bug#672030:
Hey Giovanni, I was wondering if you have heard anything from upstream on this issue yet? :) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org