Bug#799057: general: After my laptop hung and reset KDE4 doesn't start
Hello Vitaly, Am 15.09.2015 um 12:43 schrieb root: > Package: general > Severity: important > > [long Xsession dump without any further info] I'm closing your report. The "general" pseudo package is not a support channel to help debug and sort problems out. Please use one of the available support channels for that: https://www.debian.org/support https://lists.debian.org/debian-user/ http://forums.debian.net/ irc://irc.oftc.net/debian Thanks, *t
Bug#799057: marked as done (general: After my laptop hung and reset KDE4 doesn't start)
Your message dated Wed, 16 Sep 2015 08:50:41 +0200 with message-id <55f91141.9030...@sourcepole.ch> and subject line Re: Bug#799057: general: After my laptop hung and reset KDE4 doesn't start has caused the Debian Bug report #799057, regarding general: After my laptop hung and reset KDE4 doesn't start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 799057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: general Severity: important Xsession: X session started for vitalych at Tue Sep 15 13:11:41 EEST 2015 localuser:vitalych being added to access control list openConnection: connect: No such file or directory cannot connect to brltty at :0 startkde: Starting up... Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kbuildsycoca4 running... kded(18333) BackendLoader::init: "/usr/lib/x86_64-linux-gnu/kde4/plugins" This backend is only for XRandR 1.1, your version is: 1 . 4 QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QString) Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QString) Object::connect: No such signal org::freedesktop::UPower::Device::Changed() Object::connect: No such signal org::freedesktop::UPower::Device::Changed() Object::connect: No such signal org::freedesktop::UPower::Device::Changed() QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.6' kactivitymanagerd(18350)/nepomuk (library): Could not find virtuoso to connect to. Aborting kded(18333)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. kwin(18365): ""fsrestore1" - conversion of "0,0,0,0" to QRect failed" kwin(18365): ""fsrestore2" - conversion of "0,0,0,0" to QRect failed" kwin(18365): ""fsrestore3" - conversion of "0,0,0,0" to QRect failed" kwin(18365): ""restore4" - conversion of "0,0,0,0" to QRect failed" kwin(18365): ""fsrestore4" - conversion of "0,0,0,0" to QRect failed" QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QCoreApplication::sendPostedEvents: Cannot send posted events for objects in another thread QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. OpenGL version string: 3.0 Mesa 10.3.2 OpenGL shading language version string: 1.30 Driver: Intel GPU class: Haswell OpenGL version: 3.0 GLSL version: 1.30 Mesa version: 10.3.2 X server version: 1.16.4 Linux kernel version: 3.16 Direct rendering: yes Requires strict binding:yes GLSL shaders: yes Texture NPOT support: yes Virtual Machine:no QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusObjectPath: invalid path "" plasma-desktop(18374)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instability plasma-desktop(18374)/libplasma Plasma::isPluginVersionCompatible: unversioned plugin detected, may result in instab
Re: Bug#799062: ITP: target-isns -- iSNS client for the Linux LIO iSCSI target
You may want to collaborate on the packaging with us. For LIO Target, there's a group created on Alioth. For open-iscsi, I and Christian Seiler are maintaining it. You may want to check with Christian about iSNS for the other package, open-isns, as IIRC it was split recently from the open-iscsi package. On Tue, 2015-09-15 at 15:39 +0300, Peter Pentchev wrote: > Package: wnpp > Severity: wishlist > Owner: Peter Pentchev > > * Package name: target-isns > Version : 0.5 > Upstream Author : Christophe Vu-Brugier > * URL : https://github.com/cvubrugier/target-isns > * License : GPL-2+ > Programming Lang: C > Description : iSNS client for the Linux LIO iSCSI target > > Target-isns is an Internet Storage Name Service (iSNS) client for > the > Linux LIO iSCSI target. It allows to register LIO iSCSI targets to > an > iSNS server. > . > The iSNS protocol is specified in > [RFC 4171](http://tools.ietf.org/html/rfc4171) and its purpose is to > make easier to discover, manage, and configure iSCSI devices. With > iSNS, iSCSI targets can be registered to a central iSNS server and > initiators can be configured to discover the targets by asking the > iSNS server. -- Given the large number of mailing lists I follow, I request you to CC me in replies for quicker response signature.asc Description: This is a digitally signed message part
Bug#799137: ITP: debian-astro -- Debian Astronomy Pure Blend Metapackages
Package: wnpp Severity: wishlist Owner: Ole Streicher X-Debugs-Cc: debian-devel@lists.debian.org,debian-as...@lists.debian.org,debian-ble...@lists.debian.org * Package name: debian-astro Version : 0.1 Upstream Author : Debian Astronomy Maintainers * URL : http://wiki.debian.org/DebianAstro Description : Debian Astronomy Pure Blend Metapackages This metapackage will install packages for tasks of the Debian Astronomy Pure Blend. The initial content come from debian-science/astronomy and debian-science/astronomy-dev, which will be restructured to get smaller tasks. The package will stored in a git repository at https://anonscm.debian.org/cgit/debian-astro/packages/debian-astro.git and the discussion is on the Debian Astronomy mailing list https://lists.debian.org/debian-astro/ Best regards Ole
Bug#799144: ITP: ansible-lint -- Best practices checker for Ansible
Package: wnpp Severity: wishlist Owner: Sascha Girrulat * Package name: ansible-lint Version : 2.0.3 Upstream Author : Will Thames * URL : https://github.com/willthames/ansible-lint * License : MIT Programming Lang: Python Description : Best practices checker for Ansible Ansible-lint checks ansible playbooks for practices and behaviour that could potentially be improved.
Re: is the whole unstable still broken by gcc-5?
On 13/09/15 10:34, Samuel Thibault wrote: > Svante Signell, le Sun 13 Sep 2015 11:33:31 +0200, a écrit : >>> That's what Sid/Unstable is used for. You'll have to live with that :) >>> This transition was IMHO a monster compared to the usual transitions >>> and it might happen again. Se at the end we probably should discuss, >>> what to improve next time. >> >> What about transition to glibc-2.21? > > glibc has been systematically using compat symbols since a looong time > (the libc5 -> libc6 transition). The problem with the g++-5 transition is not libstdc++ itself - libstdc++ has various tricks to be compatible with both ABIs. The unusual problems with the g++-5 transition are: * merely recompiling some other library with the new compiler, without making any source changes in that library, changes its ABI; * it isn't immediately obvious whether a library is using the old or new ABI; * it isn't immediately obvious whether the new ABI even makes any difference for a particular library; * the packages whose ABI does change include apt and schroot, which are key development tools; * hundreds of packages' ABIs changed; * the new compiler makes some things FTBFS; * and the transition is entangled with moving to a new version of Boost which also makes some things FTBFS. Ordinary library transitions are easy by comparison. S
Bug#799159: ITP: puppet-module-puppetlabs-dhcp -- Install and manage a DHCP server
Package: wnpp Severity: wishlist Owner: Michael Weiser * Package name: puppet-module-puppetlabs-dhcp Version : 0.4.0 Upstream Author : Puppet Labs * URL : https://forge.puppetlabs.com/puppetlabs/dhcp * License : Apache-2 Programming Lang: Puppet Description : Install and manage a DHCP server Installs and manages a DHCP server. It has the following features: Multiple subnet support, host reservations, secure dynamic DNS updates when combined with Bind, can create a dummy (ignored) subnet so that the server can be used only as a helper-address target. Configuring a DHCP server is a necessary step in setting up network installation servers which is quite a common task in large environments. I intend to package and maintain this module inside the puppet packaging team on alioth.
Bug#799160: ITP: puppet-module-puppetlabs-tftp -- Install and manage a TFTP service and configuration
Package: wnpp Severity: wishlist Owner: Michael Weiser * Package name: puppet-module-puppetlabs-tftp Version : 0.2.3 Upstream Author : Puppet Labs * URL : https://forge.puppetlabs.com/puppetlabs/tftp * License : Apache-2 Programming Lang: Puppet Description : Install and manage a TFTP service and configuration Install tftp-hpa package and configuration files. This module will install TFTP as a xinetd service by default. It can be overridden to run as a standalone daemon by setting the inetd parameter to false. Configuring a TFTP server is a necessary step in setting up network installation servers which is quite a common task in large environments. I intend to package and maintain this module inside the puppet packaging team on alioth.
Bug#799169: ITP: golint -- Linter for Go source code
Package: wnpp Severity: wishlist Owner: "Martín Ferrari" * Package name: golint Version : 0.0+git20150623.7b7f436 Upstream Author : The Go Authors * URL : https://github.com/golang/lint * License : BSD-3-Clause Programming Lang: Go Description : Linter for Go source code Golint differs from gofmt. Gofmt reformats Go source code, whereas golint prints out style mistakes. Golint differs from govet. Govet is concerned with correctness, whereas golint is concerned with coding style. Golint is in use at Google, and it seeks to match the accepted style of the open source Go project.
suggestion to add package vlan to default instalation DVD
Hello, it is possible to add package "vlan" to the DVD instalation images? It is tiny package (36kB) and in some special environment (without Internet with DVD in vmware environmen) i have to download and install it manually. Ps. I did not find better mailing list for this purpose, so I am trying this... Regards, Josef Mašek
Re: suggestion to add package vlan to default instalation DVD
Josef Masek wrote: > it is possible to add package "vlan" to the DVD instalation images? > It is tiny package (36kB) and in some special environment (without > Internet with DVD in vmware environmen) i have to download and install > it manually. Why? The vlan package is not needed since at least Wheezy to configure VLANs on devices since the program "ip" can do everything the same or even better. Also ifupdown was changed to be able to configure VLANs using "ip" directly without the need for the "vconfig" from the vlan package. Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: suggestion to add package vlan to default instalation DVD
On Wed, Sep 16, 2015 at 3:10 PM, Sven Hartge wrote: > Josef Masek wrote: > >> it is possible to add package "vlan" to the DVD instalation images? >> It is tiny package (36kB) and in some special environment (without >> Internet with DVD in vmware environmen) i have to download and install >> it manually. > > Why? The vlan package is not needed since at least Wheezy to configure > VLANs on devices since the program "ip" can do everything the same or > even better. > > Also ifupdown was changed to be able to configure VLANs using "ip" > directly without the need for the "vconfig" from the vlan package. Pretty sure he meant VLC there. -Pascal -- Homepage (http://organact.mine.nu) Debian GNU/Linux (http://www.debian.org) COMunité/LACIME: École de technologie supérieure (http://www.comunite.ca) ISIP Laboratory: McGill (http://www.isip.ece.mcgill.ca)
how PTS tracks new upstream versions using debian/watch ?
Hello, i wonder all of this, and i tried to reply to myself. Please correct me if wrong. Is uscan run outside debian/ directory ? i suppose yes Inside debian/ directory, without upstream source ? no if optional command is not run, yes if it is Inside debian/ directory, with upstream source ? no, that would be crazy Is the optional command in debian/watch line run by the PTS tracker ? no, too dangerous security-wise, but i had to ask Jérémy.
Re: suggestion to add package vlan to default instalation DVD
On Wed, 2015-09-16 at 15:26 -0400, Pascal Giard wrote: > On Wed, Sep 16, 2015 at 3:10 PM, Sven Hartge wrote: > > Josef Masek wrote: > > > >> it is possible to add package "vlan" to the DVD instalation images? > >> It is tiny package (36kB) and in some special environment (without > >> Internet with DVD in vmware environmen) i have to download and install > >> it manually. > > > > Why? The vlan package is not needed since at least Wheezy to configure > > VLANs on devices since the program "ip" can do everything the same or > > even better. > > > > Also ifupdown was changed to be able to configure VLANs using "ip" > > directly without the need for the "vconfig" from the vlan package. > > Pretty sure he meant VLC there. Well, "vlan" in Jessie is 36KB, whereas "vlc" is nearer 1.5MB. So I'd assume he meant the former, really. Regards, Adam
Re: suggestion to add package vlan to default instalation DVD
Pascal Giard wrote: > On Wed, Sep 16, 2015 at 3:10 PM, Sven Hartge wrote: >> Josef Masek wrote: >>> it is possible to add package "vlan" to the DVD instalation images? >>> It is tiny package (36kB) and in some special environment (without >>> Internet with DVD in vmware environmen) i have to download and >>> install it manually. >> >> Why? The vlan package is not needed since at least Wheezy to >> configure VLANs on devices since the program "ip" can do everything >> the same or even better. >> >> Also ifupdown was changed to be able to configure VLANs using "ip" >> directly without the need for the "vconfig" from the vlan package. > Pretty sure he meant VLC there. I don't think so, since vlc is nowhere near 36KB in size (it is 1.5MB) while the package vlan is exactly that: Package: vlan Version: 1.9-3.2 Filename: pool/main/v/vlan/vlan_1.9-3.2_amd64.deb Size: 36542 Grüße, Sven. -- Sigmentation fault. Core dumped.
Re: suggestion to add package vlan to default instalation DVD
> it is possible to add package "vlan" to the DVD instalation images? > It is tiny package (36kB) and in some special environment (without > Internet with DVD in vmware environmen) i have to download and install > it manually. Hi Josef. In case you really need it, you can build you own live & install image with the wonderful live-build. You even don't need to that yourself since the debian-live team is providing an web auto-builder : http://cgi.build.live-systems.org/cgi-bin/live-build . Just fill a few fields and hop ! The live build system is sending you an email with what you requested. Isn't life beautiful ? Cheers, Olivier
Bug#799222: ITP: hitch -- scalable TLS proxy
Package: wnpp Severity: wishlist Owner: Stig Sandbeck Mathisen * Package name: hitch Version : 1.0.0~beta5 Upstream Author : Varnish Software AB (and others) * URL : https://hitch-tls.org/ * License : BSD Programming Lang: C Description : scalable TLS proxy hitch is a network proxy that terminates TLS/SSL connections and forwards the unencrypted traffic to some backend. It's designed to handle 10s of thousands of connections efficiently on multicore machines. . Features * TLS1.0, TLS1.1 and TLS1.2 support * SNI, with and without wildcard certificates. * Support for HAproxy's PROXY protocol. hitch is a fork of stud (https://github.com/bumptech/stud) which has not been packaged in Debian. hitch is used at my workplace for TLS termination of online newspapers, using Varnish as a backend. Hitch will be maintained in the collab-maint group, or in the pkg-varnish group. Extra hands for maintenance would be welcome.
